deployment fails with "Pcmk_bundle[haproxy-bundle]: Munging failed for value \"\" in class promoted_max: promoted_max must be an integer"

Bug #1995565 reported by Luca Miccini
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Takashi Kajinami

Bug Description

Seems like this popped up after https://review.opendev.org/c/openstack/puppet-pacemaker/+/840966 was merged.

There seem to be a few issues here:

1. haproxy-bundle uses replicas instead of promoted_max or masters (not really an issue per se):

https://github.com/openstack/puppet-tripleo/blob/master/manifests/profile/pacemaker/haproxy_bundle.pp#L286

and so both promoted_max and masters are undef.

2. pick_default coerces undef into an empty string (https://tickets.puppetlabs.com/browse/MODULES-11018)

3. https://github.com/openstack/puppet-pacemaker/blob/master/manifests/resource/bundle.pp#L159-L173 assumes either promoted_max or masters (or both) are defined but doesn't account the case where both are undef, like for haproxy-bundle.

Rabi Mishra (rabi)
Changed in tripleo:
importance: Undecided → High
assignee: nobody → Takashi Kajinami (kajinamit)
milestone: none → antelope-1
Revision history for this message
Marios Andreou (marios-b) wrote (last edit ):

I filed a bug @ https://bugs.launchpad.net/tripleo/+bug/1995719 and it was marked duplicate for this one

fix is there https://review.opendev.org/c/openstack/puppet-pacemaker/+/863480 "Avoid pick_default to detect promoted_max"

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

This was fixed by https://review.opendev.org/c/openstack/puppet-pacemaker/+/863480 . Moving this to fix released.

Changed in tripleo:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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