This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2017884 - [RFE] New Ansible module or new RHEL system role to change/remove/add grub arguments
Summary: [RFE] New Ansible module or new RHEL system role to change/remove/add grub ar...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rhel-system-roles
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: CS System Management SST QE
URL:
Whiteboard: role:bootloader
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-27 16:01 UTC by Steffen Scheib
Modified: 2023-10-09 12:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-12 10:02:57 UTC
Type: Story
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-3241 0 None Migrated None 2023-09-12 09:59:12 UTC
Red Hat Issue Tracker RHELPLAN-111479 0 None None None 2022-02-08 14:53:20 UTC

Description Steffen Scheib 2021-10-27 16:01:44 UTC
1. Proposed title of this feature request
New Ansible module or new RHEL system role to change/remove/add grub arguments

2. What is the nature and description of the request?
Currently there is no Ansible module to update/remove/add grub arguments.
Grub arguments on RHEL 8 should be updated using grubby, while for RHEL 7 the recommended approach is to update the variable GRUB_CMDLINE_LINUX in the file /etc/default/grub.
A new Ansible module which takes care of both scenarios in a sane and idempotent way is desired.

3. Why does the customer need this?
The customer is implementing automated hardening for their government customers, who require compliance in accordance to several "Security Technical Implementation Guides" (STIG) published from the Defense Information Systems Agency (DISA), in short DISA STIGs.
Some of these DISA STIGs require updating/removing/adding grub arguments. Currently that is not possible in a sane and idempotent way, only by utilizing the lineinfile in combination with the shell module.
In order to run scheduled scans with Ansible in accordance to the DISA STIGs the Ansible modules need to be idempotent to avoid a changed status, which cannot be replicated using the shell module in a sane way.

4. How would the customer like to achieve this? (List the functional requirements here)
Customer wants to update/add/remove grub arguments in a sane and idempodent way

5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Run their usual workflows utilizing the new module

6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No

7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?
As usual, ASAP

8. Is the sales team involved in this request and do they have any additional input?
No

9. List any affected packages or components.
Ansible

10. Would the customer be able to assist in testing this functionality if implemented?
Yes

Comment 16 RHEL Program Management 2023-09-12 09:57:54 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 17 RHEL Program Management 2023-09-12 10:02:57 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


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