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 1672344 - The etcd image with tag 3.2.22 -> 3.2.22-24 contains etcd binary for 3.3.11
Summary: The etcd image with tag 3.2.22 -> 3.2.22-24 contains etcd binary for 3.3.11
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: etcd-container
Version: 7.6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Sam Batschelet
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
: 1732416 (view as bug list)
Depends On:
Blocks: 1186913 1647729
TreeView+ depends on / blocked
 
Reported: 2019-02-04 16:23 UTC by Vladislav Walek
Modified: 2024-03-25 15:13 UTC (History)
29 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-06 18:17:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1672518 0 unspecified CLOSED Add etcd-3.3 to yum.conf exclude line 2021-02-22 00:41:40 UTC
Red Hat Knowledge Base (Article) 3938261 0 None None None 2019-03-06 18:17:05 UTC
Red Hat Knowledge Base (Solution) 3886811 0 None None None 2019-02-05 11:33:59 UTC

Description Vladislav Walek 2019-02-04 16:23:38 UTC 
Description of problem:

The etcd image with tag 3.2.22 -> 3.2.22-24 contains etcd binary for 3.3.11

https://access.redhat.com/containers/?architecture=AMD64&tab=package-list#/registry.access.redhat.com/rhel7/etcd/images/3.2.22-24

Shouldn't the etcd image have the binaries for 3.2.22?

Version-Release number of selected component (if applicable):
OpenShift Container Platform 3.11

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 27 Derrick Ornelas 2019-03-06 18:17:05 UTC 
On Thursday January 31, 2019 Red Hat released a version of etcd that was inappropriately labeled to the public. This bad image was released in the rhel-7-server-extras-rpms channel and the Red Hat Container Catalog. Specifically, an etcd container labeled '3.2.22-24' was released with etcd 3.3.11 inside of the container image. By Tuesday February 5th, 2019 Red Hat realized the issue and reverted the etcd container and RPM channels back to a healthy image. Etcd container 3.2.22-18 is now the correct and healthy container.

OpenShift 3.0 to 3.9 uses RPMs by default for etcd installations. OpenShift 3.10 to 3.11 uses container images for etcd installations. Not all customers will be affected by this issue. If you are running an RPM based etcd with a RHEL7 channel attached to the RHEL hosts, and issued a ‘yum update’ for all RPMs installed on your etcd hosts between the 6 days of January 31 to Feb 5th, you would have pulled the bad RPMs. Or, if you are running a container based etcd and you have upgraded your cluster, scaled up the etcd nodes or manually installed the latest etcd container image between the 6 days of January 31 to Feb 5th, you would have pulled the bad container image. 

Please refer to the following Kbase article for more information about this issue and how to check if your systems have been affected:

  https://access.redhat.com/articles/3938261
Comment 28 Sam Batschelet 2019-08-07 12:53:00 UTC 
*** Bug 1732416 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.