Public bug reported:
I had a clean environment(code version: stable/queens), and run DB
update operations.
Step 1. First upgrade to Mitaka:
# neutron-db-manage upgrade mitaka
Result: all things runs ok, the neutron and subprojects are upgrade to
Mitaka version.
Step 2. Then runs the following c
Public bug reported:
Hello Dear team,
We have just found out, that Debian 8 and 9 's cloud-init does not
support pre-hashed passwords.
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Tea
I'm closing this Won't fix because running with the LDAP backend is a
bad approach. Use SQL, with LDAP in a domain specific back end.
** Changed in: keystone
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is s
** Also affects: glance
Importance: Undecided
Status: New
** Changed in: glance
Assignee: (unassigned) => yuqian (roger-yu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.laun
Reviewed: https://review.openstack.org/576433
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=f4729795ecfbc53ae391204726fd441ce4b462ef
Submitter: Zuul
Branch:master
commit f4729795ecfbc53ae391204726fd441ce4b462ef
Author: Vishakha Agarwal
Date: Tue Jun 19 14:21:46 2
Public bug reported:
Description
===
In nova/virt/vmwareapi/vm_util.py:
Through the code, this type of "VirtualSriov\
EthernetCard" network card can be managed.
But in fact, "VirtualSriovEthernetCard" can
not be achieved through the current code
architecture.
Steps to reproduce
==
** Description changed:
When calling ``` openstack image list ```
- The call is forwarded to OS_FEDERATION/projects rather than auth/projects,
which is deprecated. This causes it not to show all the projects in the
OpenStack federation.
+ The call is forwarded to OS_FEDERATION/projects rather
Public bug reported:
If a call to ``PUT /allocations/{consumer}`` fails, for example with a
409 Conflict due to a resource provider or inventory being concurrently
updated, the consumer record that is auto-created in the handler before
calling AllocationList.create_all() is not being cleaned up pr
pycrypto was removed from most / the main openstack projects, there are
still a few outliers, but nothing core.
** Changed in: openstack-requirements
Importance: Undecided => High
** Changed in: openstack-requirements
Status: New => Fix Released
--
You received this bug notification b
Reviewed: https://review.openstack.org/571546
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=137a6d61053fb1cfb9a0a583b5a5c0f6253c75e6
Submitter: Zuul
Branch:master
commit 137a6d61053fb1cfb9a0a583b5a5c0f6253c75e6
Author: Assaf Muller
Date: Thu May 31 14:24:00 2018 -
Reviewed: https://review.openstack.org/579436
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=54d3e7096ca3b68af3cf5f0d30f7c0949e87c6d9
Submitter: Zuul
Branch:master
commit 54d3e7096ca3b68af3cf5f0d30f7c0949e87c6d9
Author: Takashi NATSUME
Date: Mon Jul 2 13:59:19 2018 +0
Public bug reported:
Even though in Placement API microversion 1.12, we began requiring
project and user ID in the PUT /allocations request payload, the project
ID and user ID for an *existing* consumer are never actually updated.
What this means is that if you created an allocation for consumer
Public bug reported:
Introduced in these new tests:
https://review.openstack.org/#/c/540679/
They are doing a primitive dict compare with nested dicts and the keys
can be in random orders. We need to use something like
self.assertJsonEqual.
Seen here:
http://logs.openstack.org/04/523604/21/che
** No longer affects: nova/newton
--
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/1678056
Title:
RequestSpec records are never deleted when destroying an instance
Status
*** This bug is a duplicate of bug 1678056 ***
https://bugs.launchpad.net/bugs/1678056
This is already fixed, they are deleted during archive:
https://github.com/openstack/nova/commit/32fd58813f8247641a6b574b5f01528b29d48b76
** This bug has been marked a duplicate of bug 1678056
RequestSpe
Public bug reported:
This was unintentionally regressed here:
https://review.openstack.org/#/c/548934/5/placement-api-
ref/source/parameters.yaml@354
** Affects: nova
Importance: Medium
Assignee: Matt Riedemann (mriedem)
Status: In Progress
** Tags: api-ref placement
--
Yo
Public bug reported:
When calling ``` openstack image list ```
The call is forwarded to OS_FEDERATION/projects rather than auth/projects,
which is deprecated. This causes it not to show all the projects in the
OpenStack federation.
version: 2.11.1
** Affects: glance
Importance: Undecided
Public bug reported:
i am running cloud-init on commit id
c42a926ae730994f66fe87c264b65f6e4dca69a1 against a FreeBSD 10.4 Host an
getting the following stacktrace:
2018-07-02 11:40:18,158 - util.py[DEBUG]: Cloud-init v. 18.3 running 'init' at
Mon, 02 Jul 2018 11:40:18 +. Up 20.11459589 secon
Public bug reported:
Description of problem:
Horizon not able to distinguish between simple tenant and address scope
networks in Network topology tab. However in "Networks" tab it does show
the difference between simple and subnet pool network.
How reproducible:
Everytime.
Steps to Reproduce:
Reviewed: https://review.openstack.org/576161
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=8cea14abf30c40da4ce5ffcfb4fb37dd79083255
Submitter: Zuul
Branch:master
commit 8cea14abf30c40da4ce5ffcfb4fb37dd79083255
Author: Matt Riedemann
Date: Mon Jun 18 10:27:43 2018 -0
If the issue still exists with current devstack, please describe the
steps needed to reproduce.
** Changed in: devstack
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horiz
Reviewed: https://review.openstack.org/579200
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=dd4e9496d37f2bc27763926327d45df01fd08a05
Submitter: Zuul
Branch:master
commit dd4e9496d37f2bc27763926327d45df01fd08a05
Author: Chris Dent
Date: Fri Jun 29 16:38:43 2018 +0100
Public bug reported:
Afaics Nova breaks with Qemu versions newer than the minimum required
version.
The change at [1] added support for setting MTU size in the libvirt settings of
guests. This code checks for a minimum libvirt version 3.3.0 [2] but not for a
required Qemu version.
The Nova mini
Public bug reported:
Placement allows setting the parent_rp_uuid of an RP to itself. This
leads to a trivial loop in the RP tree.
Version, current master:
stack@ubuntu:~/nova$ git log --oneline | head -n1
4ea64ca Merge "manage: Remove dead code"
To reproduce in devstack I used a not yet merged
Public bug reported:
Currently there are no logic in nova to clean the request_spec logic even when
the instances related to it are gone.
This will lead to the request_specs table in nova_api DB grows continuously.
** Affects: nova
Importance: Undecided
Assignee: Zhenyu Zheng (zhengzhe
25 matches
Mail list logo
