Created attachment 1611486 [details] ansible.log Description of problem: When installing ceph 4.0 beta on container , playbook fails at TASK [ceph-container-common : pulling registry.redhat.io/rhceph-beta/rhceph-4-rhel8:latest image]. Version-Release number of selected component (if applicable): ceph-ansible-4.0.0-0.1.rc14.el8cp.noarch How reproducible: 3/3 Steps to Reproduce: 1.Performed pre-installation steps 2.Run site-docker.yml Actual results: stderr: |- Trying to pull registry.redhat.io/rhceph-beta/rhceph-4-rhel8:latest...Failed error pulling image "registry.redhat.io/rhceph-beta/rhceph-4-rhel8:latest": unable to pull registry.redhat.io/rhceph-beta/rhceph-4-rhel8:latest: unable to pull image: Error determining manifest MIME type for docker://registry.redhat.io/rhceph-beta/rhceph-4-rhel8:latest: unable to retrieve auth token: invalid username/password Expected results: Ceph-ansible should handle this issue Additional info: all.yml: --- dummy: fetch_directory: ~/ceph-ansible-keys ceph_origin: repository ceph_repository: rhcs ceph_rhcs_version: 4 monitor_interface: eno1 public_network: 10.8.128.0/21 ceph_docker_image: "rhceph-beta/rhceph-4-rhel8" ceph_docker_registry: "registry.redhat.io" containerized_deployment: true inventory file: [mons] magna056 [mgrs] magna056 [osds] magna058 lvm_volumes="[{'data':'/dev/sdb'},{'data':'/dev/sdc'},{'data':'/dev/sdd'}]" osd_scenario="lvm" osd_objectstore="bluestore" [grafana-server] magna059.ceph.redhat.com
folks, this is now blocking downstream activities right now. Can we please reach a (quick) resolution here?
This is the explanation: > Our container image is in registry.redhat.io which strategically is where Redhat is moving to across > products - and it's an authenticated registry - see https://access.redhat.com/RegistryAuthentication - > which means our pulls must provide creds! Which makes this bug a blocker.
Hi @Guillaume Abrioux, Are we considering Paul Cuzner suggestion in comment #3?
Verified using ceph version 14.2.4-31.el7cp ansible-2.8.7-1.el7ae.noarch ceph-ansible-4.0.6-1.el7cp.noarch Moving the bz to "VERIFIED" state. As a separate bz has been filed to track other changes.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0312