UTAH

ubiquity messages seem to have changed

Bug #1173242 reported by Andy Doan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
UTAH
New
High
Andy Doan

Bug Description

We are seeing a job fail:

 http://10.97.0.1:8080/job/ps-generic-autopilot-release-testing/178/

Its because we aren't seeing the "install started" message we expect:

 ".*ubiquity\\[\\d+\\]: Ubiquity \\d"

Other jobs don't seem to be failing so we need to figure out what's going on.

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

for now to get the broken jobs working, I'm going to create a temporary file on magners:

 /etc/utah/conf.d/bug1173242

that includes a new pattern:

  ".*ubiquity\\[\\d+\\]: ."

for install started. Once that's in place we'll need to hunt down whether or not ubiquity has changed. If it has, we should change the pattern in config.py and then eventually delete the conf.d entry.

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

A temporary fix has been released as described in comment #1. I'm going to do a real investigation now.

Revision history for this message
Javier Collado (javier.collado) wrote :

@Dmitrijs

Do you know if there is some way to verify the patterns used in the
configuration against some documentation and/or piece of code that is
available? Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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