I came here thinking i could close this as I'd seen some green runs for the standalone-upgrade on master. However looking at the top two fails in [1] at time of writing i found [2] and [3] which have the same signature but for different services - so this is likely no keystone specific:
However I am lowering the priority for this. The job is non voting and expected to be volatile which is why master is non voting but stein is voting for standalone-upgrade.
I came here thinking i could close this as I'd seen some green runs for the standalone-upgrade on master. However looking at the top two fails in [1] at time of writing i found [2] and [3] which have the same signature but for different services - so this is likely no keystone specific:
(from [2]): 2019-05-16 00:40:19 | 2019-05-16 00:40:19.727 104318 WARNING tripleoclient. v1.tripleo_ upgrade. Upgrade [-] "CalledProcessE rror: Command '['systemctl', 'stop', u'tripleo_ nova_compute. service' ]' returned non-zero exit status 1",[00m
(from [3]): 2019-05-15 23:53:11 | 2019-05-15 23:53:11.597 95831 WARNING tripleoclient. v1.tripleo_ upgrade. Upgrade [-] "CalledProcessE rror: Command '['systemctl', 'stop', u'tripleo_ cinder_ volume. service' ]' returned non-zero exit status 1",[00m
However I am lowering the priority for this. The job is non voting and expected to be volatile which is why master is non voting but stein is voting for standalone-upgrade.
[1] http:// zuul.openstack. org/builds? job_name= tripleo- ci-centos- 7-standalone- upgrade logs.openstack. org/94/ 659394/ 1/check/ tripleo- ci-centos- 7-standalone- upgrade/ 1db3a41/ logs/undercloud /home/zuul/ standalone_ upgrade. log.txt. gz#_2019- 05-16_00_ 40_19 logs.openstack. org/58/ 658358/ 5/check/ tripleo- ci-centos- 7-standalone- upgrade/ b98b140/ logs/undercloud /home/zuul/ standalone_ upgrade. log.txt. gz
[2] http://
[3] http://