RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1400584 - undercloud installation Error: Failed to apply catalog: Insufficient credentials to authenticate
Summary: undercloud installation Error: Failed to apply catalog: Insufficient credenti...
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: instack-undercloud
Version: trunk
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: trunk
Assignee: James Slagle
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-01 14:36 UTC by Cyril Lopez
Modified: 2023-09-15 00:00 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-01-13 07:54:52 UTC
Embargoed:


Attachments (Terms of Use)
log (330.39 KB, text/plain)
2016-12-01 14:36 UTC, Cyril Lopez
no flags Details

Description Cyril Lopez 2016-12-01 14:36:49 UTC
Created attachment 1226837 [details]
log

During the undercloud installation, is failing with this error :

Error: Failed to apply catalog: Insufficient credentials to authenticate

Log file join

#Ocata-test-day-1

Comment 1 cherrytk 2017-03-20 06:20:07 UTC
I met this problem too when I install undercloud.
-------------------------------------------------------

2017-03-20 11:12:27,835 INFO: Error: Failed to apply catalog: Insufficient credentials to authenticate
2017-03-20 11:12:42,955 INFO: + rc=1
2017-03-20 11:12:42,956 INFO: + set -e
2017-03-20 11:12:42,956 INFO: + echo 'puppet apply exited with exit code 1'
2017-03-20 11:12:42,956 INFO: puppet apply exited with exit code 1
2017-03-20 11:12:42,957 INFO: + '[' 1 '!=' 2 -a 1 '!=' 0 ']'
2017-03-20 11:12:42,957 INFO: + exit 1
2017-03-20 11:12:42,957 INFO: [2017-03-20 11:12:42,957] (os-refresh-config) [ERROR] during configure phase. [Command '['dib-run-parts', '/usr/libexec/os-refresh-config/configure.d']' returned non-zero exit status 1]
2017-03-20 11:12:42,958 INFO: 
2017-03-20 11:12:42,958 INFO: [2017-03-20 11:12:42,957] (os-refresh-config) [ERROR] Aborting...
2017-03-20 11:12:42,968 ERROR: 
#############################################################################
Undercloud install failed.

Reason: os-refresh-config failed. See log for details.

See the previous output for details about what went wrong.  The full install
log can be found at /home/stack/.instack/install-undercloud.log.

#############################################################################

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1439, in install
    _run_orc(instack_env)
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1183, in _run_orc
    _run_live_command(args, instack_env, 'os-refresh-config')
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 554, in _run_live_command
    raise RuntimeError('%s failed. See log for details.' % name)
RuntimeError: os-refresh-config failed. See log for details.
Command 'instack-install-undercloud' returned non-zero exit status 1

Comment 2 Janki 2017-04-21 13:39:23 UTC
I am facing the same error. Enabled reop = rhel-7-server-openstack-beta-rpms
-----------------------------

2017-04-21 21:28:21,182 INFO: Warning: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Skipping because of failed dependencies
2017-04-21 21:28:21,486 INFO: Error: Failed to apply catalog: Insufficient credentials to authenticate
2017-04-21 21:28:30,031 INFO: + rc=1
2017-04-21 21:28:30,031 INFO: + set -e
2017-04-21 21:28:30,031 INFO: + echo 'puppet apply exited with exit code 1'
2017-04-21 21:28:30,031 INFO: puppet apply exited with exit code 1
2017-04-21 21:28:30,031 INFO: + '[' 1 '!=' 2 -a 1 '!=' 0 ']'
2017-04-21 21:28:30,031 INFO: + exit 1
2017-04-21 21:28:30,032 INFO: [2017-04-21 21:28:30,031] (os-refresh-config) [ERROR] during configure phase. [Command '['dib-run-parts', '/usr/libexec/os-refresh-config/configure.d']' returned non-zero exit status 1]
2017-04-21 21:28:30,032 INFO: 
2017-04-21 21:28:30,032 INFO: [2017-04-21 21:28:30,032] (os-refresh-config) [ERROR] Aborting...
2017-04-21 21:28:30,038 ERROR: 
#############################################################################
Undercloud install failed.

Reason: os-refresh-config failed. See log for details.

See the previous output for details about what went wrong.  The full install
log can be found at /home/stack/.instack/install-undercloud.log.

#############################################################################

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1447, in install
    _run_orc(instack_env)
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1191, in _run_orc
    _run_live_command(args, instack_env, 'os-refresh-config')
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 558, in _run_live_command
    raise RuntimeError('%s failed. See log for details.' % name)
RuntimeError: os-refresh-config failed. See log for details.
Command 'instack-install-undercloud' returned non-zero exit status 1

Comment 3 Sai Sindhur Malleni 2017-04-25 20:07:48 UTC
Seeing this with OSP11 latest bits, any update here?

Comment 4 Nilesh 2017-05-05 10:12:48 UTC
ME to facing same issue with OSP11 latest bits, please update if any workaround

Comment 5 Stephen Kitt 2017-05-22 11:48:30 UTC
I'm still seeing this with the OSP11 release artifacts.

Comment 6 alan@johnson.org 2017-06-02 15:52:05 UTC
Any updates here as I am seeing it also during Director 11 when deploying the undercloud

Comment 7 Ryan McAdams 2017-06-16 20:32:05 UTC
I ran into this same issue, turned out somehow during the overcloud installation my machine lost the default route, after I figured that out and corrected it the overcloud installation completed without problem.  I was able to reproduce this three times in a row.

Comment 8 Ryan McAdams 2017-06-16 20:32:30 UTC
Sorry, meant undercloud installation.

Comment 9 atiwary 2017-08-24 07:08:47 UTC
Hi Ryan,

can you let us know what are steps you have followed to resolve the issue.

I am continuously facing the issue.

Thanks in advance,
Abhishek Tiwary

Comment 10 Tobias Löb 2017-08-28 09:56:02 UTC
(In reply to atiwary from comment #9)
> Hi Ryan,
> 
> can you let us know what are steps you have followed to resolve the issue.
> 
> I am continuously facing the issue.
> 
> Thanks in advance,
> Abhishek Tiwary

Hi Abhishek,

i had the same issue and had to set a static default route: 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-static-routes.html

I added the Line in the file /etc/sysconfig/network:
GATEWAY=<IP>

Maybe its not the best way but it fixed it like Ryan said.

Comment 11 Udi Kalifon 2017-11-01 17:03:40 UTC
I'm hitting this in OSP12, puddle 2017-10-31.2.

Comment 12 Yatin Karel 2021-01-13 07:54:52 UTC
Ocata/Pike are EOL, closing the bug. If you still face same issue in supported release, feel free to open it for that release so it can be fixed. Also rocky+ instack-undercloud is depercated in favor of containerized undercloud.

Comment 13 Red Hat Bugzilla 2023-09-15 00:00:40 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


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