I wouldn't say that we won't ever fix this, since I've wondered why we
don't reschedule on volume failures like we do with networking failures,
but it's not a high priority.
** Tags removed: liberty-backport-potential
** No longer affects: nova/liberty
** Changed in: nova
Status: Won't
Liberty has hit the EOL, so this one is invalid. Mitaka was removed from
affected releases, so I am closing this one.
** Changed in: nova
Status: In Progress => Won't Fix
** Changed in: nova/liberty
Status: New => Won't Fix
--
You received this bug notification because you are a
** Also affects: mitaka (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: mitaka (Ubuntu)
--
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/1488111
** Tags added: liberty-backport-potential
** Also affects: nova/liberty
Importance: Undecided
Status: New
--
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/1488111
4 matches
Mail list logo
