** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
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/1846535
Title:
cloud-init 19.2.36 fails with python
*** This bug is a duplicate of bug 1846535 ***
https://bugs.launchpad.net/bugs/1846535
Public bug reported:
cloud-init was recently updated to 19.2-36-g059d049c-0ubuntu1~18.04.1
this update has broken bond and bridge configuration in MAAS. static and
DHCP configuration do not seem to be
Reviewed: https://review.opendev.org/684854
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=654c1f06d583965c4b5a2ae721a7b1f3786dc76a
Submitter: Zuul
Branch:master
commit 654c1f06d583965c4b5a2ae721a7b1f3786dc76a
Author: Erik Olof Gunnar Andersson
Date: Wed Sep 25
Public bug reported:
- [x] This doc is inaccurate in this way:
This came up in review:
https://review.opendev.org/#/c/685927/2//COMMIT_MSG@9
https://docs.openstack.org/api-ref/compute/#show-server-details
and
https://docs.openstack.org/api-ref/compute/#list-servers-detailed
response
Public bug reported:
I installed a fresh openstack test cluster in eoan today (October 3).
Neutron database initialization with the command:
sudo su -s /bin/sh -c "neutron-db-manage
--config-file /etc/neutron/neutron.conf
--config-file /etc/neutron/plugins/ml2/ml2_conf.ini
upgrade head"
** Also affects: horizon (Ubuntu Eoan)
Importance: Undecided
Status: New
--
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/bugs/1840465
Title:
Fails to list
** Also affects: horizon (Ubuntu)
Importance: Undecided
Status: New
** Also affects: horizon (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: horizon (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because
*** This bug is a duplicate of bug 1840465 ***
https://bugs.launchpad.net/bugs/1840465
Has been backported to Rocky so should not be hard to get this into
Queens. I will mark this as a duplicate of 1840465 and we can use that
bug to request the backport to Q.
** This bug has been marked a
** Changed in: neutron
Status: Invalid => New
** Description changed:
- Neutron version: 9.4.1 (EOL, but bug may still be present)
+ Neutron version: 10.0.7
Network scenario: Openvswitch with DVR
Openvswitch version: 2.6.1
- OpenStack installation version: Newton
+ OpenStack
Public bug reported:
- [x] This doc is inaccurate in this way:
This came up during a review to remove nova-net usage from functional
tests and enhance the neutron fixture used in those tests:
https://review.opendev.org/#/c/685927/2/nova/tests/functional/test_servers.py@1264
In summary, GET
(changed kolla-ansible params so that launchpad does not hide it from
me)
** Changed in: kolla-ansible
Status: Opinion => Triaged
** Changed in: kolla-ansible
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Public bug reported:
Method `nova.volume.cinder.API#create` accepts `size` as the 3rd args,
but in wrapper of `nova.volume.cinder.translate_volume_exception`, the 3rd
parameter is volume_id. If we hit cinder exception when creating volumes
like the response body down below:
```
{"itemNotFound":
Public bug reported:
Symptoms
After deployment of Ubuntu Bionic image on MAAS provider (deploying to a
bare metal server) juju cannot access any deployed machine due to
missing SSH keys and machines are stuck in pending state:
$ juju ssh 0
ERROR retrieving SSH host keys for "0": keys
Public bug reported:
This came up in the mailing list while answering some questions about
when/how various cells v2 and database related commands get run:
http://lists.openstack.org/pipermail/openstack-
discuss/2019-October/009937.html
Recent change https://review.opendev.org/#/c/671298/ was
Public bug reported:
user-data can also be provided via kernel cmdline params to the NoCloud
datsource. It probably is worth exposing at least a link to
https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html#nocloud
on the user-data formats top-level page
Public bug reported:
i have create a virtual machine using the following official debian
image: https://cdimage.debian.org/cdimage/openstack/current-10/
they have version 18.3-6 installed.
after the initial boot of the vm cloud-init works as it should. but when
a reboot occurred it seems to be
Public bug reported:
Integration tests on Eoan are failing on the lxd and nocloud kvm
platforms. In both cases the test system is not reachable via SSH.
LXD log: https://paste.ubuntu.com/p/r2hwqZQfm2/
KVM log: https://paste.ubuntu.com/p/W3N22yBxKN/
This failure mode began with the test run of
Public bug reported:
This has been observed while testing CI IPv6.
ovs-agent tries to run VXLAN over IPv6 (default port so 4789)
linux bridge provides network for CI hosts using VXLAN over IPv4 using standard
port (the 4789)
kernel bound to IPv4-only UDP 0.0.0.0:4789
ovs-agent:
2019-10-02
Notifying neutron so that they may shed some light on this observation.
** Changed in: kolla-ansible
Status: Triaged => Opinion
** Changed in: kolla-ansible
Importance: Wishlist => Undecided
** Description changed:
This has been observed while testing CI IPv6.
ovs-agent tries
Public bug reported:
I got two problems connected to IPv6 and neutron-openvswitch-agent
(Queens version of Openstack, Ubuntu 18.04):
The first problem:
The default value of "of_listen_address" is 127.0.0.1
(/etc/neutron/plugins/ml2/openvswitch_agent.ini).
When I changed it to its IPv6
** Changed in: plainbox-provider-certification-server
Status: Fix Committed => Fix Released
--
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/1819994
Title:
cloud-init selects
21 matches
Mail list logo
