.
** Affects: nova
Importance: Medium
Assignee: sean mooney (sean-k-mooney)
Status: Triaged
** Tags: libvirt pci vdpa
** Tags added: libvirt pci vdpa
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
: Undecided
Assignee: sean mooney (sean-k-mooney)
Status: Invalid
** Tags: libvirt live-migration pci
** 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 Comp
This is not a bug.
we intentionally do not provide any device ordering guarnetees.
this has been requested several times in the past however we cannot provide
this enverant since
libvirt does not guretee the addresses it will assign will be stable and the
behavior is not portable across differe
based on our irc meeting we determin we do not have enough info to fully triage
this form our side since we don't know the image
types that are in use when you careted the VM and snapshots vs uploaded an
image directly.
i suspect the issue is that the snapstho is a shallow image create by a dir
This is not a bug it is user error.
when using hugepages if you want to have non hugepage guests on the same host
then you must use
hw:mem_page_size=small or hw:mem_page_size=4k for all non hugepages guests
we do not support memory oversubscriton when using hw:mem_page_size and
this also makes t
im settign this to opipion for now since this seam to be distro-specific
we have confirmed that this can happen on fedora 36 but we have also confirmed
that
3.10 work on debian and nixos and we have ci jobs running non voting unit test
on 3.10 on ubuntu 22.04
so in general this does not appear
we can discuss deprecating the unscoped support or the filter in general
as we now have better alternatives such as
https://docs.openstack.org/nova/latest/reference/isolate-aggregates.html
but given the upgrade impact this would need a deprecation cycle at a
minium to notify operators that they w
as noted by matt this is a known issue/design choice that was made when
implementing the AggregateInstanceExtraSpecsFilter
we generally discourage using this filter for usecases that can be addressed by
the isolated aggregates feature.
https://docs.openstack.org/nova/latest/reference/isolate-agg
this was fixed by
https://github.com/openstack/nova/commit/d13412648d011994a146dac1e7214ead3b82b31b
** 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 (no
dge need to enable it via the new config option
** Affects: nova
Importance: Critical
Assignee: sean mooney (sean-k-mooney)
Status: In Progress
** Affects: os-vif
Importance: Critical
Assignee: sean mooney (sean-k-mooney)
Status: Triaged
** Tags: gate-failure neutron
**
ged 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.
https://bugs.launchpad.net/bugs/1980948
Title:
adapt ci to neutron making linux bridge exp
** Changed in: nova
Status: Incomplete => Invalid
** Changed in: neutron
Status: Opinion => 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/1982373
Title:
nova/neut
** Also affects: nova/wallaby
Importance: Undecided
Status: New
** Also affects: nova/xena
Importance: Undecided
Status: New
** Also affects: nova/yoga
Importance: Undecided
Status: New
** Also affects: nova/victoria
Importance: Undecided
Status: New
** A
this is not a bug
the meaning of host_subset_size = 4 is that after the weighers prepare
the sorted set we should take a random selection from the first 4 in the list.
by setting host_subset_size = 4 you have opted into randomising the top
4 results.
this config option is intended for use in la
nova does not supprot updating the host name in neutron via updates to the
hostname of the vm.
what is actually being updated in the tempest test is the display_name
the display name (after normalisation) is used as the initial value for the
instance.hostname
instance.hostname is what is passed
** Also affects: nova/trunk
Importance: Undecided
Status: New
** Changed in: nova/zed
Status: Fix Released => In Progress
** Changed in: nova/trunk
Status: New => Fix Released
** Changed in: nova/trunk
Assignee: (unassigned) => Thomas Goirand (thomas-goirand)
** Cha
Public bug reported:
2022-10-03 03:23:33.868 21 ERROR neutron.agent.l3.agent [-] Failed to process
compatible router: edf1cc99-879a-4fe5-a7b2-d19acb8fdcbf:
neutron.privileged.agent.linux.ip_lib.InterfaceOperationNotSupported: Operation
not supported on interface qg-4bb9d20b-a0, namespace
qrout
config.d/02-nova-secret.conf,"
we can do all three or any one of them to enable the usecase of
supporting config directories although only the first option allows
other command line args to be passed.
** Affects: nova
Importance: Medium
Assignee: sean mooney (sean-k-mooney)
Public bug reported:
This is a tracking rfe bug to enable the use of the OpenStack SDK when
calling neutron.
This is in aid of allowing neutron to deprecate and eventually remove
neutron client in a future release by removing novas dependency on it.
** Affects: nova
Importance: Wishlist
Public bug reported:
the current help text for the config option is as follows
heal_instance_info_cache_interval¶
Type
integer
Default
60
Interval between instance network information cache updates.
Number of seconds after which each compute node runs the tas
This is not really unexpected.
nova like most opesntack service depends on rabbit being reliable and if
a RPC is lost then thinks can break.
fixing that is not in scope fo nova.
it would require a fundamental reacatecure to introduced tasks and track state
to allows us to resend messages if we
s
ned) => sean mooney (sean-k-mooney)
** Changed in: nova/xena
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Changed in: nova/yoga
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Changed in: nova/zed
Assignee: (unassigned) => sean mooney (sean-k-moon
** Also affects: placement
Importance: Undecided
Status: New
** Changed in: placement
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 Compute (n
Public bug reported:
if a network vif plugged events times out in resize confirm the VM will enter
an error state.
if the VM is not using numa then a hard reboot should be enough to fix that.
if it has a numa toplgoy the instnace_numa_topogy and flavor can disagree on
the number of vcpu requeste
it is explcitly not supproted.
we intoduced the condocutor to make sure that nova compute agents do not
have db access directly.
** 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
This sounds like a issue with your networking configuration.
nova is not involved in any data copy for live migration (ram or disk)
its entirely handled by libvirt and qemu.
the libvirt live_migration_bandwidth is a maximum limit on how much bandwidth
can be used by libvirt/qemu to do the data t
Nova does not impos any limits on the mig profiles or mdev types that
can be used.
this is a hardware limitation of the nvida gpus not a nova limitation.
you are using A100 which does support using more then one type but only
on specific types which they have documented in there product docs.
if
im torn between considering this a wishlist bug or a feature request.
i think this is related perhaps to the resource provider mapings
with this configuration
[devices]
enabled_vgpu_types = nvidia-474,nvidia-475,nvidia-476
[vgpu_nvidia-474]
device_addresses = :61:00.4,:61:01.0
[vgpu_nvid
did you mean to file this to cinder.
or did you file this for disk quota in the flavor
https://github.com/openstack/nova/blob/master/nova/api/validation/extra_specs/quota.py#L149-L167
i assume for the first link
https://docs.openstack.org/cinder/latest/admin/basic-volume-qos.html
that this sh
this is a supported workflow.
its actully quite common for windows as you will create a VM and boot form an
iso with an attached data volume
then you will delete the VM and boot a second VM form the volume
so image_metadata is not required on a volume
** Changed in: nova
Status: New => I
** 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/2011127
Title:
Nova scheduler stacks allocations in heterogeneou
nova raised its min qemu version to 4.0.0 in Ussuri.
As such this should be supported in all nova deployment from Ussuri on but it
is still blocked on master today.
** Affects: nova
Importance: Undecided
Assignee: sean mooney (sean-k-mooney)
Status: New
** Tags: cinder li
setting this to invlaid for nova as multiple attempt to work around the
issue have show we cannot fix it in nova.
** Changed in: nova
Importance: Medium => High
** Changed in: nova
Status: Triaged => Invalid
** Also affects: libvirt via
https://bugzilla.redhat.com/show_bug.cgi?id=20
as of
https://github.com/openstack/nova/commit/73f1fda7e93325d3ca2b2c62afb17fe011d650f3
this is now fix in nova 20.0.0.0rc1
the osls.service issue was fixed in release 1.40.1
** Changed in: nova
Status: In Progress => Fix Released
** Changed in: oslo.service
Status: In Progress =>
dom number generator
in the refactor the code to add the rng was added to the code for adding the
qemu guest agent and as a result it would only be added if botht the rng and
qemu guest agent are both enabled.
** Affects: nova
Importance: Medium
Assignee: sean mooney (sean-k-mooney)
i miss read the indentation
_add_rng_device was only called form _set_qemu_guest_agent
but it was called uncondtionally as was _set_qemu_guest_agent
so it actully was working just hard to follow
** Changed in: nova
Status: Triaged => Invalid
--
You received this bug notification because
** 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/1691178
Title:
virt_type=qemu does not support cpu affinity.
the reporting of a devcice type is based on the capablity of the device
not its current sate
virsh # nodedev-dumpxml pci__04_00_0
pci__04_00_0
/sys/devices/pci:00/:00:02.0/:04:00.0
pci__00_02_0
vfio-pci
0
4
0
0
MT27710 Family [Connect
mplemented/libvirt-virtio-set-queue-sizes.html
** Affects: nova
Importance: Low
Assignee: sean mooney (sean-k-mooney)
Status: Triaged
** Tags: libvirt live-migration
** Description changed:
- While addressing https://bugs.launchpad.net/nova/+bug/1847367 &q
** Also affects: nova/train
Importance: Undecided
Status: New
** Changed in: nova/train
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.
Public bug reported:
while developing https://review.opendev.org/#/c/689861
i observed that test_rebuild_server_with_network_affinity
https://review.opendev.org/#/c/689861/8/nova/tests/functional/libvirt/test_numa_servers.py@838
asserted that rebuild would fail after the numa policy required by th
t/hardware.py:1920:29: F821 undefined name 'List'
nova/virt/hardware.py:1939:31: F821 undefined name 'Set'
while this is not an issue today because we pin to an old version of
flake8 we should still fix this just as a code hygiene issue. given this
has no impact on the running cod
this goes back to when the feature was intoduced but this was reported
against a centos/rhel host on rocked and release before queens will be
out of support in a week or so, as such there is likely no point in
going back further then queens. i don't think this issue will be present
on other distros
Public bug reported:
The versioned notifications for image metadata properties are out of sync with
the
nova.objects.image_meta.ImageMetaProps object.
this bug tracks fixing that and adding a test to keep them in sync going
forward.
** Affects: nova
Importance: Low
Assignee: sean
.
** Affects: nova
Importance: Low
Assignee: sean mooney (sean-k-mooney)
Status: Triaged
** Affects: nova/queens
Importance: Low
Status: Triaged
** Affects: nova/rocky
Importance: Low
Status: Triaged
** Affects: nova/stein
Importance: Low
** Changed in: neutron
Status: New => Invalid
** 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/1859976
Title:
Re
Public bug reported:
moving all legacy jobs to zuul v3 native jobs is a cycle goal.
in the ussuri cycle we have already had several issue with the nova live
migration job
such as compressed logs, distutils conflict and other failures caused by
change in devstack the only impact legacy job.
to th
Public bug reported:
when using the cpu_share_set cpu_dedicated_set or
vcpu_pin_set(deprecated) it would be nice to be able to use a ter
syntax.
currently we support negated ranges
so on a 4 core host you can set
^0-1,0-3 and the result will be {2,3}
it would be nice to be able to just set "^0
the current logic is incorrectly and expoing the host pci adress in the
metadata not the vitual guest adress
while one might think this is a security issue it is not as the host adress is
already exposed to the end user via the neutron port profile. as such this does
not represent a new informat
Public bug reported:
During development of the cyborg integration with nova the patch that
Delete ARQs for an instance when the instance is deleted
Icb95890d8f16cad1f7dc18487a48def2f7c9aec2 failed to do so in some cases
as noted in
https://review.opendev.org/#/c/673735/46/nova/conductor/manager.p
regarding the VM Resumimg before the 'brctl addif'.
the libvirt xml we generate contains the name of the linux bridge the tap
should be added
too. so the linux bridge agent does not need to actully do the brctl addif
command.
the tap should already be a member of that bridge when the vm is resum
setting this back to invalid.
there is a seperate bug for resize
https://bugs.launchpad.net/nova/+bug/1805969
this was previously marked as invalid because there was no clear
repoduce or the issue and we have other bug tracking various edge case
so let not keep this open as that has not been adr
Public bug reported:
Description
===
over the last few cyles supprot for mtu other then the default of 1500 has
gernerally been improved in both nova and neutron.
At the same time it was decided to remove the responsibility for VIF plugging
from
the virt drivers and centrailse it in os-vi
Public bug reported:
Description
===
The hw_disk_bus image metadata key
https://github.com/openstack/glance/blob/master/etc/metadefs/compute-libvirt-image.json#L13-L27
allows users to specify the bus to which guest hard disk images are attched for
libvirt instances.
The valid values of h
** Changed in: nova
Status: In Progress => Fix Released
** 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/1632372
Tit
This has been discused several times in the last few releases.
the original spec did not mandate that we invent a numa toploygy
of 1 when we request cpu pinning however it did not forbid it.
The current behavior is specific to the libvirt dirver and while it could
legally be changed without violat
)
Click on extra options for the following:
** Affects: neutron
Importance: Undecided
Assignee: sean mooney (sean-k-mooney)
Status: New
** Changed in: neutron
Assignee: (unassigned) => sean mooney (sean-k-mooney)
--
You received this bug notification because you ar
va-compute[14852]:
Aug 14 12:15:27 devstack1 nova-compute[14852]:
* Version:
** OpenStack version: Rocky RC1, neutron sha:
1dda2bca862b1268c0f5ae39b7508f1b1cab6f15, nova sha:
afe4512bf66c89a061b1a7ccd3e7ac8e3b1b284d
** Linux distro, Centos 7.5
** DevStack
* Perceived severity: low (migr
Public bug reported:
Description
===
While testing livemigration between ovs and ovs-dpdk on centos 7.5 i encountered
a qemu internal error the resulted in the qemu monitor closeing.
when the migration failed during the virDomainMigrateToURI3 it
rolled back the migration leaving the vm ru
Public bug reported:
* Summary: neutron does not form mesh tunnel overly between different
ml2 driver.
* High level description: When using multiple neutron ml2/driver it is expected
that vms on host with different ml2 backend should be able to comunicate as
segmentatoin type/ids are centralise
Public bug reported:
Description
===
live migartion between compute nodes of different distors
fails due to asstion that the emulator path on dest is
the same as the source compute node. In past releases
it was acidentally posable to migrate between ubuntu and centos
host because the qem
172.25.0.10:208] raise TypeError("this TransactionFactory is already
started")
46104 [Wed Oct 10 15:10:49.433473 2018] [:error] [pid 14] [remote
172.25.0.10:208] TypeError: this TransactionFactory is already started
** Affects: nova
Importance: Medium
Assignee: se
the max tx queue lentgh value that is supported by qemu is 1024
seting it to 1 will not help.
thisbug does not specify what netwrok backend is being used but i will assume
you are using
kernel ovs. on thing you could do is to enable multiqueue support.
see:
https://specs.openstack.org/open
i have not looked into this closely but my guess is this could be related to
the arp suppression rules
used in the dvr case not being updated correctly that said it is just a guess
so there may be something more going on here.
eric can you try doing a hard reboot of the migrated instance and see
i would set this to hi but since it has been unaddress ince 2016 and no one has
been screaming about it
im setting it to low.
** Changed in: nova
Status: Opinion => Confirmed
** Changed in: nova
Importance: Wishlist => Low
--
You received this bug notification because you are a membe
ion of OpenStack you are running.
master but i belive this will be broken on queens and rocky too.
2. Which hypervisor did you use?
libvirt kvm.
2. Which storage type did you use?
N/a cinder lvm and default libvirt image backend
3. Which networking type did you use?
N/A openvswitch
ng-ip/snat translation or routing will
be dropped.
** Affects: nova
Importance: High
Assignee: sean mooney (sean-k-mooney)
Status: Confirmed
** Tags: libvirt sriov
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscrib
this is not a but at least not as reported.
free_ram_mb is not ment to be equal to the free value of "free -m"
memory_mb is 4047 and memory_mb 4096
as a result the total amount of memery that you have acounted against
guests is 49 mb more then the avalible ram
so free_ram_mb which is caluate
** Changed in: os-vif
Status: Fix Committed => Fix Released
** Changed in: neutron
Status: In Progress => Fix Committed
** 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 s
as per my comment
https://review.openstack.org/#/c/629646/4/nova/scheduler/filters/numa_topology_filter.py@103
we cannont skip valdiating the numa toplogy of a host on rebuild as the image
can alter the guest numa toplogy.
if we rebuilt with the same image we skip going back to the schduler so
t
not that ip_allocation=None was originally not supported intentornally
due to security concerns.
it was declared out of scope in
https://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/neutron-routed-networks.html#proposed-change
i personaly am not confrotable treating this as
-vif
Status: New => Confirmed
** Changed in: os-vif
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Changed in: os-vif
Importance: Undecided => High
** Tags added: ovs
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
solution considerations
option one has the advantage of confining the change change to os-vif.
option two is the correct approach long term as it dose not require any config
change on upgrade.
option three is a compromise as while we do not need to make any change on
upgrade we cannot hanel
the
=
nova reports libvirt error that cpu affinity is not support by TCG
backend.
** Affects: nova
Importance: Undecided
Assignee: sean mooney (sean-k-mooney)
Status: New
** Changed in: nova
Assignee: (unassigned) => sean mooney (sean-k-mooney)
--
You received t
Public bug reported:
when using standard kernel ovs it may be desirable for performance reasons to
use an ovs based security group driver.
When using ovs with dpdk it is not possible to use a kernel(ip tables) based
security driver.
one effort leveraging the newly added kernel connection tracke
Undecided
Assignee: sean mooney (sean-k-mooney)
Status: New
** Changed in: nova
Assignee: (unassigned) => sean mooney (sean-k-mooney)
** Description changed:
- with certain version of iproute2 spawning of vm with vhost-user ports will
fail do to a
+ with certain version of ipro
only changes required to extent the ovs agent to suport
the netdev datapath.
documentation and unit tests will be provided to cover these changes.
a new job can be added to the intel-networking-ci to continue to validate this
configuration if additional 3rd party
testing is desired.
** Affects
stuser_socket'
# - vif_type_vhost_user: vif type to enable use of the qemu vhost-user vif
VIF_TYPE_VHOST_USER = 'vhostuser'
# default location for vhostuser sockets
VHOSTUSER_SOCKET_DIR = '/var/run/openvswitch'
** Affects: neutron
Importance: Undecided
Ass
will enabled extension of bind_port to support other port types
such as vhost-user in a separated patch-set to networking-odl without
requiring further changes to the front end component in neutron.
** Affects: networking-odl
Importance: Undecided
Assignee: sean mooney (sean-k-mooney
/
** Affects: neutron
Importance: Undecided
Assignee: sean mooney (sean-k-mooney)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1485788
Title
the auto generation behavior that created this bug has been removed by
https://review.openstack.org/#/c/40296/
marking as invalid as neutron no longer generates tables from sql
alchemy models.
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification be
marking as invalid as the bug cannot be reproduced.
please reopen if this is still an issue for you and you can provide more info
on how to recreate.
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
: Undecided
Assignee: sean mooney (sean-k-mooney)
Status: New
** 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 Compute (nova).
ht
Public bug reported:
using master horizon it is currently not possible
to boot and instance form a glance image without
allocating a cinder volume.
this prevent horizon from booting an instance if cinder is not deployed.
to reproduce on the launch instance screen go to the source tab
and select
reconnect
automatically to the backend e.g. a vswitch without requiring
the vm to reboot.
** Affects: neutron
Importance: Undecided
Assignee: sean mooney (sean-k-mooney)
Status: In Progress
** Tags: rfe
** Changed in: neutron
Assignee: (unassigned) => sean mooney (sean-k-moo
across a cluster.
Patch
===
initial patch submitted for review
https://review.openstack.org/#/c/95138/1
** Affects: neutron
Importance: Undecided
Assignee: sean mooney (sean-k-mooney)
Status: New
** Changed in: neutron
Assignee: (unassigned) => sean mooney (s
** 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 neutron.
https://bugs.launchpad.net/bugs/1236621
Title:
Disable H803: git commit title should not end with peri
Public bug reported:
Problem description
===
In the Open vSwitch neutron agent, ip_lib is currently used to list the
bridges.
as userspace only vswiches do not create bridge local ports in the kernel
ip_lib will not correctly detect the bridge configuration.
Proposed Change
===
Public bug reported:
tempest.api.network.test_ports.PortsTestJSON.test_update_port_with_second_ip
faild due
to a deadlock in the db.
the trace below from the q-svc screen log appears to be very similar to
a similar open bug in the cinder project which suggest that this class
of intermitent dead
nova provides 2 ways to configure which CPU can be used by vms
you can use the legacy vcpu_pin_set
https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.vcpu_pin_set
or the preferred cpu_share_set and cpu_dedicated_set to specify which
CPU nova will use
https://docs.openstack.
From a nova process point of view, this is a minor feature, not a bug. so we
need to track this as a specless blueprint.
in general I'm supportive of the enhancement but we need to track this properly
upstream.
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug
** 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).
https://bugs.launchpad.net/bugs/1869804
Title:
Live migration with cpu_shared_set not updatin
** Also affects: openstacksdk
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/2089030
Title:
Sdk does not call manila with use
im not going to mark this as invliad but introducing a distribute lock
manger to nova i think would require a spec.
its a very heavy weight solution to enabling a topology we do not
officially support today.
today we require that if the period is enable then its only enabled in
one scheduled isnt
ok os repoducing this locally using
https://review.opendev.org/c/openstack/oslo.utils/+/937037
the error is
[18:59:29]➜ python3 -m oslo_utils.imageutils.format_inspector
../flatcar-stable-4081.2.0-kube-v1.30.1.img.raw
inspecting file: ../flatcar-stable-4081.2.0-kube-v1.30.1.img.raw
detected fi
that not eeactly correct.
wether its https://controller/identity"; or http://controller:5000/identity
depend on how you install keystone, what port its on and if your using tls.
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member
so that is not supproted.
i think we do attpath to abort any ongoing live migration that have not proceed
to post live migrate
but we generally cant complete any that have entered post-live-migrate.
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because
resartign the comptue service while any rpc action (*live migration,
spawn any other operation) is not supported by nova.
if you take that action then you violate all pre and postcontion of
ongriong operations.
we can try and minimise the impact of this but its not a goal of nova to
make restarti
This is a feature request not a bug.
ephemeral diskss are examplty that.
from an API point of view its expected that data on ephmerl disks will
be lost if you evacuate the instance or on some other move operations.
** Changed in: nova
Importance: Undecided => Wishlist
** Changed in: nova
. This will lead to undefined behavior and is
obviously a bug. When run under other wsgi servers config errors cause
the hosting python interpreter to exit, this is not the behavior of
mod_wsgi.
** Affects: nova
Importance: Medium
Assignee: sean mooney (sean-k-mooney
101 - 200 of 213 matches
Mail list logo
