contrail api connecting to keystone insecurely needs to be suported
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Fix Committed
|
High
|
Ignatious Johnson Christopher | |||
R3.0.3.x |
Fix Committed
|
High
|
Ignatious Johnson Christopher | |||
R3.1 |
Fix Committed
|
High
|
Ignatious Johnson Christopher | |||
R3.1.1.x |
Fix Committed
|
High
|
Ignatious Johnson Christopher | |||
R3.2 |
Fix Committed
|
High
|
Ignatious Johnson Christopher | |||
Trunk |
Fix Committed
|
High
|
Ignatious Johnson Christopher |
Bug Description
contrail-api connecting to keystone insecurely needs to be supported.
when insecure=True is set in the /etc/contrail/
Traceback (most recent call last):
File "/usr/bin/
load_
File "/usr/lib/
main()
File "/usr/lib/
vnc_api_server = VncApiServer(
File "/usr/lib/
auth_svc = vnc_auth_
File "/usr/lib/
if args.auth_protocol == 'https' and args.cafile:
AttributeError: 'Namespace' object has no attribute 'cafile'
no longer affects: | juniperopenstack/r3.0.2.x |
summary: |
- contrail api and vncapi client connecting to keystone insecurely is - broken + contrail api and vncapi client connecting to keystone insecurely needs + to be suported |
description: | updated |
Workaround is to set
cafile = ''
in the [KEYSTONE] section of /etc/contrail/ contrail- keystone- auth.conf along with the insecure flag.