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.
Description of problem:
We need to mention about running of a command for migration of compliance reports from sat6.1 to sat6.2.
a) After sat6.1 to sat6.2 upgrade is completed on a setup with oscap capsule feature already running, we would need this command to migrate the older compliance reports from sat6.1 to sat6.2.
b) Run this command, foreman-rake foreman_openscap:migrate[1]
to migrate compliance reports which had been created during sat6.1 to be visible after upgrade to sat6.2
Also some explanation about the above command mentioned in b)
-----------XXX as per shlomizadok XXX-----------------
One note regarding the capsules in migration:
In satellite 6.1 we supported only ONE capsule. In sat 6.2 we support multiple capsules serving openscap feature.
The migration is moving old XML files which are saved on the satellite DB and save them to the selected capsule (<proxy_id>) file system.
Because in Satellite 6.1 we had only one capsule with openscap feature, the migration is moving all of the old reports to the selected capsule.
New reports are saved in the selected openscap_proxy (could be more than one).
-------------------XXXXXX------------------------------
c) Also for the "View full report" and "Download XML in bzip" to be possible, we need to assign "oscap proxy" to the host.
So for that to be done for multiple hosts, I did the following:
i) Assign the "oscap proxy" to host_group
ii) And make sure all the hosts are setup with a "oscap proxy", even for the older hosts and new hosts that would be created.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Document URL:
Section Number and Name:
Describe the issue:
Suggestions for improvement:
Additional information:
Small correction:
1) For the "View full report" and "Download XML in bzip" to be possible, we need to assign "oscap proxy" to the host. So for that to be done for multiple hosts, I did the following:
a) Assign the "oscap-proxy" to host_group.
b) And make sure all the hosts are setup with a "oscap proxy", even for the older hosts and new hosts that would be created.
c) One way which I tried to do is to search for hosts via "content_source" and "os_major" , and unassign and reassign the host-group for the hosts so that the oscap-proxy is set for all the hosts in one go.
2) Ran this below command, for migration of reports from sat6.1 to Sat6.2 "foreman-rake foreman_openscap:migrate[1]"
Both steps 1) and 2) are required and are mandatory, without which we cannot see the reports after the upgrade from sat61 to sat62.
Looking at current releases, the steps mentioned are not required.
The upgrade process is to be done by satellite-maintain and should take care of all scap related checks