User populated images not present in local registry after B&R
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
David Sullivan |
Bug Description
Brief Description
-----------------
After a B&R user created pods using images from local registry.local remained in an ImagePullBackOff state.
Severity
--------
Major
Steps to Reproduce
------------------
Method A)
During first bootstrap use `additional_
additional_
- my-domain/
Method B)
After unlock manually download and push a custom image `my-domain/
After either method A or B:
Deploy a pod container using registry.
Perform the backup and restore.
Expected Behavior
------------------
All pods recover after the restore
Actual Behavior
----------------
A few pods were stuck in ImagePullBackOff state, eg:
test test-pod-
Reproducibility
---------------
Reproducible
System Configuration
-------
ALL
Branch/Pull Time/Commit
-------
ISO built on July 1
Last Pass
---------
Timestamp/Logs
--------------
Test Activity
-------------
Workaround
----------
User has to manually populate local registry with his custom pod container images.
Changed in starlingx: | |
assignee: | nobody → Dan Voiculeasa (dvoicule) |
tags: | added: stx.update |
Reviewed: https:/ /review. opendev. org/739195 /git.openstack. org/cgit/ starlingx/ ansible- playbooks/ commit/ ?id=e2cbd22b3fe 79fc2e0e69a6de0 bd0f6c14417b0c
Committed: https:/
Submitter: Zuul
Branch: master
commit e2cbd22b3fe79fc 2e0e69a6de0bd0f 6c14417b0c
Author: Dan Voiculeasa <email address hidden>
Date: Fri Jul 3 12:01:10 2020 +0300
Optimize download image list
Use `unique` filter to remove duplicates in the list.
Partial-Bug: 1886152 e413ec5402a9c2e 0d804f66f9b
Change-Id: Ia9b2276e1654b9
Signed-off-by: Dan Voiculeasa <email address hidden>