rocky deploy fail waiting for compute service

Bug #1852893 reported by Adam Ratcliff
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

Description:
Deploying Rocky on baremetal (with ceph) fails on Step 4 with Http 503 waiting for nova-compute-service.

Steps to reproduce:
Something like this happened about twice in 20 deployments. See the config files in the links which includes the command line and the sosreport. See links for config, sosreport from node which failed and openstack overcloud failures.
This deployment has network isolation run from cli, on a few nodes of baremetal with 3 controllers and 1 ceph.

Expected result:
I expect the deployment to complete successfully but instead get a failure which is hard to imagine how to debug on the logs.

Actual result:
Deployment failed

Environment:
Rocky, network isolation, 3 controllers 2 compute 1 ceph.

Config etc. to be attached.

Revision history for this message
Adam Ratcliff (adamjr) wrote :

I have a feeling the response to this is incorrect but not sure if the request is correct:
[heat-admin@overcloud-novacompute-0 ~]$ $(echo "curl -g -i -X GET http://172.26.32.122:8774/v2.1/os-services?binary=nova-compute -H \"Accept: application/json\" -H \"User-Agent: python-novaclient\" -H \"X-Auth-Token: {SHA1}6c5724867c555d36c30d340c87070bae0e5a5907\" -H \"X-OpenStack-Nova-API-Version: 2.11\"")
HTTP/1.1 401 Unauthorized
Date: Sun, 17 Nov 2019 10:46:40 GMT
Server: Apache
x-openstack-request-id: req-7c6f6a8e-cdc7-440a-b4be-af9c186971b3
x-compute-request-id: req-7c6f6a8e-cdc7-440a-b4be-af9c186971b3
WWW-Authenticate: Keystone uri="http://172.26.32.122:5000"
Content-Length: 114
Content-Type: application/json

{"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}curl: (6) Could not resolve host: application; Unknown error
curl: (6) Could not resolve host: python-novaclient"; Unknown error
curl: (6) Could not resolve host: {SHA1}6c5724867c555d36c30d340c87070bae0e5a5907"; Unknown error
curl: (6) Could not resolve host: 2.11"; Unknown error

Revision history for this message
Adam Ratcliff (adamjr) wrote :

Attachments as promised

Revision history for this message
Adam Ratcliff (adamjr) wrote :
Revision history for this message
Adam Ratcliff (adamjr) wrote :
Revision history for this message
Adam Ratcliff (adamjr) wrote :

The Sosreport is big, 11MB tar.xz. Let me know if you want it attached.

wes hayutin (weshayutin)
Changed in tripleo:
status: New → Triaged
milestone: none → ussuri-3
Revision history for this message
John Fulton (jfulton-org) wrote :

During step2 of the deployment ceph is configured. If there was a ceph issue, then it would have happened during step2. Since you got to step4 I think it's something else.

Adam, is this still happening? I see it's from Nov 2019 (sorry for the late response).

wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-3 → ussuri-rc3
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-rc3 → victoria-1
Changed in tripleo:
milestone: victoria-1 → victoria-3
Changed in tripleo:
milestone: victoria-3 → wallaby-1
Changed in tripleo:
milestone: wallaby-1 → wallaby-2
Changed in tripleo:
milestone: wallaby-2 → wallaby-3
Revision history for this message
Marios Andreou (marios-b) wrote :

This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo

Changed in tripleo:
milestone: wallaby-3 → none
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for tripleo because there has been no activity for 60 days.]

Changed in tripleo:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.