Bug 1850991

Summary: upgrade fails when checking for haproxy backends status
Product: Red Hat OpenStack Reporter: Giulio Fidente <gfidente>
Component: puppet-tripleoAssignee: Francesco Pantano <fpantano>
Status: CLOSED ERRATA QA Contact: Alfredo <alfrgarc>
Severity: high Docs Contact:
Priority: high    
Version: 16.1 (Train)CC: amcleod, astillma, bperkins, jjoyce, johfulto, jpretori, jschluet, mrunge, ndeevy, slinaber, spower, tvignaud, yrabl
Target Milestone: z1Keywords: Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-tripleo-11.5.0-0.20200616033428.8ff1c6a.el8ost Doc Type: Bug Fix
Doc Text:
Before this update, the Red Hat Ceph Storage dashboard listener was created in the HA Proxy configuration, even if the dashboard is disabled. As a result, upgrades of Red Hat OpenStack Platform with Ceph Storage could fail. + With this update, the service definition has been updated to distinguish the Ceph MGR service from the Dashboard service so that the Dashboard service is not configured if it is not enabled and upgrades are successful.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-27 15:19:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Giulio Fidente 2020-06-25 11:29:22 UTC
Description of problem:
ceph_dashboard listener is created in haproxy.cfg when dashboard is disabled; causing upgrade to stop and fail when checking for haproxy backends status (dashboard never comes back UP)

Probably due to condition in [1] which is mistakenly assuming dashboard in haproxy to be provisioned when mgr is enabled

1. https://github.com/openstack/puppet-tripleo/blob/stable/train/manifests/haproxy.pp#L667

Version-Release number of selected component (if applicable):
puppet-tripleo-11.5.0-0.20200611115535.e86dd81.el8ost.noarch

Comment 13 errata-xmlrpc 2020-08-27 15:19:10 UTC
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 (Red Hat OpenStack Platform 16.1 director bug fix 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/RHBA-2020:3542