[AURORA-677] test_end_to_end_v2.sh fails on config list

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Cannot Reproduce
• Fix Version/s: 0.8.0
• Assignee: Unassigned
• Reporter: Joshua Cohen
• Created: 29/Aug/14 23:09
• Updated: 04/May/15 14:28
• Resolved: 12/Nov/14 23:14

Description

$ bash src/test/sh/org/apache/aurora/e2e/test_end_to_end_v2.sh
+ . src/test/sh/org/apache/aurora/e2e/test_common.sh
++ exec
+ RETCODE=1
+ export EXAMPLE_DIR=/vagrant/src/test/sh/org/apache/aurora/e2e/http
+ EXAMPLE_DIR=/vagrant/src/test/sh/org/apache/aurora/e2e/http
+ TEST_CLUSTER=devcluster
+ TEST_ROLE=vagrant
+ TEST_ENV=test
+ TEST_JOB=http_example
+ TEST_SCHEDULER_IP=192.168.33.7
+ TEST_ARGS=($TEST_CLUSTER $TEST_ROLE $TEST_ENV $TEST_JOB $TEST_SCHEDULER_IP $EXAMPLE_DIR/http_example.aurora $EXAMPLE_DIR/http_example_updated.aurora)
+ trap collect_result EXIT
+ vagrant up
Bringing machine 'devcluster' up with 'virtualbox' provider...
==> devcluster: VirtualBox VM is already running.
+ test_http_example devcluster vagrant test http_example 192.168.33.7 /vagrant/src/test/sh/org/apache/aurora/e2e/http/http_example.aurora /vagrant/src/test/sh/org/apache/aurora/e2e/http/http_example_updated.aurora
+ local _cluster=devcluster _role=vagrant _env=test _job=http_example _sched_ip=192.168.33.7
+ local _base_config=/vagrant/src/test/sh/org/apache/aurora/e2e/http/http_example.aurora _updated_config=/vagrant/src/test/sh/org/apache/aurora/e2e/http/http_example_updated.aurora
+ jobkey=devcluster/vagrant/test/http_example
++ vagrant ssh -c 'aurora2 config list /vagrant/src/test/sh/org/apache/aurora/e2e/http/http_example.aurora'
Connection to 127.0.0.1 closed.
+ joblist='jobs=[devcluster/vagrant/test/http_example]
'og(info): Command terminated successfully
+ test 'jobs=[devcluster/vagrant/test/http_example]
' = 'jobs=[devcluster/vagrant/test/http_example]'
+ collect_result
+ [[ 1 = 0 ]]
+ echo '!!!'
!!!
+ echo 'FAIL (something returned non-zero)'
FAIL (something returned non-zero)
+ echo ''

+ echo 'This may be a transient failure (as in scheduler failover) or it could be a real issue'
This may be a transient failure (as in scheduler failover) or it could be a real issue
+ echo 'with your code. Either way, this script DNR merging to master. Note you may need to'
with your code. Either way, this script DNR merging to master. Note you may need to
+ echo 'reconcile state manually.'
reconcile state manually.
+ echo '!!!'
!!!
+ vagrant ssh -c 'aurora killall devcluster/vagrant/test/http_example'
WARNING: killall is an aurora clientv1 command which will be deprecated soon
To run this command using clientv2, use 'aurora job killall devcluster/vagrant/test/http_example --max-total-failures=1'
 INFO] Killing tasks for job: devcluster/vagrant/test/http_example
 INFO] Starting new HTTP connection (1): 192.168.33.7
 INFO] Starting new HTTP connection (1): 192.168.33.7
 INFO] Response from scheduler: OK (message: No tasks to kill.)
 INFO] Job url: http://192.168.33.7:8081/scheduler/vagrant/test/http_example
 INFO] Starting new HTTP connection (1): 192.168.33.7
Connection to 127.0.0.1 closed.
+ exit 1

Issue Links

• blocks: AURORA-710 make aurora v2 client the default client