Public bug reported:
List resource type associations. Erroneous Response Example.
** Affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.n
** Also affects: cinder
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1560965
Title:
libvirt selects wrong root device name
Reviewed: https://review.openstack.org/525842
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=2200b1c3697a478af9f25a20ce09564bc2c9a968
Submitter: Zuul
Branch:master
commit 2200b1c3697a478af9f25a20ce09564bc2c9a968
Author: zhsun
Date: Wed Dec 6 08:53:55 2017 +0800
** Changed in: glance/liberty
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/1537626
Title:
`glance location-update` deletes locations and backend images
St
Public bug reported:
Description
===
Currently we have a large number of rows in our nova databases, which
will greatly benefit from `nova-manage archive_deleted_rows` (thanks!).
What we would like to do is to archive all deleted records before a
certain time (say >1 year ago). This will
Public bug reported:
In our environment we have multiple sites, each with their own flat
provider networks. We also have a centralised neutron-server, but each
site runs their neutron-dhcp-agent service.
I've been looking to upgrade some networks to MTU 9000, keeping others
as is. What I want to
Public bug reported:
Description
===
instance_group_members record also exist in database after delete vm
Steps to reproduce
==
1:create affinity instance_group
2:create vm
3:delete vm
Actual result
=
Database changed
MariaDB [nova_api]> select * from instan
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Released
--
You
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Released
--
You
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
** Changed in: cloud-init
Status: In Progress => 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/1751145
Title:
release 18.1
Status in cloud-init:
Fix Released
Public bug reported:
This bug simply tracks release of cloud-init 18.1.
Below is the complete set of changes between 17.2 and 18.1.
- OVF: Fix VMware support for 64-bit platforms. [Sankar Tanguturi]
- ds-identify: Fix searching for iso9660 OVF cdroms. (LP: #1749980)
- SUSE: Fix groups used fo
Reviewed: https://review.openstack.org/540073
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=ee2f65d91fb632f04be3572967029cd58be4c614
Submitter: Zuul
Branch:master
commit ee2f65d91fb632f04be3572967029cd58be4c614
Author: Surya Seetharaman
Date: Thu Feb 1 18:56:10 2018
I think the issue is:
a.) there is no default locale set in the subiquity installed system.
b.) python3 subprocess is doing a 'decode' for each argument in the
command list.
python2 default encoding *is* supposed to be based on the environment [1],
but python3 default encoding is not. python3 is
** Changed in: maas
Importance: Undecided => Low
** Changed in: maas
Status: Invalid => 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/1750884
Title:
[2.4, bionic]
Public bug reported:
Add a statement to the install guide that Glance does not currently
support deployment under uwsgi.
** Affects: glance
Importance: Medium
Assignee: Brian Rosmaita (brian-rosmaita)
Status: Triaged
** Tags: documentation
** Changed in: glance
Importance
This bug was fixed in the package glance - 2:16.0.0~rc3-0ubuntu1
---
glance (2:16.0.0~rc3-0ubuntu1) bionic; urgency=medium
* New upstream release candidate for OpenStack Queens (LP: #1750705).
-- James Page Thu, 22 Feb 2018 14:46:15 +
** Changed in: glance (Ubuntu)
S
The enabled_apis in nova are fixed for interoperability reasons. There
is only one nova compute API.
If you want to run another API, then you should do so like the ec2 or
GCE proxies, e.g.:
https://github.com/openstack/gce-api/blob/master/gceapi/cmd/api.py#L34
You can run your own service and ad
Including in rc3 so uploading that to bionic now.
** Changed in: glance
Status: New => Fix Released
** Changed in: glance (Ubuntu)
Milestone: None => ubuntu-18.02
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
Public bug reported:
Upstream Linux kernel has removed[*] the 'perf cqm' (Cache
Quality-of-Service Monitoring) from the following kernels onwards:
[linux]$> git tag --contains c39a0e2
v4.14
Impact for OpenStack / Nova
---
Quoting the summary from Dan Berrangé f
Public bug reported:
In Queens release, neutron-vpnaas-agent has gone and the vpnaas feature
is now implemented as l3-agent extension.
Looking at the VPNaaS release notes, there is no information in Queens [1].
vpnaas-agent change is an important topic and it should be documented in the
release
This bug was fixed in the package openvswitch - 2.8.1-0ubuntu0.17.10.2~cloud0
---
openvswitch (2.8.1-0ubuntu0.17.10.2~cloud0) xenial-pike; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
openvswitch (2.8.1-0ubuntu0.17.10.2) artful; urgency=medium
.
* d/p/dpif-k
Public bug reported:
In an environment with an ldap server as identity backend, if a group
with no members has a role on a project, if you try to resolve the
memberships on a specific project it will throw an exception.
This is caused as when searching from members in a group in LDAP, if it
does
Public bug reported:
I was testing subiquity, and at the user creation prompt typed in "André
D'Silva" for the username, and just "andre" for the login.
The installer finished fine, but upon first login I couldn't login.
Booting into rescue mode showed me that the user had not been created.
Chec
Public bug reported:
In an environment with an ldap server as identity backend, if a group is
deleted out-of-band, the role assignment entry cannot be deleted as it
checks for the existence of the group in the backend.
Therefore the assignments on groups cannot be deleted.
There is already a par
Public bug reported:
Currently [1] resource extensions are asked to retrieve all attributes when
calling resource_extend.
This poses some problems:
- Extensions need to gather all attributes for the resource they extend
- ML2 mechanism drivers cannot make a difference between list and show of a
Public bug reported:
After the upgrade of our OpenStack Cloud infrastructure from Newton to Pike,
the following error has appeared:
Traceback (most recent call last):
File "/usr/bin/nova-api", line 10, in
sys.exit(main())
File "/usr/lib/python2.7/site-packages/nova/cmd/api.py", line 44, in main
Well, the post-live-migration action actually needs to update the
scheduler in order to modify its view of the existing instances, hence
why it calls the message queue.
If you restarted the nova-scheduler while the live-migration was in
progress, that's why you got that MQ exception... If you want
That's not really a bug, right ? It's more about asking to have a new
possibility for resize, hence what we call a feature.
Please rather see
https://docs.openstack.org/nova/latest/contributor/process.html#overview
about our process, and create a new blueprint if you want so.
** Changed in: nova
Public bug reported:
Seen in log:
2018-02-22 07:20:11.940 10009 INFO bgpspeaker.peer [-] Connection to peer:
fd40:9dc7:b528:80::3 established
2018-02-22 07:20:11.942 10009 INFO
neutron_dynamic_routing.services.bgp.agent.driver.ryu.driver [-] BGP Peer
0.0.0.82 for remote_as=65001 is UP.
Expect
This bug was fixed in the package open-vm-tools - 2:10.2.0-3ubuntu1
---
open-vm-tools (2:10.2.0-3ubuntu1) bionic; urgency=medium
* d/open-vm-tools.service: Add After=local-fs.target dependency ensuring
filesystems are ready to fix a race on startup (LP: #1750780)
-- Christian
Public bug reported:
FAIL:
neutron_lbaas.tests.unit.drivers.haproxy.test_jinja_cfg.TestHaproxyCfg.test_render_template_https
neutron_lbaas.tests.unit.drivers.haproxy.test_jinja_cfg.TestHaproxyCfg.test_render_template_https
--
_St
Public bug reported:
While building the neutron-lbaas package in Debian Sid with Python 3.6,
I get the below failure. As this looks like a broken test rather than a
software bug, I've disabled running the unit test at package build time,
however, it'd be nice to have it fixed.
FAIL:
neutron_lbaa
Public bug reported:
While building the neutron-lbaas package in Debian Sid with Python 3.6,
I get the below failure.
FAIL:
neutron_lbaas.tests.unit.drivers.radware.test_v2_plugin_driver.TestLBaaSDriverRestClient.test_recover_was_called
neutron_lbaas.tests.unit.drivers.radware.test_v2_plugin_dri
Public bug reported:
While building the neutron-lbaas package in Debian Sid with Python 3.6,
I get the below failure. As this looks like a broken test rather than a
software bug, I've disabled running the unit test at package build time,
however, it'd be nice to have it fixed.
My wet finger doubl
Public bug reported:
There are duplicated logs records in cloud-init logs with default
logging configuration.
Default logging configuration is used (via tee)
output: { all: "| tee -a /var/log/cloudinit/cloudinit.log" }
In the attached cloudinit.log duplicated logs starts from line 314:
WARN: n
1. I updated the ppa we test for a potential xenial-backport.
It now has 10.2.0-3ubuntu0.16.04.1~ppa2 with the fix applied
2. Pushed said fix to Bionic [1] (need to check proposed migration)
3. reported the same to Debian, but then found [2] and chimed in there
[1]: https://launchpad.net/ubun
56 matches
Mail list logo
