INSVC patch install failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
ZhangXiao |
Bug Description
Brief Description
-----------------
Sometimes INSVC patch can not be installed.
Severity
--------
Major
Steps to Reproduce
------------------
sw-patch upload 22.12_GEO_
sw-patch apply 22.12_GEO_
sudo sw-patch host-install controller-0
Expected Behavior
------------------
Patch is applied, installed and removed successfully
Actual Behavior
----------------
Patch is applied, installed successfully, but it fails on random nodes during removal
Reproducibility
---------------
For some ISO installation, 100%; for others, 0.
System Configuration
-------
WRCPENG-DC1 and WRCPENG-DC1_1
Branch/Pull Time/Commit
-------
Branch and the time when code was pulled or git commit or cengn load info
Last Pass
---------
Did this test scenario pass previously? If so, please indicate the load/pull time info of the last pass.
Use this section to also indicate if this is a new test scenario.
Timestamp/Logs
--------------
2023-11-
OSTree:
assertion failed (kernel_
("f3628ac3f7309
"4604edd0da60ff
2023-11-
sw-patch-
changes and create deploymentduring host-install.
Traceback (most recent call last):
File "/usr/lib/
subprocess.
File "/usr/lib/
raise CalledProcessEr
subprocess.
Test Activity
-------------
[Sanity, Feature Testing, Regression Testing, Developer Testing, Evaluation, Other - Please specify]
Workaround
----------
No
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.9.0 stx.distro.other stx.tools |
When construction the ostree repo, ostree needs us to make a checksum(boot checksum) of kernel images and initramfs file stored in /usr/lib/ ostree- boot. Each time to make a new deployment, that very checksum will be checked, once it is not correct, error occurred;
To avoid resetting target with INSVC patch installation, we just remount the /usr. While the principle is INSVC patch should not contain any modification on kernel or initramfs to avoid the checksum failure above;
The method to make the boot checksum is `cat file1 file2 file3 ... | sha256sum`, same file set with different order will lead to different checksum result. If this occurred when building INSVC patch without modification on kernel or initramfs, the boot checksum changed thus case the deploy failed.