Bug 1388523

Summary:	Attempting to restart haproxy with external loadbalancer during convergence
Product:	Red Hat OpenStack	Reporter:	Tomas Jamrisko <tjamrisk>
Component:	puppet-tripleo	Assignee:	Michele Baldessari <michele>
Status:	CLOSED ERRATA	QA Contact:	Udi Shkalim <ushkalim>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	unspecified	CC:	bperkins, fdinitto, jjoyce, jschluet, oblaut, slinaber, tvignaud
Target Milestone:	rc	Keywords:	Triaged
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	puppet-tripleo-5.3.0-4.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-14 16:25:13 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 Tomas Jamrisko 2016-10-25 14:47:18 UTC

Description of problem:
There is an attempt to restart haproxy during upgrade with external lb, which fails as the resource is not available on the controllers:

{
  "deploy_stdout": "Matching apachectl 'Server version: Apache/2.4.6 (Red Hat Enterprise Linux)\nServer built:   Aug  3 2016 08:33:27'\n\u001b[mNotice: Scope(Class[Tripleo::Firewall::Post]): At this stage, all network traffic is blocked.\u001b[0m\n\u001b[mNotice: Compiled catalog for controller-0.localdomain in environment production in 3.94 seconds\u001b[0m\n", 
  "deploy_stderr": "exception: connect failed\n\u001b[1;31mError: Could not find dependency Concat[/etc/haproxy/haproxy.cfg] for Tripleo::Pacemaker::Resource_restart_flag[haproxy-clone] at /etc/puppet/modules/tripleo/manifests/profile/pacemaker/haproxy.pp:50\u001b[0m\n", 
  "deploy_status_code": 1

Comment 2 Tomas Jamrisko 2016-11-15 08:36:51 UTC

Convergence with external loadbalancer now passes without issues

Comment 4 errata-xmlrpc 2016-12-14 16:25:13 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, 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://rhn.redhat.com/errata/RHEA-2016-2948.html