This bug was fixed in the package keystone - 2:13.0.2-0ubuntu3
---
keystone (2:13.0.2-0ubuntu3) bionic; urgency=medium
* d/p/0002-fixing-dn-to-id.patch: Dropped. This patch shouldn't have
been backported to stable/queens (LP: #1850634).
-- Corey Bryant Wed, 30 Oct 2019
This bug was fixed in the package keystone - 2:13.0.2-0ubuntu3
---
keystone (2:13.0.2-0ubuntu3) bionic; urgency=medium
* d/p/0002-fixing-dn-to-id.patch: Dropped. This patch shouldn't have
been backported to stable/queens (LP: #1850634).
-- Corey Bryant Wed, 30 Oct 2019
Reviewed: https://review.opendev.org/695453
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=49964bdc649bab88813fdcd34a2e54616057ac8d
Submitter: Zuul
Branch:master
commit 49964bdc649bab88813fdcd34a2e54616057ac8d
Author: Matt Riedemann
Date: Thu Nov 21 10:11:28 2019
This was merged as is live, so marking fix released.
** Changed in: cloud-init
Status: Triaged => 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/1827021
Title:
Public bug reported:
the vendor data documentation:
https://cloudinit.readthedocs.io/en/latest/topics/vendordata.html
describes that we can override or disable vendor data, but does not explain how.
this might be causing some confusion…?
related?
Public bug reported:
Description
===
Performing rebuild of a vm with a different image passes when the images have
different cpu_threads_policy defined in image metadata, when it should fail
Steps to reproduce
==
1. Create two images, one with
Hi Vasili,
>From a cloud-init perspective, there isn't anything we can do so I'm
going to move the upstream task to Invalid too. I'm afraid I don't
really have any advice on how to proceed, as this appears to be a
hypervisor or cloud issue.
Dan
** Changed in: cloud-init
Status: New =>
You mean the VNC server(s) that are created on the compute hosts for
their instances? Those are not supposed to be publically accessible.
Access to those is done via the consoles API [1] which provides an
authentication token to the client. The client the connects to the
publically-facing console
Hello, thanks for the feature request.
Unfortunately, it is very unlikely that someone will work on it (unless
you yourself chose to do so), so I'm going to close this bug in order to
set realistic expectations. If you want to work on this yourself, please
file a blueprint.
** Changed in: nova
** Changed in: cloud-archive
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1782922
Title:
LDAP: changing user_id_attribute
** Changed in: nova
Status: Confirmed => Invalid
--
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/1858877
Title:
Silent wasted storage with multiple RBD backends
Patches to neutron-tempest-plugin, SDK and OSC also got merged, so I'd consider
this thing finished.
https://review.opendev.org/679833
https://review.opendev.org/680384
https://review.opendev.org/679834
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug
Reviewed: https://review.opendev.org/702026
Committed:
https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=a363edd761e2c99bae6d4492d0ca44a404e5d904
Submitter: Zuul
Branch:master
commit a363edd761e2c99bae6d4492d0ca44a404e5d904
Author: Rodolfo Alonso Hernandez
Date:
13 matches
Mail list logo
