** Also affects: nova
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/1316926
Title:
failed to reach ACTIVE status and task st
Public bug reported:
So in the process of converting certain test case from using an instance
dict to a fake instance object, I noticed the following:
self.instance_object.config_drive = False
self.assertFalse(self.instance_object.config_drive) # Fails
The reason the config_drive attribute
Public bug reported:
In http://developer.openstack.org/api-ref-compute-v2-ext.html, the
'disabled_reason" field will be None for xml format and 'null’ for json
format. However, in the documentation, it's stated as "", which is not
correct.
Below is the output of nova client:
yjiang5@otccloud06
Public bug reported:
Cinder returns a response including 'x-openstack-request-id' in the HTTP
response header when nova calls cinder.
But nova cannot output 'x-openstack-request-id' to the log( if the call is
successful).
If nova outputs 'x-openstack-request-id' to the log, it will enable us to
Public bug reported:
Control Node: 101.0.0.20(also has compute service , but do not use it)
Compute Node: 101.0.0.30
nova version:
2014.1.b2-847-ga891e04
in control node nova.conf
allow_resize_to_same_host = True
and
in compute node nova.conf
allow_resize_to_same_host = False
detail:
1. boot a
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
Public bug reported:
check_env method for extension descriptor is not documented or used.
** Affects: neutron
Importance: Undecided
Assignee: YAMAMOTO Takashi (yamamoto)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering T
According to
http://docs.openstack.org/trunk/openstack-ops/content/security_groups.html:
All projects have a "default" security group, which is applied to instances
that have no other security group defined. Unless
changed, this security group denies all incoming traffic.
The fact that
Public bug reported:
The Big Switch servermanager records the consistency hash to the
database every time it gets updated but it does not retrieve the latest
value from the database whenever it includes it in an HTTP request. This
is fine in single neutron server deployments because the cached ver
Public bug reported:
The consistency watch dog is calling the wrong method for a health check
which is raising an exception. However, since it is in a greenthread,
the exception is silently discarded so the watchdog dies without any
indication.
** Affects: neutron
Importance: Undecided
Sorry to bother you :)
The problem is on line 72 of
http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config-user-groups.txt
I'm not too familiar with bzr, but I assume that this is the trunk version, so
it's not fixed.
Please see also the attached diff fi
Public bug reported:
This keystone change [1] failed with an error in the
tempest.api.compute.servers.test_delete_server.DeleteServersTestXML.test_delete_server_while_in_attached_volume
test in the gate-tempest-dsvm-full job.
Here's the log:
http://logs.openstack.org/45/84945/13/gate/gate-tempes
Public bug reported:
The openvswitch agent will try to construct veth pairs with names longer
than the maximum allowed (15) and fail. VMs will then have no external
connectivity.
This happens in cases where the bridge name is very long (e.g. int-br-
bonded).
** Affects: neutron
Importance:
** Also affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1303856
Title:
please mark a volume as read-only
Public bug reported:
This test boots two server almost at the same time (starting the second
instance before 1 first active),
waits until both server is ACTIVE.
Than creates the first snapshot create:
http://logs.openstack.org/32/97532/3/check/check-tempest-dsvm-full/ae1f95a/logs/screen-n-cpu.tx
Public bug reported:
very, very minor nitpick.
It may be a personal preference, but I would like to see the order of
the columns show 'Used | Total' instead of vice versa.
Right now in the Hypervisors table, the columns are:
Hostname | Type | VCPUs (total) | VCPUs (used) | RAM (total) | RAM
(us
Reviewed: https://review.openstack.org/98263
Committed:
https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=76ed427ca17fb271974b4882c0b5e3c18ed3d889
Submitter: Jenkins
Branch:master
commit 76ed427ca17fb271974b4882c0b5e3c18ed3d889
Author: Mathieu Gagné
Date: Thu Jun 5 16:50:4
Public bug reported:
If booting from a volume, the virt driver does the setup of the volume
with cinder before starting the instance. This differs from the attach
volume case, which is managed by nova itself. Since the connect
operation could yield new details in the connection_info structure that
Public bug reported:
The consistency header is included in the full topology sync which
requires special-casing on the backend to ignore. It should just removed
the header since it's a full sync that replaces all of the data anyway.
** Affects: neutron
Importance: Undecided
Status:
Public bug reported:
The Big Switch full topology synchronization function isn't including
all of the information about a network. It's only including the ports
and floating IP addresses. The subnets are missing as well as the tenant
of the network.
** Affects: neutron
Importance: Undecided
Public bug reported:
The simple_cert extension has a check that prevents fetching
certificates if the Token provider is not the PKI provider.
** Affects: keystone
Importance: Critical
Assignee: Adam Young (ayoung)
Status: In Progress
** Changed in: keystone
Importance: Unde
Fixed version uploaded to trusty-proposed for SRU team review.
** Description changed:
- I'm currently trying to integrate an OpenStack testbed (based on
- Icehouse nova-2014.1 , Ubuntu 14.04 standard packages) with VCenter. I
- configured nova.conf http://docs.openstack.org/trunk/config-
- refer
Public bug reported:
The remove_router_interface for the VMware NSX plugin expects a precise number
of SNAT rules for a subnet.
If the actual number of NAT rules differs from the expected one, an exception
is raised.
The reasons for this might be:
- earlier failure in remove_router_interface
-
** Changed in: keystone
Importance: Undecided => Critical
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: python-keystoneclient
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Yahoo!
Engi
Public bug reported:
Similar to bug #1314313 but this is another failure.
In some tempest runs a test fails to delete firewall within 300 seconds.
That happens because at the point firewall agent sends deleting
confirmation to neutron server, firewall object is already updated to a
state unexpec
Public bug reported:
I have a /24 for my floating ips and a revolving set of users. I delete
unused floating ips and clear router gatways regularly, but my ports
don't clear and I start to get ip allocation errors for setting the
gateway:
Error: Failed to set gateway No more IP addresses availabl
Yes, I think it would make sense to issue a security note on that topic. The
article by Pablo is a good read.
It's a well known issue so i'll make it public.
** Information type changed from Private Security to Public
** Also affects: ossn
Importance: Undecided
Status: New
** Changed
** Project changed: nova => ubuntu
--
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/1328134
Title:
[SRU] packaging for openstack icehouse 2014.1.1 release
Status in Ubunt
** Also affects: ossn
Importance: Undecided
Status: New
** Changed in: ossa
Status: Incomplete => Won't Fix
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
** Also affects: suds (Ubuntu)
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/1314674
Title:
Unable to connect to VCenter 5.5
Public bug reported:
OpenStack 2014.1.1 released today (09 June, 2014).
>From the release email from Alan Pevec:
A total of 79 bugs have been fixed across all projects. These
updates to Icehouse are intended to be low risk with no
intentional regressions or API changes. The list of bugs, tarball
Public bug reported:
When a port is added, ovs agent runs scan_ports to get all changed
ports, so it will be in port_info['current'] and port_info['added'].
Then this port is removed (by nova or ohters) before
treat_devices_added_or_updated called, means
self.int_br.get_vif_port_by_id(device) retu
Joern, Sorry for the doc bug.
This looks like it is documented correctly in trunk and in Ubuntu
releases other than 12.04. See doc/examples/cloud-config-user-groups.txt
at [1].
So I'm going to mark this as fix-released, and I wouldn't plan on doing
through a StableReleaseUpdates [2] process for t
I don't think you should report this as a bug. V3cloudsample policy file
is just for a reference. You could easily modify it to meet your needs.
For e.g. you could do:
"project_admin_required": "role:admin and
project_id:%(target.user.default_project_id)s "
"identity:create_user": "rule:cloud_adm
Public bug reported:
ovs-agent failed to launch if br-int is not existed.
$ sudo neutron-openvswitch-agent --config-file /etc/neutron/neutron.conf
--config-file /etc/neutron/plugins/ml2/ml2_conf.ini
2014-06-09 18:55:04.780 20321 DEBUG neutron.agent.linux.utils [-] Running
command: ['ip', '
*** This bug is a duplicate of bug 1219658 ***
https://bugs.launchpad.net/bugs/1219658
** This bug is no longer a duplicate of bug 1247467
resizing of rbd volumes is still broken
** This bug has been marked a duplicate of bug 1219658
Wrong image size using rbd backend for libvirt
--
Yo
Public bug reported:
We're seeing test failures, where it seems that an invalid token is
issued, with the ID of "placeholder"
http://logs.openstack.org/69/97569/2/check/check-tempest-dsvm-
full/565d328/logs/screen-h-eng.txt.gz
See context_auth_token_info which is being passed using the auth_toke
Public bug reported:
Project admins should be allowed to create, list, edit and delete users
in their domains. Here is the rule from the v3cloudsample policy file:
"admin_and_matching_target_user_domain_id": "rule:admin_required and
domain_id:%(target.user.domain_id)s",
"admin_and_matchi
Public bug reported:
add_column() of alembic does not work for adding a non-nullable column with a
default value to an existing database table in DB2.
in this bug,
neutron/db/migration/alembic_migrations/versions/128e042a2b68_ext_gw_mode.py
adds a column 'enable_snat' to table 'routers'.
*
*** This bug is a duplicate of bug 1004114 ***
https://bugs.launchpad.net/bugs/1004114
Thanks for the reply, I will mark this as a duplicate of bug 1004114.
** This bug has been marked a duplicate of bug 1004114
Password logging
--
You received this bug notification because you are a mem
Public bug reported:
The hyperv unit appear to not properly mock all cases of report_state
calls so an occasional exception will be thrown on an unrelated
patch.[1]
1. http://logs.openstack.org/01/96201/6/gate/gate-neutron-
python27/2b0de5e/console.html
** Affects: neutron
Importance: Undec
Public bug reported:
The name of the synchronized queue class is queue instead of Queue in
Python3.
** Affects: neutron
Importance: Undecided
Assignee: Christian Berendt (berendt)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Eng
Public bug reported:
when creating firewall rule if destination/source ipaddress as 10.10.10.0, it
doesnt throw error and took it as 10.10.10.0/32
Steps to Reproduce:
create firewall rule with destination ip address as 10.10.10.0
Actual Results:
root@IGA-OSC:~# fwru re --source-ip-address
** Changed in: nova
Milestone: next => None
** Changed in: nova
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/1235112
Ti
Public bug reported:
Error not thrown when setting protocol as icmp and destination /source
port while creating firewall rule
Steps to Reproduce:
create firewall rule with protocol as icmp and destination port as 20
Actual Results:
It is creating firewal rule with protocol as icmp and destinat
45 matches
Mail list logo
