upgrade scripts are not invoked in expected order
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Adriano Oliveira |
Bug Description
Brief Description
-----------------
A upgrade scripts with prefix "1xx" will be invoked before a scripts with prefix "2x".
For example:
115-exempt-
will be invoked before:
25-coredns-
50-dcmanager-
60-k8s-
80-dc-cert-
95-apply-
Looks like the sorting is based on only the first digit.
Severity
--------
Minor
Steps to Reproduce
------------------
Add a upgrade script in controllerconfig packages, with prefix "1xx" (e.g, 115-exempt-
Do stx 4.0 to 5.0 upgrade
Check /var/log/
Expected Behavior
------------------
The script with prefix "1xx" should be invoked after these with prefix "xx" where the first "x" is greater than 1.
Actual Behavior
----------------
The script with prefix "1xx' is invoked before these with prefix "xx" where the first "x" is greater than 1.
Reproducibility
---------------
100% reproducible
System Configuration
-------
Any
Branch/Pull Time/Commit
-------
stx master
Last Pass
---------
N/A
Timestamp/Logs
--------------
2020-07-
2020-07-
2020-07-
2020-07-
2020-07-
2020-07-
2020-07-
2020-07-
Test Activity
-------------
Developer testing.
Workaround
----------
N/A
tags: | added: stx.update |
Changed in starlingx: | |
assignee: | John Kung (john-kung) → Adriano Oliveira (aoliveir) |
Changed in starlingx: | |
status: | Triaged → In Progress |
description: | updated |
Marking stx.5.0 gating. Upgrades testing during development was successful but this issue should be addressed in stx.5.0.