Bug 1703031 - Could not establish a connection to the Zaqar websocket: certificate verify failed
Summary: Could not establish a connection to the Zaqar websocket: certificate verify f...
Keywords:
Status: CLOSED DUPLICATE of bug 1702918
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: Sasha Smolyak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-25 10:38 UTC by Filip Hubík
Modified: 2019-04-26 11:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-25 12:36:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
zaqar.log (16.29 KB, text/plain)
2019-04-25 10:38 UTC, Filip Hubík
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1817634 0 None None None 2019-04-25 12:10:13 UTC
OpenStack gerrit 655626 0 None None None 2019-04-25 12:10:13 UTC

Description Filip Hubík 2019-04-25 10:38:49 UTC
Created attachment 1558610 [details]
zaqar.log

Description of problem:

OSP14 deployment fails with error on command:

undercloud-0 $ openstack overcloud node import --instance-boot-option=local /home/stack/instackenv.json

Could not establish a connection to the Zaqar websocket. The command was sent but the answer could not be read.
[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)

Version-Release number of selected component (if applicable):
OSP14, started since puddle 2019-04-24.2

How reproducible:
100%

Steps to Reproduce:
1. Deploy OSP14 using InfraRed, specify puddle 2019-04-24.2
2. Task [register hosts to instack and configure boot] will fail

Additional info:
python2-openstackclient.noarch  3.16.2-1.el7ost
/var/log/containers/zaqar/zaqar.log attached
structure of instackenv.json is not changed between latest working puddle (with exception MAC addresses)

Comment 3 Emilien Macchi 2019-04-25 12:36:58 UTC

*** This bug has been marked as a duplicate of bug 1702918 ***


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