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

Bug 1262596

Summary: Ironic-API seems to be unresponsive and cause installation / introspection to fail
Product: Red Hat OpenStack Reporter: Ofer Blaut <oblaut>
Component: openstack-ironicAssignee: Lucas Alvares Gomes <lmartins>
Status: CLOSED DUPLICATE QA Contact: Toure Dunnon <tdunnon>
Severity: urgent Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: calfonso, jslagle, mburns, oblaut, rhel-osp-director-maint, ukalifon, yeylon
Target Milestone: z3Keywords: Triaged, ZStream
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-28 11:49:51 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
API traceback
none
logs none

Description Ofer Blaut 2015-09-13 07:34:34 UTC
Created attachment 1072830 [details]
API traceback

Description of problem:


[root@puma33 stack]# grep -i haproxy /var/log/messages
Sep 13 09:56:40 puma33 haproxy[17181]: Server ironic/192.0.2.1 is DOWN, reason: Layer7 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Sep 13 09:56:40 puma33 haproxy[17181]: proxy ironic has no server available!
Sep 13 09:58:14 puma33 haproxy[17181]: Server ironic/192.0.2.1 is UP, reason: Layer7 check passed, code: 200, info: "OK", check duration: 9105ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.






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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ofer Blaut 2015-09-13 07:37:38 UTC
Created attachment 1072831 [details]
logs

Comment 2 Ofer Blaut 2015-09-13 07:44:08 UTC
(In reply to Ofer Blaut from comment #0)
> Created attachment 1072830 [details]
> API traceback
> 
> Description of problem:

overcloud  deployment  failed because of 0 nodes, while i had 6 discovered by ironic.

Logs are attached 

> 
> 
> [root@puma33 stack]# grep -i haproxy /var/log/messages
> Sep 13 09:56:40 puma33 haproxy[17181]: Server ironic/192.0.2.1 is DOWN,
> reason: Layer7 timeout, check duration: 10001ms. 0 active and 0 backup
> servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
> Sep 13 09:56:40 puma33 haproxy[17181]: proxy ironic has no server available!
> Sep 13 09:58:14 puma33 haproxy[17181]: Server ironic/192.0.2.1 is UP,
> reason: Layer7 check passed, code: 200, info: "OK", check duration: 9105ms.
> 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
> 
> 
> 
> 
> 
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> 
> 
> Steps to Reproduce:
> 1.
> 2.
> 3.
> 
> Actual results:
> 
> 
> Expected results:
> 
> 
> Additional info:

Comment 3 Ofer Blaut 2015-09-13 07:52:39 UTC
(In reply to Ofer Blaut from comment #0)
> Created attachment 1072830 [details]
> API traceback
> 
> Description of problem:

overcloud deployment fails since there are NO nodes found .
Error to the screen tell haproxy has not ironic server found 
> 
> 
> [root@puma33 stack]# grep -i haproxy /var/log/messages
> Sep 13 09:56:40 puma33 haproxy[17181]: Server ironic/192.0.2.1 is DOWN,
> reason: Layer7 timeout, check duration: 10001ms. 0 active and 0 backup
> servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
> Sep 13 09:56:40 puma33 haproxy[17181]: proxy ironic has no server available!
> Sep 13 09:58:14 puma33 haproxy[17181]: Server ironic/192.0.2.1 is UP,
> reason: Layer7 check passed, code: 200, info: "OK", check duration: 9105ms.
> 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
> 
> 
> 
> 
> 
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> 
> 
> Steps to Reproduce:
> 1.
> 2.
> 3.
> 
> Actual results:
> 
> 
> Expected results:
> 
> 
> Additional info:

Comment 4 chris alfonso 2015-09-14 16:06:50 UTC
Are there any steps to reproduce this outside of the normal flow of installation?

Comment 6 Ofer Blaut 2015-09-16 11:44:59 UTC
No, Just install and check logs 
It happnes from time to time

Comment 8 Ofer Blaut 2015-09-16 11:58:18 UTC
*** Bug 1263645 has been marked as a duplicate of this bug. ***

Comment 9 James Slagle 2015-09-28 11:49:51 UTC

*** This bug has been marked as a duplicate of bug 1246525 ***