Yes, this is what I did in this (partial) backport:
https://review.opendev.org/c/openstack/networking-ovn/+/831349/
** Changed in: neutron
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to ne
adding tempest for
https://review.opendev.org/q/topic:wait_until_sshable_pingable fixes and
we will see if that fixes the things. if it does then we can remove the
nova from this bug.
** Also affects: tempest
Importance: Undecided
Status: New
** Changed in: tempest
Status: New =>
Public bug reported:
Description
The "mo-ref" in VMware is not guaranteed to be stable. It can change after a
recovery or simply un-registering and re-registering a vm. So making it stable
is often necessary for the vcenter to be able to manage vms which were "lost"
somehow.
Possi
Public bug reported:
example user-data file with jinja
## template: jinja
#!/bin/sh
{% set data_result = [] %}
{% set data_input = [1,2,3] %}
{% for i in data_input %}
{% do data_result.append(i) %}
{% endfor %}
echo results: {{data_result}} >>results.out
The following exception is thrown wh
Looking at comment #4 of this bug. So Changing its status to invalid.
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/b
Reviewed: https://review.opendev.org/c/openstack/neutron/+/831490
Committed:
https://opendev.org/openstack/neutron/commit/10caa1e101a04525559f104d651ab5b2cd8108c2
Submitter: "Zuul (22348)"
Branch:master
commit 10caa1e101a04525559f104d651ab5b2cd8108c2
Author: uchenily
Date: Wed Mar 2 08:16
Public bug reported:
Description
===
Currently create Key-pair API without actual key content returns the key
generated at server side which is formatted in ssh-rsa.
However ssh-rsa is no longer supported by default since openssh 8.8
https://www.openssh.com/txt/release-8.8
```
This rel
Public bug reported:
Recently, our CI/CD environment changed, and ipv6 was disabled by
default, which caused some unit tests to fail.
$ cat /proc/sys/net/ipv6/conf/default/disable_ipv6
0
$ tox -e py3 neutron.tests.unit.agent.linux.test_dhcp.TestDeviceManager
==
Totals
==
Ran: 8 tests in
Public bug reported:
With Kuryr, when a service of LoadBalancer type is created in kubernetes the
process is the next:
- Create a load balancer
- Associate FIP to the load balancer VIP
In busy enviroments, with HA, there may be a race condition where
the method to associate the FIP to the loadbal
9 matches
Mail list logo