scripts/tests/rollingupgrade: explicitly set debug port for old

satellite api during rolling upgrade test

The old api is using the same config file as the new satellite in the
rolling upgrade test, so we need to set it to something different so
that there is no conflict when we spin up a new storj-sim instance while
the old api is running concurrently.

Change-Id: Ia4ec2db4953f36f43275495710992831ad3916a2
This commit is contained in:
Moby von Briesen 2020-01-29 18:29:01 -05:00
parent d10d6fd153
commit 8c19855871

View File

@ -252,7 +252,7 @@ setup_stage "${test_dir}" "${stage2_sat_version}" "${stage2_storagenode_versions
echo -e "\nRunning stage 2." echo -e "\nRunning stage 2."
# Starting old satellite api in the background # Starting old satellite api in the background
old_api_cmd="${test_dir}/local-network/satellite/0/old_satellite run api --config-dir ${test_dir}/local-network/satellite/0/ --server.address 127.0.0.1:30000 --server.private-address 127.0.0.1:30001 --console.address 127.0.0.1:30002 --marketing.address 127.0.0.1:30003" old_api_cmd="${test_dir}/local-network/satellite/0/old_satellite run api --config-dir ${test_dir}/local-network/satellite/0/ --debug.addr 127.0.0.1:30009 --server.address 127.0.0.1:30000 --server.private-address 127.0.0.1:30001 --console.address 127.0.0.1:30002 --marketing.address 127.0.0.1:30003"
nohup $old_api_cmd & nohup $old_api_cmd &
# Storing the background process' PID. # Storing the background process' PID.
old_api_pid=$! old_api_pid=$!