Bug 2096367 - Need to remove "4.6. Upgrading the MongoDB Storage Engine" section from satellite upgrade guide [NEEDINFO]
Summary: Need to remove "4.6. Upgrading the MongoDB Storage Engine" section from satel...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: 6.9.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: Marie Hornickova
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-13 16:05 UTC by Ashish Humbe
Modified: 2023-07-26 13:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-26 13:05:00 UTC
Target Upstream Version:
Embargoed:
mdolezel: needinfo? (bangelic)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-15447 0 None None None 2023-07-22 00:29:24 UTC
Red Hat Issue Tracker SATDOC-943 0 None None None 2022-06-13 16:19:36 UTC

Description Ashish Humbe 2022-06-13 16:05:46 UTC
Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/html-single/upgrading_and_updating_red_hat_satellite/index#upgrading_the_mongodb_storage_engine

Section Number and Name: 4.6. Upgrading the MongoDB Storage Engine

Describe the issue: As per the confirmation with Eric, this step is not required on Satellite 6.9 as from Satellite 6.10 we dropped MongoDB support. 

Suggestions for improvement: We need to remove "4.6. Upgrading the MongoDB Storage Engine" section from the upgrade guide. 

Additional information:

Comment 3 Brad Buckingham 2023-07-21 21:06:39 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.


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