barbican is not added in the keystone service-list
Bug #1626761 reported by
Vinoth Kannan Ganapathy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | ||||||
| R3.0 |
Won't Fix
|
Medium
|
Unassigned | |||
| R3.0.2.x |
Won't Fix
|
High
|
Unassigned | |||
Bug Description
with the build 3.0.2.0-51 liberty,
because of the bug, https:/
hence upgrading from this version to any later version will not have barbican in the keystone service-list..
Workaround is to either manually add barbican service to keystone, else run the following script
/opt/contrail/
| tags: | added: releasenote |
Revision history for this message
| Jeba Paulaiyan (jebap) wrote | #1 |
| no longer affects: | juniperopenstack |
| information type: | Proprietary → Public |
To post a comment you must log in.
Notes for 3.0.3.0 release notes:
If a cluster is upgraded from a contrail release without barbican support to 3.0.3.0 (ie., upgrade from releases before 3.0.2.0 to 3.0.3.0), to use barbican service, the following script need to be invoked one time after upgrade on the openstack node:
/opt/contrail/