Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
(PE-18516,PE-18170) Temporarily set pe.conf when upgrading to Flanders
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.
- Loading branch information