UTAH

Upgrade tests hang after release upgrade and reboot

Bug #1247883 reported by Para Siva
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
UTAH
Fix Released
High
Andy Doan

Bug Description

Starting from 29th Oct. the upgrade tests are hanging with /usr/share/utah/client/utah-done.py returning code 4 all the time until the job times out.

Looking at the state.yaml file in, it's noticed that the status values do not change after reboot (after the release upgrades). apt-get update , dist-upgrade and reboot work fine but after that after the end of release-upgrade and the resulting reboot, the state file doesn't get modified. This makes utah-done.py to return code 4 all the time until the job times out.
The resulting state.yaml file that's present in the machine is attached.

This issue only popped up after 29th Oct the tests were running to completion before that.

The job config:
http://10.98.0.1:8080/job/upgrade-saucy-amd64-desktop/?

http://10.98.0.1:8080/job/upgrade-saucy-amd64-desktop/17/console is one of such jobs

http://10.98.0.1:8080/job/upgrade-saucy-amd64-desktop/8/console
http://10.98.0.1:8080/job/upgrade-saucy-i386-desktop/10/consoleText
are a few more.

Related branches

lp://qastaging/~doanac/utah/jsonschema-for-trusty
Paul Larson: Approve
Para Siva: Pending requested
Diff: 96 lines (+54/-32)
1 file modified
utah/client/common.py (+54/-32)
Revision history for this message
Para Siva (psivaa) wrote :
Revision history for this message
Andy Doan (doanac) wrote :

psiva - was looking that the VM you gave me access to. Something odd is going on. Its running an old version of the utah-client:

  Version: 0.14.1ubuntu1~precise1

We are on 0.15 series now. I'm wondering if this is related?

Revision history for this message
Andy Doan (doanac) wrote : Re: [Bug 1247883] Re: Upgrade tests hang after release upgrade and reboot

Not sure the issue. I ran this command at home:

  bzr branch lp:utah
  cd utah
  sudo PYTHONPATH=./ ./client.py -d -r <your master.run> -s <your state>

things work. I run this on your trusty VM and it fails. So it seems like
its a yaml change. However, the packages look the same to me.

Revision history for this message
Para Siva (psivaa) wrote :

So aldebaran still has 0.14.1ubuntu1~precise1 and I was under the impression that it's with this older version for a reason. But i dont know why. All the desktop and server smoke tests are running there and there is no problem with them at the moment. So I am at the moment a little reluctant to upgrade the utah version there before doing some trian runs.

Revision history for this message
Andy Doan (doanac) wrote :

On 11/06/2013 07:04 AM, Parameswaran Sivatharman wrote:
> So aldebaran still has 0.14.1ubuntu1~precise1 and I was under the
> impression that it's with this older version for a reason. But i dont
> know why. All the desktop and server smoke tests are running there and
> there is no problem with them at the moment. So I am at the moment a
> little reluctant to upgrade the utah version there before doing some
> trian runs.

The version shouldn't matter. At least from my notes in this bug. I
tried running lp:utah and still see it fail on that host (just can't
make it fail at home).

Revision history for this message
Andy Doan (doanac) wrote :

python-jsonschema is at a new version in trusty that's breaking our code. here's a simple way to show the failure:

http://paste.ubuntu.com/6378431/

Andy Doan (doanac)
Changed in utah:
assignee: nobody → Andy Doan (doanac)
importance: Undecided → High
status: New → In Progress
Andy Doan (doanac)
Changed in utah:
status: In Progress → Fix Committed
Andy Doan (doanac)
Changed in utah:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

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