yahoo-eng-team team mailing list archive

[iain MacDonnell <1796192@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When online_data_migrations raise exceptions, nova/cinder-manage catches
the exception, prints a fairly useless "something didn't work" message,
and moves on. Two issues:

1) The user(/admin) has no way to see what actually failed (exception is not logged)
2) The command returns exit status 0, as if all possible migrations have been completed successfully - this can cause failures to get missed, especially if automated

** Affects: cinder
     Importance: Undecided
         Status: New

** Affects: nova
     Importance: Undecided
     Assignee: iain MacDonnell (imacdonn)
         Status: In Progress

** Also affects: cinder
   Importance: Undecided
       Status: New

** Description changed:

  When online_data_migrations raise exceptions, nova/cinder-manage catches
  the exception, prints a fairly useless "something didn't work" message,
  and moves on. Two issues:
  
  1) The user(/admin) has no way to see what actually failed (exception is not logged)
- 2) The command returns exit status 0, as if all possible migrations have been completed successfully
+ 2) The command returns exit status 0, as if all possible migrations have been completed successfully - this can cause failures to get missed, especially if automated

** Changed in: nova
     Assignee: (unassigned) => iain MacDonnell (imacdonn)

** Changed in: nova
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1796192

Title:
  online_data_migrations exceptions quietly masked

Status in Cinder:
  New
Status in OpenStack Compute (nova):
  In Progress

Bug description:
  When online_data_migrations raise exceptions, nova/cinder-manage
  catches the exception, prints a fairly useless "something didn't work"
  message, and moves on. Two issues:

  1) The user(/admin) has no way to see what actually failed (exception is not logged)
  2) The command returns exit status 0, as if all possible migrations have been completed successfully - this can cause failures to get missed, especially if automated

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1796192/+subscriptions