Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
This is supoprted with Satellite 6.2 now:
1) Create a product called "Oval Files"
2) Create a repo of type "file" called Red Hat. Make the upstream url be https://www.redhat.com/security/data/oval/. Set the repo to be exposed via http
3) Sync the repo
4) $$PROFIT
At this point you have a local http repo of the oval files. Create a sync plan and it will update at your convenience. This repo can be promoted through environments in the same way as any other content.
This could be applied in two locations:
a) Content Management Guide
b) Host Configuration Guide (Chapter 5. Security Compliance Management)
It could also be something to document in both guides, not just in one guide.
@adahms, did you have a preference for what we should do? I'm happy to take this BZ on.
Hi Dan,
At a glance, this looks like it would be a good candidate for the Content Management Guide, but what do you think?
If needed, we can always link to it from the chapter on security compliance management, and when this content is also converted into AsciiDoc, we can explore having a single-sourced version of the content in both guides then if that would be appropriate.
Happy for you to take this on as well, and we can verify and publish the changes as soon as they're in.
Kind regards,
Andrew
The bugs were included as part of technical review of the full guide. In addition, the guide has been peer reviewed.
Setting the QA contact to adahms and flipping the status to ON_QA.