Probably needs to come in as spec as this requires work outside of the
virt driver
** Tags added: vmware
** Summary changed:
- [sr-iov] pci passthrough whitelist doesn't support mult node
+ [vmware] [sr-iov] pci passthrough whitelist doesn't support mult node
** Changed in: nova
Status:
it's fine to keep doing this, but the bug hasn't been updated as to
what's left.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Low => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
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/1656978
Title:
Looks like it was fixed in master?
** 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/1671815
Title:
Can not use custom ne
This sounds like an issue with the documentation, as it's a permissions
error outside of Nova
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whi
The discussion in the patch is that a bigger standardization is required
here.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribe
** Changed in: nova
Status: New => Fix Released
--
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/1675393
Title:
Add lan9118 as valid nic for hw_vif_model proper
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
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/1623809
Title:
KILL (-9) is supposed to exit immediately without doing any work. TERM
(-15) is supposed to work like you proposed. Don't use kill -9 if you
want cleanup.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Status: Opinion => Won't Fix
--
You received this bug notificat
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
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/1681465
Title:
As this is a cells v1 issue, it's in the won't fix category.
** Tags added: cellsv1
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launch
This really should come in as a spec, it's a feature add.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
** Tags added: needs-spec
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is sub
** Changed in: nova
Status: New => Won't Fix
--
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/1682811
Title:
nova boot apis raises 500 error if scheduler_hints
ad
Self over allocating VCPUs is not a good idea. If your machine only has
4 CPUs and you expose that as 5 CPUs to a guest, you'll get
pathologically bad performance as the guest tries to optimize workloads
across those, which are causing cache flushes in the CPUs below.
Definitely in the Won't Fix c
Fixed in docs.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1679703
Title:
Unable to boot instance with VF( direct-port ) because the
Ok, given the docs are fixed, lets put this into Opinion (which is a
closed state) for the actual code changes which don't have concensus.
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscri
I think this is one of those edge cases that the work around you
provided is the right way through. The decorating on images is meant to
be part of the original image build process, and doesn't magically fix
things.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug not
If nova cli allows you to do that, it means the REST API allows you to
do that. Permissions should not be done on the client side as they can
be circumvented with curl.
This looks like it's a permissions issue on the server side where you'd
like a different policy?
** Changed in: nova
Stat
** Changed in: nova
Status: New => Won't Fix
--
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/1677892
Title:
nova scheduler_default_filter ComputeCapabilities filte
Working as design, device_name is since removed from the API.
** Tags added: shelve
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launch
What real world scenario would you expect to expose a situation where
the neutron environment is turned off and nova-compute is restarted?
This seems pretty synthetic, and the fact that it recovers ones the
neutron agent restarts seems like most of the environment is working as
expected.
** Change
This is really a note to self. Moving to Opinion as there are a lot of
mights here. :)
** Tags added: note-to-self
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Comput
The device_name was removed from the API. I think the only place it ever
worked was xenserver.
** 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://bug
If there is a request for a Nova feature here, please bring it in via
the Nova Specs process - https://specs.openstack.org/openstack/nova-
specs/readme.html
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
I think on the Nova side this is pretty much working as designed. If
there is different / better ironic behavior, perhaps it could be brought
up with the Ironic team?
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engine
I think this is the kind of enhancement that would come through the
specs process - https://specs.openstack.org/openstack/nova-
specs/readme.html
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
You received this bug notification beca
I expect this was an issue with a stale installation of dependencies. If
this is still an issue, please reopen
** 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 (no
** Tags added: note-to-self
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchp
Evacuate behavior changes are so dicey at this point that I think
anything like this probably needs a spec to actually think through the
edge conditions.
Please dive in here if you are interested -
https://specs.openstack.org/openstack/nova-specs/readme.html
** Tags added: evacuate
** Changed in
Managing the AppArmor config is currently beyond scope for Nova, thus
marking this as Opinion. It would be good if those rules from the
distros were able to do this better.
If you wanted to put that in scope for Nova, that would require a Nova
spec - https://specs.openstack.org/openstack/nova-spec
This would be a spec enhancement I think, please look at the specs
process here - https://specs.openstack.org/openstack/nova-
specs/readme.html
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
You received this bug notification becaus
** Changed in: nova
Status: Confirmed => Won't Fix
--
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/1454418
Title:
Evacuate fails when using cells - AttributeError:
It does feel like it might be better to fix this on the client side.
Marking as opinion as the patch author abandoned the nova patch. It is
welcome to come back later.
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engin
*** This bug is a duplicate of bug 1562681 ***
https://bugs.launchpad.net/bugs/1562681
** Tags added: evacuate
** This bug has been marked a duplicate of bug 1562681
Post instance evacuation, image metadata is not retained when using shared
storage
--
You received this bug notification
There definitely could be enhancements to the recovery mode when things
start up again, but this is more than a simple bug, and probably needs a
spec to work through all the edge conditions here.
The Nova spec process is here - https://specs.openstack.org/openstack
/nova-specs/
** Changed in: nov
This is apparently fixed in os-vif for Newton and beyond. Marking
Invalid on the Nova side because the logic doesn't live in Nova in any
supported version.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
This references the wadl, it can be closed
** Changed in: nova
Status: In Progress => Won't Fix
--
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/1616134
Title:
api
*** This bug is a duplicate of bug 1683972 ***
https://bugs.launchpad.net/bugs/1683972
** This bug has been marked a duplicate of bug 1683972
Overlapping iSCSI volume detach/attach can leave behind broken SCSI devices
and multipath maps.
--
You received this bug notification because you
This references the old api-ref, marking won't fix. If this is an issue
in the new one please update the bug.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (n
cells v1 is deprecated, we're not going to document it fully
** Changed in: nova
Status: New => Won't Fix
--
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/1674486
Ti
So, this really seems like going out of the way to break the system. A
better error message would be fine if it was submitted, but this is very
unlikely to hit in the real world.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
** Tags ad
Exposing system metadata in the compute API is something we really don't
want to do.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launch
This is really only a devstack fix
** Changed in: nova
Status: New => Confirmed
** No longer affects: nova
** No longer affects: neutron
** No longer affects: cinder
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutro
For questions like this, please engage in IRC or the mailing list
** 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/1713466
Kernel panics in guests are unlikely to be Nova bugs. This is probably
an underlying kvm / libvirt issue.
** Changed in: nova
Status: New => Incomplete
** Also affects: openstack-gate
Importance: Undecided
Status: New
** No longer affects: nova
--
You received this bug notific
This is pretty much working as designed. Nova is the owner of that
state, and will drive services to that state.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
This should be tracked by a blueprint, not a bug, on the nova side.
** Changed in: nova
Status: New => Opinion
** Tags added: ironic
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.la
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1714416
Title:
Incorrect response returned for invalid Accept header
Status in Cinder:
This is working as designed. It's not possible for Nova to map anything
until it's registered. Additional documentation for Ironic might be
appropriate here.
** Tags added: ironic
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member
** 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/1715615
Title:
it throws 'Unexpected API Error ' when i try to create fi
This looks like an upstream libvirt/qemu issue that got exposed with the
version bump in Ubuntu. Closing the upstream Nova side.
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Ope
** No longer affects: nova
--
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/1671422
Title:
charms: nova/cinder/ceph rbd integration broken on Ocata
Status in OpenStack ci
Neutron configuration is not setup correctly in your nova.conf
** 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/1670737
Ti
This should probably be tagged to the distro Nova, not the upstream
Nova, unless we can figure out that upstream has a specific issue here
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Comput
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
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/1668295
Title:
This is a libvirt bug
** 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/1661184
Title:
libvirtd: malloc.c:3720: _int_mall
Closing this out because it's a Liberty issue, which we can't fix any
more.
** Summary changed:
- migrate flavor data impossible
+ Kilo to Liberty: migrate flavor data impossible
** Description changed:
+ NOTE: (in comment #9) there is a proposed solution to fix this about
+ dropping foreign ke
** Also affects: oslo.db
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/1690819
Title:
nova-manage [..] api_db sync on F25 re
Public bug reported:
During some gate runs (especially multinode ones) we end up with the
following kinds of failures (all in this log
http://logs.openstack.org/66/258166/1/check/gate-tempest-dsvm-
full/41867ce/logs/syslog.txt.gz)
Dec 16 00:12:16 devstack-trusty-hpcloud-b3-6590764 dnsmasq-dhcp[25
It's especially frustrating in that Nova doesn't use Alembic, however
it's dragged in because of the tests in oslo.db
** Also affects: oslo.db
Importance: Undecided
Status: New
** Changed in: oslo.db
Importance: Undecided => Critical
--
You received this bug notification because yo
This has popped back in Alembic 0.8.4 because of oslo.db tests
** Also affects: oslo.db
Importance: Undecided
Status: New
** Changed in: oslo.db
Importance: Undecided => Critical
** Summary changed:
- neutron stable jobs are busted by alembic 0.8.1
+ oslo.db model tests broken by a
really?
Please actually look at the code a little bit before filing security
bugs. This is a very specific tool used to compare the state of
migrations. It's not installed as part of normal nova process.
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notifica
This is going to require a spec, as it will be a microversion. I agree
GET is the wrong method for these kinds of things.
** Changed in: nova
Importance: Undecided => Wishlist
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of
** Also affects: tempest
Importance: Undecided
Status: New
** No longer affects: nova
--
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/1513558
Title:
test_creat
Nova is an API server, it's fine to put whatever into these fields.
Should the clients scrub this, probably.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engineering
These changes all come from keystone libraries. Nova doesn't do any
registration of this config variables itself. Please poke the keystone
auth folks about this.
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Incomplete
--
You rec
It's not there in 2.0 either. The help text is super out of whack saying
that volumes have 'gpu' associated with them.
I just don't think this ever existed.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Tea
It is not clear that this is a nova issue, but a wholely ironic issue.
** 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/152
If you are creating a tracking bug for yourself, please move to
confirmed
** Changed in: nova
Status: New => Opinion
--
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/
This is definitely a core oslo.service issue with shutting down, this
keeps tripping us up.
** Changed in: oslo.service
Status: New => Confirmed
** Changed in: oslo.service
Importance: Undecided => Critical
** Changed in: nova
Status: New => Invalid
--
You received this bug no
It seems really weird about why keystone just stops working. That is the
thing that really needs to be sorted out.
** 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
Yes, that is by design
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
** Changed in: nova
Status: Opinion => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscrib
This was released in oslo.db 4.1.0.
Something else must be wrong about your environment for this to be an
issue, because it's definitely in 4.2
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whic
Is there an upstream eventlet bug for this?
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1482633
Title:
requests to SSL wrapped socke
evacuate assumes you've done all the fencing and cleanup of the node
itself, this is by design.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://
I'm not really sure why this is filed against nova.
** Changed in: nova
Status: New => Opinion
--
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/1522381
Title:
Supp
This is legacy behavior in Nova network, and the kind of issue that
isn't going to be addressed at this point.
** Changed in: nova
Status: Confirmed => Won't Fix
** Changed in: nova
Importance: High => Wishlist
--
You received this bug notification because you are a member of Yahoo!
E
As explained above, this would change the behavior of the API for
portions that we are trying to deprecate out. People wanting a paginated
API should go directly to Glance.
** Changed in: nova
Status: In Progress => Won't Fix
** Changed in: nova
Importance: Medium => Low
--
You receiv
I think we have now decided the old behavior was never intended, and
will not be supported in Nova moving forward. Permission restriction
should be by project_id.
** Changed in: nova
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Not a nova bug, this is completely in the display layer for novaclient
** Also affects: python-novaclient
Importance: Undecided
Status: New
** Changed in: python-novaclient
Status: New => Confirmed
** Changed in: nova
Status: Confirmed => Invalid
** Tags removed: api
**
I believe that this is the issue with Glance incompatibilities with v1
vs. v2 images. If you create an image with v2 via the glance API, glance
explodes when you probe for that image over the v1 API because of
property incompatibilities. Pushing back as a glance issue for now for
that team to look
*** This bug is a duplicate of bug 1544989 ***
https://bugs.launchpad.net/bugs/1544989
** This bug is no longer a duplicate of bug 1317515
flavor-access-add doesn't validate the tenant id
** This bug has been marked a duplicate of bug 1544989
Nova doesn't validate user/project is valid f
Public bug reported:
For any API call to Nova which takes a tenant_id / user_id as a
parameter, and inserts it into the Nova database, no validation is done
of these values.
This is currently by design, largely because there is no clear way to
check the existence of those users/projects. Nova has
*** This bug is a duplicate of bug 1544989 ***
https://bugs.launchpad.net/bugs/1544989
** This bug is no longer a duplicate of bug 1317515
flavor-access-add doesn't validate the tenant id
** This bug has been marked a duplicate of bug 1544989
Nova doesn't validate user/project is valid f
Closing an a possible, though unlikely future feature
** Changed in: nova
Status: Confirmed => Opinion
--
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/1325736
Title
I think we're actually going to not fix this issue, the extra headers
are mostly bloat
** Changed in: nova
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bug
** Changed in: nova
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1326124
Title:
Allow for editing of existing Security Rules
Status in OpenStack Da
This is really a devstack setup issue, not a nova api issue
** Changed in: nova
Status: In Progress => 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/146784
This is really a feature as it changes quite substantially how the bulk
create works and is accounted for. This should really come in as a spec
I think.
** Changed in: nova
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
The API semantics are really async. For different semantics we should
probe directly to neutron.
** Changed in: nova
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
h
We've updated the Nova docs that this is no longer optional.
** Changed in: nova
Status: In Progress => Won't Fix
--
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/143
This requires a change to the Nova API, so move to a feature
** Changed in: nova
Status: In Progress => Opinion
** Changed in: nova
Importance: Medium => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStac
The manual updated needed here is for a new configuration option called:
live_migration_inbound_addr
Setting this allows for compute hosts to advertise the address which
live migrations should come in on. This allows fine grained control in
environments so that compute to compute live migration tr
I believe the issue is just that Cells does not support PCI pass
through. Cells v1 is frozen, and only regressions will be fixed. So this
is getting marked as Opinion as a future feature which will likely not
ever be done on cells v1.
** Tags added: pci
** Tags added: cells
** Changed in: nova
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
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/1536610
Title:
*** This bug is a duplicate of bug 1451860 ***
https://bugs.launchpad.net/bugs/1451860
** This bug has been marked a duplicate of bug 1451860
Attached volume migration failed, due to incorrect arguments order passed
to swap_volume
--
You received this bug notification because you are a
This isn't really enough to go on, there aren't even links to logs in
the gate.
** 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
This feels like it needs neutron experts to weigh in because under this
kind of environment the network setup is basically done by neutron.
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Incomplete
--
You received this bug notifica
This is definitely a feature rather than a bug, given the complexity. We
should track it as a spec or blueprint instead.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Y
Given the clearly invalid python in the stack trace that mriedem pointed
out, marking as Invalid.
** Changed in: nova
Status: Incomplete => Invalid
** Changed in: nova
Importance: High => Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, wh
901 - 1000 of 1444 matches
Mail list logo