Manage Puppet containers fails with Can't run container

Bug #1983281 reported by Ananya Banerjee
6
This bug affects 1 person
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-puppet-horizon, cinder, keystone, nova etc) in standalone deploy.

Logs:

Error: Evaluation Error: Error while evaluating a Resource Statement, Apache::Vhost[horizon_ssl_vhost]: parameter 'priority' expects a value of type Undef, Integer, or Boolean, got String (file: /etc/puppet/modules/horizon/manifests/wsgi/apache.pp, line: 309) on node standalone.localdomain

https://logserver.rdoproject.org/openstack-component-tripleo/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-9-standalone-tripleo-master/dbeae09/logs/undercloud/home/zuul/standalone_deploy.log.txt.gz
https://logserver.rdoproject.org/openstack-component-tripleo/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-9-containers-multinode-tripleo-master/dcf694a/logs/undercloud/var/log/containers/stdouts/container-puppet-neutron.log.txt.gz

Affected jobs:
- periodic-tripleo-ci-centos-9-standalone-tripleo-master
- periodic-tripleo-ci-centos-9-containers-multinode-tripleo-master
- periodic-tripleo-ci-centos-9-ovb-3ctlr_1comp-featureset001-tripleo-master
- periodic-tripleo-ci-centos-9-standalone-on-multinode-ipa-tripleo-master
- periodic-tripleo-ci-centos-9-scenario000-multinode-oooq-container-updates-tripleo-master
- periodic-tripleo-ci-centos-9-scenario004-standalone-tripleo-master
- periodic-tripleo-ci-centos-9-containers-multinode-tripleo-master-validation

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
Revision history for this message
Takashi Kajinami (kajinamit) wrote :

This is the known issue caused by recent change in puppetlabs-apache.
 https://bugs.launchpad.net/puppet-aodh/+bug/1983300

In Puppet CI, especially in unit tests, we pin dependent modules to specific versions and we are not testing the unreleased versions.
 https://github.com/openstack/puppet-openstack-integration/blob/master/Puppetfile#L157-L159

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.

Revision history for this message
Ananya Banerjee (frenzyfriday) wrote :

Thanks Takashi. Could you please point me to where I should make the change to pin the released version? Is it here https://github.com/openstack/puppet-openstack-integration/blob/master/Puppetfile#L6 ?

Revision history for this message
Ananya Banerjee (frenzyfriday) wrote :
Revision history for this message
Takashi Kajinami (kajinamit) wrote :

The change should be made in RDO side as RDO is packaging the master code instead of the latest release.

Revision history for this message
Ananya Banerjee (frenzyfriday) wrote :
Revision history for this message
Ananya Banerjee (frenzyfriday) wrote :
Changed in tripleo:
status: Triaged → Fix Released
Revision history for this message
Marios Andreou (marios-b) wrote :

@Takashi do we need to continue tracking this to unpin puppet-apache?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.