Standalone upgrade takes too long.

Bug #1805120 reported by Sofer Athlan-Guyot
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Invalid
Medium
Sofer Athlan-Guyot

Bug Description

Hi,

You can see $title happening in [1] and [2]

The problem here is that the standalone upgrade run takes a long time to run. This particular case is 2h38 and is currently representative. First it brings us closer to the hard 3h time limit and second it's just very long for a single node upgrade.

In order to cut the time it takes to run the standalone upgrade it would be better to run it only at the end of the upgrade. The the standalone deployment in the N-1 deployment already run it and patch in N branch shouldn't affect it. Removing the first tempest run would decrease the total run time by ~15min.

[1] http://logs.openstack.org/90/614290/2/check/tripleo-ci-centos-7-standalone-upgrade/d721011/job-output.txt.gz#_2018-11-26_07_47_03_071968
[2] http://logs.openstack.org/90/614290/2/check/tripleo-ci-centos-7-standalone-upgrade/d721011/job-output.txt.gz#_2018-11-26_08_57_20_400562

Tags: ci upgrade
Changed in tripleo:
milestone: stein-2 → stein-3
Changed in tripleo:
milestone: stein-3 → train-1
Changed in tripleo:
milestone: train-1 → train-2
Changed in tripleo:
milestone: train-2 → train-3
Changed in tripleo:
milestone: train-3 → ussuri-1
Changed in tripleo:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.