Migration issue from 4.15.07 to 4.16.01

Google Cloud Apigee
1

Hi,

Was trying migration from 4.15.07 to 4.16.01.

It is on a 5 node cluster.

We have about 500 orgs.

Following was successfull on nodes 4, 5, 1:

/opt/apigee/apigee-migrate/bin/migrate.sh -c edge -f configFile

When I execute the following

Migrate Message Processors on machines 2 and 3:

/opt/apigee/apigee-migrate/bin/migrate.sh -c mp -f configFile

it is failing as

Error: Call: http://10.x.x.x:8080/v1/o/prod/e/prod/virtualhosts returned: 404

Error: migrate.sh: python exited with unexpected status 1

Also curl displays error as follows;

curl -u suraj.pai.airody@sap.com:xxxxx “http://10.x.x.x.:8080/v1/o/prod/e/prod/virtualhosts”

{

“code” : “organizations.OrganizationDoesNotExist”,

“message” : “Organization : prod does not exist”,

“contexts” :

Please help as we are stuck with the upgrade in this inconsistent state.

BR, Suraj

2

Hi there!

You should remove the orphan org entries from zk if it is not present in ldap. You can use the ZK tree utility to get the zk data dump and then run ‘rmr /organizations/<org_name>’. Hope this helps.

Thanks,

Archendra

3

Thanks @archendra for the quick reply.

But again the python script validation results in the following warnings;

Is it mandatory that during migration that VH needs to be resolved? WHY?

Is there any way to by pass this check, or is it mandatory?

The list is huge. Plus the delay.

Error: There are some virtual hosts with conflicting aliases. Please resolve this before you continue with the migration Error: There are some virtual hosts with no alias. Please resolve this before you continue with the migration { “no_alias”: [ “/o/exp/e/prod/virtualhosts/default”, “/o/sangam/e/test/virtualhosts/default”, “/o/test/e/prod/virtualhosts/default” ], { “count”: 4, “alias”: “sef.mo.sap.corp”, “virtualhosts”: [ “/o/xf80820ff/e/test/virtualhosts/default”, “/o/x453c9177/e/test/virtualhosts/default”, “/o/x8f0f1069/e/test/virtualhosts/default”, “/o/xefc8998c/e/test/virtualhosts/default” ], “port”: “9034” }, { “count”: 7, “alias”: “apim1.mo.sap.corp”, “virtualhosts”: [ “/o/x72e9503f/e/test/virtualhosts/default”, “/o/x185e1d09/e/test/virtualhosts/default”, “/o/xfb4d7cef/e/test/virtualhosts/default”, “/o/x3e6e4e00/e/test/virtualhosts/default”, “/o/x6529e94c/e/test/virtualhosts/default”, “/o/x95517d38/e/test/virtualhosts/default”, “/o/x50724fd7/e/test/virtualhosts/default” ], “port”: “9034” }, { “count”: 2, “alias”: “aaaa.mo.sap.corp”, “virtualhosts”: [ “/o/x5b4a642f/e/trial/virtualhosts/default”, “/o/x4c8add5c/e/trial/virtualhosts/default” ], “port”: “9001” } ] } { “count”: 2, “alias”: “test.mo.sap.corp”, “virtualhosts”: [ “/o/x2c4d54b9/e/test/virtualhosts/default”, “/o/x4d48b76b/e/test/virtualhosts/default” ], “port”: “9034” },

Error: migrate.sh: python exited with unexpected status 1

What are the best practices to avoid this situation in future?

BR, Suraj