Public bug reported:
Currently we use socket.getshostname() to determine the heyervisor
hostname assuming that is what is used in libvirt.
However libvirt actually ues the following steps to generate hypervisor
hostname and socket.gethostname() doesn't match in some cases.
/* Who knew getting a
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
Public bug reported:
Right now, the IDL connections between ml2/ovn are not resilient
enough when connecting. It doesn't make sense to give up on that
since the ml2/ovn is useless w/out that access.
If ovsdb-server is slow and takes more than timeout seconds, everything
reconnecting after partial
Reviewed: https://review.opendev.org/c/openstack/neutron/+/787681
Committed:
https://opendev.org/openstack/neutron/commit/9911d414c6a03cbdcc5f46a9ed7cfc59d70a5168
Submitter: "Zuul (22348)"
Branch:master
commit 9911d414c6a03cbdcc5f46a9ed7cfc59d70a5168
Author: Rodolfo Alonso Hernandez
Date:
Public bug reported:
Designate tempest plugin patches keep failing because of: "neutron-
tempest-plugin-designate-scenario" Neutron gate
For example:
https://review.opendev.org/c/openstack/designate-tempest-plugin/+/773477
>From Gate's log:
2021-04-29 14:29:32.979245 | controller | all run-test-
You have been subscribed to a public bug:
Designate tempest plugin patches keep failing because of: "neutron-
tempest-plugin-designate-scenario" Neutron gate
For example:
https://review.opendev.org/c/openstack/designate-tempest-plugin/+/773477
>From Gate's log:
2021-04-29 14:29:32.979245 | contr
Volume multiattach is clearly marked as an unsupported feature within
the ironic driver [1] so I'm marking this as invalid. If you would like
to add support please raise a blueprint and/or spec [2].
[1]
https://github.com/openstack/nova/blob/91e53e4c2b90ea57aeac4ec522dd7c8c54961d09/nova/virt/iron
As the LOG requests please attach the stack trace from the logs. Based
on the exception type "AccessRefused" I suggest to check your AMQP
credentials in your service config.
I'm setting this to Invalid. If you still see the problem after double
checked your credentials then please provide more log
I've added cinder and os-brick here as AFAICT this isn't a Nova issue
given the description in c#0 and logs in c#1.
The attempt by Cinder to retype the detached volume doesn't appear to
have encrypted anything.
This might be the result of another issue in os-brick when connecting
the volume to th
The information is moved to
https://docs.openstack.org/nova/latest/admin/sev.html
Setting this to Invalid. If you disagree then please set it back to new.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Public bug reported:
Context:
- Openstack Victoria deployment
- Separate ceph pools for Cinder volumes and Nova VMs.
- Trying to rescue a volume-backed instance with --image parameter.
The rescue disk is not even created in the VMs pool, so the instance is
put into ERROR because of the following
17 matches
Mail list logo
