yum cache corruption causes build-iso to fail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Davlet Panech |
Bug Description
Brief Description
-----------------
build-iso fails with
18:08:17 Not using downloaded local-std/
18:08:17 Current : Sat Mar 14 18:07:32 2020
18:08:17 Downloaded: Sat Mar 14 18:07:08 2020
18:08:17 rpm2cpio: ////localdisk/
Severity
--------
Major: unable to build an iso
Steps to Reproduce
------------------
A little unclear ... here is what I know
- At minimum two different projects must build in the same environment i.e. docker instance.
- The two projects must not agree on the version of platform-
e.g. platform-
- Alternate running build-pkgs and build-iso in the two different projects
- At some point the yum cache of one project contaminated the other, and build-iso starts looking for package versions only available in the other.
Expected Behavior
------------------
build-iso passes for both projects.
Actual Behavior
----------------
build-iso fails.
Reproducibility
---------------
Intermittent: In terms of inducing the initial yum cache contamination. After contamination, build-iso fails consistently.
System Configuration
-------
N/A
Branch/Pull Time/Commit
-------
2020-03-14_16-00-00
Last Pass
---------
2020-03-07_16-00-00
Timestamp/Logs
--------------
18:07:14 Installing PKG=platform-
...
18:08:17 Not using downloaded local-std/
18:08:17 Current : Sat Mar 14 18:07:32 2020
18:08:17 Downloaded: Sat Mar 14 18:07:08 2020
18:08:17 rpm2cpio: ////localdisk/
Test Activity
-------------
Build
Workaround
----------
Clean yum cache with ...
yum clean all -c $MY_WORKSPACE/
Changed in starlingx: | |
assignee: | Scott Little (slittle1) → Davlet Panech (dpanech) |
stx.4.0 / high priority - results in build iso failures