Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1358309 - Need steps for oscap upgrade from sat61 to sat62 [NEEDINFO]
Summary: Need steps for oscap upgrade from sat61 to sat62
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Docs Release Notes
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
high vote
Target Milestone: 6.3.6
Assignee: satellite-doc-list
QA Contact: satellite-doc-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-20 13:36 UTC by Kedar Bidarkar
Modified: 2019-04-09 03:33 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Clone Of:
Environment:
Last Closed:
adahms: needinfo? (kbidarka)


Attachments (Terms of Use)

Description Kedar Bidarkar 2016-07-20 13:36:46 UTC
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:

Comment 1 Kedar Bidarkar 2016-07-22 14:08:07 UTC
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.


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