Public bug reported:
Description
===
nova compute service is down.
caompute Unable to execute any server related requests.
Steps to reproduce
==
not sure, this has happend 2wice in newly deployed VM on 5th-day-operation,
there is enough disk available
stack@devstack-jan
Public bug reported:
Description
File
"/home/zuul/src/opendev.org/openstack/openstacksdk/openstack/tests/functional/examples/test_compute.py",
line 47, in test_compute
create.create_server(self.conn)
File
"/home/zuul/src/opendev.org/openstack/openstacksdk/examples/compute/
Public bug reported:
Description
===
After evacuation, when original host/node become seriveable (like nova is
running properly in host ), VM status changed in nova DB as 'SHUTOFF'
automatically from 'ACTIVE'.
This is because on nova initialization nova checks for all evacuated
instance
Public bug reported:
Description
===
A VM created as booted from volume, went to error state on reboot.
reason Volume attachment is getting deleted at Cinder side.
https://paste.opendev.org/show/bgMKY9lwrIatIJ6Acl0H/
Steps to reproduce
==
1- Create a VM.
$ openstack
Public bug reported:
This is not a bug, same PROJECT_ID const defined in many places.
ex:
fixtures/nova.py:75:PROJECT_ID = '6f70656e737461636b20342065766572'
functional/api_samples_test_base.py:25:PROJECT_ID =
"6f70656e737461636b20342065766572"
for full list, inside tests, grep for 6f70656e737
Public bug reported:
tests:
https://9d880f4dac5b6d1509a3-d490a441310dc4e25f1212d07e075dda.ssl.cf1.rackcdn.com/893744/1/check/nova-live-migration/8e97128/testr_results.html
https://291f4451bebc670e507b-a999ae1d5baedde86711d4f3bf719537.ssl.cf1.rackcdn.com/873648/23/check/nova-live-migration/8634c7c/
ects: nova
Importance: Undecided
Assignee: Amit Uniyal (auniyal)
Status: New
** Tags: low-hanging-fruit
** Changed in: nova
Assignee: (unassigned) => Amit Uniyal (auniyal)
** Tags added: low-
** Tags removed: low-
** Tags added: low-hanging-fruit
--
You received t
Public bug reported:
A live migration failure created a scenario when the volume is deleted
from the system but its BDM is present in Nova DB.
Nova does not support deleting a volume that is attached to a VM.
On rebooting Nova failed to find the volume listed as attached in DB and
the instance
Public bug reported:
here https://wiki.openstack.org/wiki/Nova/CoreTeam
below links should be updated
Last 30 Days:
https://stackalytics.com/report/contribution/nova/30
to
https://www.stackalytics.io/report/contribution?module=nova-group&project_type=openstack&days=30
Last 90 days
https://stacka
from the correct host
Verify if instance is attached to correct compute host before removing
volume connection.
** Affects: nova
Importance: Undecided
Assignee: Amit Uniyal (auniyal)
Status: New
** Tags: nova-manage
** Tags added: nova-manage
** Changed in: nova
Public bug reported:
here: https://specs.openstack.org/openstack/nova-specs/
Under nova project plans -> Priorities
https://specs.openstack.org/openstack/nova-specs/priorities/ussuri-priorities.html
...
https://specs.openstack.org/openstack/nova-specs/priorities/2023.1-priorities.html
Since Us
Public bug reported:
Description
===
launchpad links do not work from this/these pages:
https://specs.openstack.org/openstack/nova-specs/specs/wallaby/template.html
..
https://specs.openstack.org/openstack/nova-specs/specs/2023.1/template.html
ex:
https://blueprints.launchpad.net/nova/+
Public bug reported:
Description
===
VM creation from a volume with no image data should not be allowed.
Right now, we can create a bootable volume with no image, and then we can
create a VM from the volume. The VM will get created, but it won't boot as
there is no image to boot from.
Public bug reported:
In multinode devstack setup nova scheduler fails to start after reboot
Steps to reproduce
==
1 - deploy multinode devstack
https://docs.openstack.org/devstack/latest/guides/multinode-lab.html
2 - Verify all compute nodes are listed and setup is working
14 matches
Mail list logo
