RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1230937 - instack-undercloud: multiple "openstack No user with a name or ID of" errors during overcloud deployment.
Summary: instack-undercloud: multiple "openstack No user with a name or ID of" errors ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: instack-undercloud
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Kilo
Assignee: James Slagle
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-11 19:54 UTC by Alexander Chuzhoy
Modified: 2016-05-19 15:47 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:47:35 UTC
Embargoed:


Attachments (Terms of Use)

Description Alexander Chuzhoy 2015-06-11 19:54:03 UTC
instack-undercloud: multiple "openstack No user with a name or ID of" errors during  overcloud deployment.

Environment:
instack-undercloud-2.1.2-dev8.el7.centos.noarch


Steps to reproduce:
1. instack-deploy-overcloud --tuskar

Result:
Although the overcloud is deployed successfully, the following errors appear on the screen.

ERROR: openstack No user with a name or ID of 'heat' exists.
ERROR: openstack No user with a name or ID of 'neutron' exists.
ERROR: openstack No user with a name or ID of 'glance' exists.
ERROR: openstack No user with a name or ID of 'ec2' exists.
ERROR: openstack No user with a name or ID of 'nova' exists.
ERROR: openstack No user with a name or ID of 'ceilometer' exists.
ERROR: openstack No user with a name or ID of 'cinder' exists.
ERROR: openstack No user with a name or ID of 'cinderv2' exists.
ERROR: openstack No user with a name or ID of 'swift' exists.

Expected results:
No errors.

Comment 2 Chandan Kumar 2016-05-19 15:47:35 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.


Note You need to log in before you can comment on or make changes to this bug.