[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs
Reviewed: https://review.opendev.org/c/openstack/neutron/+/881943
Committed:
https://opendev.org/openstack/neutron/commit/c0af5b3b5ea89d3147adf1054625f29d5b01b309
Submitter: "Zuul (22348)"
Branch:master
commit c0af5b3b5ea89d3147adf1054625f29d5b01b309
Author: Felix Huettner
Date: Wed Mar 1
Public bug reported:
This isn't really a bug in nova, but it's something that we're hitting
in CI quite a bit, so I'm filing here to record the details and so I can
recheck against it. The actual bug is either in the guest (cirros 0.5.2)
kernel, QEMU, or something similar. In tests where we attach
Yes, there is nothing we can do with this, and it's 7 years old, moving
to invalid.
** Changed in: glance
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs
I have no idea how to reproduce that, and it's 7 years old, I'll move to
invalid.
** Changed in: glance
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1599553
Public bug reported:
Summary.
We use neutron ml2/ovs plugin. Version of neutron is Ussuri. We set config
option use_random_fully=false.
After reboot neutron-l3-agent only one router configured without iptables
option "--random-fully" in SNAT configuration, all other routers, including
newly cre
Public bug reported:
My cloud provider is Linode (Akamai) https://www.linode.com/
While I have to particular issue, I get:
This message at login, asking me to report error:
Last login: Thu May 4 09:03:42 2023 from 104.158.25.145
**
Public bug reported:
Example commandd affected: openstack network qos rule type list
Several qos test case are skipped due to this chanmge beahavior because:
(Pdb) p cls.os_tempest.network_client
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1816210
T
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Triaged
** Changed in: cloud-init
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscrib
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Triaged
** Changed in: cloud-init
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscrib
cc_ntp.py allows for configuring timesyncd and provides defaults for
each distro. This was addressed in https://bugs.launchpad.net/cloud-
init/+bug/1749722
** Changed in: cloud-init
Status: Confirmed => Fix Released
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Release
This was implemented in https://github.com/canonical/cloud-
init/pull/114/files
** Changed in: cloud-init
Status: Triaged => Fix Released
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
--
13 matches
Mail list logo
