Provision is failed with the Import Error while installing openstack

Bug #1805578 reported by musharani
40
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R5.0
Fix Released
Critical
Leela Bharath Kumar Kassetti
Trunk
Fix Released
Critical
Leela Bharath Kumar Kassetti

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",
        "kolla_toolbox",
        "openstack",
        "--os-interface",
        "internal",
        "--os-auth-url",
        "http://10.204.216.140:35357/v3",
        "--os-identity-api-version",
        "3",
        "--os-project-domain-name",
        "default",
        "--os-tenant-name",
        "admin",
        "--os-username",
        "admin",
        "--os-password",
        "c0ntrail123",
        "--os-user-domain-name",
        "default",
        "compute",
        "service",
        "list",
        "-f",
        "json",
        "--service",
        "nova-compute"
    ],
    "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/bin/openstack", line 7, in <module>
    from openstackclient.shell import main
  File "/opt/ansible/lib/python2.7/site-packages/openstackclient/shell.py", line 29, in <module>
    from openstackclient.common import clientmanager
  File "/opt/ansible/lib/python2.7/site-packages/openstackclient/common/clientmanager.py", line 153, in <module>
    'openstack.cli.base',
  File "/opt/ansible/lib/python2.7/site-packages/openstackclient/common/clientmanager.py", line 124, in get_plugin_modules
    __import__(ep.module_name)
  File "/opt/ansible/lib/python2.7/site-packages/openstackclient/network/client.py", line 17, in <module>
    from openstack import profile
ImportError: cannot import name profile

MSG:

non-zero return code

NO MORE HOSTS LEFT *************************************************************
 to retry, use: --limit @/tmp/ansible.q8aved_contrail/contrail-ansible-deployer/playbooks/install_openstack.retry

musharani (musharani)
Changed in juniperopenstack:
importance: Undecided → Critical
milestone: none → r5.1.0
Revision history for this message
Leela Bharath Kumar Kassetti (klbharat) wrote :

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.

Revision history for this message
Leela Bharath Kumar Kassetti (klbharat) wrote :

The fix is merged in Ocata branch also. I verified the same with the latest build and I don't see this issue with Ocata build. Can you retest and update back?

More details below:

Upstream Bug info:
https://bugs.launchpad.net/kolla/+bug/1799109

Fix details:
Ocata: https://review.openstack.org/#/c/619469/
Pike: https://review.openstack.org/#/c/615810/
Queens: https://review.openstack.org/#/c/612684/

Revision history for this message
musharani (musharani) wrote :

Not seen this issue in the latest build ocata-master-414. Hence moved to fix released state.

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.