[Expired for cloud-init because there has been no activity for 60 days.]
** Changed in: cloud-init
Status: Incomplete => Expired
--
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/17
[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
https://review.openstack.org/#/c/480031/
** Changed in: tap-as-a-service
Importance: Undecided => Critical
** Changed in: tap-as-a-service
Status: New => Fix Released
** Changed in: tap-as-a-service
Assignee: (unassigned) => SUZUKI, Kazuhiro (kaz-kaz)
--
You received this bug no
Reviewed: https://review.openstack.org/579058
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=f5f682c63a043d59388731d78fae98481685019e
Submitter: Zuul
Branch:master
commit f5f682c63a043d59388731d78fae98481685019e
Author: Yasuhiro Kimura
Date: Fri Jun 29 14:19:02 201
Reviewed: https://review.openstack.org/575444
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=54aa6e81cb17b33ce4d5d469cc11dec2869c762d
Submitter: Zuul
Branch:master
commit 54aa6e81cb17b33ce4d5d469cc11dec2869c762d
Author: Miguel Lavalle
Date: Thu Jun 14 09:21:09 2018
By referring to the multiple ipv6 prefixes spec [1], it is intentional
to include all the stateless IPv6 addresses into the port. The current
implementation seems to be correct. In addition, you can look at this
bug [2], in which people was complaining that neutron was not picking
all the SLAAC add
I'm re-opening this task for MAAS, as a user has been able to reproduce
this issue in a different context. While there's a work-around on
comment #22, the situation is that even when the same network
configuration sent for xenial and bionic deployments is the same, the
configuration differs, due to
** Also affects: tripleo
Importance: Undecided
Status: New
** Changed in: tripleo
Status: New => Triaged
** Changed in: tripleo
Importance: Undecided => Critical
** Changed in: tripleo
Milestone: None => rocky-3
--
You received this bug notification because you are a me
Reviewed: https://review.openstack.org/581346
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=83e72d74431526b27b8a2f4ac362582a73edea44
Submitter: Zuul
Branch:master
commit 83e72d74431526b27b8a2f4ac362582a73edea44
Author: Sami MAKKI
Date: Tue Jul 10 14:21:28 2018 +0
The KeyError is coming from python-novaclient, not nova, so I'm going to
mark this Invalid for nova and add python-novaclient to this bug.
** Changed in: nova
Status: New => Invalid
** Also affects: python-novaclient
Importance: Undecided
Status: New
--
You received this bug no
Public bug reported:
I978fdea51f2d6c2572498ef80640c92ab38afe65 /
https://review.openstack.org/#/c/565604/ added placement microversion
1.28, which made various API operations consumer generation-aware. One
of the affected routes was /resource_providers/{u}/allocations - but
this route wasn't cover
Public bug reported:
AllocationList.delete_all() looks like this:
```
def delete_all(self):
# Allocations can only have a single consumer, so take advantage of
# that fact and do an efficient batch delete
consumer_uuid = self.objects[0].consumer.uuid
_delete_al
I've confirmed this with a devstack setup that this was fixed indirectly
in pike with change https://review.openstack.org/#/c/446053/.
** Changed in: nova
Status: In Progress => Fix Released
** Changed in: nova
Assignee: Matt Riedemann (mriedem) => Dan Smith (danms)
--
You received
Public bug reported:
This is semi-related to bug 1497253 but I found it while triaging that
bug to see if it was still an issue since Pike (I don't think it is).
If you run devstack with default superconductor mode configuration, and
configure nova-cpu.conf with:
[cinder]
cross_az_attach=False
Public bug reported:
Problematic Situation:
1 check the hosts visible to nova compute
nova hypervisor-list
id hypervisor hostname state status
xx compute2 upenbled
2 check the hosts visible to cellv2
nova-manage cell_v2 list_hosts
cell name cell uuid hostname
cell
Public bug reported:
ENV:
neutron: stable/queens 12.0.2
$ uname -r
3.10.0-862.3.2.el7.x86_64
$ sudo ovs-appctl vlog/list
consolesyslogfile
-------
backtrace OFFDBG INFO
...
ALL-app OFFDBG I
Public bug reported:
It maybe occur KeyError flavor when nova boot vm
# nova --debug boot vm --image image-id --flavor flavor-id --nic net-
id=id
It will show vm's information, but it return Error like that:
DEBUG (session:419) RESP: [202] Content-Length: 462 Location:
controller:8774/v2.1/7fc
Public bug reported:
While using IKE policy with version v2, the IPsec siteconnection status
always down, but the network traffic is OK.
>From the ipsec status we can see that the ipsec connection is
established:
# ip netns exec snat-a4d93552-c534-4a2c-96f7-c9b0ea918ba7 ipsec whack --ctlbase
/v
18 matches
Mail list logo
