Reviewed: https://review.openstack.org/577751
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=a558eb0baba05280747ea67556e1041e86898ef3
Submitter: Zuul
Branch:master
commit a558eb0baba05280747ea67556e1041e86898ef3
Author: wangxiyuan
Date: Mon Jun 25 15:45:33 2018
Reviewed: https://review.openstack.org/579618
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=00b13a2e2fab6e9a9635c4df186269a16d9fbfbd
Submitter: Zuul
Branch:master
commit 00b13a2e2fab6e9a9635c4df186269a16d9fbfbd
Author: Balazs Gibizer
Date: Mon Jul 2 15:21:17 2018
Reviewed: https://review.openstack.org/536243
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=2bca6431e69bf2c6e657736b7fe11f5a2fbb9433
Submitter: Zuul
Branch:master
commit 2bca6431e69bf2c6e657736b7fe11f5a2fbb9433
Author: shuangyang.qian
Date: Mon Jan 22 15:55:14 2018
Public bug reported:
I have installed stable/queens 17.0.5 using openstack-ansible on Ubuntu
with ODL.
When i reboot compute node, instances go in shut off state.
Log in /var/log/nova/nova-compute.log:
2018-07-04 10:00:58.496 5519 ERROR nova.virt.libvirt.host libvirtError:
Failed to connect
[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).
Public bug reported:
When we deploy OpenStack by using devstack and enable FW v1 in
local.conf "enable_service neutron-fwaas-v1", deploying process is
successful, but when we create FW instance, instance will stuck in
"PENDING_CREATE" status forever, I found a related bug
Reviewed: https://review.openstack.org/499908
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=006113e3bfd566f3b394580262a60345eec160d6
Submitter: Zuul
Branch:master
commit 006113e3bfd566f3b394580262a60345eec160d6
Author: Reedip
Date: Fri Sep 1 06:20:01 2017 +
Public bug reported:
The resource tracker (in n-cpu) used to be the only place we were
pushing changes to placement, all funneled through a single mutex
(COMPUTE_RESOURCE_SEMAPHORE) to prevent conflicts.
When we started mirroring host aggregates as placement aggregates [1],
which happens in the
Public bug reported:
cpu-topologies documentation should contain configuration for emulator
threads policy. There currently is no mention of how to configure this
feature: https://github.com/openstack/nova/blob/master/doc/source/admin
/cpu-topologies.rst
** Affects: nova
Importance:
** Changed in: tripleo
Status: Fix Committed => Fix Released
--
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/1773449
Title:
VM rbd backed block devices
This bug was fixed in the package nova - 2:18.0.0~b2-0ubuntu2
---
nova (2:18.0.0~b2-0ubuntu2) cosmic; urgency=medium
* d/control: Drop circular dependencies. nova-compute depends on
nova-compute-* packages. nova-compute-* packages shouldn't depend
on nova-compute.
Reviewed: https://review.openstack.org/576025
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=209462c90d44df7bf58fd3786887047adefdc22b
Submitter: Zuul
Branch:master
commit 209462c90d44df7bf58fd3786887047adefdc22b
Author: wangxiyuan
Date: Mon Jun 18 11:39:31 2018
Public bug reported:
when a project is deleted, its limits should be purged as well.
** Affects: keystone
Importance: Undecided
Assignee: wangxiyuan (wangxiyuan)
Status: New
** Changed in: keystone
Assignee: (unassigned) => wangxiyuan (wangxiyuan)
--
You received this
** Changed in: nova
Assignee: Balazs Gibizer (balazs-gibizer) => Matt Riedemann (mriedem)
** Changed in: nova
Status: Confirmed => Triaged
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
This bug was fixed in the package keepalived - 1:1.3.9-1ubuntu1
---
keepalived (1:1.3.9-1ubuntu1) cosmic; urgency=medium
* d/p/fix-removing-left-over-addresses-if-keepalived-abort.patch:
Cherry-picked from upstream to ensure left-over VIPs and eVIPs are
properly removed on
Public bug reported:
Keystone supports the ability for service users to validate expired user
tokens. This solved an issue where a user would initiate a long-running
operation (e.g. live migration, instance back-ups, uploading large
images to glance), and by the time the operation finished the
Public bug reported:
When attempting to delete a port on a system with 1K ports, it takes
around 35 seconds to complete:
$ time openstack port delete port60_2
real0m34.367s
user0m3.497s
sys 0m0.187s
Log is *full* of the following messages when I issue the CLI:
Public bug reported:
Erasure coded pools for rbd have been supported since the ceph
luminous release. To use this feature the erasure coded pool where
the data will be held needs to be specified during image creation.
The rbd_pool option still needs to point to a replicated pool where
a small
Public bug reported:
No image description field with Angularized panel.
Steps to reproduce:
1. Create image
2. Try to set some description for it using horizon
3. Check out the full information about this image
Expected result:
Description field has been updated
Actual result:
No description
Public bug reported:
In case if evacuation or rebuild fails there is a possibility to have more than
one records for a failed evacuation in 'accepted' state.
At the same time, _destroy_evacuated_instances() in
nova.compute.manager.ComputeManager performs db query in assumption that there
is
As reported by Xav in https://bugs.launchpad.net/ubuntu/+bug/1731595:
"Comment for the folks that are noticing this as 'fix released' but
still affected - see
https://github.com/acassen/keepalived/commit/e90a633c34fbe6ebbb891aa98bf29ce579b8b45c
for the rest of this fix, we need keepalived to be
Reviewed: https://review.openstack.org/579615
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=ac9acce283a28326c6f9af4a158e6f3c1e09db45
Submitter: Zuul
Branch:master
commit ac9acce283a28326c6f9af4a158e6f3c1e09db45
Author: Matt Riedemann
Date: Mon Jul 2 11:50:18 2018
Since this bug is already marked as fix released for the cloud-archive,
let's please track this issue in the following bug:
https://bugs.launchpad.net/ubuntu/+bug/1744062
** No longer affects: keepalived (Ubuntu)
** No longer affects: keepalived (Ubuntu Xenial)
** No longer affects: keepalived
** No longer affects: keepalived (Ubuntu Zesty)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1731595
Title:
L3 HA: multiple agents are active at the same time
Status in Ubuntu Cloud
** Also affects: keepalived (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: keepalived (Ubuntu Artful)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1731595
Public bug reported:
im using the copr repo for cloud-init on centos 7.
i tested the latest 18.2 version cloud-init-18.2+5.g01ff5c2e-1.el7.centos.noarch
and the nightly build from yesterday for the 18.3 version.
both have the problem that if i use package_update package_upgrade for
example apt
Public bug reported:
Blueprints hide-hypervisor-id-flavor-extra-spec and add-kvm-hidden-feature
allow hiding KVM's signature for guests, which is necessary for Nvidia drivers
to work in VMs with passthrough GPUs.
While this works well for linux guests on KVM hypervisors, it doesn't work for
Public bug reported:
When deleting the image of an instance of the SHELVED_OFFLOADED state
and then executing the unshelve instance operation, the unshelve
instance fails, but there is no corresponding error message in the fault
table of the target instance.
You can reproduce the bug by
** Changed in: tempest
Status: Won't Fix => In Progress
--
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/1631872
Title:
Not all neutron ports are ACTIVE after the
Public bug reported:
Description
===
You can update a resource provider(old root RP)'s parent RP from None to a
specific existing RP(original root RP).
But if the resource provider(old root RP) has a child RP, the child RP's root
RP is not updated automatically to the new root RP.
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
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
32 matches
Mail list logo
