Manage Puppet containers fails with Can't run container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Unassigned |
Bug Description
TASK | Manage Puppet containers (generate config) for step 1 fails with Can't run container (container-
Logs:
Error: Evaluation Error: Error while evaluating a Resource Statement, Apache:
https:/
https:/
Affected jobs:
- periodic-
- periodic-
- periodic-
- periodic-
- periodic-
- periodic-
- periodic-
We see this error from at least 2022-07-29 19:35:07
Changed in tripleo: | |
importance: | Undecided → Critical |
status: | New → Triaged |
milestone: | none → zed-1 |
tags: | added: ci promotion-blocker |
This is the known issue caused by recent change in puppetlabs-apache. /bugs.launchpad .net/puppet- aodh/+bug/ 1983300
https:/
In Puppet CI, especially in unit tests, we pin dependent modules to specific versions and we are not testing the unreleased versions. /github. com/openstack/ puppet- openstack- integration/ blob/master/ Puppetfile# L157-L159
https:/
While we are currently working on adapting that change, IMO we should consider using the latest released version instead of the latest master, to use the consistent version tested in Puppet CI.