olso.policy patch.
https://review.openstack.org/#/c/168798/
** Also affects: oslo.policy
Importance: Undecided
Status: New
** Changed in: oslo.policy
Status: New = Confirmed
** Changed in: oslo.policy
Assignee: (unassigned) = Eli Qiao (taget-9)
--
You received this bug
Public bug reported:
I have user, which have access to several tenants. E.g. qa, persistent,
scratch. I can select my current tenant in scroll box on top of page of
Horizon dashboard. It is kept under current session.
However when session timeouts and I have to re-login, then chosen tenants is
Public bug reported:
this problem can be reprodeced as bellow:
1. vm A in computeA, vm B in computeB, l2 pop enable;
2. vmB continue ping vmA
3. live migrate vmA to computeB
4. when live-migrate finish, vmB ping vmA failed
the reason is bellow, in l2pop driver, when vmA migrate to computeB,
Public bug reported:
The conductor is consuming messages form single queue which has performance
limitation due to various reasons.:
- per queue lock
- Some broker also limiting same part of the message handling to single CPU
thread/queue
- Multiple broker instances needs to synchronise to
@yatin Hey, I think you might be confused with what this bug aimed to
do. The bug proposed that the `size` field should match the
`virtual_size` instead of the `size`. What we did to fix this was adding
a new `virtual_size` field that would represent the `virtual_size` value
in some of the images.
Public bug reported:
https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/fwaas.py#L52
Duplicated init function from what appears to be a bad merge, but
unsure.
** Affects: horizon
Importance: Undecided
Assignee: Rob Cresswell (robcresswell)
Status: In
** Also affects: oslo-incubator
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/1437992
Title:
policy file in policy.d will
Public bug reported:
when the status changes the corresponding row is not updating in vpn table.
needs manual page reload.
** Affects: horizon
Importance: Undecided
Assignee: Masco Kaliyamoorthy (masco)
Status: New
** Changed in: horizon
Assignee: (unassigned) = Masco
Public bug reported:
In this file:
https://github.com/openstack/nova/blob/master/nova/conductor/manager.py#L600
Implementing _set_vm_state() method in _live_migrate() method is unnecessary.
It could be used method from line #590:
def _set_vm_state_and_notify(self, context, instance_uuid,
** Changed in: nova
Status: Triaged = Opinion
--
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/1260617
Title:
Provide the ability to attach volumes in the
Marking as Opinion as it is a bug by a core contributor without much
context.
** Changed in: nova
Status: Triaged = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Changed in: nova
Status: Triaged = Opinion
--
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/1276154
Title:
suspending a paused instance
Status in OpenStack
Public bug reported:
nova-compute doesn't shutdown gracefully on SIGTERM, e.g. booting a VM
fails with:
09:29:18 AUDIT nova.compute.manager [req-9cdbba9c-af3b-4845-9deb-c68bffe63d75
None] [instance: 7ea3e761-6b85-49db-8dcc-79f6f2286
df8] Starting instance...
09:29:18 INFO
@john has said it was a feature, marking as Opinion therefore
** Changed in: nova
Status: Triaged = Opinion
--
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/1206877
Public bug reported:
Using json type default data in a template causes annoying
inconsistencies in the second step of creating a stack. For example for
this template:
heat_template_version: 2013-05-23
parameters:
key:
type: string
default: key
description: This is keypair to
This is actually working as designed. Manually assigned floating IPs can
be deleted in a single go, auto assigned ones must be disassociated
first. Changing this default would probably *break* lots of users, so I
don't think we should.
** Changed in: nova
Status: New = Opinion
** Changed
Public bug reported:
Problem.: Neutron agents does a lot of periodic task which leads an rpc call +
database transaction, which does not even provide a new information, because
nothing changed.
This behaviour in scale can be called as `DDOS attack`, generally this kind of
architecture is bad
Looks fixed in code:
libvirt/driver.py
def rescue(self, context, instance, network_info, image_meta,
rescue_password):
Loads a VM using rescue images.
A rescue is normally performed when something goes wrong with the
primary images and data needs to be
this looks fixed upstream, no idea when, but quota show now includes
keypairs.
os1:~ nova quota-show
+-+---+
| Quota | Limit |
+-+---+
| instances | 10|
| cores | 20
This is really old, owned by a core contributor. Marking as an invalid
bug that was probably used for self tracking.
** Changed in: nova
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
This is a novnc bug, not a nova one
** Changed in: nova
Status: Triaged = Won't Fix
--
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/1260274
Title:
NoVNC Console
Triage indicates the bug is basically fixable with the information
provided in the bug. This is a nice to have enhancement, but not
triaged.
** Changed in: nova
Status: Triaged = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
This is unclear that it's a real bug, as it was disabled in the past.
Definitely not in a triaged state.
** Changed in: nova
Status: Triaged = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
** Changed in: nova
Status: Triaged = Opinion
--
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/1173430
Title:
cleanup_running_deleted_instances should not be
Can't see where this code even exists in Nova at this point. The bug
report also doesn't provide enough context to figure out where it might
have existed.
** Changed in: nova
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
Marking as Opinion as this bug discusses internal code structure changes
which are partially out of date. In future bugs that have a reproduce
would be more valuable.
** Changed in: nova
Status: Triaged = Opinion
--
You received this bug notification because you are a member of Yahoo!
** Changed in: nova
Status: Triaged = Opinion
--
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/1190076
Title:
virt xenapi driver does not throw
Very old bug that seems to not have a current reproduce. Putting to
invalid for now, it's definitely not triaged.
** Changed in: nova
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
The constraint checking kind of needs to be in the db layer because
that's the only place we have access to it. Possibly a future clean up.
But I think Opinion marks the current real state.
** Changed in: nova
Status: Triaged = Opinion
--
You received this bug notification because you
** Changed in: cinder
Status: Triaged = Incomplete
** Changed in: cinder
Status: Incomplete = Invalid
--
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/1161557
doc patches welcomed, but I'm not convinced a bug is needed for this.
** Changed in: nova
Status: Triaged = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
ec2 in nova is deprecated, this should probably be addressed in the out
of tree code
** Changed in: nova
Status: Triaged = Opinion
** Changed in: nova
Importance: Low = Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
There was a reproduce ask over 6 months ago which was not done. Marking
as Invalid.
** Changed in: nova
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
This really isn't addressable in current API, need new APIs to address
this.
** Changed in: nova
Status: Triaged = Opinion
** Changed in: nova
Importance: Low = Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
A recent commit [1] removed the relationship between compute_node and
service tables and in addition also made the compute_node.service_id
column nullable. These changes were never replicated to the object
counterparts.
[1] 551be2c52a29cb2755de4825a3fcb2c8f7d7b3f1
**
ec2 apis in tree are deprecated, probably should be fixed out of tree
instead
** Changed in: nova
Status: Triaged = Opinion
** Changed in: nova
Importance: Low = Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
That said, documentation recommends setting up 0.0.0.0 so that live
migration can work:
http://docs.openstack.org/admin-guide-cloud/content/section_configuring-compute-migrations.html
You must specify vncserver_listen=0.0.0.0 or live migration will not work
correctly.
qpid is used by nearly no one. Marking the nova bug as invalid, this
should be the upstream fix
** Changed in: nova
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
*** This bug is a duplicate of bug 1414708 ***
https://bugs.launchpad.net/bugs/1414708
We removed the dependency on libvirt in unit tests here:
https://github.com/openstack/nova/commit/50861d3221f625a5cc589d903054bb2c440b4026
** This bug has been marked a duplicate of bug 1414708
libvirt
Public bug reported:
The issue happens when multiple scheduling attempts that request CPU pinning
are done in parallel.
015-03-25T14:18:00.222 controller-0 nova-scheduler err Exception during
message handling: Cannot pin/unpin cpus [4] from the following pinned
set [3, 4, 5, 6, 7, 8, 9]
This code isn't in nova any more, moving to oslo.db
** Also affects: oslo.db
Importance: Undecided
Status: New
** Changed in: nova
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
CPU pinning support was implemented as part of this blueprint:
http://specs.openstack.org/openstack/nova-specs/specs/juno/approved
/virt-driver-cpu-pinning.html
However, CPU pinning support is broken in some libvirt versions
(summarized below), resulting in exceptions
This is being handled with a backend-specific condition in the 247
migration:
https://review.openstack.org/#/c/69047/45/nova/db/sqlalchemy/migrate_repo/versions/247_nullable_mismatch.py
** Changed in: nova
Status: Triaged = Invalid
--
You received this bug notification because you are a
** Changed in: nova
Status: Triaged = Invalid
--
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/1014647
Title:
Tempest has no test for soft reboot
Status in
Addressed in Havana
** Changed in: nova
Status: Triaged = 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/1237683
Title:
inconsitent virtual size in
** Changed in: nova
Status: Triaged = Invalid
--
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/1257405
Title:
Not checking image format produces lots of useless
Attilla, please don't file specs kinds of issues as bugs, this is really
a specs level rearchitecture.
** Changed in: nova
Status: New = Invalid
** Changed in: nova
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering
** Changed in: nova
Status: Confirmed = Won't Fix
--
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/1359136
Title:
vmware: display incorrect host_ip for hypervisor
** Changed in: nova
Status: Triaged = Opinion
** Changed in: nova
Importance: Low = Wishlist
--
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/1102714
Title:
Can this just be handled with changing the required upgrade order? Just
make ironic go first?
** Changed in: nova
Status: New = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Working as designed. it's reporting that you have a problem with the ini
file...no?
** Changed in: nova
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
There are other bits of the nova-network code which assume bridge # maps
to vlan #, so I'm not sure this is reasonably changable above the driver
layer. I suspect a warning that vlan and bridge are incompatibile
options in the client would be the near term fix.
** Changed in: nova
Importance:
Not an actual bug
** Changed in: nova
Status: In Progress = Won't Fix
--
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/1438020
Title:
replace hpy.host with
** No longer affects: nova
--
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/1394462
Title:
nova show output should display sec-group id instead of name
Status in Python
Right, optional means you are allowed to not provide the parameter. Not
that you can provide it as null. There is a python-novaclient bug here.
** Changed in: nova
Status: Incomplete = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
No longer reproducable, was fixed by the user
** Changed in: nova
Status: Incomplete = Invalid
--
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/1326345
Title:
Public bug reported:
At some stage over the last 10 days tripleo has stared to to fail to run
DJANGO_SETTINGS_MODULE=openstack_dashboard.settings django-admin.py
collectstatic --noinput
Exiting with the following error
os-collect-config: dib-run-parts Fri Mar 27 03:56:44 UTC 2015 Running
This is definitely way beyond a bug, it should be done as a nova-spec
** Changed in: nova
Status: New = Invalid
** Changed in: nova
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
When you try to create a metadef object without any properties
associated with it you get an Internal Server Error 500:
glance md-object-create --name obj_name --schema '{description: some
desc}' OS::Software::DBMS
AttributeError: 'NoneType' object has no attribute
*** This bug is a duplicate of bug 1231254 ***
https://bugs.launchpad.net/bugs/1231254
** This bug has been marked a duplicate of bug 1231254
Windows instances need timezone to be localtime
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Moving to Opinion as EC2 in tree API is deprecated.
** Changed in: nova
Status: Triaged = Opinion
** Tags added: ec2
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Moving to Opinion as EC2 in tree API is deprecated.
** Tags added: ec2
** Changed in: nova
Status: Triaged = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
I don't think this is really a nova side issue. Polling from nova seems
really odd here.
** Changed in: nova
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
This is kind of working as designed. The concurency mode of n-cpu kind
of needs to work this way.
** Changed in: nova
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Marking as Opinion because the solution here really needs to be
encryption at rest so that a crashed nova compute doesn't leave customer
data out there.
** Changed in: nova
Status: Triaged = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering
I think the point of using UUID for instance names is probably spot on.
Marking as Opinion, because it seems like for consistency it should be
done that way.
** Changed in: nova
Status: In Progress = Opinion
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
The resize_fs_using_block_device config option allows to configure if a
filesystem within an image is resized by nova during spawn or not. When
it's set to False (which is the default) nova still tries to access the
image to find out if it's extendable or not, although it's
*** This bug is a duplicate of bug 1330873 ***
https://bugs.launchpad.net/bugs/1330873
** This bug has been marked a duplicate of bug 1330873
Instance name set in horizon is not set in VMware vCenter
--
You received this bug notification because you are a member of Yahoo!
Engineering
Public bug reported:
See log stash query:
Device allocation failed. Will retry in 2 seconds.
Example:
http://logs.openstack.org/10/163910/6/check/gate-rally-dsvm-cinder/46d89ab/logs/screen-n-cpu.txt.gz#_2015-03-30_14_55_56_941
Logs:
2015-03-30 14:55:56.940 ERROR nova.virt.disk.mount.nbd
This is really a UX feature addition
** Changed in: nova
Status: Triaged = Opinion
--
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/1202965
Title:
The name VCPUs
This has been fixed by some of the work to move nova-net to objects.
** Changed in: nova
Status: Triaged = Fix Released
** Changed in: nova
Assignee: (unassigned) = Dan Smith (danms)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
Some of the driver unit tests mock execute() from Neutron, which creates
a (brittle) dependency (as seen by a recent breakage).
The dependency can be removed, but mocking higher up, from within the
*Swan process _execute() method.
In addition, there are some unit tests that
*** This bug is a duplicate of bug 1417667 ***
https://bugs.launchpad.net/bugs/1417667
Public bug reported:
We conduced a series of resize checks on instances with/without the CPU
pinning parameters provided as part of this blueprint:
Public bug reported:
Using a CPU policy of dedicated ('hw:cpu_policy=dedicated') results in
vCPUs being pinned to pCPUs, per the original blueprint:
http://specs.openstack.org/openstack/nova-
specs/specs/kilo/implemented/virt-driver-cpu-pinning.html
When combined with the 'vcpu_pin_set'
Public bug reported:
The following commit to oslo-incubator [1], that was supposed to optimize
waiting for children processes
to exit, will break neutron-server behavior (i.e. signal handling).
1. In neutron-server eventlet monkey-patching (including patching os
module) is done in parent
Public bug reported:
Creation of subnet pools should be blocked when
allow_overlapping_ips=False. This conflicts with the notion of subnet
pools and causes allocation of overlapping prefixes to be blocked, even
when allocating across different pools. The simplest solution is to
declare subnet
Public bug reported:
Access and Security tab became very unresponsive and may time out on
environments with more that 3k VMs.
Deep analisys shown that it because of Floating IPs tab even if there is no
floating IPs assigned :).
It looks like code on this tab is suboptimal and trying to get
Public bug reported:
When removing guests that have been booted on Ceph, Nova will
occasionally put guests in to ERROR state with the following ...
Reported to the controller:
| fault| {message: error removing image,
code: 500, details: File
Public bug reported:
Creating this from https://bugs.launchpad.net/python-
novaclient/+bug/1394462
In nova-network security group names can't be duplicated, but in
neutron, they can. For this reason, it would be nice to return server
security groups as ids instead of names.
Here's is a sample
*** This bug is a duplicate of bug 1336127 ***
https://bugs.launchpad.net/bugs/1336127
Thanks andrew, marked this as a duplicate
** This bug has been marked a duplicate of bug 1336127
The volumes will be deleted when creating a virtual machine fails with the
parameter
This looks like deep rework of current messaging strategy and probably
should be worked on within a scope of a blueprint rather than a bug.
So I would suggest to file a bp for this and provide a spec explaining
these ideas so spec review could be a better place to discuss these
ideas.
** Changed
Public bug reported:
The example configuration files in the source repository lack the
changes in the list of new, updated, and deprecated options in the Kilo
configuration reference guide [1]. For example, the example neutron.conf
file [2] lacks the [nova] and [oslo_messaging_*] sections and
With the moving of instance_type information into the instance metadata
this should be addressed moving forward. There will be some legacy
instances that don't yet have this, but moving forward it's fixed.
** Changed in: nova
Status: Triaged = Fix Released
--
You received this bug
Public bug reported:
Unlike keystone, glance does not notify systemd when the
api|registry|scrubber services are up.
root@controller:~# time systemctl start glance-api
Job for glance-api.service failed. See systemctl status glance-api.service
and journalctl -xe for details.
real1m30.310s
Nova is being asked to do a thing, which it can't, which is put files in
the guest. This retry is actually kind of important.
The bug really is exposing the fact that *no* working file injection
mechanism exists in these rally jobs, but they are asking guests to do
something.
** Changed in:
** Also affects: openstack-api-site
Importance: Undecided
Status: New
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1418635
Title:
Neutron API
** Changed in: nova
Status: Triaged = Incomplete
** Changed in: nova
Status: Incomplete = Opinion
** Changed in: nova
Importance: Low = Wishlist
** Changed in: nova
Assignee: Leandro Ignacio Costantino (leandro-i-costantino) = (unassigned)
--
You received this bug
** Changed in: nova
Status: Triaged = Opinion
--
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/1274732
Title:
Instances table doesn't get cleaned up
Status in
case 1: I think that creating a DVR router connecting Subnets that reach
VM's whose compute hosts are not DVR aware should lead to an error
case 2: I think that moving agents willy nilly should lead can't be
expected to work. Moving DVR routers from one agent to another has
always been a bit
** Tags added: horizon
** No longer affects: horizon
--
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/1438325
Title:
Access and Security tab slowness
Status in
** Changed in: nova
Status: Triaged = Opinion
--
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/1089343
Title:
Resize confirm should raise NotFound instead of
This is a much bigger architecture issue to address.
** Changed in: nova
Status: Triaged = Invalid
** Changed in: nova
Status: Invalid = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
Public bug reported:
2015-03-30 15:02:58.287 28424 DEBUG oslo_messaging._drivers.amqp [-] UNIQUE_ID
is 9c2e286750e7407cb78e273becca4ab0. _add_unique_id
/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqp.py:224
Traceback (most recent call last):
File
The code structure has changed significantly and haven't heard of any
other citing of this specific issue for a while so marking it as invalid
for now.
** Changed in: neutron
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
Currently, if the select-all checkbox is clicked, all rows are selected
even if it's not visible. For example, when a table is paginated or
filtered.
The select-all checkbox should only select all the visible checkboxes in
the table.
** Affects: horizon
Importance:
This optimization has been awaiting someone to add unit tests for 4
months. Calling it Opinion not In Progress.
** Changed in: nova
Status: In Progress = Confirmed
** Changed in: nova
Status: Confirmed = Opinion
** Changed in: nova
Assignee: wingwj (wingwj) = (unassigned)
--
Public bug reported:
A recent change to devstack [1] removed lib/neutron which the functional
testing setup script depends on. The script should be updated to refer
to lib/neutron-legacy instead.
1: https://review.openstack.org/#/c/168591/
** Affects: neutron
Importance: Critical
Public bug reported:
Angular module hz.dashboard should have unit tests.
** Affects: horizon
Importance: Undecided
Assignee: Shaoquan Chen (sean-chen2)
Status: In Progress
** Changed in: horizon
Assignee: (unassigned) = Shaoquan Chen (sean-chen2)
--
You received this
Public bug reported:
When auth_version is set to be v3.0 in glance-api.conf, I see this in
the logs Auth Token proceeding with requested v3.0 apis but in the
very next debug log I see that the authentication request actually
appends v2.0 to the identity url, which seems incorrect.
2015-03-31
** Also affects: keystonemiddleware
Importance: Undecided
Status: New
** Summary changed:
- ConnectionFailed: Connection to neutron failed: 'HTTPSConnectionPool' object
has no attribute 'insecure'
+ ConnectionFailed: Connection to XX failed: 'HTTPSConnectionPool' object
has no
1 - 100 of 116 matches
Mail list logo
