Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1703031

Summary: Could not establish a connection to the Zaqar websocket: certificate verify failed
Product: Red Hat OpenStack Reporter: Filip Hubík <fhubik>
Component: python-tripleoclientAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: Sasha Smolyak <ssmolyak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14.0 (Rocky)CC: apevec, emacchi, hbrock, jpichon, jslagle, lhh, mburns
Target Milestone: ---Keywords: Automation, AutomationBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-25 12:36:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
zaqar.log none

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 ***