Offline Deployment: When executing ./manage-offline-container-images.sh register
with using podman, obtaining image_id fails and the script is interrupted
#11865
Labels
kind/bug
Categorizes issue or PR as related to a bug.
What happened?
I run
./manage-offline-container-images.sh register
to register an image in the container registry with using Podman, the following error is output and the script execution is interrupted.What did you expect to happen?
I expected the script has complete running and the image has been registered in the container registry.
How can we reproduce it (as minimally and precisely as possible)?
[Node configuration]
[Version]
OS
Linux 5.14.0-427.13.1.el9_4.x86_64 x86_64
NAME="Red Hat Enterprise Linux"
VERSION="9.4 (Plow)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="9.4"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux 9.4 (Plow)"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_BUGZILLA_PRODUCT_VERSION=9.4
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.4"
Version of Ansible
ansible [core 2.16.13]
config file = None
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.11/site-packages/ansible
ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/local/bin/ansible
python version = 3.11.7 (main, Jan 22 2024, 00:00:00) [GCC 11.4.1 20231218 (Red Hat 11.4.1-3)] (/usr/bin/python3.11)
jinja version = 3.1.4
libyaml = True
Version of Python
Python 3.9.18
Version of Kubespray (commit)
v2.25.0
Network plugin used
calico
Full inventory with variables
None
Command used to invoke ansible
None
Output of ansible run
None
Anything else we need to know
No response
The text was updated successfully, but these errors were encountered: