Public bug reported:
By set config ovn.enable_distributed_floating_ip, we can set whether the
floating IP of the entire cluster is distributed or centralized.
There is no way to set a floating IP separately, and the flow of floating IP
cannot be finely controlled.
If the backend is ovn, we can
Public bug reported:
AgentCache method update[1] has a parameter "updated_at", I didn't find this
parameter passed in anywhere except for some unit tests. currently we have used
nb_cfg_timestamp[2] as agent updated time. there are no other scenarios for
this parameter.
can we remove this parame
The evacuate API states:
Preconditions
The failed host must be fenced and no longer running the original
server.
The failed host must be reported as down or marked as forced down
using Update Forced Down.
So when you detect the control network failure you have to make sure
that the host
** Also affects: designate-dashboard
Importance: Undecided
Status: New
** No longer affects: designate
** Changed in: designate-dashboard
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to O
Thanks for the info, I'll re-assign to Nova component based on that.
** Project changed: neutron => nova
--
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/1977485
Title:
N
I agree that deducing hostname from display name is problematic.
Therefore I don't think we should further complicate the logic currently
in place. But instead move away from it. I suggest to provide the
hostname specifically with the hostname field in the POST /servers REST
API request. I suggest
This issue was fixed in the openstack/glance 24.1.0 release.
** Changed in: glance/yoga
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1972666
Public bug reported:
Error: https://paste.openstack.org/show/814826/
Method: "OVNClient._handle_lb_fip_cmds"
Seems that the section handling the load balancer members is incorrectly
indented.
** Affects: neutron
Importance: Undecided
Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
Reviewed: https://review.opendev.org/c/openstack/neutron/+/843253
Committed:
https://opendev.org/openstack/neutron/commit/e09b128f416a809cd7734aba8ab52220ea01b2e2
Submitter: "Zuul (22348)"
Branch:master
commit e09b128f416a809cd7734aba8ab52220ea01b2e2
Author: Henning Eggers
Date: Wed May 2
Public bug reported:
Hi!
We have some user-data files where we use the phone-home module of cloud-init.
So far we did not use it's "tries" parameter and everything worked.
However now in version 22.2 there was a change which causes cloud-init to fail.
https://github.com/canonical/cloud-init/comp
10 matches
Mail list logo