Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1505287 - scap content/policy/tailoring file info don't show locations and organizations
Summary: scap content/policy/tailoring file info don't show locations and organizations
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Ondřej Pražák
QA Contact: Nikhil Kathole
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-23 08:28 UTC by Nikhil Kathole
Modified: 2019-08-12 14:02 UTC (History)
6 users (show)

Fixed In Version: foreman_openscap 0.7.11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:46:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 21509 0 None None None 2017-10-30 15:14:06 UTC

Description Nikhil Kathole 2017-10-23 08:28:02 UTC 
Description of problem: We created tailoring file/policy/scap content including location and organization parameter and tried to see info using hammer CLI of created tailoring file/policy/scap content. But location and organization info found blank.


Version-Release number of selected component (if applicable): sat 6.3 snap 21


How reproducible: always


Steps to Reproduce:

1. hammer> tailoring-file create --name rhel_1 --scap-file ssg-rhel7-ds-tailoring1.xml --original-filename rhel7_tailoring_file --location-ids 2 --organization-ids 1
Tailoring file successfully created

2. hammer> tailoring-file list
---|-----------------
ID | NAME
---|-----------------
1  | tailoring1_rhel7
2  | rhel_1
---|-----------------

3. hammer> tailoring-file info --id 2
Id:                      2
Name:                    rhel_1
Created at:              2017-10-23 05:38:28 UTC
Original filename:       rhel7_tailoring_file
Tailoring file profiles:
 1) Id:         31
    Profile id: xccdf_org.ssgproject.content_profile_common_customized_tailoring1
    Title:      Common Profile for General-Purpose Systems [CUSTOMIZED1]
Locations:

Organizations:

Same behaviour for policy and scap content.

Actual results:
Locations and organizations parameters was blank.

Expected results:
Locations and organizations info should display.

Additional info:
Comment 4 Ondřej Pražák 2017-10-30 15:14:05 UTC 
Created redmine issue http://projects.theforeman.org/issues/21509 from this bug
Comment 5 Satellite Program 2017-10-30 16:25:07 UTC 
Upstream bug assigned to oprazak
Comment 6 Satellite Program 2017-10-30 16:25:10 UTC 
Upstream bug assigned to oprazak
Comment 7 Satellite Program 2017-11-06 17:24:55 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21509 has been resolved.
Comment 8 Nikhil Kathole 2017-12-07 08:11:45 UTC 
VERIFIED

Version Tested:
Satellite-6.3 Snap 27

steps:
1. hammer> tailoring-file create --name rhel_2 --scap-file /tmp/ssg-rhel7-ds-tailoring2.xml --original-filename rhel7_tailoring_file --location-ids 2 --organization-ids 1
Tailoring file successfully created

2. hammer> tailoring-file info --id 8
Id:                      8
Name:                    rhel_2
Created at:              2017-12-07 08:05:02 UTC
Original filename:       rhel7_tailoring_file
Tailoring file profiles:
 1) Id:         180
    Profile id: xccdf_org.ssgproject.content_profile_common_customized_tailoring1
    Title:      Common Profile for General-Purpose Systems [CUSTOMIZED1]
 2) Id:         181
    Profile id: xccdf_org.ssgproject.content_profile_common_customized_tailoring2
    Title:      Common Profile for General-Purpose Systems [CUSTOMIZED2]
Locations:
    Default Location
Organizations:
    Default Organization

3. hammer> policy info --id 1
Id:                        1
Name:                      RHEL 7 policy
Created at:                2017-12-02 07:18:50 UTC
Period:                    weekly
Weekday:                   monday
Day of month:
Cron line:
SCAP content Id:           4
SCAP Content profile Id:   23
Tailoring file Id:         1
Tailoring file profile Id: 30
Locations:
    Default Location
Organizations:
    Default Organization
Hostgroups:
    RHEL 7 Server 64-bit HG

4. hammer> scap-content info --id 2
Id:                    2
Title:                 Red Hat jre default content
Created at:            2017-12-01 20:07:01 UTC
Original filename:     ssg-jre-ds.xml
SCAP content profiles:
 1) Id:         2
    Profile id: xccdf_org.ssgproject.content_profile_stig-java-upstream
    Title:      Java Runtime Environment (JRE) STIG
Locations:
    Default Location
Organizations:
    Default Organization


Found location and organization info displayed for policy/tailoring file/scap-content.
Comment 9 Bryan Kearney 2018-02-21 16:42:26 UTC 
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, 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-2018:0336
Comment 10 Bryan Kearney 2018-02-21 16:46:30 UTC 
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, 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-2018:0336
Note You need to log in before you can comment on or make changes to this bug.