Bug 2035287 - The online backup attempt still shows a warning about mongodb when executed in Satellite 6.10
Summary: The online backup attempt still shows a warning about mongodb when executed i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.10.1
Hardware: All
OS: All
unspecified
medium
Target Milestone: 6.12.0
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-23 13:23 UTC by Sayan Das
Modified: 2022-11-28 10:15 UTC (History)
6 users (show)

Fixed In Version: rubygem-foreman_maintain-1.1.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-16 13:33:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35195 0 Normal Closed The database backup dumps refer to mongodb 2022-07-28 13:00:04 UTC
Red Hat Issue Tracker SAT-13532 0 None None None 2022-10-21 15:34:07 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:33:17 UTC

Description Sayan Das 2021-12-23 13:23:34 UTC
Description of problem:

While the foreman-maintain or satellite-maintain tools is not tied to any version of Satellite specifically, We have made a major change in 6.10 i.e. now there is no mongo.

So from that point of view, having a WARNING message during backup that shows a precaution about both MongoDB and Postgresql DB, could lead to certain confusion for the end-user.


Version-Release number of selected component (if applicable):

Satellite 6.10
rubygem-foreman_maintain-0.8.21-1.el7sa

How reproducible:
Always

Steps to Reproduce:

1. Install Satellite 6.10

2. Try initialing an online backup 

   # mkdir /var/backup; chmod 777 /var/backup

   # satellite-maintain backup online /var/backup



Actual results:

satellite-maintain backup online -s /var/backup
Starting backup: 2021-12-23 18:03:12 +0530
Running preparation steps required to run the next scenarios
================================================================================
Make sure Foreman DB is up:
/ Checking connection to the Foreman DB                               [OK]      
--------------------------------------------------------------------------------
Make sure Candlepin DB is up:
\ Checking connection to the Candlepin DB                             [OK]      
--------------------------------------------------------------------------------
Make sure Pulpcore DB is up:
/ Checking connection to the Pulpcore DB                              [OK]      
--------------------------------------------------------------------------------
 
 
Running Backup
================================================================================
Data consistency warning:
*** WARNING: The online backup is intended for making a copy of the data
*** for debugging purposes only. The backup routine can not ensure 100% consistency while the
*** backup is taking place as there is a chance there may be data mismatch between
*** Mongo and Postgres databases while the services are live. If you wish to utilize the online backup
*** for production use you need to ensure that there are no modifications occurring during
*** your backup run.
 
Do you want to proceed?, [y(yes), q(quit)] q
                                                                      [ABORTED]
--------------------------------------------------------------------------------
Scenario [Backup] failed.


Expected results:

The WARINING needs to be modified in a way that, We are making the customer aware of MongoDB for pulp2 or <= Satellite 6.9 only or else, It should clearly convey that Postgres is the only database of concern here.


Additional info:

NA

Comment 1 Bryan Kearney 2022-07-12 16:04:19 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35195 has been resolved.

Comment 7 errata-xmlrpc 2022-11-16 13:33:03 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 (Important: Satellite 6.12 Release), 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-2022:8506


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