B&R restore fails because of missing custom image in backup file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Ovidiu Poncea |
Bug Description
Brief Description
----------------
On a system with many custom images in registry.local custom images may fail to be backed up when more than 100 images are present and the custom images are listed after the first 100.
Severity
--------
Provide the severity of the defect.
Minor: System/Feature is usable with minor issue - Users rarely have so many images in registry.local & even if they do there is a workaround available.
Steps to Reproduce
------------------
1. put more than 100 images in registry.local
2. run backup procedure
Expected Behavior
------------------
All images should be in the backup
Actual Behavior
----------------
If images above 100 are custom images they are not backed up.
Reproducibility
---------------
100% in given conditions.
System Configuration
-------
All configurations
Branch/Pull Time/Commit
-------
master
Last Pass
---------
never
Test Activity
-------------
Developer Testing
Workaround
----------
Re-upload the missing images manually to registry.local
tags: | added: stx.update |
tags: | added: stx.5.0 |
Changed in starlingx: | |
importance: | Undecided → Medium |
On an HTTP request registry.local is responding with first 100 images. Thisis API default behavior, we should
request all of them.