Repository navigation
Conversation
miharp
force-pushed
the
docs/openvox8-to-9-upgrade
branch
2 times, most recently
from
September 3, 2026 14:07
25bf2e7 to
3934834
Compare
miharp
force-pushed
the
docs/openvox8-to-9-upgrade
branch
7 times, most recently
from
September 10, 2026 12:45
72cf95f to
524eaff
Compare
miharp
marked this pull request as ready for review
September 10, 2026 12:47
miharp
force-pushed
the
docs/openvox8-to-9-upgrade
branch
from
September 10, 2026 13:02
524eaff to
f4821b4
Compare
bastelfreak
reviewed
Sep 10, 2026
bastelfreak
reviewed
Sep 10, 2026
| On EL, the two release packages can be installed side by side and the package manager prefers the 9.x packages; remove `openvox8-release` once the host is upgraded. | ||
|
|
||
| ```bash | ||
| sudo rpm -Uvh https://yum.voxpupuli.org/openvox9-release-el-9.noarch.rpm |
Contributor
There was a problem hiding this comment.
Suggested change
| sudo rpm -Uvh https://yum.voxpupuli.org/openvox9-release-el-9.noarch.rpm | |
| sudo dnf install https://yum.voxpupuli.org/openvox9-release-el-9.noarch.rpm |
let's promote new tools!
miharp
force-pushed
the
docs/openvox8-to-9-upgrade
branch
2 times, most recently
from
September 13, 2026 11:47
cbf8a44 to
e773e6f
Compare
miharp
force-pushed
the
docs/openvox8-to-9-upgrade
branch
from
September 18, 2026 10:57
e773e6f to
d0bdb6b
Compare
miharp
marked this pull request as draft
September 24, 2026 12:32
This was referenced Sep 29, 2026
miharp
force-pushed
the
docs/openvox8-to-9-upgrade
branch
from
October 1, 2026 12:01
c812e13 to
82bd1a2
Compare
miharp
force-pushed
the
docs/openvox8-to-9-upgrade
branch
from
October 3, 2026 13:42
a62e1d3 to
f46a167
Compare
miharp
marked this pull request as ready for review
October 3, 2026 14:15
miharp
force-pushed
the
docs/openvox8-to-9-upgrade
branch
2 times, most recently
from
October 5, 2026 10:02
4d0b4c4 to
61cf262
Compare
9 of 17 tasks
miharp
force-pushed
the
docs/openvox8-to-9-upgrade
branch
2 times, most recently
from
October 8, 2026 15:49
2a0fa0b to
621ab3e
Compare
Add "Upgrading from OpenVox 8 to OpenVox 9", an upgrade-planning page that sits beside the package-mechanics page (upgrade_minor) and covers what to review and change before moving a production deployment. Every claim was checked against the OpenVox 9 sources, the published packages and repository metadata, and where possible a lab run, rather than copied from Puppet Core's guide. The page covers: - The component bump (Ruby 4.0, OpenSSL 3.5, OpenFact 6, JRuby 10.1, Java 21 or 25, resource_api 2.0, curl no longer bundled) and the new major versions of the vendored *_core modules. - Platform coverage at GA and the six-month support window for 8. - Ruby 4.0 review for facts, functions, types, providers, and gems, including Kernel#open pipes, Net::HTTP's dropped default Content-Type, and the libraries no longer shipped (base64, multi_json, cgi, gettext). - Reinstalling gems after the gem directory moves to 4.0.0. - OpenFact 6 changes that affect fact code. - Behavior changes: deferred functions preprocessed by default, reports off by default, no default server (with both error texts), checksum- like file content now literal, the removed settings and other removals, and the systemd provider's invoke-rc.d fallback. - Server and OpenVoxDB: Java packaging and the launcher, filebucket read authorization and the kept auth.conf caveat, Jetty 12 and the bootstrap.cfg pitfall, PostgreSQL versions, package dependencies, and the removed start/stop subcommands. - Windows agents defaulting to UTF-8 and the MSYS2 build. - A test-then-upgrade checklist with the openvox9-release repository switch and the rule that every OpenVox package on a server host upgrades in one transaction. Also add the nav entry, cross-link the page from upgrade_minor, and add the one-transaction caveat to its recommended order. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Michael Harp <mike@mikeharp.com>
miharp
force-pushed
the
docs/openvox8-to-9-upgrade
branch
from
October 12, 2026 12:53
621ab3e to
7e568d0
Compare
jay7x
approved these changes
Oct 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an upgrade-planning page to the 9.x collection, "Upgrading from OpenVox 8 to OpenVox 9", covering what to review before moving a production deployment, alongside the existing package-mechanics page (
upgrade_minor). Modeled on the shape of Puppet Core's 8-to-9 guide, with every claim checked against the OpenVox 9 sources rather than copied. Updated for the 9.0.0 release: the prerelease callout and the rc-specific notes are gone, and the page carries the details from the GA release notes and announcement (support window for OpenVox 8, platform drops, Java packaging and the Java 17 crash symptom, PostgreSQL versions, unvendored gems, theinvoke-rc.dfallback removal, and a section on Windows agents defaulting to UTF-8).Part of #456. The page links to the server 9.x, OpenVoxDB 9.x, and OpenFact 6.x release notes and to the server 9.x
auth.confpage; #457, #458, and #459 have merged, so every link on the page resolves on master.What the page covers
*_coremodules.Kernel#openpipe removal,Net::HTTPno longer sending a defaultContent-Typeheader, and the libraries no longer shipped (base64,multi_json, the fullcgilibrary on the agent;gettexton the server).exec/whichdeprecations,time_limit/limitaliases,ldapnameremoval,/opt/puppetlabs/binsearch path).serversetting fallback (openvox#536). An agent with nothing that names a server fails whether it runs as root or not; the page quotes both messages, since the non-root text differs. As of 9.0.0-rc2 the check is satisfied byserver,server_list, SRV records, or (for their own services)ca_serverandreport_server(openvox#659), so the rc1 workaround of keeping aserverentry next toserver_listis gone from the page.configprint,pluginsync,data_binding_terminus,environment_data_provider) and other removals (checksum-likefilecontentvalues no longer fetched from the filebucket (openvox#170),regsubstencoding argument, the systemd provider'sinvoke-rc.dfallback on Debian (openvox#562),pe_serverversion,zone_core, Java keystores, legacy PAL APIs).ClassNotFoundException: java.util.SequencedCollection), the launcher andJAVA_BINhandling, the filebucket read-authorization change (openvox-server#549) and the caveat that a modifiedauth.confis kept by the package and so keeps its 8.x rules, Jetty 12 with the OpenVoxDBbootstrap.cfgjetty10-servicepitfall for upgrades from 8.14.0 or earlier, PostgreSQL 14 minimum (tested against 15, 16, and 18), and theopenvox-serverandopenvoxdbpackages' dependency on agent 9 (openvoxdb-terminiis unversioned, verified against the published rc1 apt and yum metadata).OpenVoxProject/puppet-runtimeappliesrevert_ruby_utf8_default_encoding.patchon Windows and the Ruby 4.0 build applies no patches, so OpenVox 9 Windows agents get upstream Ruby's UTF-8 default external encoding (the same change Puppet Core 9 documents). Also notes the MSYS2/UCRT build and theopenvox9installer directory.openvox9-releaserepository package (on Debian and Ubuntuopenvox8-releasehas to be removed first, since both ship/etc/apt/preferences.d/openvox-release.pref; on EL they coexist). The 9.xupgrade_minorpage points at that step. The final step upgrades every OpenVox package on a server host in one package manager transaction, because the 8.x server and database packages requireopenvox-agentbelow 9.0.0 while the 9.x packages require 9.0.0 or newer, so a host running both cannot upgrade them one at a time; the server-before-database order applies only across separate hosts.Also adds the nav entry (before "Upgrading OpenVox 9") and cross-links the page from the breaking-changes callout in
upgrade_minor.upgrade_major.mdupgrade_minor.mdopenvox_9x.ymlChecks
jekyll buildclean; the page renders under/openvox/9.x/upgrade_major.htmland the nav andupgrade_minorcallout link to it. Every cross-collection link resolves now that Add OpenVox Server 9.x docs collection as a preview (latest stays on 8.x) #457, Add OpenVoxDB 9.x docs collection as a preview (latest stays on 8.x) #458, and Add OpenFact 6.x docs collection as a preview (latest stays on 5.x) #459 are merged.servermessage, the removedldapnameoption making a fact resolve to nothing rather than raising, a version 3hiera.yamlstill loading with a deprecation warning, and the removed settings being ignored silently where 8 warned. Not testable there and taken from sources only: the dropped Debian 11/12 and Amazon Linux 2 packages, the gem's Ruby floor, module unit tests on Ruby 4, report processors under JRuby 10, and the PAL APIs.servercheck, its root error text, the checksum-likecontentchange, and theNet::HTTPheader change) is taken from the rc4 source and Ruby 4.0's NEWS file and has not been run in the lab._data/supported_platforms.yml, and the puppet-runtime Ruby build configs for the Windows encoding section. Nothing in it has been run in the lab, and the Windows section in particular has not been tried on a Windows node.auth.confbullet:auth.confisconfig(noreplace)in the 9.0.0-rc2 EL10 rpm and is listed inconffilesin the Ubuntu 24.04 deb, and the two rule differences come from a diff of the shipped file between 8.15.2 and 9.0.0-rc2. In an 8.28.1 to 9.0.0-rc2/rc4 lab upgrade (EL10 server, EL9 and Ubuntu 24.04 agents) with the stock file, a filebucket read with an agent certificate returned 403 and the same read with the server's certificate succeeded. The kept-file behavior was observed on that run forpuppet.conf(.rpmnewon EL,.dpkg-diston Ubuntu); an upgrade with a modifiedauth.confitself has not been run.Assisted by Claude.