Public bug reported:
When we try to delete a security group, unnecessary query is running to
update the resource of the security group which we are deleting.
Example: At the time of delete operation 'quotausages' table is being updated
by resource (security_group_rule) which are not available
Public bug reported:
communication from a vm without floating-ip to another vm with floating-ip
doesn't work in dvr-multinode setup. [1]
see the result of tempest test cases. [2]
the same test is working well for midonet [3] and linuxbridge. [4]
[1]
Public bug reported:
Description
===
When I is ready to install [nova-placement-api], I find that not detailed
document describe how to install and configure [nova-placement-api].
Steps
=
When I have installed [nova-compute], I found many *WARNNING* logs. eg:
WARNING
Reviewed: https://review.openstack.org/470016
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=527468be33407d65a940f1cd1e7a5a0bbbe12795
Submitter: Jenkins
Branch:master
commit 527468be33407d65a940f1cd1e7a5a0bbbe12795
Author: Ihar Hrachyshka
Date:
Public bug reported:
When I set the rule below:
[
{
"local": [
{
"user":{
"name":"{0}"
}
},
{
"group": {
"id":"c59d9770089b4d5aaa893973bbcfb538"
}
}
],
Public bug reported:
This issue seemed be fixed in https://bugs.launchpad.net/nova/+bug/1693010.
But it has not been fixed yet.
http://logs.openstack.org/47/460847/5/check/gate-nova-specs-docs-ubuntu-
xenial/e4e669b/console.html
2017-06-01 23:31:09.904757 | Running Sphinx v1.6.2
(snipped...)
Public bug reported:
In the Pike cycle there were some refactoring to the DVR db classes and
resource handler mixin.
This lead to the regression where it was not creating the SNAT namespace for
the DVR routers if it has gateway configured.
The only namespace seen was the fipnamespace.
This
Reviewed: https://review.openstack.org/466414
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=d8334b41d2c5bcd4916347d20008b1538d48b0ef
Submitter: Jenkins
Branch:master
commit d8334b41d2c5bcd4916347d20008b1538d48b0ef
Author: Felipe Reyes
Public bug reported:
cloud-init master
Testing bridging configuration. First, empty subnets break sysconfig
rendering; this has been reported in other bugs), after that, the
resulting ifcfg-br0 does not include the static network configuration.
Upon closer examination the
Workaround for now would be to use anything other than a '.' as
delimiter. The server freaks out when it sees one in tags.
** Changed in: python-neutronclient
Importance: Critical => Low
** Also affects: neutron
Importance: Undecided
Status: New
** No longer affects:
Public bug reported:
cloud-init master using net-convert, we can see that the bond
configuration is not complete with the following input network
configuration
% cat bonding.yaml
network:
version: 1
config:
- type: physical
name: interface0
mac_address:
This bug was fixed in the package nova - 2:14.0.5-0ubuntu1
---
nova (2:14.0.5-0ubuntu1) yakkety; urgency=medium
[Saverio Proto]
* New upstream point release for OpenStack Newton (LP: #1688557).
[Corey Bryant]
* SECURITY UPDATE: Failed notification payload is dumped in logs
Reviewed: https://review.openstack.org/469231
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=73701bf75b964509c7d7e8b62dba97f7cbe9c87a
Submitter: Jenkins
Branch:master
commit 73701bf75b964509c7d7e8b62dba97f7cbe9c87a
Author: Ihar Hrachyshka
Date:
Public bug reported:
Trying to use this feature on newton,
https://specs.openstack.org/openstack/nova-specs/specs/mitaka/implemented/libvirt-real-time.html
Is low latency (realtime) kernel a requirement?
Anyway, I'm using 4.4.0-78-lowlatency now, following failed
(It worked if I manually copy
Public bug reported:
Steps to reproduce:
- Login as admin
- Go to admin settings
- Set "Item Per Page" to 2
- Create a volume if no volumes are present
- Create 3 snapshots of a volume via dropdown menu
- Go to "Volume" -> "Snapshots" tab
Expected result:
-Button "Next>>" is displayed
Actual
** Changed in: cloud-archive/newton
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/1673411
Title:
config-drive support is broken
Status
** Changed in: nova
Status: Invalid => Incomplete
--
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/1694417
Title:
dhcp_domain used when use_neutron is not set
Looks like this was fixed:
https://github.com/openstack/nova/commit/eb22047abd80f218f009a1df169a3e4695558790
** Changed in: nova
Status: New => Fix Released
** Changed in: nova
Importance: Undecided => High
** Changed in: nova
Assignee: (unassigned) => Davanum Srinivas (DIMS)
use_neutron defaults to True, so you don't need to explicitly set it in
nova.conf to be using neutron. The dhcp_domain option is deprecated
since the Ocata release as it's only used for nova-network, which it
sounds like you're not using.
I think there is a misunderstanding here about how things
https://docs.openstack.org/cli-reference/glance-property-keys.html
should be updated with the new image metadata property.
** Also affects: openstack-manuals
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Invalid
--
You received this bug notification
Going to need more details about this. What is the recreate scenario?
What type of instance is it - is it volume-backed or using nova local
disk (ephemeral)?
Are there errors in the nova-compute logs during the snapshot? Are there
errors in the Glance logs? Is a snapshot image created in glance
Public bug reported:
Quick Overview
==
OpenStack is already running with networks and instances created.
Port security extension is not enabled.
When enabling port_security, instances in old networks not get DHCP.
Instances in new networks work fine.
Bug Description
===
Public bug reported:
Description
===
I resize an instance and revert it, it works correctly, but when I resize this
instance again, the instance set to error, and I check the compute log like
below.
I use the rbd backend, I think the reason should be like this, If instance use
shared
*** This bug is a duplicate of bug 1681989 ***
https://bugs.launchpad.net/bugs/1681989
** This bug has been marked a duplicate of bug 1681989
the deletion of the instance does not release the memory quota for vram
--
You received this bug notification because you are a member of Yahoo!
24 matches
Mail list logo