-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(MODULES-10873) Add support for puppet7 collection #524
Conversation
puppet_agent::install::solaris is a classthat may have no external impact to Forge modules. puppet_agent::service is a classthat may have no external impact to Forge modules. This module is declared in 3 of 575 indexed public
|
puppet_agent::install::solaris is a classthat may have no external impact to Forge modules. puppet_agent::service is a classthat may have no external impact to Forge modules. This module is declared in 3 of 575 indexed public
|
Seems like the task does not want to upgrade ubuntu 18.04 nodes:
|
I think i figured it out what is happening:
|
I verified I could upgrade from 6.19.1 to 7.0.0 on centos and ubuntu:
The upgrade from 5.5.21 completes but fails to save the report due code mismatch. Filed as https://tickets.puppetlabs.com/browse/MODULES-10875 |
Thanks @gimmyxd that makes sense. If I change the line to
That said I'm thinking either the module should check if the package is actually installed prior to purging it, or somehow capture the fact that
Is there a flag we can pass to Also note this PR should pass once we resolve the release packages for bionic (and buster and el8). |
Ah, it looks like the code assumes if |
bionic packages were updated, should be good to go now |
This makes it possible to install puppet-agent from the puppet7 collection, while keeping the current behavior of defaulting to puppet6. Bump the github action to ruby 2.5 as puppet7 doesn't support earlier versions. Add `--trace` argument to puppet apply run that performs the upgrade.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested with PE on debian and centos agents, and works as expected
This makes it possible to install puppet-agent from the puppet7 collection,
while keeping the current behavior of defaulting to puppet6.
Bump the github action to ruby 2.5 as puppet7 doesn't support earlier versions.
Add
--trace
argument to puppet apply run that performs the upgrade.