stx-openstack application sometimes indicates apply-failed when configuring overrides
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Triaged
|
Low
|
Frank Miller |
Bug Description
Brief Description
-----------------
When we activate additional openstack services using application overrides we sometimes
get an apply-failed status after stx-openstack is applied
Severity
--------
Minor
Steps to Reproduce
------------------
1. Upload the stx-application charts e.g. $ system application-upload stx-openstack-
2. (Optional) You can inspect the overrides with: $ system helm-override-list stx-openstack --long
3. Override the original enable attributes to activate some openstack services that are deactivated by default e.g. ceilometer, aodh, gnocchi, panko
$ system helm-chart-
$ system helm-chart-
$ system helm-chart-
$ system helm-chart-
4. Apply stx-openstack: $ system application-apply stx-openstack (YOu have to do this very fast after the overrides are configured (within one minute), you can run this command and previous in a batch)
Expected Behavior
------------------
Application stx-openstack is succesfuly applied
Actual Behavior:
-----------------
Sometimes the stx-openstack is succesfuly applied and after at most one minute the applicatin passes into an apply-failed state.
Reproducibility
---------------
Intermittent
System Configuration
-------
Virtual
Any Configuration
Branch/Pull Time/Commit
-------
master/ (Seen on multiple builds)
Last Pass
---------
Not sure
Preliminary investigation:
---------
There seem to be some inconsistencies on the way application overrides are generated and checked after the installation of stx-openstack application which generated an Invalid override exception. for the aditional chart group e.g.
cg-openstack-
Timestamp/Logs
--------------
Attached.
Test Activity
-------------
Developer Testing
Workaround:
----------
Wait at least 60 seconds after manually configure the overrides
system application-apply stx-openstack and the issue does not appear.
Low priority / not gating - intermittent issue with openstack helm overrides for optional services. Issue can be avoided by waiting 60 seconds before re-applying the application after the overrides are specified.