[InstanceHA] Error:Unable to read /etc/corosync/corosync.conf: Is a directory

Bug #1905033 reported by Jose Luis Franco
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Undecided
Jose Luis Franco

Bug Description

Bug based on https://bugzilla.redhat.com/show_bug.cgi?id=1899935

When upgrading from queens to train an InstanceHA compute node, any pcs command executed on the already upgraded environment fails with:

Error:Unable to read /etc/corosync/corosync.conf: Is a directory

When the /etc/corosync directory was checked we could see that /etc/corosync/corosync.conf was really a directory.

This directory was present also on all the other computes which were not upgraded yet, however in queens it seems this wasn't a problem for pacemaker.

Therefore, we need to add an upgrade task that checks if the directory exists and remove it if it's empty or back it up if it isn't.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (stable/train)

Fix proposed to branch: stable/train
Review: https://review.opendev.org/763556

Changed in tripleo:
milestone: wallaby-1 → wallaby-2
Changed in tripleo:
milestone: wallaby-2 → wallaby-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 11.4.0

This issue was fixed in the openstack/tripleo-heat-templates 11.4.0 release.

Revision history for this message
Marios Andreou (marios-b) wrote :

Bug status has been set to 'Fix-Released' based on the discussion and/or patches above. If you disagree please re-set 'Triaged' and reach out to us on freenode #tripleo thank you!

Changed in tripleo:
status: Triaged → Fix Released
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.