puppet package versions break ocata deployments and upgrades to pike
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Local testing with tripleo.sh --repo-setup shows we have issues with a number of puppet modules where packages installed aren't the latest so deployment/upgrade fails, here's an example:
[root@overcloud
puppet-
[root@overcloud
puppet-
[root@overcloud
puppet-
Here we can see we've installed the version from delorean-deps, instead of the correct delorean-current version, which breaks upgrade like this:
deploy_stderr: |
exception: connect failed
Error: Evaluation Error: Error while evaluating a Function Call, os_transport_url(): port should be a String at /etc/puppet/
because we don't have https:/
We can see this set priorities but the newer release is installed anyway:
[root@overcloud
yum-plugin-
[root@overcloud
baseurl=https:/
priority=20
[root@overcloud
baseurl=http://
baseurl=http://
baseurl=http://
tags: | added: alert ci |
tags: | removed: alert |
Changed in tripleo: | |
milestone: | pike-1 → pike-2 |
Changed in tripleo: | |
milestone: | pike-2 → pike-3 |
The same problem exists for deployment as puppet-tripleo is outdated, ref https:/ /review. openstack. org/#/c/ 439759/
Discussion with apevec in #rdo indicates we need to do some rework to the packaging to fix this, and I'm still not clear why we don't see the same issues in CI