magnum deploy fail

Bug #1674894 reported by zhubingbing
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
kolla-ansible
Invalid
High
zhubingbing

Bug Description

i deploy magnum in kolla-ansible(master centos/source);

2017-03-22 14:15:12.117 7 INFO magnum.common.cert_manager.barbican_cert_manager [req-8a123738-6e9f-4465-9043-4ab0dc6a3035 - - - - -] Storing certificate container 'Magnum-Conductor' in Barbican.
2017-03-22 14:15:15.397 7 ERROR magnum.common.keystone [req-f4f470c7-1200-41b8-8daf-90b7d850c809 - - - - -] Keystone API connection failed: no password, trust_id or token found.
2017-03-22 14:15:15.398 7 ERROR magnum.common.exception [req-f4f470c7-1200-41b8-8daf-90b7d850c809 - - - - -] Exception in string format operation, kwargs: {'code': 500}
2017-03-22 14:15:15.398 7 ERROR magnum.common.exception Traceback (most recent call last):
2017-03-22 14:15:15.398 7 ERROR magnum.common.exception File "/var/lib/kolla/venv/lib/python2.7/site-packages/magnum/common/exception.py", line 92, in __init__
2017-03-22 14:15:15.398 7 ERROR magnum.common.exception self.message = self.message % kwargs
2017-03-22 14:15:15.398 7 ERROR magnum.common.exception KeyError: u'client'
2017-03-22 14:15:15.398 7 ERROR magnum.common.exception
2017-03-22 14:15:15.398 7 ERROR oslo.service.loopingcall [req-f4f470c7-1200-41b8-8daf-90b7d850c809 - - - - -] Fixed interval looping call 'magnum.service.periodic.ClusterUpdateJob.update_status' failed

Changed in kolla-ansible:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → zhubingbing (zhubingbing)
milestone: none → pike-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (master)

Fix proposed to branch: master
Review: https://review.openstack.org/448438

Changed in kolla-ansible:
status: Confirmed → In Progress
Changed in kolla-ansible:
milestone: pike-2 → pike-3
Revision history for this message
Mark Goddard (mgoddard) wrote :

I think the bug description here is actually describing magnum bug 1666790 which is fixed in master and stable/ocata. The proposed fix (https://review.openstack.org/448438) resolves a different issue, but one that I have also seen.

Revision history for this message
Mark Goddard (mgoddard) wrote :
Download full text (3.2 KiB)

Actually, perhaps the bug description is correct, it is just made more confusing by bug 1666790 which causes an exception while handling the error. Here's a trace from a conductor with bug 1666790 resolved:

2017-06-21 14:44:30.441 7 ERROR magnum.common.keystone [req-aaddc765-a943-4e26-a304-be98e3cac6e6 - - - ee5fa53979ea47fc81178c9c1d5177a5 -] Keystone API connection failed: no password, trust_id or token found.
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall [req-aaddc765-a943-4e26-a304-be98e3cac6e6 - - - ee5fa53979ea47fc81178c9c1d5177a5 -] Fixed interval looping call 'magnum.service.periodic.ClusterUpdateJob.update_status' failed
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall Traceback (most recent call last):
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/oslo_service/loopingcall.py", line 137, in _run_loop
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall result = func(*self.args, **self.kw)
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/magnum/service/periodic.py", line 71, in update_status
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall cdriver.update_cluster_status(self.ctx, self.cluster)
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/magnum/drivers/heat/driver.py", line 80, in update_cluster_status
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall poller.poll_and_check()
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/magnum/drivers/heat/driver.py", line 169, in poll_and_check
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall stack = self.openstack_client.heat().stacks.get(
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/magnum/common/exception.py", line 59, in wrapped
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall return func(*args, **kw)
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/magnum/common/clients.py", line 94, in heat
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall region_name=region_name)
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/magnum/common/clients.py", line 45, in url_for
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall return self.keystone().session.get_endpoint(**kwargs)
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/magnum/common/keystone.py", line 59, in session
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall auth = self._get_auth()
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/magnum/common/keystone.py", line 100, in _get_auth
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall message='reason %s' % msg)
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall AuthorizationFailure: reason Keystone API connection failed: no password, trust_id or token found.
2017-06-21 14:44:30.442 7 ERROR oslo.service.loopingcall

Looks like there is ...

Read more...

Changed in kolla-ansible:
milestone: pike-3 → pike-rc1
Changed in kolla-ansible:
milestone: pike-rc1 → pike-rc2
milestone: pike-rc2 → queens-1
Changed in kolla-ansible:
milestone: queens-2 → queens-3
Changed in kolla-ansible:
milestone: queens-3 → queens-rc1
Changed in kolla-ansible:
milestone: queens-rc1 → rocky-1
Changed in kolla-ansible:
milestone: rocky-2 → rocky-3
Revision history for this message
Mark Goddard (mgoddard) wrote :

Fixed in magnum in pike, backported to ocata.

Changed in kolla-ansible:
status: In Progress → Invalid
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on kolla-ansible (master)

Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.opendev.org/448438
Reason: Very old

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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