Bug 1879895 - [RFE] Clear confusion around using backup with --skip-pulp-content
Summary: [RFE] Clear confusion around using backup with --skip-pulp-content
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Maintain
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: Anurag Patel
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-17 10:06 UTC by Sean O'Keeffe
Modified: 2021-04-07 12:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Sean O'Keeffe 2020-09-17 10:06:03 UTC
Description of problem:
Customers want clarity on why we have the option --skip-pulp-content but do not support restore using it. Lets make it clear when you create a backup by printing a message along the lines of:

"WARNING: The integrity of a restored Satellite with missing Pulp content can not be ensured. Restoring Satellite without Pulp content is
unsupported and provided for testing and evaluation purposes only."

Actual results:

forman-maintain backup --skip-pulp-content prints
(no warning message)

Expected results:

forman-maintain backup --skip-pulp-content prints
WARNING: The integrity of a restored Satellite with missing Pulp content can not be ensured. Restoring Satellite without Pulp content is
unsupported and provided for testing and evaluation purposes only.

Comment 1 Mike McCune 2020-09-17 17:05:25 UTC
The restore side will have a similar warning when restoring without Pulp content:

# foreman-maintain restore /var/tmp/sat-backup
...
WARNING: No Pulp Contents archive found. The integrity of a restored Satellite with missing Pulp content can not be ensured. Restoring Satellite without Pulp content is unsupported and provided for testing and evaluation purposes only.
...

but it will not block you from running the restore.


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