Public bug reported:
Description
===
Libvirt uses swtpm_ioctl to shutdown the swtpm process at VM termination,
because QEMU does not send shutdown command.
However the binary is not included in the required binaries (swtpm and
swtpm_setup, at the time of writing) checked by libvirt drive
Public bug reported:
Description
===
Currently libvirt driver ensures any of swtpm_setup and swtpm is present for
vTPM support.
However libvirt requires BOTH of these to setup and run swtpm.
Steps to reproduce
==
* Deploy nova-compute with swtpm support
* Remove swtpm_se
Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/nova/+/908536
** Changed in: nova
Status: Opinion => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https:
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
Public bug reported:
Hi community,
When you type:
$ watch openstack nova compute service list
You will see the status of components such as "nova-conductor", "nova-
scheduler" and "nova-compute" continuously jump between "up" and "down",
this is not normal and it has absolutely no end. This happ
Public bug reported:
Hi,
I have 46 isolated cpus in my server. I have made grub entry for that
isolcpus=2-47. I have configured cpu_dedicated_set=6-47 and cpu_shared_set=0-5.
But hypervisor is showing 8 vcpus and when I am assigning cpus (the flavor also
has cpu_policy=dedicated) to an instance
Reviewed: https://review.opendev.org/c/openstack/neutron/+/908255
Committed:
https://opendev.org/openstack/neutron/commit/4df5f2f41baede43b3e87ff8b716a7e6c773fbea
Submitter: "Zuul (22348)"
Branch:master
commit 4df5f2f41baede43b3e87ff8b716a7e6c773fbea
Author: Rodolfo Alonso Hernandez
Date:
Public bug reported:
Attempting to run the 'attach interface' action on an instance in
Horizon results in an error message.
This error is specific to one project in Horizon and does not occur in
other projects or with the OpenStack client.
Openstack Version is Zed
The error message:
[Tue Feb 0
This issue was fixed in the openstack/requirements yoga-eom release.
** Changed in: nova/yoga
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).
https://bugs.launchpad
Public bug reported:
Hello everyone, I am currently using OpenStack 2023.1 (Antelope) on my test
environment. I followed the instructions for install and am now having problems
creating the instances.
I am currently at the following step in the OpenStack instructions.
"Lauch the Instance | Ste
10 matches
Mail list logo
