Provision is failed with the Import Error while installing openstack
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R5.0 |
Fix Released
|
Critical
|
Bharath Kumar | |||
Trunk |
Fix Released
|
Critical
|
Bharath Kumar |
Bug Description
While installing openstack getting the below Import Error. Seen this issue in working builds in both master and 5.0 branch
master build - 395
5.0 build - 364
TASK [nova : Waiting for nova-compute service up] *******
FAILED - RETRYING: Waiting for nova-compute service up (20 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (19 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (18 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (17 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (16 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (15 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (14 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (13 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (12 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (11 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (10 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (9 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (8 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (7 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (6 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (5 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (4 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (3 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (2 retries left).
FAILED - RETRYING: Waiting for nova-compute service up (1 retries left).
fatal: [10.204.216.103 -> 10.204.216.103]: FAILED! => {
"attempts": 20,
"changed": false,
"cmd": [
"docker",
"exec",
"internal",
"http://
"3",
"default",
"admin",
"admin",
"default",
"compute",
"service",
"list",
"-f",
"json",
],
"delta": "0:00:00.790513",
"end": "2018-11-27 17:20:45.028358",
"rc": 1,
"start": "2018-11-27 17:20:44.237845"
}
STDERR:
Traceback (most recent call last):
File "/opt/ansible/
from openstackclient
File "/opt/ansible/
from openstackclient
File "/opt/ansible/
'openstack.
File "/opt/ansible/
__import_
File "/opt/ansible/
from openstack import profile
ImportError: cannot import name profile
MSG:
non-zero return code
NO MORE HOSTS LEFT *******
to retry, use: --limit @/tmp/ansible.
Changed in juniperopenstack: | |
importance: | Undecided → Critical |
milestone: | none → r5.1.0 |
Which OpenStack SKU are you using (Ocata or Queens) ?
The issue is because of upstream changes. The upstream fix is available in Queens but not yet in Ocata.