Public bug reported:
Description
===
Nova skips removing VHostUser from libvirt, thinking that it
already deleted the interface
Error happened here:
https://github.com/openstack/nova/blob/c9dca64fa64005e5bea327f06a7a3f4821ab72b1/nova/virt/libvirt/driver.py#L1709
Interface was not present
@Andres Rodriguez (andreserl),
Thank you for the prompt reply \o/
I have read comment # 3 (or comment # 4) as in 'could be in MAAS' but
'MAAS layer' (quoting the reporter), from Juju perspective, could be
interpreted as a MAAS provider and, indeed, could involve modification
to juju maas provider
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1806504
Title:
userdata runcmd overwrites runcmd under cloud.cfg.d
Status in cloud-in
Adding cloud-init and MAAS as projects to this report and marking as
Invalid for Juju since Juju operates as expected.
** Also affects: maas
Importance: Undecided
Status: New
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: juju
Status: New
Public bug reported:
When there are multiple interfaces with their own default gateways, this
could result in asymmetric routing. In order to solve this, policy based
routing would have to be configured.
- There is already support to configure routes in cloud-init, but it misses
ability to speci
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/queens
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://bug
So, should this be marked invalid then?
** 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/1607400
Title:
UEFI not
Public bug reported:
I am using Queens and when i looked at horizon (admin) overview Usage
summary i am seeing following numbers
Active Instances: 367
Active RAM: 1.9TB
This Period's VCPU-Hours: 95711.23
This Period's GB-Hours: 404773.71
This Period's RAM-Hours: 80477125.24
But on command line i
Public bug reported:
This happens for master branch in tempest-full-py3 job, test case
tempest.api.compute.admin.test_delete_server.DeleteServersAdminTestJSON
http://logs.openstack.org/67/622967/1/check/tempest-full-
py3/399318c/testr_results.html.gz
In the log you can find this:
Traceback (mos
Public bug reported:
Deployment is Queens with ML2/OVS and DPDK. Instance ports are neutron
trunk ports with DPDK vhu in vhostuserclient mode. When an instance is
rebooted, nova/os_vif deletes the ovs port connected to the trunk bridge
and then recreates it when the host comes back online. This
Public bug reported:
- [x] This is a doc addition request.
I was looking at this nova config option:
https://docs.openstack.org/nova/rocky/configuration/config.html#DEFAULT.non_inheritable_image_properties
And noticed that those img_signature* properties are not documented in
the useful image p
Public bug reported:
This is split out from bug 1807044 where nova-api sometimes takes more
than 60 seconds to start on slow CI nodes which causes devstack to
timeout and fail.
Specifically, every nova.compute.api.API constructs a
SchedulerReportClient, which grabs an in-memory lock per API worke
Mitaka is very old at this point. Is this still a problem on newer
releases, like Pike or Rocky?
** 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://b
Public bug reported:
The metering agent running on compute nodes fails to report metering
data for DVR routers.
How to reproduce:
1. Have a multi-node OpenStack Pike deployment with a network node and a
compute node (alongside other nodes needed).
2. Create a distributed public router and attach
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova
Importance: Undecided => Medium
** Changed in: nova/pike
Status: New => In Progress
** Changed in: nova/queens
Sta
Isn't this covered by blueprint
https://blueprints.launchpad.net/nova/+spec/per-aggregate-scheduling-
weight ? If so, this is a feature request already covered by the
blueprint...
** Changed in: nova
Importance: Undecided => Wishlist
** Changed in: nova
Status: New => Invalid
** Tags a
Public bug reported:
Sometimes the metering agent fails to send meter information. When this
happens and I ssh into the network node and run `ip netns qrouter
- iptables -nvL` I see no metering rules in the output.
Restarting the metering agent fixes this.
I suspect that this is a race condition
This is working as designed. The underlying issues that require CERN to
set max_placement_results to such a low number (10 when there are ~200
hosts per cell, and ~14K hosts total in the deployment) are what we need
to focus on, like bug 1805984 for example.
** Changed in: nova
Status: New
Hmm, this is an interesting point. Setting the protected=true flag on
the image seems like a good solution, except I don't see any kind of
force delete option for images. Would a user be able to change the
protected value from true to false if they really knew what they were
doing and wanted to del
Public bug reported:
In neutron.agent.linux.ip_lib.add_ip_rule, the "table" argument can be
an integer or a string ("default", "main", "local").
This parameter is incorrectly treated in "_make_pyroute2_args".
** Affects: neutron
Importance: Undecided
Status: New
--
You received t
Public bug reported:
When shelving an instance with nova storage (instead of boot from
volume), a glance snapshot of the VM is created before it is shelved.
The user is free to delete this snapshot with no warning, indication or
error that the snapshot is needed by the shelved instance other than
21 matches
Mail list logo
