Update failure will rollback to old_app even if app metadata indicates otherwise
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Dan Voiculeasa |
Bug Description
Brief Description
-----------------
An app can request that the rollback should be skipped in case the update fails. But the request is ignored.
Severity
--------
Critical: System/Feature is not usable due to the defect
Steps to Reproduce
------------------
This can be forced by modifying the metadata.yaml of the app, and forcing an armada failure for the N+1 version(for example increase the PVC size).
metadata.yaml
upgrades:
update_
Do system application-update new_app_version.tgz
Expected Behavior
------------------
Framework doesn't try recover the old app.
Actual Behavior
----------------
Framework tries to recover the old app.
Reproducibility
---------------
100%
System Configuration
-------
Any
Branch/Pull Time/Commit
-------
13 May
Last Pass
---------
I don't think it did.
Timestamp/Logs
--------------
N/A
Test Activity
-------------
Developer Testing
Workaround
----------
No.
tags: | added: stx.6.0 stx.containers |
Changed in starlingx: | |
importance: | Undecided → Medium |
Attached the modified app used to test: vault-1.0-17.tgz. Can be used over vault-1.0.16.tgz, by using "system application-update vault-1.0-17.tgz".