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:
Created attachment 1072831 [details] logs
(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:
(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:
Are there any steps to reproduce this outside of the normal flow of installation?
No, Just install and check logs It happnes from time to time
*** Bug 1263645 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 1246525 ***