Bug 1777388 - cloud-utils-growpart install conflicts with gce-disk-expand in google managed image when scale up rhel node
Summary: cloud-utils-growpart install conflicts with gce-disk-expand in google managed...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3.0
Assignee: Russell Teague
QA Contact: Yang Yang
URL:
Whiteboard:
Depends On: 1773446
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-27 14:57 UTC by Russell Teague
Modified: 2020-01-23 11:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1773446
Environment:
Last Closed: 2020-01-23 11:14:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift openshift-ansible pull 12037 0 'None' closed Bug 1777388: Remove cloud-utils-growpart from node package list 2020-04-26 08:02:57 UTC

Description Russell Teague 2019-11-27 14:57:24 UTC
+++ This bug was initially created as a clone of Bug #1773446 +++

Description of problem:

Version-Release number of the following components:
openshift-ansible-4.3.0-201911150628.git.186.b95edd2.el7

How reproducible:
Always

Steps to Reproduce:
1. Install a UPI cluster on GCP
2. Launch a RHEL instance using google managed image
3. Run openshift-ansbile playbook to scale up a rhel worker node.


Actual results:
gce-disk-expand is pre-installed in google managed image, which confilicts some packages which is trying to be installed by installer.

TASK [openshift_node : Install openshift support packages] *********************
Monday 18 November 2019  14:35:25 +0800 (0:00:00.062)       0:00:03.514 ******* 

FAILED - RETRYING: Install openshift support packages (3 retries left).

FAILED - RETRYING: Install openshift support packages (2 retries left).

FAILED - RETRYING: Install openshift support packages (1 retries left).

fatal: [10.0.32.7]: FAILED! => {"ansible_job_id": "277562400775.5314", "attempts": 3, "changed": true, "changes": {"installed": ["setools-console", "dracut-network", "podman", "skopeo", "runc", "containernetworking-plugins", "cri-tools", "nfs-utils", "dnsmasq", "lvm2", "iscsi-initiator-utils", "device-mapper-multipath", "mdadm", "cryptsetup", "sssd", "bzip2", "tmux", "nmap-ncat", "bind-utils", "strace", "bash-completion", "nano", "iptables-services", "bridge-utils", "container-storage-setup", "cloud-utils-growpart", "ceph-common", "microcode_ctl", "irqbalance", "glusterfs-fuse"], "updated": []}, "finished": 1, "msg": "Error: gce-disk-expand conflicts with cloud-utils-growpart-0.29-5.el7.noarch\n", "obsoletes": {"python-urllib3": {"dist": "noarch", "repo": "@rhui-rhel-7-server-rhui-rpms", "version": "1.10.2-7.el7"}}, "rc": 1, "results": 

Expected results:
No conflicts, scale up succeed.

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 2 Yang Yang 2019-12-12 07:50:29 UTC
Verified with payload 4.3.0-0.nightly-2019-12-08-215349.
RHEL node scaleup works well using rhel-7-v20191121 image which is managed by google.


Checking the RHEL node status
[cloud-user@yyupi-6css5-w-a-l-0 ~]$ oc get node
NAME                                            STATUS   ROLES    AGE    VERSION
yyupi-6css5-m-0.c.openshift-qe.internal         Ready    master   3d3h   v1.16.2
yyupi-6css5-m-1.c.openshift-qe.internal         Ready    master   3d3h   v1.16.2
yyupi-6css5-m-2.c.openshift-qe.internal         Ready    master   3d3h   v1.16.2
yyupi-6css5-w-a-86hr5.c.openshift-qe.internal   Ready    worker   3d3h   v1.16.2
yyupi-6css5-w-a-l-0                             Ready    worker   20m    v1.16.2
yyupi-6css5-w-a-l-1                             Ready    worker   20m    v1.16.2
yyupi-6css5-w-b-7qq8j.c.openshift-qe.internal   Ready    worker   3d3h   v1.16.2


Getting the OS version of the RHEL node
[cloud-user@yyupi-6css5-w-a-l-0 ~]$ cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.7 (Maipo)

Comment 4 errata-xmlrpc 2020-01-23 11:14:45 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:0062


Note You need to log in before you can comment on or make changes to this bug.