Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1788889

Summary: podman resource agent fail to detect specific image names are pulled locally
Product: Red Hat Enterprise Linux 8 Reporter: Damien Ciabrini <dciabrin>
Component: resource-agentsAssignee: Oyvind Albrigtsen <oalbrigt>
Status: CLOSED ERRATA QA Contact: pkomarov
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.0CC: agk, cluster-maint, fdinitto, pkomarov
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: resource-agents-4.1.1-40.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 15:24:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Damien Ciabrini 2020-01-08 10:09:06 UTC
Description of problem:
Currently the podman resource agent implements some logics to check
whether the container image to be used for a bundle is present on the
host. Checking for the image is implemented by running 'podman images'
and using a regular expression to parse the text output looking for
the target image.

The regular expression used for parsing the output of podman images
doesn't work when the container image tag doesn't look like a FQDN
or a host:port pattern. So the resource agent won't find image whose
tag is e.g. "foo/bar/gee:hux". This is because internally, podman
stores such tags as "localhost/foo/bar/gee:hux" in the container
storage.

Version-Release number of selected component (if applicable):
resource-agents-4.1.1-33.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1. create a 3 nodes cluster <ra1,ra2,ra3>

   pcs cluster setup --force --name ratester ra1 ra2 ra3
   pcs cluster start --all
   pcs property set stonith-enabled=false

2. pull an image on all nodes and add a tag to it

   podman pull docker.io/tripleoqueens/centos-binary-mariadb:current-tripleo-rdo
   podman tag docker.io/tripleoqueens/centos-binary-mariadb:current-tripleo-rdo foo/bar/gee:hux

3. create a random bundle that will hold an ocf resource

   pcs resource bundle create tst-bundle container podman image=foo/bar/gee:hux network=host options="--user=root --log-driver=journald" run-command="/usr/sbin/pacemaker_remoted" network control-port=3123 storage-map id=tst0 source-dir=/dev/log target-dir=/dev/log storage-map id=tst1 source-dir=/dev/zero target-dir=/etc/libqb/force-filesystem-sockets options=ro storage-map id=tst2 source-dir=/var/log/pacemaker target-dir=/var/log/pacemaker options=rw --disable
   pcs resource create dummy ocf:pacemaker:Dummy meta bundle tst-bundle
   pcs resource enable tst-bundle

Actual results:
The bundle will fail to start because the resource agent thinks the image is not pulled locally

Expected results:
The bundle should start

Additional info:
The issue is fixed upstream with https://github.com/ClusterLabs/resource-agents/commit/90eddad56e688fca4fca82ab1e51b12e11f9cc78

Comment 2 pkomarov 2020-01-19 07:35:00 UTC
[root@controller-0 ~]# rpm -q resource-agents
resource-agents-4.1.1-40.el8.x86_64

                podman pull docker.io/tripleoqueens/centos-binary-mariadb:current-tripleo-rdo
                podman tag docker.io/tripleoqueens/centos-binary-mariadb:current-tripleo-rdo foo/bar/gee:hux
                pcs resource bundle create tst-bundle container podman image=foo/bar/gee:hux network=host options="--user=root --log-driver=journald" run-command="/usr/sbin/pacemaker_remoted" network control-port=3123 storage-map id=tst0 source-dir=/dev/log target-dir=/dev/log storage-map id=tst1 source-dir=/dev/zero target-dir=/etc/libqb/force-filesystem-sockets options=ro storage-map id=tst2 source-dir=/var/log/pacemaker target-dir=/var/log/pacemaker options=rw --disa
ble
                pcs resource create dummy ocf:pacemaker:Dummy meta bundle tst-bundle
                pcs resource enable tst-bundle
                sleep 30s
                pcs status |grep tst-bundle|grep Started

[root@controller-0 ~]#                 pcs status |grep tst-bundle|grep Started
   tst-bundle-0	(ocf::pacemaker:Dummy):	Started controller-0

Comment 4 errata-xmlrpc 2020-04-28 15:24:25 UTC
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:1565