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 1454455 - tailoring saved from opened tailoring loses extends flag, and contains all rules and groups explicitly
Summary: tailoring saved from opened tailoring loses extends flag, and contains all ru...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: scap-workbench
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Watson Yuuma Sato
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-22 19:43 UTC by Marek Haicman
Modified: 2019-02-26 17:18 UTC (History)
2 users (show)

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


Attachments (Terms of Use)
first tailoring (4.92 KB, application/xml)
2017-05-22 19:43 UTC, Marek Haicman
no flags Details
re-saved tailoring (24.18 KB, application/xml)
2017-05-22 19:44 UTC, Marek Haicman
no flags Details

Description Marek Haicman 2017-05-22 19:43:09 UTC
Description of problem:
When saving tailoring created from fresh profile, it contains just small set of groups. After opening this tailoring, and saving again, new tailoring file contains much higher number of group states.

Both are effectively the same, but tailoring-xccdf is much bigger file.

Version-Release number of selected component (if applicable):
scap-workbench-1.1.4-4.el7.x86_64

How reproducible:
reliably

Steps to Reproduce:
1. create simple tailoring
2. save as customization only
3. open this customization
4. save it again

Actual results:
both customizations differ


Expected results:
both customizations are same, apart from timestamps

Additional info:

Comment 2 Marek Haicman 2017-05-22 19:43:41 UTC
Created attachment 1281186 [details]
first tailoring

Comment 3 Marek Haicman 2017-05-22 19:44:10 UTC
Created attachment 1281187 [details]
re-saved tailoring

Comment 4 Marek Haicman 2017-09-07 11:54:09 UTC
Please note that description does not mention rules and values, but all of that is added to the re-saved tailoring. It also loses extends attribute of the profile.

Comment 5 Watson Yuuma Sato 2018-11-30 12:42:17 UTC
Goal of the tailoring file is to be like a diff from the tailored profile, i.e. containing only the changes.

We should strive for idem-potency of the tailoring file, it should not change if no changes were made.

Comment 6 Marek Haicman 2019-02-26 17:18:48 UTC
This issue was not selected to be included in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small number of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise, we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.


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