Bootstrap ansible fails in creation of barbican credentials on replay

Bug #1859726 reported by Ghada Khalil on 2020-01-14
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Medium
Andy

Bug Description

Brief Description
-----------------
** Opening this LP on behalf of Eddy Raineri
The ansible script intermittently fails during the barbican credential creation on ansible re-play. Even in the re-play case, it is a random failure depending on the order of the endpoints in the service catalog.

During the initial play, the Barbican secret was created prior to populating the initial system configuration and the SystemController endpoints were not populated. The un-configured region name in the Barbican config file does not cause a problem.

Sysinv applies the keystone endpoint runtime manifest when populating the initial system config, which creates the SystemController keystone endpoints. After the first play, the endpoints are populated and re-play does not re-configure the endpoints since the distributed_cloud_role is not changed.

Severity
--------
Minor - intermittent issue

Steps to Reproduce
------------------
On DC, run ansible re-play after the initial bootstrap

Expected Behavior
------------------
Ansible re-play is successful on DC system

Actual Behavior
----------------
Ansible re-play intermittently fails

Reproducibility
---------------
Intermittent; frequency is unknown

System Configuration
--------------------
Distributed Cloud

Branch/Pull Time/Commit
-----------------------
Designer load equivalent to stx.3.0

Last Pass
---------
N/A

Timestamp/Logs
--------------
N/A

Test Activity
-------------
Lab setup

Workaround
----------

Ghada Khalil (gkhalil) wrote :

stx.4.0 / medium priority - intermittent issue on ansible replay

tags: added: stx.4.0 stx.config stx.distcloud
Changed in starlingx:
importance: Undecided → Medium
status: New → Triaged
assignee: nobody → Andy (andy.wrs)
Andy (andy.wrs) on 2020-01-17
Changed in starlingx:
status: Triaged → In Progress
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers