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 1819010 - Automatic --uname-pattern for Red Hat distributions doesn't appear to work
Summary: Automatic --uname-pattern for Red Hat distributions doesn't appear to work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: boom-boot
Version: 8.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 8.0
Assignee: Bryn M. Reeves
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-30 23:30 UTC by Corey Marthaler
Modified: 2021-09-06 15:19 UTC (History)
4 users (show)

Fixed In Version: boom-boot-1.2-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-29 12:36:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Corey Marthaler 2020-03-30 23:30:14 UTC
Description of problem:
There were no devel results in rebase bug 1771584 so I'm not sure if I'm even using this command's new feature correctly, but according to that report, automatic --uname-pattern for Red Hat distributions should now work instead of the user providing it manually.


[root@hayes-02 ~]# uname -ar
Linux hayes-02.lab.msp.redhat.com 4.18.0-190.el8.x86_64 #1 SMP Wed Mar 18 09:34:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

# this is what I would have now expected to work. 
[root@hayes-02 ~]#  boom profile create --from-host 
Could not determine uname pattern for 'Red Hat Enterprise Linux'

# now I tried to add each required argument one at a time to see if anything was gathered automatically
[root@hayes-02 ~]# boom profile create
profile create requires --name
[root@hayes-02 ~]# boom profile create --name "Red Hat Enterprise Linux"
profile create requires --short-name
[root@hayes-02 ~]# boom profile create --name "Red Hat Enterprise Linux" --short-name rhel
profile create requires --os-version
[root@hayes-02 ~]# boom profile create --name "Red Hat Enterprise Linux" --short-name rhel --from-host
Could not determine uname pattern for 'Red Hat Enterprise Linux'
[root@hayes-02 ~]# boom profile create --name "Red Hat Enterprise Linux" --short-name rhel --os-version 8.2
profile create requires --os-version-id
[root@hayes-02 ~]# boom profile create --name "Red Hat Enterprise Linux" --short-name rhel --os-version 8.2 --os-version-id 8.2
Could not determine uname pattern for 'Red Hat Enterprise Linux'


# in the end, the profile appeared to need to be created the exact same way it did in past releases.
[root@hayes-02 ~]#  boom profile create --from-host --uname-pattern el8
Created profile with os_id 1ba0043:
  OS ID: "1ba00433fd7ba24532ec42c3cdf9f457821e6e02",
  Name: "Red Hat Enterprise Linux", Short name: "rhel",
  Version: "8.2 (Ootpa)", Version ID: "8.2",
  Kernel pattern: "/vmlinuz-%{version}", Initramfs pattern: "/initramfs-%{version}.img",
  Root options (LVM2): "rd.lvm.lv=%{lvm_root_lv}",
  Root options (BTRFS): "rootflags=%{btrfs_subvolume}",
  Options: "root=%{root_device} ro %{root_opts}",
  Title: "%{os_name} %{os_version_id} (%{version})",
  Optional keys: "", UTS release pattern: "el8"



Version-Release number of selected component (if applicable):
boom-boot-1.0-1.el8    BUILT: Fri Nov 29 05:18:30 CST 2019


How reproducible:
Everytime

Comment 1 Corey Marthaler 2020-03-30 23:45:44 UTC
I assume this is what's being discussed in comment: https://bugzilla.redhat.com/show_bug.cgi?id=1771584#c5

Comment 2 Bryn M. Reeves 2020-03-31 13:43:00 UTC
Yes; there were two bugs affecting the automatic uname pattern on RHEL8. I spoke with Marian and I thought that these were going to be included in the final build (they were discovered immediately after the release and we discussed re-issuing the 1.0 release to include them). It looks like those were never picked up for the RHEL8 build:

commit 6e9e11b94d403061cc8edf9baa99efc4bc42d5a0
Author: Bryn M. Reeves <bmr>
Date:   Mon Dec 2 16:10:45 2019 +0000

    boom.command: fix uname heuristic table
    
    RHEL7 and RHEL8 use slightly different strings for the OS name in
    the /etc/os-release file: extend the table of RHEL OS name strings
    accordingly.
    
    Signed-off-by: Bryn M. Reeves <bmr>


commit 073ca72b44109766df8e9e22b8b4937f00296700
Author: Bryn M. Reeves <bmr>
Date:   Thu Nov 28 12:44:21 2019 +0000

    boom.command: replace '.' with '_' in automatic --uname-pattern
    
    Signed-off-by: Bryn M. Reeves <bmr>

Comment 3 Marian Csontos 2020-04-01 09:40:36 UTC
The `boom.command: replace '.' with '_' in automatic --uname-pattern` is included as discussed. I do not remember discussing the other one which was mentioned in the Bug 1771584 which was verified without the patch.

Now the question is, is this Z-stream material?

Risk is low and fix improves user experience significantly. No problem for me.

Comment 5 Bryn M. Reeves 2021-01-29 12:36:00 UTC
This is fixed in boom-1.2.


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