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 1472389 - default LVM volume group has different name when using ISO vs cloud image
Summary: default LVM volume group has different name when using ISO vs cloud image
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rhel-server-atomic
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Colin Walters
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-18 15:34 UTC by Micah Abbott
Modified: 2017-07-19 13:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-19 13:46:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Micah Abbott 2017-07-18 15:34:35 UTC 
After booting a 7.4 cloud image:

# vgdisplay | grep 'VG Name'
  VG Name               atomicos


After installing via ISO:

# vgdisplay | grep 'VG Name'
  VG Name               rhelah



Turns out this has been around for a while.  Found the same discrepancy when comparing a 7.3.x ISO and 7.3.x cloud image
Comment 1 Jonathan Lebon 2017-07-18 16:33:05 UTC 
Yeah, I suppose we should try to be consistent. :) Between the two, I'd vote for atomicos, since that's what's used upstream as well.
Comment 3 Jonathan Lebon 2017-07-18 21:32:15 UTC 
This took some digging around, though it seems like blivet takes "rhelah" from anaconda, which comes up with it by just taking the first letter of each word in the product name (in our case, the product name being "Red Hat Enterprise Linux Atomic Host").

Changing this would require mucking around with one or more of rpm-ostree-toolbox, anaconda, or blivet. I'm not sure how much it's worth it given the issue, so I'm inclined to change my opinion and instead change the cloud image to also be "rhelah". Does that work?

AFAIU, this is just for cosmetics, right? (And I suppose, to make KBs & docs more easily apply to both cases?) Or is this discrepancy causing some other subtle issues?
Comment 5 Micah Abbott 2017-07-19 12:55:22 UTC 
> AFAIU, this is just for cosmetics, right? (And I suppose, to make KBs & docs
> more easily apply to both cases?) Or is this discrepancy causing some other
> subtle issues?

Correct, cosmetics and consistency in docs.
Comment 6 Jonathan Lebon 2017-07-19 13:46:25 UTC 
Closing as NOTABUG. Docs for cloud images which use "atomicos" are too prevalent already. Changing the default on the installer ISO side is not worth it, given that admins could just as well rename it at install time.
Note You need to log in before you can comment on or make changes to this bug.