Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1175260

Summary: After rebooting the controller and compute VMs they're stuck for a long time on "no route to host"
Product: Red Hat OpenStack Reporter: Udi Kalifon <ukalifon>
Component: openstack-tripleoAssignee: James Slagle <jslagle>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: medium Docs Contact:
Priority: unspecified    
Version: DirectorCC: calfonso, mburns, yeylon
Target Milestone: gaKeywords: TestOnly, Triaged, ZStream
Target Release: Director   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:50:01 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:
Attachments:
Description Flags
Screenshot of the VM console showing the errors none

Description Udi Kalifon 2014-12-17 11:37:18 UTC 
Created attachment 970058 [details]
Screenshot of the VM console showing the errors

Description of problem:
With the instack setup on virtual machines, when you restart the VM it takes it too long to boot, and it logs the same error numerous times: "no route to host". See attached screenshot.


How reproducible:
100%


Steps to Reproduce:
1. Install using instack-virt-setup, instack-install-undercloud and instack-deploy-overcloud
2. Restart the compute and controller VMs (with libvirt, destroy and launch Baremetal_X domains)
3. Open the console to the VMs like in the attached screenshot.


Actual results:
The same error repeats in a loop over and over again. Eventually it stops but I didn't wait to measure exactly how long it takes.


Additional info:
When rebooting the VM, it first gets stuck on PXE boot and you need to send it ctrl+alt+del to start the boot process again. Then you see the above errors... There is also a bug reported on the PXE problem (bug #1174293).
Comment 6 Udi Kalifon 2015-06-29 10:52:59 UTC 
Looks good with puddle 2015-06-26
Comment 8 errata-xmlrpc 2015-08-05 13:50:01 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-2015:1549