Rollback from 4.5 to 4.19.01

[x2ddhava]

Hello

We are considering a rollback from 4.5 onprem to our previous 4.19.01 version.

Since our vms are in a zone where there is NO internet access, we have to create bundles for no-internet install using apigee mirror.

We are facing issues trying to create a bundle for 4.19.0.1. We get the following error and then the gz file never gets created

(76/81): edge-ui-4.19.01-0.0.20156.noarch.rpm | 70 MB 00:03
apigee-sap-drupal-devportal-4.19.01-0.0.306.noarch: [Errno 256] No more mirrors to try.
apigee-sap-drupal-devportal-4.19.01-0.0.107.noarch: [Errno 256] No more mirrors to try.
apigee-sap-drupal-devportal-4.19.01-0.0.305.noarch: [Errno 256] No more mirrors to try.
apigee-sap-drupal-devportal-4.19.01-0.0.100.noarch: [Errno 256] No more mirrors to try.
Creating symlinks for release aliases 6->6Server 7->7Server 6->latest (for aws linux)

Any help would be appreciated

Thank you

[#2]

I would suggest creating the tar file in a server where the internet is available. then copy that tar to your apigee nodes and follow the rollback processes.

ref for tar creation: https://docs.apigee.com/private-cloud/v4.19.01/install-edge-apigee-setup-utility

[x2ddhava]

Thank you for prompt response.
Are you suggesting that we ignore the errors as part of the sync process and bundle/package whatever we have into a tar file and install on no-internet access vms?

Because the sync itself has failed, there is no way to know if we have the bundle with everything in it or not.

[#4]

the one failing is related to sap-drupal. This will not have any issue with apigee edge rollaback.

[x2ddhava]

Agreed, but that's what it shows. We don't know what all it doesn't display. So, should we assume we have everything and move on OR not is the question.

Has anyone else seen this error/behavior was the second question.

We just don't want to go all the way with the bundle we got, only to realize later that some functionality isn't working because of missing rpms.

Thots?

[#6]

you can try

/opt/apigee/apigee-service/bin/apigee-service apigee-mirror clean


/opt/apigee/apigee-service/bin/apigee-service apigee-mirror update

And if that doesn't work do a bootstrap fresh installation and try mirroring.

in worst case, you can ask apigee support to share the tar with you.