Public bug reported:
downstream we had a bug report where live migration was failing on the
az filter after a customer renamed an az.
https://bugzilla.redhat.com/show_bug.cgi?id=2303395
nova does not support renaming AZs in general, or moving hosts with
instance between AZs
5 years ago as part
Public bug reported:
the flavor image conflict check for the virtio packed ring format
is not correctly converting the values to booleans when comparing them
as a result, the comparison is case sensitive when it should not be.
** Affects: nova
Importance: Low
Status: Triaged
** Ta
since the intorduction of AZ nova has documented that pinning to the
nova az should never be done
https://docs.openstack.org/nova/latest/admin/availability-zones.html
"""
The use of the default availability zone name in requests can be very
error-prone. Since the user can see the list of availab
The disable feature on the comptue service is intended to prevent any scudling
of new workload to a disabled host.
this is intended to include new workload and all move operations to a disabled
host.
the host is being rejected as intended so setting this to invalid as the
expectations of the r
** Changed in: nova
Status: In Progress => 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/1913016
Title:
nova api os-resetState should not reset the state
=> Low
** Changed in: nova/2024.2
Importance: Undecided => Low
** Changed in: nova/2025.1
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Changed in: nova/2024.2
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Changed in: nova/2024.1
Importance: Undecided =&g
Assignee: sean mooney (sean-k-mooney)
Status: New
** Tags: rfe
** Changed in: neutron
Assignee: (unassigned) => sean mooney (sean-k-mooney)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
ht
actions.
- performance
performance of l3 routing is expected to approach l2 performance for
east/west traffic.
performance is not expected to change for north/south.
** Affects: neutron
Importance: Undecided
Assignee: sean mooney (sean-k-mooney)
Status: New
** Tags:
** Also affects: nova/victoria
Importance: Undecided
Status: New
** Also affects: nova/train
Importance: Undecided
Status: New
** Also affects: nova/ussuri
Importance: Undecided
Status: New
** Also affects: nova/wallaby
Importance: Undecided
Status: New
-
** 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).
https://bugs.launchpad.net/bugs/1747496
Title:
MTUs are not set for VIFs if using kernel ov
** Changed in: nova/train
Status: Fix Released => New
** Also affects: neutron/ussuri
Importance: Undecided
Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
Status: In Progress
** Also affects: neutron/wallaby
Importance: Undecided
Status: New
** Also affects:
Public bug reported:
today when ever you use a realtime guest you are required to enable cpu
pinning and other feature such as spcifing a real time core mask via
hw:cpu_realtime_mask or hw_cpu_realtime_mask.
in the victoria release this requriement was relaxed somewhat with the
intoduction of mix
in: os-vif
Importance: Undecided => Medium
** Changed in: nova
Status: Triaged => Invalid
** Changed in: os-vif
Assignee: (unassigned) => sean mooney (sean-k-mooney)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is s
Public bug reported:
as seen in http://paste.openstack.org/show/806818/ if we use machine type "Q35"
instead of "q35" we fail to boot the vm. This is because the machine type name
in libvirt are case sensitvie.
however due to the way libvirt validates the xml it retruns a "No PCI buses
availabl
** Also affects: os-vif
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/1933517
Title:
[RFE][OVN] Create an intermediate OVS bridge between VM
actully the operator woudl be deleting the comptue service after removing the
compute nodes.
you shoudl remove the compute service first but we shoudl fix this regardless.
you should be able to recreate this bug by just creating a compute servce
and then deleteing it.
** Changed in: nova
** Also affects: neutron
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/1934742
Title:
nova may leak net interface in guest i
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Triaged
** Changed in: nova
Importance: Undecided => Critical
** Changed in: nova
Assignee: (unassigned) => sean mooney (sean-k-mooney)
--
You received this bug not
setting to critical since this blocks packaging of xena
** Also affects: nova/xena
Importance: Critical
Status: In Progress
** Also affects: nova/yoga
Importance: Undecided
Status: New
** Changed in: nova/yoga
Status: New => In Progress
** Changed in: nova/yoga
Imp
im not sure that nova is incontrol of this.
this seams like a issue likely with dhcp?
i dont think nova actully set /32 routes for the gateways itself.
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
E
adding neutron as i think neutron shoudl also be normaliasing the mac
adress that users provide and alwasy storign it in lower case. a mac is
technically a number not a string we just use hex encoding for human
readablity so the caseing does not matter but it would be nice to at
least consider mov
This is an RFE not a bug.
This should be addressed via a specless blueprint as it is a new capablity.
** 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 (nov
** Also affects: devstack-plugin-ceph
Importance: Undecided
Status: New
** Changed in: devstack
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.launchp
setting this to invilad since the bug is in tempest.
it is currently blocking the nova-next job so it is a gate-blocker for nova
until this is fixed in tempest.
as there are already 2 patches up to fix this we expect it to be
resolved soon so we will just clost the nova part for now.
** Changed
ack i kind of agree with gmann here
gmann is correct that this does not align with the direction we are moving in
with our new policy/rbac work and that our intent was to eventually remove it
outside of keypairs.
the spec linked above clearly state what our intentions were and the
enpoint on whi
support back in 2015
https://github.com/eventlet/eventlet/issues/8#issuecomment-75490457
so we should not need to work around the lack of ipv6 support anymore.
https://review.opendev.org/c/openstack/nova/+/830966
** Affects: nova
Importance: Medium
Assignee: sean mooney (sean-k-mooney
its not released yet but ill be releaseing os-vif today.
it looks like teh rule for setting fix released are wrong.
it sould only be set when we release that commit in a tagged release on pypi/
tarballs.openstack.org.
** Changed in: os-vif
Status: Fix Released => Fix Committed
--
You rece
Public bug reported:
the lower constraints tox env attempts to run nova's unit tests with
the minium supported software versions declared in nova lower-constraints.txt
due to the way the install command is specified in the default tox env
install_command = pip install
-c{env:UPPER_CONSTRAINTS_FI
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Importance: Undecided => High
** Changed in: nova
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Changed in: nova
Status: New => In Progress
** Tags added: stein-rc-potential
Public bug reported:
The tempest jobs have stared to periodicaly fail with
Could not install packages due to an EnvironmentError:
HTTPSConnectionPool(host='git.openstack.org', port=443)
starting on may 6th
http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22Could%20n
Stable device naming within the guest is OS dependent and strictly out of scope
of nova to fix.
nova does not chose the address at which device are attached and the nova api
doe not
guarentee stable nic ordering. the vm pci adress is determined by libvirt.
the device role tagging feature was dev
Public bug reported:
During the implementation of enabling hypervisor hiding for windows guests
it became apparent that a latent bug exits that allows non privaldges users
to override the policy set by the admin in the flavor by uploading a custom
image.
by convention back in the havan/icehouse
Public bug reported:
The q35 machine type support native pcie instead of legacy ahci
based pci hotplug. This has several advantages and one majour disadvantage
with the new pcie approch you need to pre allocate the pcie slot so that
they will be available for use with hotplug if needed.
to suppor
the device_type is optional but if set it will be checked
https://github.com/openstack/nova/blob/51e3787bf89f19af8a9d37288a63731563c92fca/nova/pci/request.py#L136-L138
type-pci is not intended for fore use with device that are capable of
sriov and exits primarly for use with pci device that are n
*** This bug is a duplicate of bug 1805891 ***
https://bugs.launchpad.net/bugs/1805891
** This bug has been marked a duplicate of bug 1805891
pci numa polices are not followed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
as this feature never worked on rocky and queens i am marking it as wont
fix as it would be effectivly a feature backport based on matt's comment
here https://review.opendev.org/#/c/641653/1//COMMIT_MSG@13
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: no
Nova does not currently have support for neutron ports without an ip.
when support was added for the neutron port ip_allocation polices only support
for intimidate and defer where implemented.
i believe work is planned to add support for addresses port in train but
i am close this as invalid as i
you are conflating two different things
alias are not used for neutron based sriov networking
and nic that are pastthoyhg via flaovr aliase are not managed by neutorn
or the sriov nic agent.
the documentation in https://docs.openstack.org/nova/pike/admin/pci-
passthrough.html
describe how to do
*** This bug is a duplicate of bug 1768917 ***
https://bugs.launchpad.net/bugs/1768917
i have closed this as a duplicate as i explain in the other bug that you
miss understood how to use this feature.
based on teh in fomation you provdied on the ohter bug i am assumin you
have only one nic av
i belive you are correct that this behavior is caused by the fact you
are creating a usever via cloud init.
if you think this is really a nova bug feel free to set the status back
to New for the bug to be retriaged.
** Changed in: nova
Status: New => Invalid
--
You received this bug noti
this might be somthing that could be added to the exsiting
neutron-ovs-cleanup script
that is generated by this entry point
https://github.com/openstack/neutron/blob/master/setup.cfg#L49
and impmeneted here
https://github.com/openstack/neutron/blob/master/neutron/cmd/ovs_cleanup.py
but this sho
making as invalid as there appears to be sever different issues from you
database to the kernel locking up which seam unrelated to nova.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribe
marking as invalid as this is likely an issue wiht the ssh client you are using
ro the ssh server in the guest.
the fact it works on linux but not windows/android suggest to me it might be
related to the authentication methods
or encryption algothims and key types supproted in the client/server a
** Changed in: os-vif
Status: New => Invalid
** Changed in: nova
Status: New => In Progress
** Changed in: nova
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Changed in: nova
Importance: Undecided => Medium
--
You received this bug notification bec
*** This bug is a duplicate of bug 1774249 ***
https://bugs.launchpad.net/bugs/1774249
** This bug has been marked a duplicate of bug 1774249
update_available_resource will raise DiskNotFound after resize but before
confirm
--
You received this bug notification because you are a member o
Assignee: sean mooney (sean-k-mooney)
Status: Confirmed
** Tags: libvirt
--
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/1835822
Title:
vms loose acess to config
can you check that the ovs-dpdk is actully working on the host.
if you do "ps aux | grep ovs" do you see the ovs-vswitchd or ovs-db
running?
if so please run "ovs-vsctl show" and "ovs-ofctl dump-flows br-int"
to confirm your ovs is actully functional via the commandline.
im not familar with the
intentinal.
ill fix this shortly and backport it.
** Changed in: os-vif
Importance: Undecided => High
** Changed in: os-vif
Status: New => Confirmed
** Changed in: os-vif
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Changed in: nova
Status: New =
** Also affects: os-vif/stein
Importance: Undecided
Status: New
** Also affects: os-vif/trunk
Importance: High
Assignee: sean mooney (sean-k-mooney)
Status: In Progress
** Changed in: os-vif/stein
Status: New => Confirmed
** Changed in: os-vif/stein
Assig
in: nova/train
Status: New => In Progress
** Changed in: nova/train
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Changed in: nova/ussuri
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Changed in: nova/stein
Assignee: (unassigned) => sean
http://paste.openstack.org/show/795679/
i was able to repoduce this once on master but not reliably yet.
so im moving this to confimed.
we also have a downstream report of this on train
https://bugzilla.redhat.com/show_bug.cgi?id=1850400
sill at that to the affeted versions
i am setting the impo
Assignee: sean mooney (sean-k-mooney)
Status: New
** Tags: numa
--
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/1887377
Title:
nova does not loadbalance
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/train
Importance: Undecided
Status: New
** Also affects: nova/ussuri
Importance: Undecided
Status: New
** Changed in: nova/train
Importance: Undecided => Medium
** Changed in: nova/train
S
this has a signicant upgrade impact so i think this is imporant to fix and
backport.
i have repoduced this locally too so moveing to triaged.
** Changed in: nova
Importance: Undecided => High
** Changed in: nova
Status: New => Triaged
** Also affects: nova/ussuri
Importance: Undeci
reading the nic feature flags was intoduced in pike
https://github.com/openstack/nova/commit/e6829f872aca03af6181557260637c8b601e476a
but this only seams to happen on mondern version of libvirt so setting
as wont fix. it can be backported if someone hits the issue and care to
do so
** Also affec
** Also affects: networking-opencontrail
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/1888395
Title:
shared live migration
moving this to triaaged and setting this to high
the regression was introduced in train by
https://opendev.org/openstack/nova/commit/fd8fdc934530fb49497bc6deaa72adfa51c8783a
specifically
https://github.com/openstack/nova/blob/b8ca3ce31ca15ddaa18512271c2de76835f908bb/nova/compute/manager.py#L7654-L
ode when
we boot the vm.
this bug applies to all currently supported release of nova.
** Affects: nova
Importance: Undecided
Assignee: sean mooney (sean-k-mooney)
Status: Confirmed
** Tags: libvirt numa pci scheduler
** Summary changed:
- nova does not blance vm aross numa node
Public bug reported:
seen in upstream ci in grenade multi node job
as part of a livemigation.
in this canse the error happens on the destination host.
Traceback (most recent call last):
File "/opt/stack/old/nova/nova/virt/libvirt/host.py", line 605, in
_get_domain
return conn.lookupB
This is a feature not a bug.
there is already a blueprint open for thsi so markin this as invlaid.
https://blueprints.launchpad.net/nova/+spec/volume-backed-server-rebuild
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/ussuri
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/train
Importance: Undecided
Status: New
** Al
** Also affects: neutron
Importance: Undecided
Status: New
** Tags added: libvirt neutron ovs
--
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/1896226
Title:
Th
just adding the previous filed downstream redhat bug
https://bugzilla.redhat.com/show_bug.cgi?id=1852110
this can happen in queens for context so when we root cause the issue
and fix it it should like be backported to queens. tjere are other older
bugs form newton that look similar related to unsh
personally i thihnk we whoudl clouse this as invlid.
this is either a feature request to allow setting different hostnames
form displayname as part of nova booth or a request to expand the
allowed set of vm names to allow '.' which currently not allowed and
transfrom it to some other value to gene
: nova
Status: New => Triaged
** Changed in: nova
Importance: Undecided => High
** Changed in: nova
Assignee: (unassigned) => sean mooney (sean-k-mooney)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStac
im reopening this and marking it as triaged
ppc64le has been supported with thrid party integration testing provide by the
IBM PowerKVM CI on ppc64el for years here is an example test run
https://oplab9.parqtec.unicamp.br/pub/ppc64el/openstack/nova/68/767368/1/check/tempest-dsvm-full-focal-py3/ef
setting this back to invalid as Matt Riedemann siad this is a feature not a bug
fix.
it is trcked as a blueprint
https://blueprints.launchpad.net/nova/+spec/allow-disabling-cpu-flags and we
shoudl use that to track it
not this bug.
** Changed in: nova
Status: Triaged => Invalid
--
You
** 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/1915055
Title:
launched_at's reset when resizing/reverting and unshelv
** 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/1913641
Title:
Incorrect Shelved_offloaded instance metrics on
; Triaged
** Changed in: nova/victoria
Importance: Undecided => Medium
** Changed in: nova
Assignee: (unassigned) => sean mooney (sean-k-mooney)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Comput
im going to move the os-vif bug to fixed released as
https://github.com/openstack/os-vif/commit/d291213f1ea62f93008deef5224506fb5ea5ee0d
fixes what can be fixed by os-vif alone. this was part of
https://github.com/openstack/os-vif/releases/tag/1.13.0
i am going to leave the nova bug as is until
updating this to fix release sicne
https://review.opendev.org/c/openstack/nova/+/768352 is merged on master
backports have been propsoed to u and v so i have add those and i also
added train since i assume we want this in Train downstream?
if this need to go back futher then feel free to add thos
in general i dont feel like this is a valid bug.
it is perhaps a feature request which chould be acomplished by an extention to
Provider.yaml
to allow standard resouce class inventories to be updated by the operator.
in general what you are asking for is intentionally not allowed.
max_unit must
** 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/2017358
Title:
VM doesn't boot after qemu-img convert from VMDK to RAW/Q
** 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/2018318
Title:
'openstack server resize --flavor' should not mig
CONF.agent_down_time // 3)
to increase the likelihood that we send the heartbeat in time.
when we are making calls to privsep and ovs the logs stop for multiple
second while those operations are happening and if that happens the the
wrong time i belive this leads to use missing the heartbeat interv
This is the expected behavior.
evacuate of image-backed vms rebuilds the root disk because that is the
expected behaviour in a cloud env where the instance root disk should
not contain any valuable data.
This is functioning precisely how the API was designed to work.
in fact, the preservation fo
** Changed in: nova/antelope
Status: New => In Progress
** Changed in: nova/antelope
Importance: Undecided => Critical
** Changed in: nova/antelope
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Changed in: nova/yoga
Status: New => Triaged
** Changed i
this is a bug in devstack-plugin-ceph-multinode-tempest-py3 we need to backport
https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/882987
** Also affects: devstack-plugin-ceph
Importance: Undecided
Status: New
--
You received this bug notification because you are a member o
Public bug reported:
test_get_console_output_server_id_in_shutoff_status
https://github.com/openstack/tempest/blob/04cb0adc822ffea6c7bfccce8fa08b03739894b7/tempest/api/compute/servers/test_server_actions.py#L713
is failing consistently in the nova-lvm job starting on July 24 with 132
failures in
This is not a bug this is intentional bevhior added by
https://github.com/openstack/nova/commit/26c41eccade6412f61f9a8721d853b545061adcc
To address https://bugs.launchpad.net/nova/+bug/1633120
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you
Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Status: New => In Progress
** Changed in: nova
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Changed in: nova
Importance: Undecided => Critical
--
You received this bug notifi
reviewing the steps rene performed and the initial bug description this
work flow is not supported
nova has never supported attaching a volume to a guest via the cidner API
and detaching it has been explicitly blocked due to the cve exposures
so for nova i belive this is invalid.
cinder likely
for cinder this would likely require a spec as its an api change to be
able to pass the barbican secrete i belive.
for nova this might be a specless blueprint if the changes were minor
enough and we coudl capture the details in the cinder spec otherwisse we
would need a spec for nova as well.
in
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: horizon
Status: New => Invalid
** Changed in: nova
Status: New => Triaged
** Changed in: nova
Importance: Undecided => Medium
** Changed in: nova
Assignee: (unassigned) => zhou zhong (zhouzhon
I dont belive this is in the scope of nova to fix.
the requirement to have consistent time synchronisation is well know and
it strongly feels like a problem that should be address in an
installation too not in code.
we mention that the controllers should be rujing shared service like ntp in the
=> In Progress
** Changed in: nova
Importance: Undecided => Critical
** Changed in: nova
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Tags added: gate-failure
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subs
*** This bug is a duplicate of bug 2003991 ***
https://bugs.launchpad.net/bugs/2003991
this sound like you have count_usage_from_placement=true
https://docs.openstack.org/nova/latest/configuration/config.html#quota.count_usage_from_placement
in which case this is not a bug and is the intende
https://review.opendev.org/q/topic:%22bug/2003991%22
note there were bugs backport filed back to train but those branches are
now unsupproted.
** Also affects: nova/yoga
Importance: Undecided
Status: New
** Also affects: nova/xena
Importance: Undecided
Status: New
** Also af
this is a neutron bug not a nova one.
the behavior should not change between using the dhcp aganet and native
dhcp
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you ar
Public bug reported:
Long version instance actions are ment to have a start and ending
ideally one of Success or failure with the option to have intermediate
events for complex operation like resize.
For at least interface attach and detach that does not happen Possible all
instance actions th
** 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/2002400
Title:
When adding ironic compute host to an aggregate,
** 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/1542491
Title:
Scheduler update_aggregates race causes incorrect a
setting this to medium severity
there is an existing race in how the cache is updated.
the workaround is to periodically restart the scheduled to clear the cache.
this looks like it affects all stable releases of OpenStack.
however its unlikely but not impossible that a fix for this can be backpo
** Also affects: nova/bobcat
Importance: Undecided
Status: New
** Also affects: nova/antelope
Importance: Undecided
Status: New
** Also affects: nova/2024.1
Importance: Undecided
Status: New
** Changed in: nova
Importance: Undecided => Low
** Changed in: nova/an
Nova does not support internationalised hostnames so it does not support
https://www.rfc-editor.org/rfc/rfc5891
the conversion of the display name to a hostname is the best effort and
we make no guarantee of its validity for DNS.
the conversion utility is intended to produce a valid hostname name
that not the reason, rhel based distos disabel nested virt on amd by
default if i recall correctly and you have to explicitly enabled it.
its not supported on RHEL and is considered tech preview as there are several
know bugs.
intel is also not supported downstream for production workload however
** 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/2059800
Title:
Image download immediately fails when glance re
victoria.
this only applies to non-pinned vms with a numa topology i.e.
hw:mem_page_size= or hw:numa_nodes=
** Affects: nova
Importance: High
Assignee: sean mooney (sean-k-mooney)
Status: In Progress
** Tags: numa
** Changed in: nova
Assignee: (unassigned) => sean moo
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1969794
Title:
backport of the fix for bug #1947370 mak
1 - 100 of 203 matches
Mail list logo
