Bug 1384652

Summary:	OSP Director interface not working after reboot
Product:	Red Hat Quickstart Cloud Installer	Reporter:	Tasos Papaioannou <tpapaioa>
Component:	Installation - RHELOSP	Assignee:	Jason Montleon <jmontleo>
Status:	CLOSED ERRATA	QA Contact:	Tasos Papaioannou <tpapaioa>
Severity:	medium	Docs Contact:	Dan Macpherson <dmacpher>
Priority:	unspecified
Version:	1.1	CC:	bthurber, qci-bugzillas
Target Milestone:	---	Keywords:	Triaged
Target Release:	1.1
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-28 01:40:06 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:

Description Tasos Papaioannou 2016-10-13 18:54:56 UTC

Description of problem:

Networking-related OpenStack services fail to start when a successfully installed undercloud director gets rebooted.


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

QCIOOO-10.0-RHEL-7-20160930.n.1

How reproducible:

100%

Steps to Reproduce:
1.) Install QCIOOO.
2.) Reboot server.
3.) See that br-ctlplane interface has no IP address, and journalctl shows that neutron-server.service failed to start:

Oct 13 11:52:41 undercloud.example.com mistral-server[1233]: 2016-10-13 11:52:41.216 1233 ERROR oslo.messaging._drivers.impl_rabbit [-] [2e95328a-d0e9-49b2-b77c-35f8a2263498] AMQP server on 192.168.101.1:5672 is unreachable: timed out. Trying again in 22 seconds. Client port: None
Oct 13 11:52:41 undercloud.example.com systemd[1]: neutron-server.service start operation timed out. Terminating.
Oct 13 11:52:41 undercloud.example.com systemd[1]: Failed to start OpenStack Neutron Server.
Oct 13 11:52:41 undercloud.example.com systemd[1]: Unit neutron-server.service entered failed state.
Oct 13 11:52:41 undercloud.example.com systemd[1]: neutron-server.service failed.



Actual results:

Reboot of OOO server fails to restart OpenStack services.

Expected results:

Reboot of OOO server successfully restarts OpenStack services.

Additional info:

Comment 2 John Matthews 2016-10-17 19:19:37 UTC

Plan is to wait for us to update for OSP 10, that isn't ready yet

Comment 3 Jason Montleon 2016-12-01 19:34:09 UTC

We needed a newer version of openvswitch.

What I think was going on is:
Older versions created ovs bridges in an up state
ifup script gets run as a noop when the network service starts because the interface is already up
bad things ensue

Newer versions no longer create the bridge in an up state so when the network service starts it gets configured properly.

Comment 4 Tasos Papaioannou 2016-12-15 15:47:46 UTC

Verified on QCIOOO-10.0-RHEL-7-20161130.t.1.

Comment 7 errata-xmlrpc 2017-02-28 01:40:06 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://access.redhat.com/errata/RHEA-2017:0335