Public bug reported:
When setting resize_rootfs to 'noblock', cloud-init should fork a new
process and continue with it's own initialization process. However, it
seems that this is currently broken, as you see from these logs that it
still blocks on it:
Jul 7 12:34:20 localhost [CLOUDINIT]
*** This bug is a duplicate of bug 1102477 ***
https://bugs.launchpad.net/bugs/1102477
** Changed in: nova
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
This has been taken care of in this merged review
https://review.openstack.org/#/c/69266/
** Changed in: nova
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Assignee: Mohammed Naser (mnaser)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) = Mohammed Naser (mnaser)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https
Public bug reported:
With the release of Icehouse, the RPC APIs were not updated for their
version aliases.
** Affects: nova
Importance: Undecided
Assignee: Mohammed Naser (mnaser)
Status: New
** Changed in: nova
Assignee: (unassigned) = Mohammed Naser (mnaser)
--
You
Public bug reported:
There is an issue that is causing unit tests to fail with the following
error:
MessagingTimeout: No reply on topic conductor
MessagingTimeout: No reply on topic scheduler
2014-04-23 13:45:52.017 | Traceback (most recent call last):
2014-04-23 13:45:52.017 | File
Public bug reported:
When trying to use the new native OVSDB provider, the connectivity never
goes up due to the fact that what seems to be the db_set operation
failing to change the patch ports from "nonexistant-peer" to the correct
peer, therefore not linking the bridges together.
Public bug reported:
In our environment, we have some large compute nodes with a large number
of VIFs. When the update_device_list call happens on the agent start
up:
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L842
This
Public bug reported:
OpenStack Nova Kilo release requires 1.8.2 or higher, this is due to the
addition of on_execute and on_completion to the execute(..) function.
The latest Ubuntu OpenStack Kilo packages currently have code that
depend on this new updated release. This results in a crash in
Public bug reported:
The metrics collection on compute nodes is currently not working.
When the compute node creates the object to save, it is divided to be a
value inside [0,1]. However, at the same time, when the scheduler needs
to pull out the numbers, it divides it once again as it pulls
Public bug reported:
When an instance fails the quota rechecks codebase which is here:
https://github.com/openstack/nova/blob/master/nova/conductor/manager.py#L992-L1006
It raises an exception, however, the cell mapping is only saved much
later (thanks help of dansmith for finding this):
Public bug reported:
With versioned notifications, the instance payload tries to attach a
flavor payload which it looks up from the instance. It uses the one
which is attached in instance_extras however there seems to be a
scenario where the disabled field is missing in the database, causing
all
Public bug reported:
The online data migration generates a context in order to be able to
execute migrations:
https://github.com/openstack/nova/blob/master/nova/cmd/manage.py#L747
However, this context does not contain a `project_id` when running this
via CLI.
Public bug reported:
https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L674-L718
In _get_host_states, a list of all computes nodes is retrieved with a
`state_key` of `(host, node)`.
https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L692
Public bug reported:
When using ImagePropertiesFilter for something like hardware
architecture, it can cause very unpredictable behaviour because of the
lack of default value.
In our case, a public cloud user will most likely upload an image
without `hw_architecture` defined anywhere (as most
Public bug reported:
If you try to boot and instance and delete it early before scheduling,
the '_delete_while_booting' codepath hits
`_attempt_delete_of_buildrequest` which tries to remove the block device
mappings.
However, if the cloud contains compute nodes before Pike, no block
device
Public bug reported:
There has been situations where due to an unrelated issue such as an RPC
or DB problem, the nova_api instance_mappings table can end up with
instances that have cell_id set to NULL which can cause annoying and
weird behaviour such as undeletable instances, etc.
This seems to
Public bug reported:
When using OpenDaylight with Open vSwitch, the Neutron Open vSwitch
agent does not exist in the environment anymore.
When an instance is started up for the first time, OpenDaylight will
successfully bind the port and send the vif plugged notification.
However, since the
Public bug reported:
At the moment, nova-compute will die if it fails to authenticate to the
messaging cluster and it will not retry on start. It is possible that
the vhost is not ready yet so it should be handled here:
Public bug reported:
During a rolling upgrade, once the control plane is upgraded and running
on Rocky (but computes still in Queens), the consoles will stop working.
It is not obvious however it seems that the following is missing:
```
[workarounds]
enable_consoleauth = True
```
There isn't a
** Affects: nova
Importance: High
Assignee: Mohammed Naser (mnaser)
Status: Triaged
** Tags: libvirt live-migration upgrade
** Changed in: nova
Assignee: (unassigned) => Mohammed Naser (mnaser)
--
You received this bug notification because you are a member of Ya
Public bug reported:
I ran into this upgrading another environment into Rocky, deleted the
problematic resource provider, but just ran into it again in another
upgrade of another environment so there's something wonky. Here's the
traceback:
=
2018-10-25 09:18:29.853 7431 ERROR
Public bug reported:
It is possible that placement gets out of sync which can cause
scheduling problems that would go unknown. I've built out this script
would would be nice to have as `nova-manage placement audit`:
Public bug reported:
If you are taking a nova-compute service out of service permanently, the
logical steps would be:
1) Take down the service
2) Delete it from the service list (nova service-delete )
However, this does not delete the compute node record which stays
forever, leading to the
candidates match, it throw a message in DEBUG
and exits out, leaving important information for the operator.
https://github.com/openstack/nova/blob/c3fe54a74d8a3b5d5338a902e3562733a2b9a564/nova/scheduler/manager.py#L150-L153
** Affects: nova
Importance: Undecided
Assignee: Mohammed Naser
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
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/1807400
Title:
Public bug reported:
The online_data_migrations should be ran after an upgrade and contains a
list of tasks to do to backfill information after an upgrade, however,
some of those queries are extremely inefficient which results in this
online data migrations taking an unacceptable period of time.
Public bug reported:
For a long time, noVNC set the token inside a cookie so that when the
/websockify request came in, we had it in the cookies and we could look
it up from there and return the correct host.
However, since the following commit, they've removed this behavior
itical
** Changed in: openstack-ansible
Assignee: (unassigned) => Mohammed Naser (mnaser)
--
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/1715374
Title:
Reloadin
Public bug reported:
Keystone has introduced roles for reader/member/admin which we should
leverage in order to be able to provide an easy way for read-only access
to APIs.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a
/nova/compute/utils.py#L1260
This would fail with:
AttributeError: 'NoneType' object has no attribute 'get'
** Affects: nova
Importance: Undecided
Assignee: Mohammed Naser (mnaser)
Status: New
** Changed in: nova
Assignee: (unassigned) => Mohammed Naser (mnaser)
--
** Changed in: openstack-ansible
Status: Fix Committed => 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/1749574
Title:
[tracking] removal and
** Also affects: openstack-ansible
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/1825386
Title:
nova is looking for OVMF
Public bug reported:
If you use the Ironic API to set a node into a maintenance (for whatever
reason), it will no longer be included in the list of available nodes to
Nova.
When Nova refreshes it's resources periodically, it will find that it is
no longer in the list of available nodes and
Public bug reported:
At the moment, in order to clean up a database, you will have to archive
first and then run the delete afterwards.
If the operator doesn't care about the ability of restoring deleted
instances, it means that the archive step is useless for them.
It would be nice if we added
Public bug reported:
During an upgrade of a cloud from Stein to Train, there is a migration
which adds the `hidden` field to the database.
In that migration, it was assumed that it does not backfill all of the
columns. However, upon verifying, it actually does backfill all columns
and the order
Public bug reported:
The function which counts resources using the legacy method involves
getting a list of all cell mappings assigned to a specific project:
https://github.com/openstack/nova/blob/575a91ff5be79ac35aef4b61d84c78c693693304/nova/quota.py#L1170-L1209
This code can be very heavy on
Public bug reported:
In our database migrations, we run the following:
'ALTER DATABASE %s DEFAULT CHARACTER SET utf8'
If usnig a database name that includes a dash, the migration fails
because it requires to be wrapped by `.
** Affects: nova
Importance: Undecided
Assignee: Mohammed
*** This bug is a duplicate of bug 1786298 ***
https://bugs.launchpad.net/bugs/1786298
** This bug has been marked a duplicate of bug 1786298
nova-manage db archive_deleted_rows does not cleanup table
instance_id_mappings
--
You received this bug notification because you are a member of
Public bug reported:
It looks like whenever we create an instance, we create an EC2 instance
ID mapping for it:
https://github.com/openstack/nova/blob/df49ad9b29afcafa847b83df445b6627350721b5/nova/db/sqlalchemy/api.py#L1137-L1138
Which is used by the EC2 objects:
Public bug reported:
oslo.db has plenty of infrastructure for detecting deadlocks, however,
it seems that at the moment, neutron has it's own implementation of it
which is missing a bunch of deadlocks, causing issues when doing work at
scale.
this bug is to track the work in refactoring all of
Public bug reported:
When trying to boot an instance where the image size is larger than the
volume size, there seems to be no 'protection' mechanism of stopping you
from doing that, it ends up failing in the compute manager layer making
it more complicated for the user to debug.
We should
Public bug reported:
We have an environment where users can plug their VMs both to tenant and
provider networks on the hypervisor. This environment does not have
jumbo frames. The MTU for VMs plugged directly into provider networks
is 1500 (physical network) however it is 1450 for tneant
Public bug reported:
When enabling CORS, by default, the `X-OpenStack-Nova-API-Version` API
header is not included in the allowed headers. It should be by default
because it's critical to the operation of the OpenStack Nova API.
** Affects: nova
Importance: Undecided
Status: New
As per sean-k-mooney advice, I've added this to be an oslo.messaging bug
since it's more of an issue in there than it is in Nova.
** Also affects: oslo.messaging
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering
Public bug reported:
You'll get an alert similar to this:
"Unable to retrieve instance size information."
reference: https://github.com/vexxhost/atmosphere/issues/574
** Affects: horizon
Importance: Undecided
Status: In Progress
--
You received this bug notification because you
Public bug reported:
When using Neutron, it will prevent you to delete a port if the subports
are still attached:
https://review.opendev.org/c/openstack/neutron/+/885154
Because of this, if you delete a VM with subports attached, you will end
up with a VM in ERROR state:
```
2023-09-27
Public bug reported:
When using OVN, if you have a virtual router with a gateway that is in
subnet A, and has a port that has a floating IP attached to it from
subnet B, they seem to not be reachable.
https://mail.openvswitch.org/pipermail/ovs-dev/2021-July/385253.html
There was a fix brought
Invalid now, 16.04 is long gone :)
** Changed in: neutron
Status: Confirmed => 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/1645516
Title:
openswan package is not
This is no longer relevant and I do not see these warnings, closing
because of age.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Correct, resolved by the comment Dmitriy added.
** Changed in: neutron
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1680484
Title:
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1598652
Title:
Neutron VPNaaS API CI is not enabled
Status in neutron:
Public bug reported:
At the moment, if a device attempts to be detached and times out (using
libvirt), it will log a message:
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L2570-L2573
However, this is not a failure, since we actually retry the process a
few more
Public bug reported:
At the moment, the `_get_pci_passthrough_devices` function is prone to
race conditions.
This specific code here calls `listCaps()`, however, it is possible that
the device has disappeared by the time on method has been called:
Public bug reported:
At the moment, if the cloud sustain a large number of VIF plugging
timeouts, it will lead into a ton of leaked green threads which can
cause the nova-compute process to stop reporting/responding.
The tracebacks that would occur would be:
===
2022-04-17 00:21:28.651 877893
Public bug reported:
When using federation and having the values of `groups` in the mapping
set to a number, it will be parsed into a a number and then fail to
authenticate:
```
{"error":{"code":400,"message":"'int' object is not iterable","title":"Bad
Request"}}
```
I believe the bad bit is
Public bug reported:
For a VM that's using an RBD volume when `volume_use_multipath` is set
to true, VMs will fail to go up.
https://github.com/openstack/os-
brick/blob/28ffcdbfa138859859beca2f80627c076269be56/os_brick/initiator/linuxscsi.py#L212-L233
It seems like we always call os_brick with
Public bug reported:
At the moment, it seems that when using a DNS hostname for
`ovn_nb_connection` or `ovn_sb_connection`, the connection never seems
to go up.
It seems that the `ovs` library does not resolve an IP address before
proceeding, I'm not sure if we should be resolving things and
Public bug reported:
When using OVN, the `veth` interfaces which get created inside the
network namespace (and the other half that goes into the OVS bridge)
both do not get an MTU configured for them when they are provisioned.
Nova is also affected by this.
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2052915
Title:
Public bug reported:
We're running into an issue in our CI with Atmosphere where we
frequently see failures when a router port is removed from an interface,
the traceback is the following:
==
2024-04-03 21:13:09.804 10 ERROR neutron.api.v2.resource [None
Public bug reported:
We've got an interesting scenario where one of the backends of a load
balancer is not reachable given the following test environment:
2x networks
- provider network, IPv4 + IPv6 subnets
- tenant network (Geneve), IPv4 + IPv6 subnets
3x VMs
- 2x single port, 2 IP addresses
Public bug reported:
We've noticed the following issue with the OVN octavia provider and
we've narrowed it down to the following:
- Member with floating IP not reachable through load balancer
We've noticed that at first, it loses all connectivity. Once the
floating IP gets removed and added,
Public bug reported:
At the moment, the OVN octavia provider does not set `hairpin_snat_ip`
out of the box which means that if a backend server is sending requests
to a load balancer which it is also a backend server of, it will get
that request where the source IP of the request is the floating
64 matches
Mail list logo
