Upgrade 4.15.07 to 4.16.01 - fails on Message Processor (HTTP 401)

dbannikov
Participant I

I'm trying to upgrade from 4.15.07 to 4.16.01 using apigee-migrate tool:

sudo  /opt/apigee/apigee-migrate/bin/migrate.sh -c all -f /opt/apigee/migrate.properties

It upgrades all components except Message Processor.

This is what I get:

Finished Apigee Enterprise management-server upgrade
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Service upgrade: Apigee Enterprise message-processor
Error: Call: http://<EXTERNAL_IP>:8080/v1/o/ returned: 401
Error: migrate.sh: python exited with unexpected status 1

My migrate.properties file includes Admin credentials that work when I do curl to the same IP and port, for example:

curl -u '<sysAdminEmail>:<sysAdminPwd>' http://<EXTERNAL_IP>:8080/v1/servers

Here is my migrate.properties file:

IP1=<EXTERNAL_IP>

# Edge sys admin credentials. 
ADMIN_EMAIL="<sysAdminEmail>" # Read by default from existing installation.
APIGEE_ADMINPW="<sysAdminPwd>" # If omitted, you are prompted for it.

OLD_APIGEE_ROOT=/apps # Edge .07 installation directory 
OLD_DATA_ROOT=/apps # Edge .07 data directory 

# Management Server IP or DNS name. 
MSIP="$IP1" # Read by default from existing installation. 

# Set CASS_HOSTS to the same values you did when installing Edge. 
# IP or DNS names of the Cassandra hosts separated by spaces. 
CASS_HOSTS="$IP1:1,1" 

# If you have SSL enabled on the Edge UI, specify the keystore password. 
# KEY_PASS="keystorePassword" 

# If you installed Monetization, the Monetization 
# Postgres username and password. 
# MO_PG_USER="postgre" # Default is postgre 
# MO_PG_PASSWD="postgrePword"
0 5 259
5 REPLIES 5

in your response file; is the sysdamin id or pw in " " ?

Yes, both are in " "

Tried to remove the double quotes - same error

did you try not including the PW in the properties file ? put only the sysadmin email address with no quotes and leave the pw field out and please let me know if you get prompted and still 401

Not applicable

Make sure IP1 is the Private IP for the instance. If you are doing this on a VM or IaaS provider (GPC, AWS, etc), you need to use the Private IPs in Edge config.