-
Notifications
You must be signed in to change notification settings - Fork 57
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
(PE-18516,PE-18170) Temporarily set pe.conf when upgrading to Flanders #40
(PE-18516,PE-18170) Temporarily set pe.conf when upgrading to Flanders #40
Conversation
At the moment, MEEP does not create a 2.0 pe.conf when recovering configuration for an upgrade. This is preventing all upgrade tests from PE >= 2016.2 (when meep was introduced) to PE >= 2017.1 from completing because meep ends up using a 1.0 pe.conf that has no node_roles. Without the node_roles information, the node is not considered infrastructure, and meep's enc returns no classes for it, so nothing happens in the upgrade apply. This is not currently a problem upgrading from < 2016.2 because beaker-pe is providing the beaker-answers pe.conf in those cases. To work around this, I've added a check, just if we are upgrading to a Flanders version, which supplies the beaker-answers generated pe.conf. This patch is just intended to get upgrades from earlier meep versions working in CI. When we get to PE-18170 (also scheduled for Flanders) we'll work on improving recover configuration to generate a 2.0 pe.conf, with the goal being that beaker-answers should not need to provide anything for pe.conf for Flanders upgrades unless some additional parameters were added in the beaker configuration.
Can one of the admins verify this patch? |
./frankenbuilder 2017.1 --install --upgrade --upgrade-from 2016.4.2 --smoke --vmpooler The upgrade from 2016.4.2 now succeeds. The check_package_version test fails, but only because 2016.4.2 has more recent postgresql and license packages (this is a separate issue that I'll open an RE ticket for).
|
./frankenbuilder 2017.1 --install --upgrade --upgrade-from 2016.1.2 --smoke --vmpooler Continues to upgrade properly from pre meep versions...
|
Refer to this link for build results (access rights to CI server needed): |
At the moment, MEEP does not create a 2.0 pe.conf when recovering
configuration for an upgrade. This is preventing all upgrade tests from
PE >= 2016.2 (when meep was introduced) to PE >= 2017.1 from completing
because meep ends up using a 1.0 pe.conf that has no node_roles. Without
the node_roles information, the node is not considered infrastructure,
and meep's enc returns no classes for it, so nothing happens in the
upgrade apply.
This is not currently a problem upgrading from < 2016.2 because
beaker-pe is providing the beaker-answers pe.conf in those cases.
To work around this, I've added a check, just if we are upgrading to a
Flanders version, which supplies the beaker-answers generated pe.conf.
This patch is just intended to get upgrades from earlier meep versions
working in CI. When we get to PE-18170 (also scheduled for Flanders)
we'll work on improving recover configuration to generate a 2.0 pe.conf,
with the goal being that beaker-answers should not need to provide
anything for pe.conf for Flanders upgrades unless some additional
parameters were added in the beaker configuration.