Bug 1908847
Summary: | [4.6.z] RHCOS 4.6 - Missing Initiatorname | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Micah Abbott <miabbott> |
Component: | RHCOS | Assignee: | Jonathan Lebon <jlebon> |
Status: | CLOSED ERRATA | QA Contact: | Michael Nguyen <mnguyen> |
Severity: | urgent | Docs Contact: | |
Priority: | medium | ||
Version: | 4.6 | CC: | aghadge, bbreard, dornelas, imcleod, jlebon, jligon, kholtz, miabbott, mnguyen, nstielau, oarribas, Piyush_Tandon, umesh_sunnapu |
Target Milestone: | --- | ||
Target Release: | 4.6.z | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: The service unit which regenerates the iSCSI initiator name only worked on first boot.
Consequence: Upgrading nodes would not receive uniquely generated initiator names.
Fix: The service unit now runs on every boot.
Result: Upgrading nodes now receive generated initiator names if one doesn't already exist.
|
Story Points: | --- |
Clone Of: | 1908830 | Environment: | |
Last Closed: | 2021-01-18 17:59:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1908830 | ||
Bug Blocks: |
Description
Micah Abbott
2020-12-17 17:50:24 UTC
This change landed in RHCOS 4.6 build 46.82.202012182233-0 Verfied on 4.6.0-0.nightly-2021-01-05-203053 $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.0-0.nightly-2021-01-05-203053 True False 104s Cluster version is 4.6.0-0.nightly-2021-01-05-203053 $ oc get node -o name | xargs -I {} oc debug {} -- chroot /host cat /etc/iscsi/initiatorname.iscsi Starting pod/ip-10-0-131-102us-west-2computeinternal-debug ... To use host binaries, run `chroot /host` InitiatorName=iqn.1994-05.com.redhat:6e85fe3e93db Removing debug pod ... Starting pod/ip-10-0-151-28us-west-2computeinternal-debug ... To use host binaries, run `chroot /host` InitiatorName=iqn.1994-05.com.redhat:c6d700ece9 Removing debug pod ... Starting pod/ip-10-0-165-63us-west-2computeinternal-debug ... To use host binaries, run `chroot /host` InitiatorName=iqn.1994-05.com.redhat:75da27f1f1b7 Removing debug pod ... Starting pod/ip-10-0-167-229us-west-2computeinternal-debug ... To use host binaries, run `chroot /host` InitiatorName=iqn.1994-05.com.redhat:a3c3d08b871b Removing debug pod ... Starting pod/ip-10-0-208-239us-west-2computeinternal-debug ... To use host binaries, run `chroot /host` InitiatorName=iqn.1994-05.com.redhat:b682506b4a98 Removing debug pod ... Starting pod/ip-10-0-221-245us-west-2computeinternal-debug ... To use host binaries, run `chroot /host` InitiatorName=iqn.1994-05.com.redhat:ef47875b4dc0 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 (Moderate: OpenShift Container Platform 4.6.12 bug fix and security update), 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/RHSA-2021:0037 |