Public bug reported:
The auth tests used a stub to alter `nova.RequestContext` to become
`FakeRequestContext`. The problem with this is that `FakeRequestContext`
inherits from `nova.RequestContext` which has the effect of making
`FakeRequestContext` point to itself for it's parent class.
This
lines,
meaning that the patch algorithm has less of chance of becoming
confused and misapplying the patch.
** Affects: nova
Importance: Undecided
Assignee: Rick Harris (rconradharris)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) = Rick Harris
and happen to be running the
test_api tests after test_inject.
Anyway, the solution is to add the appropriate `tearDown` methods which
restore the state of the modules to their pre-test condition.
** Affects: nova
Importance: Undecided
Assignee: Rick Harris (rconradharris
`arch.i686` so the test behaves consistently across platforms.
** Affects: nova
Importance: Undecided
Assignee: Rick Harris (rconradharris)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) = Rick Harris (rconradharris)
** Changed in: nova
Status: New
Public bug reported:
The current min version of testtools (0.3.4) doesn't have the `message`
parameter in `assertIn`, so we need to bump up to at least 0.3.6.
** Affects: nova
Importance: Undecided
Assignee: Rick Harris (rconradharris)
Status: In Progress
--
You received
pipe
If we detect this, we should abort the retry loop immediately, and
switch to the unclean shutdown (_destroy_instance).
** Affects: nova
Importance: Undecided
Assignee: Rick Harris (rconradharris)
Status: In Progress
--
You received this bug notification because you
Public bug reported:
Seeing this at the gate:
2014-07-18 21:01:58.253 | ==
2014-07-18 21:01:58.254 | Failed 1 tests - output below:
2014-07-18 21:01:58.254 | ==
2014-07-18 21:01:58.254 |
2014-07-18 21:01:58.254 |
, we may want to consider a writable `/proc/sys/net` (we just
need to verify that this can be done securely).
** Affects: nova
Importance: Undecided
Assignee: Rick Harris (rconradharris)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) = Rick Harris
into the root filesystem of the
guest at spawn time.
** Affects: nova
Importance: Undecided
Assignee: Rick Harris (rconradharris)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) = Rick Harris (rconradharris)
** Changed in: nova
Status: New = In Progress
Importance: Undecided
Assignee: Rick Harris (rconradharris)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) = Rick Harris (rconradharris)
** Changed in: nova
Status: New = In Progress
--
You received this bug notification because you are a member of Yahoo
it, so we just need to pass that
`image_meta` into `_get_guest_xml` and it will work.
** Affects: nova
Importance: Undecided
Assignee: Rick Harris (rconradharris)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) = Rick Harris (rconradharris)
** Changed
Public bug reported:
If an error occurs creating a Libvirt+LXC domain, the code can leave the
guest FS mounted to host preventing the `lvremove` of a delete from
working.
The core problem here is that any code between `setup_container` and
`teardown_container` needs be within a `try/finally`
Public bug reported:
We have some strings in fakelibvirt related to exceptions that need
internationalization.
** Affects: nova
Importance: Undecided
Assignee: Rick Harris (rconradharris)
Status: New
--
You received this bug notification because you are a member of Yahoo
these exceptions
explicitly.
Reference:
https://wiki.openstack.org/wiki/LoggingStandards#Log_Translation
** Affects: nova
Importance: Undecided
Assignee: Rick Harris (rconradharris)
Status: New
** Changed in: nova
Assignee: (unassigned) = Rick Harris (rconradharris)
--
You
Hold on, this might be a dupe, and possibly already fixed...
** Changed in: nova
Status: New = Invalid
--
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/1312372
99% of the time that's what we want).
** Affects: neutron
Importance: Undecided
Assignee: Rick Harris (rconradharris)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) = Rick Harris (rconradharris)
** Changed in: neutron
Status: New = In Progress
a warning when we detect
this case.
** Affects: nova
Importance: Undecided
Assignee: Rick Harris (rconradharris)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) = Rick Harris (rconradharris)
** Changed in: nova
Status: New = In Progress
--
You
.
The solution is to catch the InstanceInfoCacheNotFound exception (like
we do with other NotFound exceptions around this code), and continue on.
** Affects: nova
Importance: Undecided
Assignee: Rick Harris (rconradharris)
Status: In Progress
** Changed in: nova
Assignee
Public bug reported:
If you're trying to delete an instance which is out-of-sync such that
it's missing a InstanceInfoCache entry, you'll will receive a traceback:
http://paste.openstack.org/show/60685/
Delete in this case should be allowed so that you can cleanup these
'broken' instances.
The
Dup'd https://bugs.launchpad.net/nova/+bug/1266919
** Changed in: nova
Status: New = Invalid
--
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/1266916
Title:
Not a lot of traction for this going in trunk:
https://review.openstack.org/#/c/36293/
Leaving this out is probably the best course at this point.
** Changed in: nova
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
21 matches
Mail list logo
