[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).
Public bug reported:
Cloud Vendor: Amazon AWS
Platform: RHEL7.6
Cloud-Init: cloud-init-18.5-3.el7.x86_64
Kernel: 3.10.0-1062.el7.x86_64
SELinux: selinux-policy-targeted-3.13.1-252.el7.1.noarch
--
We have identified an issue where SELinux labeling appears to be
conflicting with
** Also affects: nova/stein
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Changed in: nova/rocky
Assignee: (unassigned) => Takashi NATSUME (natsume-takashi)
** Changed in: nova/queens
Assignee: (unassigned) =>
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Assignee: (unassigned) => Takashi NATSUME (natsume-takashi)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
** Changed in: charm-neutron-openvswitch
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1832021
Title:
Checksum drop of metadata traffic on
Reviewed: https://review.opendev.org/633616
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=78e382c3a5e84fa838d1ede8c49bab515150a7dd
Submitter: Zuul
Branch:master
commit 78e382c3a5e84fa838d1ede8c49bab515150a7dd
Author: nicolas
Date: Mon Jan 28 14:45:43 2019 -0800
Public bug reported:
[Problem]
When mutliple network interfaces are present in a CloudStack VM, cloud-init
randomly chooses the gateway address to fetch the metadata from. This is not a
problem when all network interfaces offer metadata. However, if a shared
network interface is attached to
Public bug reported:
There are some tests, mostly related to BuildRequest objects, that are
calling nova.objects.base.obj_equal_prims which does not assert
anything, it only returns True or False - the test code itself must
assert the expected result of the obj_equal_prims method.
** Also affects: horizon
Importance: Undecided
Status: New
** Changed in: horizon
Status: New => Confirmed
** Changed in: horizon
Assignee: (unassigned) => Ivan Kolodyazhny (e0ne)
** Changed in: horizon
Importance: Undecided => Medium
** Changed in: python-cinderclient
Cloud-init is the one performing the resize and MAAS images are based
off the Ubuntu cloud images, it is more an issue with cloud-init and the
cloud images than MAAS.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Invalid
--
Public bug reported:
The "Instance Metadata" documentation [1] describes nicely, how to use Jinja in
cloud-config templates as well as shell scripts.
It states that the first line must be
> ## template: jinja
But only after reading the code, I found out that parsing only happens,
when the MIME
12 matches
Mail list logo
