Description of problem:

takumar@redhat.com  has brought up some interesting points about disconnected deployment and upgrades. 

Namely: 

• can a customer follow the instruction for disconnected install of RHODS 1.28 when RHODS 1.29 has already been released. Hopefully the answer is yes.
• can a customer who has fallen behind on upgrades actually catch up, in a disconnected environment. i.e. they are at 1.28, but the current version is 1.32. Are they actually able to upgrade to 1.29, 1.30, 1.31, and finally 1.32. The answer should also be yes. 

Based on what I read in the doc, I don't see anything that is RHODS-version specific. Only some OpenShift-version-specific content. 

This is a problem, for example, because I have a customer currently working on deploying RHODS 1.28.1. 
If there mirroring script starts to behave differently the day we release 1.29, this will be a problem. 

I don't know for a fact whether the above would work, but since we are not certain, it should be investigated and tested. 

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

1. <steps>

Actual results:

Expected results:

Reproducibility (Always/Intermittent/Only Once):

Build Details:

Workaround:

Additional info: