On Saturday, February 11, 2023 22:00 CET, "Sebastian Reitenbach" <sebas...@l00-bugdead-prods.de> wrote:
> On Saturday, February 11, 2023 21:55 CET, "Sebastian Reitenbach" > <sebas...@l00-bugdead-prods.de> wrote: > > > On Saturday, February 11, 2023 11:35 CET, Giovanni Bechis > > <giova...@paclan.it> wrote: > > > > > On Sat, Feb 11, 2023 at 11:03:57AM +0100, Giovanni Bechis wrote: > > > > On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach wrote: > > > > > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > > > > > <giova...@openbsd.org> wrote: > > > > > > > > > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > > > > > Hi, > > > > > > > > > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a > > > > > > > Puppet master on OpenBSD was gone. > > > > > > > These two new packages replace the old PuppetDB 5, with PuppetDB > > > > > > > 7 and introduces the new Puppetserver. > > > > > > > > > > > > > > Similarly to systuls/ruby-puppet, they go into branches based on > > > > > > > the major version, to have future room for Puppet 8. > > > > > > > Their paths where software gets installed is aligned to Puppet, > > > > > > > under /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > > > > > > > > > > > Puppetserver usually comes bundled with a Ruby interpreter and > > > > > > > Puppet agent. That doesn't work out > > > > > > > on OpenBSD. Therefore some bootstrapping has to be done manually > > > > > > > that is OpenBSD specific, and noted > > > > > > > in the Puppetserver pkg/README. > > > > > > > > > > > > > > A couple of tweaks I had to do to my hiera files, as well as to > > > > > > > some of the modules, mostly updating > > > > > > > them. Overall, the changes weren't that big. As everyone might > > > > > > > have different (custom) modules or > > > > > > > hiera plugins in use, ymmv. Therefore I can't really provide a > > > > > > > step by step upgrade path. Install on a test > > > > > > > environment before attempting to upgrade/replace your former > > > > > > > Puppet 5 Master. > > > > > > > That said, Puppet 7 works for me standalone with puppet apply ... > > > > > > > but also against this Puppetserver with PuppetDB backend, > > > > > > > autosigning setup... > > > > > > > > > > > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > > > > > > > > > > > cheers, > > > > > > > Sebastian > > > > > > > > > > > > > > > > thanks for testing. > > > > > > Few issues: > > > > > > - puppetdb is missing pkg/README file in the tarball > > > > > This is missing on purpose, forgot to remove that, as I did > > > > > last-minute clean-ups before sending out the tarball. > > > > > Puppetdb is quite standard, so the upstream doc should more or less > > > > > just work. Also the old puppetdb 5 README > > > > > contained quite some outdated/misleading info > > > > > If there turns to be out some OpenBSD specific issues, I'm happy to > > > > > re-add. > > > > > > > > > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver > > > > > > directory > > > > > oops > > > > > > > > > > > - puppetserver doesn't start on my server log file attached, it > > > > > > seems there is a dependency missing (no such file to load...). > > > > > puppetserver is quite non-standard, compared to puppetdb, just to > > > > > make sure, did you do the initial bootstrap as described in the > > > > > README? > > > > > > > > > actually I did not bootstrapped it. > > > > After bootstrap it fails with a slightly different error (no such file > > > > to load -- facter). > > > > > > > this diff fixes the issue. > > > > I don't think puppetserver picks up facter from "outside" > > > > but it seems I forgot to add facter as a gem to install in the README: > > > > # puppetserver gem install --no-document puppet hiera-eyaml \ > > hiera-file ipaddress msgpack facter > > > > This is not in the packages I just sent, but have it updated in my mystuff/ > > or wait, it actually should have pulled pulled facter in via the bootstrap > step. > > Do you can check > sudo puppetserver gem list > Facter should actually be there? forgot that facter is BAD, due to the extra copy step, until the OpenBSD patch is merged upstream and released. So yes, for the time being, the facter version installed via puppetserver gem install and in the system should be the same version. maybe commenting and bugging on the PR might help: https://github.com/puppetlabs/facter/pull/2531 Therefore, as it seems to work for you, OK for the ruby-facter update. Sebastian > > Sebastian > > > > > Sebastian > > > > > Thanks > > > Giovanni > > > > > > Index: Makefile > > > =================================================================== > > > RCS file: /cvs/ports/sysutils/ruby-facter/Makefile,v > > > retrieving revision 1.92 > > > diff -u -p -r1.92 Makefile > > > --- Makefile 22 Jan 2023 19:21:56 -0000 1.92 > > > +++ Makefile 11 Feb 2023 10:34:05 -0000 > > > @@ -1,7 +1,6 @@ > > > COMMENT = Puppet module management > > > > > > -DISTNAME = facter-4.2.14 > > > -REVISION = 0 > > > +DISTNAME = facter-4.3.0 > > > CATEGORIES = sysutils > > > HOMEPAGE = https://github.com/puppetlabs/facter > > > MAINTAINER = Sebastian Reitenbach <sebas...@openbsd.org> > > > Index: distinfo > > > =================================================================== > > > RCS file: /cvs/ports/sysutils/ruby-facter/distinfo,v > > > retrieving revision 1.30 > > > diff -u -p -r1.30 distinfo > > > --- distinfo 22 Jan 2023 15:42:43 -0000 1.30 > > > +++ distinfo 11 Feb 2023 10:34:05 -0000 > > > @@ -1,2 +1,2 @@ > > > -SHA256 (facter-4.2.14.gem) = nee+3CaHwnSVo0YRrzc0CB6VkXYVYPQNr7s17Zvefbs= > > > -SIZE (facter-4.2.14.gem) = 159232 > > > +SHA256 (facter-4.3.0.gem) = 0kWX0P3GqSGcsW9X9xUSzZchlhF3XiSGi9MJdbBsrSw= > > > +SIZE (facter-4.3.0.gem) = 159232 > > >
