In an effort to clean up stale bugs, I'm marking this as Invalid for
Nova because the issue is in Cinder.
** 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).
I believe this is expected behavior as there are no guarantees given
about the ordering of devices, so I'm marking this Invalid as a bug.
There is a device tagging feature in Nova for this use case, if I have
understood the issue correctly:
https://specs.openstack.org/openstack/nova-
In an effort to clean up stale bugs, I'm marking this Won't Fix because
1) the Rocky release is EOL [1] and we're no longer merging patches for
it and 2) the current doc on the master branch no longer has the unused
"project" variable.
[1] https://releases.openstack.org/rocky/index.html
**
https://review.opendev.org/c/openstack/nova/+/877056 merged to master
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Also affects: nova/yoga
Importance: Undecided
Status: New
** Also affects: nova/zed
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).
Moving this to the neutron project as networking-ovn has been retired
for a while.
My first question is are you able to test this with a later release?
Since it's been 10 months since it was filed just want to make sure it
hasn't been fixed.
** Project changed: networking-ovn => neutron
** Tags
You have been subscribed to a public bug:
We noticed a strange behavior regarding Floating IPs in an OpenStack
environment using ML2/OVN with DVR. Consider the provided test setup
consisting of 3 projects. Each project has exactly one Network with two
subnets, one for IPv4 one for IPv6,
Public bug reported:
GET /v3/users?name= will return duplicates if the user have
federated data
I have a federated local user in the default domain:
REQ: GET https://identity/v3/users/91665ebad88b497cb90eaf4f856357ec
RESP: 200: OK
{
"user": {
"description": "Local federated user",
Reviewed: https://review.opendev.org/c/openstack/neutron/+/89
Committed:
https://opendev.org/openstack/neutron/commit/1e9f50c73638171403b71d742321464dcd5ef7ed
Submitter: "Zuul (22348)"
Branch:master
commit 1e9f50c73638171403b71d742321464dcd5ef7ed
Author: Luis Tomas Bolivar
Date: Fri
** Changed in: ironic-lib
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1489059
Title:
"db type could not be
Train release is reached end of life so the stable/train branch was
deleted. You can use the train-eol tag instead[1].
[1]https://github.com/openstack/nova/tree/train-eol
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
You need to set the auth_url to point to URL where the keystone API is
accessible. So you have to check how keystone is deployed in your
environment.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
** 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/2024579
Title:
when i am trying to launch an instance iam getting this
I don't see how this relates to the nova project so I close this as
invalid.
** 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).
If I understand correctly the proposed solution did not need changes in
nova but changes in other projects to disable some nova specific tests.
So I close this for nova.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Ssh known hosts file handling is not in scope for nova. I glad to see
that this is progressing in charms. Closing this for nova.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Abandoned, because now i see that the mac-binding entry is updated
correctly by OVN when trying to recreate the same situation.
** Changed in: neutron
Status: In Progress => Incomplete
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification
** Changed in: horizon
Assignee: (unassigned) => Vishal Manchanda (vishalmanchanda)
** Changed in: horizon
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
Public bug reported:
Description
===
After upgrade of nova, including compute and conductor nodes, VM rebuild
fails. All computes, that have service state UP, and all conductors are
having version 66. Though, there was 1 compute during upgrade that is
DOWN, which does have version 64.
Public bug reported:
As we know, we can use ipv6 address end with '0' like 2001::.
But when we allocate ipv6 pool use neutron, we could find the error like
follows:
neutron net-create net-v6
neutron subnet-create --ip-version 6 --allocation-pool start=2001::,end=2001::2
net-v6 2001::/64
The
20 matches
Mail list logo
