Public bug reported:
Property vnc_keymap is properly handled by KVM compute but not managed
at all by vmware compute.
As a consequence, the corresponding property in vmx file
RemoteDisplay.vnc.keyMap is never set and whatever we put in
vnc_keymap option we will have an english (en-us) keyboard.
Ah, no, it is using this to get an override in the case of sql.
** Changed in: keystone
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1435315
Title:
Ah, now I get what is going on - it is overriding the default one in the
Driver class...
** Changed in: keystone
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
Looks like i just tested nova-compute and not nova api for reload of
config files...!
** 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).
Public bug reported:
After v2.1 policy separated into policy.d. The unittest will failed.
Because fake policy fixture will load policy config from real
'/etc/nova/policy.d' which override the fake policy rules.
{7}
** 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/1174153
Title:
data from previous tenants accessible with nova
Public bug reported:
The v3 catalog is created from the v2 catalog in the catolog
manager/driver, and the sql backend get_v3_catalog method is therefore
never called - and should be removed.
** Affects: keystone
Importance: Medium
Assignee: Henry Nash (henry-nash)
Status: New
Public bug reported:
Default policy.json file in Keystone is focused on v2 API nowadays. From
the (Tempest) testing point-of-view we need to test both supported API's
simultaneously, which can not be done so far (without manual
intervention, one API at the time). Automated testing of identity v2
** 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/1246623
Title:
metadata server running on mod_wsgi blocks on
Very good catch! I think the Ironic part is largely duplicate of
#1433727, so I'm closing it here.
** Changed in: ironic
Status: New = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
Both the v2 and v3 get catalog calls take an optional parameter called
'metadata' - but this is never used. It should be removed.
** Affects: keystone
Importance: Medium
Assignee: Henry Nash (henry-nash)
Status: New
--
You received this bug notification
Public bug reported:
The Driver section of our manages should only hold abstract methods (or
internal methods) - but the get_v3_catalog() method is neither of these,
yet is still in the Driver section. It should be moved to the manager.
** Affects: keystone
Importance: Medium
Public bug reported:
taget@taget-ThinkStation-P300:~/devstack$ nova flavor-create Test1 100
^C11 1 1
when create/delete a flavor, nova considers the name as lower case letter.
but it doesn't for update
for example:
1. I have a flavor named TEST1
taget@taget-ThinkStation-P300:~/devstack$
All hits are from a single review which was attempting to change the api
(https://review.openstack.org/#/c/166692/)
** Changed in: nova
Status: Confirmed = Won't Fix
** Changed in: oslo.messaging
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).
** Changed in: neutron
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1405528
Title:
Migration of legacy router to distributed router should remove
Public bug reported:
use_namespaces was introduced because at the time not all kernels
properly supported namespaces. That time has passed, and since:
1) The non-default (False) value is not being tested
2) It has introduced complexity in the L3 and DHCP agents
More information may be found
Looks like we still have 2 reviews in progress in **Nova**:
https://review.openstack.org/#/c/161474/
https://review.openstack.org/#/c/164313/
** Changed in: nova
Status: Won't Fix = In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Public bug reported:
When theming recently landed (https://review.openstack.org/#/c/159300/)
the customizing section of the docs was not updated to reflect this. See
https://github.com/openstack/horizon/blob/4fdc42cf6332579c162de57ec5ec833343bff3e5/doc/source/topics/customizing.rst
** Affects:
Public bug reported:
In this patch
https://review.openstack.org/#/c/149931/8/etc/nova/policy.json add some
rules for servers' actions.
But those rule's default rule finally missing in the policy.d/00-os-
compute-api.json
** Affects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
Public bug reported:
If you use the v3 API to add or remove role grants, you get notifications that
it happened, but if you use the v2.0 API, you don't get notifications.
Keystone needs to send notifications when the v2 API is used, also.
For example, start with devstack, then grant a role:
Public bug reported:
A user is able to perform some actions even after that user is disabled
from keystone. Steps to reproduce
1) Log into dashboard
2) open instance tab
3) click on launch instance
4) from keystone disable user
5) now i am able to launch instance
I can not see other tabs
Public bug reported:
In v2.1, os-hypervisors/servers API returns empty servers list in case where
hypervisors does not have any servers. This is not case with v2 API.
v2 API does not put 'servers' field in response if it is empty.
So v2.1 should be same as v2 in all cases.
** Affects: nova
*** This bug is a duplicate of bug 1379451 ***
https://bugs.launchpad.net/bugs/1379451
** This bug has been marked a duplicate of bug 1379451
anti-affinity policy only honored on boot
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Changed in: neutron
Status: In Progress = Won't Fix
** Changed in: neutron
Status: Won't Fix = Invalid
** Changed in: neutron
Status: Invalid = Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
** 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/1435507
Title:
Compute API v2.0 vs v2.1 labelling
Public bug reported:
In Launch Instance work flow Configuration step, `disk_config` should be
handle only when certain service is enabled.
** Affects: horizon
Importance: Undecided
Assignee: Shaoquan Chen (sean-chen2)
Status: In Progress
--
You received this bug notification
Public bug reported:
Hi there!
I'm getting a bunch of KeyError: 'port_security' when building Neutron
Kilo b3 in Debian (see below). I'm cut/pasting only a single trace dump
here, though there's about a dozen similar issues. Please help me to fix
this. Note that the package is building under a
Public bug reported:
Hi,
I get the bellow issues when building Keystone in Debian (Jessie chroot
using sbuild). Help from the keystone team would be appreciate to
resolve this. Cheers! :)
==
FAIL:
Public bug reported:
We get warnings:
UserWarning: Module novaclient.v1_1 is deprecated (taken as a basis for
novaclient.v2).
** Affects: horizon
Importance: Undecided
Assignee: Radomir Dopieralski (thesheep)
Status: In Progress
** Changed in: horizon
Assignee:
Public bug reported:
The admin context is used when nova-compute init host, the instance with
task_states.POWERING_OFF would been stopped, but the method decorators
@wrap_instance_event would try to query the InstanceAction record by
request_id in admin context and instance_uuid, because the
The tempest fix healed the breakage that was captured by this report.
Having said that the stability of the DVR seems pretty good these days:
Public bug reported:
ovs-vsctl supports looking up records in some tables by non-indexed
columns.
For example,
attr = [('connection-mode', connection_mode)]
self.ovsdb.db_set('Controller', self.br_name, *attr).execute(
check_error=True)
with the vsctl backend will run:
ovs-vsctl
Public bug reported:
During trigger_rules_refresh(), we get this from compute manager:
2015-03-23 03:50:49.677 ERROR oslo_messaging.rpc.dispatcher
[req-117e72d4-8c12-4805-9c65-695b62fad491 alt_demo alt_demo] Exception during
message handling: 'dict' object has no attribute 'uuid'
2015-03-23
Public bug reported:
This is a test bug. Ignore it.
** Affects: keystone
Importance: Undecided
Assignee: Rafael Toschi Chiafarelli (rafael-chiafarelli)
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
Public bug reported:
In order to suppress recent jshint errors, we need to add 'spyOn' to the
global config.
** Affects: horizon
Importance: Undecided
Assignee: Thai Tran (tqtran)
Status: In Progress
** Tags: jshint low-hanging-fruit test
--
You received this bug
** Also affects: nova/juno
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/1392773
Title:
Live migration of volume backed
Public bug reported:
The attributes aren't nullable [1], but in the ServiceProviderModel they
have nullable=True [2].
[1]
https://github.com/openstack/keystone/blob/master/keystone/contrib/federation/migrate_repo/versions/006_fixup_service_provider_attributes.py#L39-L40
[2]
** Changed in: keystone
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1435448
Title:
just for test(ignore it)
Status in OpenStack Identity (Keystone):
Public bug reported:
When adding properties from the compute host capabilities namespace, it
displays them differently than glance seems to process them, making me
unable to delete them and it doesn't resolve them correctly the next
time I open the widget. Next time I open, it shows them all in
Public bug reported:
my nova.conf contains pci_passthrough_whitelist parameter
launch vm after openstack installation the vm was successfully booted.
when restarting nova compute and then again trying to launch vm I can see the
following error
An object of type PciDevicePoolList is required
Public bug reported:
We need styling for action-list menu-item for disabled and danger items.
Currently, bootstrap does not support a way to do this. We have to add
this via our own css.
** Affects: horizon
Importance: Undecided
Assignee: Thai Tran (tqtran)
Status: In Progress
Public bug reported:
All the instance with volume backed should not have a image ref, so the
code at
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/servers.py#L1065-L1072
is not reasonable for now.
** Affects: nova
Importance: Low
Assignee: Fei Long Wang
Keystone doesn't log the request ids either:
http://logs.openstack.org/48/165548/4/gate/gate-tempest-dsvm-neutron-
full/5cbdc8e/logs/apache/keystone.txt.gz?level=INFO#_2015-03-19_20_35_44_383968
request ids were only recently added to keystone with:
https://review.openstack.org/#/c/155901/ I
Public bug reported:
Now neutron does not allow to manually assign a distributed router to a l3
agent which is in 'dvr' mode, but in bellow use case, it does not work ok:
1 case:
(1)there are two computeA, B nodes which l3 agent are in legacy mode, l2 agent
'enable_distributed_routing = False'
Public bug reported:
I have two compute node, host lxlconductor1 and host lxlcompute1.
A migration failed at function of _call_livem_checks_on_host because
check_can_live_migrate_destination rpc call's MessagingTimeout Exception, but
the status of this instance is still migrating.
2015-05-23
AFAICT - the API says a request with no description in the body should be
allowed:
http://developer.openstack.org/api-ref-compute-v2-ext.html
In the controller, the description value is not checked but goes to
validate_property...
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1406854
Public bug reported:
Break out Security and Access into two steps (Security Groups /
Keypairs).
** 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
an example of the failure:
http://172.17.16.18/ryuci/14/139914/1/check/check-tempest-dsvm-ofagent/ad71969/
relevant ovs log:
2014-12-09T00:00:56.384Z|00024|bridge|INFO|bridge br-int: added interface
qvoa0effc8a-2c on port 8
2014-12-09T00:01:27.467Z|00027|bridge|INFO|bridge br-int: added
Public bug reported:
Move the form to its own step
** 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).
51 matches
Mail list logo
