Bug 2037397

Document URL:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/release_notes/index

Section Number and Name: 

Describe the issue: 

Recently one of our big customer observed some issues while updated satellite to 6.10 and they experienced that it could have been avoided if they can have a consolidated view of list of important changes somewhere in release notes.

- Customer using satellite as image registry for container images when deploying RHOSP and till version sat 6.9 they were using domain.abc.net:5000 as a registry URL.
But, after the update to sat 6.10 the image pull failed and later it was found that Satellite 6.10 the port has changed and the port 5000 is no longer required as per the documents:

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/content_management_guide/managing_container_images#using_container_registries

- Customer also observed another issue with sat6.10 when pulp api command has to be update to v3 instead of v2.

Suggestions for improvement:

- These are important updates and information that can cause issues if not followed properly. 
though, we have captured them somewhere within the docs but those are good when someone is deploying a new satellite server and not when someone is updating satellite form 6.9 to 6.10.

So, some explicit mentioning of these kind of important changes from older to newer version of satellite should be either captured in  release notes or any other doc to gives a clear and explicit view to customer so that upfront precautions can be taken instead of observing a failed deployment and then looking for it.