linaro-release team mailing list archive

[Paul Larson <paul.larson@xxxxxxxxxxxxx>]

Public bug reported:

Here's one where the dispatcher had an error when trying to deploy the
testboot filesystem: http://validation.linaro.org/lava-
server/scheduler/job/1367

There were some strange errors, maybe corrupt master image? maybe
strange network problem? not sure.  But the tar command failed and the
dispatcher continued happily to the next step.  We should try to detect
things like this better.  I'll open one for each of these that I find,
but they are all related, but will require a slightly different fix
based on the new rc detection branch.

** Affects: lava-dispatcher
     Importance: Medium
     Assignee: Spring Zhang (qzhang)
         Status: New

** Changed in: lava-dispatcher
     Assignee: (unassigned) => Spring Zhang (qzhang)

** Changed in: lava-dispatcher
    Milestone: None => 2011.09

** Changed in: lava-dispatcher
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Linaro
Validation Team, which is the registrant for LAVA Dispatcher.
https://bugs.launchpad.net/bugs/844301

Title:
  dispatcher didn't detect deployment failure

Status in LAVA Dispatcher:
  New

Bug description:
  Here's one where the dispatcher had an error when trying to deploy the
  testboot filesystem: http://validation.linaro.org/lava-
  server/scheduler/job/1367

  There were some strange errors, maybe corrupt master image? maybe
  strange network problem? not sure.  But the tar command failed and the
  dispatcher continued happily to the next step.  We should try to
  detect things like this better.  I'll open one for each of these that
  I find, but they are all related, but will require a slightly
  different fix based on the new rc detection branch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lava-dispatcher/+bug/844301/+subscriptions