Reping on this. @packaging ?
Debian/Ubuntu is still held back on Puppet plugin 1.0.0
there were no packaging requests for puppet 1.0.3 for deb/3.0 – @ezr-ondrej?
and I think there also was no request to update discovery to 18.0.0 in deb/3.0 – @lzap?
getting this error when i click on create host after it is discovered. do i have to wait for the 1.0.3 puppet plugin ?
If using Deb based, you’ll need to wait for Discovery18 and Puppet1.0.3, I believe, to be propped
foreman_puppet 1.0.4 has now been published to both rpm/3.0 and deb/3.0
how did u update the foreman_puppet i am not able to
apt-get update && apt-get upgrade -y
that didn’t work?
I usually do a foreman-installer after.
il give that a try again, i didnt run foreman installer.
I have updated my puppet to 1.0.4 still getting the same error when trying to clikc on
“provision” → then Create Host.
Am i missing something still ?
Discovery 18 is still not propped I think.
did you install the 18.0.0 plugin?
no im still on 14 i think
sudo dpkg -i ruby-foreman-discovery_9999-18.0.0-plugins+scratchbuild20210920154157_all.deb
Just depricated bundle code.
what does ‘bundle info foreman_discovery’ show for build info?
(Reading database … 155807 files and directories currently installed.)
Preparing to unpack ruby-foreman-discovery_9999-18.0.0-plugins+scratchbuild20210920154157_all.deb …
Unpacking ruby-foreman-discovery (9999-18.0.0-plugins+scratchbuild20210920154157) over (9999-18.0.0-plugins+scratchbuild20210920154157) …
Setting up ruby-foreman-discovery (9999-18.0.0-plugins+scratchbuild20210920154157) …
Bundler attempted to update foreman_discovery but its version stayed the same
[DEPRECATED] use bundle info foreman_discovery
instead of bundle show foreman_discovery
t@foremanhostvm:~$ bundle info foreman_discovery
Could not locate Gemfile or .bundle/ directory
t@foremanhostvm:~$
Well hot dang. See if discovery works properly now!
Best to get a restart of the Foreman Server and a re-pxe discover of the systems.