Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1502576 - Upgrade O to P failing due to rabbitmq missconfiguration
Upgrade O to P failing due to rabbitmq missconfiguration
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates (Show other bugs)
12.0 (Pike)
Unspecified Unspecified
urgent Severity urgent
: beta
: 12.0 (Pike)
Assigned To: Emilien Macchi
Marius Cornea
: Triaged, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-10-16 05:26 EDT by Jose Luis Franco
Modified: 2018-02-05 14:15 EST (History)
11 users (show)

See Also:
Fixed In Version: openstack-tripleo-heat-templates-7.0.3-3.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-13 17:15:46 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1723899 None None None 2017-10-16 05:26 EDT
OpenStack gerrit 512278 None None None 2017-10-16 08:40 EDT
Red Hat Product Errata RHEA-2017:3462 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-15 20:43:25 EST

  None (edit)
Description Jose Luis Franco 2017-10-16 05:26:59 EDT
Description of problem:

The following error has been displayed after an unsuccessful upgrade from Ocata to Pike in the centos-7-containers-multinode-upgrades-nv CI job:

"Error: Evaluation Error: Error while evaluating a Resource Statement, Class[Rabbitmq]: parameter 'file_limit' expects a value of type Integer[-1, default] or Enum['infinity', 'unlimited'], got String at /etc/puppet/modules/tripleo/manifests/profile/base/rabbitmq.pp:144:7 on node centos-7-2-node-citycloud-sto2-11384567-964146.localdomain",

http://logs.openstack.org/64/508964/3/check/gate-tripleo-ci-centos-7-containers-multinode-upgrades-nv/dd33a2f/logs/undercloud/home/jenkins/failed_upgrade.log.txt.gz

file_limit field is in fact configured as a string:
http://logs.openstack.org/64/508964/3/check/gate-tripleo-ci-centos-7-containers-multinode-upgrades-nv/dd33a2f/logs/subnode-2/etc/puppet/hieradata/service_configs.json.txt.gz

"rabbitmq::file_limit": "65536"

While the rabbitmq configuration mentions that it should be an integer after the following commit in puppet-rabbitmq module:
https://github.com/voxpupuli/puppet-rabbitmq/commit/faf24bccecfeced313859e933484b9d76bb96484

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Issue found in multinode upgrades job where an upgrade from Ocata to Pike containerized is deployed using the following commnads:
1.1 Deploy: http://logs.openstack.org/64/508964/3/check/gate-tripleo-ci-centos-7-containers-multinode-upgrades-nv/dd33a2f/logs/undercloud/home/jenkins/overcloud-deploy.sh

1.2 Upgrade: http://logs.openstack.org/64/508964/3/check/gate-tripleo-ci-centos-7-containers-multinode-upgrades-nv/dd33a2f/logs/undercloud/home/jenkins/overcloud-upgrade.sh


Actual results:
Upgrade failed due to error: "2017-10-14 21:04:20,925 ERROR: 52064 -- ERROR configuring rabbitmq"
http://logs.openstack.org/64/508964/3/check/gate-tripleo-ci-centos-7-containers-multinode-upgrades-nv/dd33a2f/logs/undercloud/home/jenkins/failed_upgrade.log.txt.gz

Expected results:


Additional info:
Comment 2 mathieu bultel 2017-11-15 10:59:28 EST
openstack-tripleo-heat-templates-7.0.3-3.el7ost
Comment 6 errata-xmlrpc 2017-12-13 17:15:46 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3462

Note You need to log in before you can comment on or make changes to this bug.