Bug 1123783 - Stuypuft stuck on 15% during deployment
Summary: Stuypuft stuck on 15% during deployment
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rubygem-staypuft
Version: Foreman (RHEL 6)
Hardware: x86_64
OS: Linux
urgent
unspecified
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Mike Burns
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-28 09:12 UTC by Tzach Shefi
Modified: 2014-09-08 05:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-28 13:13:06 UTC


Attachments (Terms of Use)
screen shot 1 (42.26 KB, image/png)
2014-07-28 09:13 UTC, Tzach Shefi
no flags Details
Screen shot 2 (25.48 KB, image/png)
2014-07-28 09:13 UTC, Tzach Shefi
no flags Details

Description Tzach Shefi 2014-07-28 09:12:12 UTC
Description of problem: Stuypuft stuck on 15% while running deployemnt, using virt manager looked inside the vm's, setup included nova network 1 controller, plus 2 compute hosts.  

1. Why 4 host vm's (none including foreman vm) were booted im not sure I'd expect to see only three up. 

2. Access to my pysical server running the vm's was down not sure when this happened, service network start fixed this. 

3. Looking into vm's using virt manager from my laptop I noticed two things
One of the hosts can't reach a source see picture 1. 
All the other hosts are stuck on same page see picture 2. 



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

How reproducible:
not sure

Steps to Reproduce:
1. Install on physical server, using guide.
2. Nova network, 1 CC + 2 compute nodes
3.

Actual results:
Deployment stuck at 15%, not error logs no indication or problem, until I checked vms using virt manager.  

Expected results:

Should complete deployment, if fails hangs no timeout is given. 
 

Additional info:

Comment 1 Tzach Shefi 2014-07-28 09:13:06 UTC
Created attachment 921734 [details]
screen shot 1

Comment 2 Tzach Shefi 2014-07-28 09:13:34 UTC
Created attachment 921735 [details]
Screen shot 2

Comment 4 Jason Guiditta 2014-07-28 12:58:45 UTC
This looks to be an error in the discovery phase, an so before ofi puppet is involved, switching components

Comment 5 Mike Burns 2014-07-28 13:13:06 UTC
Closing this as notabug.  This is environmental.

screen shot 2 shows a host that hasn't provisioned yet, but is otherwise fine, just waiting it's turn.

Screen shot 1 shows a host that failed to download from an external site.  This is either a bad url in the installation media location you configured or a bad gateway setup.


Note You need to log in before you can comment on or make changes to this bug.