Public bug reported:
There are some uesless variables and parameters in
nova.api.openstack.compute.server.py and nova.compute.api.py.
nova.api.openstack.compute.server.py lines 650 except Exception as error --
except Exception
nova.compute.api.py. lines 563 remove the context parameter.
Public bug reported:
nova rescue do not actual works in a lot of situation.
Although nova rescue generate the right libvirt.xml (at least in my
opinion), the virtual machine OS do not use the rescue disk to boot. It
still use the origin disk to boot(I tested it in icehouse,Juno,Kilo).
I am not
Public bug reported:
1. Exact version of Nova
ii nova-api
1:2014.1.100+git201410062002~trusty-0ubuntu1 all OpenStack
Compute - API frontend
ii nova-cert
1:2014.1.100+git201410062002~trusty-0ubuntu1 all
Public bug reported:
Steps to reproduce:
1. Create instance
2. Shutdown instance
3. Perform resize
4. Try to start instance.
Expected behaviour: instance starts in resize_confirm state
Actual behaviour: ERROR (Conflict): Instance
d0e9bc6b-0544-410f-ba96-b0b78ce18828 in vm_state resized. Cannot
Public bug reported:
Now, after launching instance from image(create new volume), we can't
see image name in instance tables.
** Affects: horizon
Importance: Undecided
Assignee: Lawrance (jing)
Status: In Progress
--
You received this bug notification because you are a
Public bug reported:
The spec
http://specs.openstack.org/openstack/neutron-specs/specs/juno-incubator/lbaas-api-and-objmodel-improvement.html
says - If a neutron port is encountered that has many fixed_ips then a load
balancer should be created for each fixed_ip with each being a deep
Public bug reported:
nova version:
2.25.0
according the bp :
https://blueprints.launchpad.net/neutron/+spec/ml2-ovs-portsecurity
repro:
1.create a network with port_security_enabled is false, and create a sample
subnet.
2.create a port with port_security_enabled is true on this network through
Public bug reported:
the overview pie chart is so big for master branch, because we use
width: 100% , delete it
** Affects: horizon
Importance: Undecided
Assignee: Lawrance (jing)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
*** This bug is a duplicate of bug 1452312 ***
https://bugs.launchpad.net/bugs/1452312
** This bug has been marked a duplicate of bug 1452312
glance-registry process spins if rsyslog restarted with syslog logging
enabled
--
You received this bug notification because you are a member of
Public bug reported:
reproduce steps:
1. a VM A in default security group
2. default security group has rules: 1. allow all traffic out; 2. allow it self
as remote_group in
3. firstly delete rule 1, then delete rule2
I found the iptables in compute node which VM A resids didn't be reload,
and
Nova allows to live migrate multiple VMs at a time, there's no limit for
simultaneous live migrations - everything depends on use case and setup
configuration (particularly network configuration and bandwidth).
host-evacuate-live is implemented in python-novaclient, so nothing to
fix in nova.
**
Public bug reported:
Specifically, we get the following output in
cc_disk_setup.exec_mkpart_mbr:
sfdisk: --Linux option is unnecessary and deprecated
sfdisk: unsupported unit 'M'
and the manpage says:
-u, --unit S
Deprecated option. Only the sector unit is supported.
So
Public bug reported:
The ipv6 router BP
(https://blueprints.launchpad.net/neutron/+spec/ipv6-router) added a new
L3 agent config called ipv6_gateway wherein an admin can configure the
IPv6 LLA of the upstream physical router, so that the neutron virtual
router has a default V6 gateway route to
** Changed in: glance
Status: Triaged = Confirmed
** Changed in: glance
Status: Confirmed = Won't Fix
** Changed in: glance
Importance: High = Undecided
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
** Changed in: python-troveclient
Status: Fix Committed = Fix Released
** Changed in: python-troveclient
Milestone: None = 1.2.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
** Changed in: python-ironicclient
Status: Fix Committed = Fix Released
** Changed in: python-ironicclient
Milestone: None = 0.7.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
I am running a Openstack Juno on a bunch of docker containers. When my
neutron-network container reboots, neutron dhcp logs has a bunch of
015-05-28 17:49:14.629 475 TRACE neutron.agent.dhcp_agent Stderr:
'RTNETLINK answers: Invalid argument\n' 2015-05-28 17:49:14.629 475
** Summary changed:
- Sanitation of metadata label (CVE-2015-3988)
+ [OSSA 2015-009] Sanitation of metadata label (CVE-2015-3988)
** Changed in: ossa
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
nova-manage fails if instance has no flavor in sys_meta when trying to
move them all to instance_extra.
But mostly the instance_type table includes the correct information, so
it should be possible to copy it from there.
** Affects: nova
Importance: Medium
Public bug reported:
The iptables implementation of security groups includes a default rule
to drop any INVALID packets (according to the Linux connection state
tracking system.) It looks like this:
-A neutron-openvswi-od0518220-e -m state --state INVALID -j DROP
This is placed near the top of
Public bug reported:
WIth private network plugged into a router and router serving metadata:
When windows accesses metadata url, it tries to resolve mac address of it
despite of routing table that tells to go to default gateway. That is because
of nature of 169.254 which is considered local by
If this can be reproduced against 2014.1 icehouse, I would consider it
to be a critical issue for our core use case (default SSL configuration
w/ apache httpd).
** Changed in: keystone
Importance: Undecided = Critical
** Also affects: keystone/icehouse
Importance: Undecided
Status:
Public bug reported:
JSHint is throwing and error on master.
horizon/static/horizon/js/horizon.d3linechart.js: line 760, col 11,
'now' is defined but never used.
** Affects: horizon
Importance: Undecided
Assignee: Aaron Sahlin (asahlin)
Status: New
** Changed in: horizon
Public bug reported:
Instead of horizon validating the project name is unique.
I think the project name validation should be handled by Keystone. we
should just catch the Conflict error instead and display the appropriate
error msg.
Related patch:
https://review.openstack.org/#/c/175096/
**
** Changed in: keystonemiddleware
Status: Incomplete = 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/1202785
Title:
Authentication is not checked before sending
Public bug reported:
Keystone currently has the keystone_conservative profile in bandit.yaml
defined as follows:
keystone_conservative:
include:
- blacklist_functions
- blacklist_imports
- request_with_no_cert_validation
- exec_used
Public bug reported:
Bug caused by jshint complaining about unused variable 'now'.
Gate failing due to this bug, this patch fixes it.
horizon/static/horizon/js/horizon.d3linechart.js: line 760, col 11, 'now' is
defined but never used.
Public bug reported:
If not specifying description parameter on create a security group
API, an internal error happens like the following:
$ curl [..] -X POST
http://192.168.11.62:8774/v2/138c5606916a468abec3dd9371e66975/os-security-groups
-H Content-Type: application/json -H Accept:
** Also affects: oslo.messaging
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/1460652
Title:
nova-conductor infinitely
Public bug reported:
From the Admin - Hypervisor panel, I notice that the Hypervisort stats
is converted from megabyte to Gibibyte.
However, the calculation seems incorrect.
Here is my observation:
From nova CLI:
vagrant@precise64:~/devstack$ nova hypervisor-stats
Public bug reported:
Now,when backup a vm booted from volume ,the error information is:The
request is invalid.
Users don't know why.
So we can support more information like:
It's not supported to backup volume backed instance.
** Affects: nova
Importance: Undecided
Assignee:
** Changed in: nova
Status: In Progress = 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/1356737
Title:
nova backup vm should not backup those vm
32 matches
Mail list logo
