[Yahoo-eng-team] [Bug 1419141] [NEW] [data processing] The submit button on the Launch cluster form should read Launch

[Chad Roberts]

Public bug reported:

*Low  priority*

On the data processing - clusters - Launch Cluster dialog, the button
on the first dialog (plugin select) currently reads Create.  Ideally,
that should read Next.

On the actual cluster launching dialog, the submit button reads
Create.  Ideally it should read Launch.

** Affects: horizon
 Importance: Undecided
 Status: New


** Tags: sahara

-- 
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/1419141

Title:
  [data processing] The submit button on the Launch cluster form should
  read Launch

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  *Low  priority*

  On the data processing - clusters - Launch Cluster dialog, the
  button on the first dialog (plugin select) currently reads Create.
  Ideally, that should read Next.

  On the actual cluster launching dialog, the submit button reads
  Create.  Ideally it should read Launch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1419141/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419114] [NEW] Nova api 'Authorization failed for token' with federated scoped token

[William Lynch]

Public bug reported:

OpenStack Release:  Juno

I am investigated k2k and I'm seeing the following behavior

I have setup a keystone 2 keystone environment.
I get a unscoped federated token
I then get a project scoped token from the unscoped.
I attempt to something simple by listing the flavors

-- curl -i -X GET -H X-Auth-Token:eb2966a9b55e4836907b956b79187341
http://keystone.service.provider:8774/v2/031a04fd26da4d74b9d2375de2d80be0/flavors

I see this in the nova api.log:
---

2015-02-06 10:20:32.787 3970 WARNING keystonemiddleware.auth_token [-] 
Authorization failed for token
2015-02-06 10:20:32.788 3970 INFO nova.osapi_compute.wsgi.server [-] 
9.10.111.91 GET /v2/031a04fd26da4d74b9d2375de2d80be0/flavors HTTP/1.1 status: 
401 len: 261 time: 0.0038319

I see this in the keystone.log:
---

2015-02-06 10:55:00.753 5910 DEBUG keystone.common.controller [-] RBAC: 
Authorization granted inner 
/usr/lib/python2.6/site-packages/keystone/common/controller.py:155
2015-02-06 10:55:00.769 5910 ERROR keystone.common.wsgi [-] 'domain'
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi Traceback (most recent 
call last):
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/keystone/common/wsgi.py, line 223, in 
__call__
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi result = 
method(context, **params)
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/keystone/common/controller.py, line 156, in 
inner
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi return f(self, 
context, *args, **kwargs)
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/keystone/token/controllers.py, line 445, in 
validate_token
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi return 
self.token_provider_api.validate_v2_token(token_id, belongs_to)
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/keystone/token/provider.py, line 246, in 
validate_v2_token
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi token = 
self._validate_v2_token(token_ref)
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/dogpile/cache/region.py, line 1008, in 
decorate
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi should_cache_fn)
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/dogpile/cache/region.py, line 637, in 
get_or_create
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi async_creator) as 
value:
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/dogpile/core/dogpile.py, line 158, in 
__enter__
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi return self._enter()
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/dogpile/core/dogpile.py, line 98, in _enter
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi generated = 
self._enter_create(createdtime)
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/dogpile/core/dogpile.py, line 149, in 
_enter_create
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi created = 
self.creator()
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/dogpile/cache/region.py, line 609, in 
gen_value
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi created_value = 
creator()
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/dogpile/cache/region.py, line 1004, in 
creator
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi return fn(*arg, 
**kw)
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/keystone/token/provider.py, line 329, in 
_validate_v2_token
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi return 
self.driver.validate_v2_token(token_id)
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/keystone/token/providers/common.py, line 
540, in validate_v2_token
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi 
self._assert_default_domain(token_ref)
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi   File 
/usr/lib/python2.6/site-packages/keystone/token/providers/common.py, line 
502, in _assert_default_domain
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi if 
(token_ref['token_data']['token']['user']['domain']['id'] !=
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi KeyError: 'domain'
2015-02-06 10:55:00.769 5910 TRACE keystone.common.wsgi 

The token body of the scoped token is:
--

{
token: {
methods: [
saml2
], 
roles: [
{
   

[Yahoo-eng-team] [Bug 1419115] [NEW] IndexError adding host to availability zone

[Chris Friesen]

Public bug reported:

There appears to be a bug in the code dealing with adding a disabled
host to an aggregate that is exported as an availability zone.

I disable the nova-compute service on a host and then tried to add it to
an aggregate that is exported as an availabilty zone. This resulted in
the following error.


   File /usr/lib64/python2.7/site-packages/oslo/utils/excutils.py, line 82, 
in __exit__
 six.reraise(self.type_, self.value, self.tb)
   File /usr/lib64/python2.7/site-packages/nova/exception.py, line 71, in 
wrapped
 return f(self, context, *args, **kw)
   File /usr/lib64/python2.7/site-packages/nova/compute/api.py, line 3673, in 
add_host_to_aggregate
 aggregate=aggregate)
   File /usr/lib64/python2.7/site-packages/nova/compute/api.py, line 3591, in 
is_safe_to_update_az
 host_az = host_azs.pop()
 IndexError: pop from empty list
 

The code looks like this:

if 'availability_zone' in metadata:
_hosts = hosts or aggregate.hosts
zones, not_zones = availability_zones.get_availability_zones(
context, with_hosts=True)
for host in _hosts:
# NOTE(sbauza): Host can only be in one AZ, so let's take only
#   the first element
host_azs = [az for (az, az_hosts) in zones
if host in az_hosts
and az != CONF.internal_service_availability_zone]
host_az = host_azs.pop()

It appears that for a disabled host, host_azs can be empty, resulting in
an error when we try to pop() from it.

It works fine if the service is enabled on the host, and it works fine
if the service is diabled and I try to add the host to an aggregate that
is not exported as an availability zone.

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: compute

-- 
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/1419115

Title:
  IndexError adding host to availability zone

Status in OpenStack Compute (Nova):
  New

Bug description:
  There appears to be a bug in the code dealing with adding a disabled
  host to an aggregate that is exported as an availability zone.

  I disable the nova-compute service on a host and then tried to add it
  to an aggregate that is exported as an availabilty zone. This resulted
  in the following error.

  
 File /usr/lib64/python2.7/site-packages/oslo/utils/excutils.py, line 82, 
in __exit__
   six.reraise(self.type_, self.value, self.tb)
 File /usr/lib64/python2.7/site-packages/nova/exception.py, line 71, in 
wrapped
   return f(self, context, *args, **kw)
 File /usr/lib64/python2.7/site-packages/nova/compute/api.py, line 3673, 
in add_host_to_aggregate
   aggregate=aggregate)
 File /usr/lib64/python2.7/site-packages/nova/compute/api.py, line 3591, 
in is_safe_to_update_az
   host_az = host_azs.pop()
   IndexError: pop from empty list
   

  The code looks like this:

  if 'availability_zone' in metadata:
  _hosts = hosts or aggregate.hosts
  zones, not_zones = availability_zones.get_availability_zones(
  context, with_hosts=True)
  for host in _hosts:
  # NOTE(sbauza): Host can only be in one AZ, so let's take only
  #   the first element
  host_azs = [az for (az, az_hosts) in zones
  if host in az_hosts
  and az != CONF.internal_service_availability_zone]
  host_az = host_azs.pop()

  It appears that for a disabled host, host_azs can be empty, resulting
  in an error when we try to pop() from it.

  It works fine if the service is enabled on the host, and it works fine
  if the service is diabled and I try to add the host to an aggregate
  that is not exported as an availability zone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1419115/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419150] [NEW] resource usage modify should be modal

[David Lyle]

Public bug reported:

The Resource Usage modify query should be a modal, but is not. It opens
as a base view.

** Affects: horizon
 Importance: Low
 Assignee: David Lyle (david-lyle)
 Status: New


** Tags: ceilometer

-- 
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/1419150

Title:
  resource usage modify should be modal

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  The Resource Usage modify query should be a modal, but is not. It
  opens as a base view.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1419150/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419187] [NEW] ldap unicode issue

[Kevin Fox]

Public bug reported:

exception when listing users in ldap:

2015-02-06 14:52:21.934 27199 ERROR keystone.common.wsgi [-] 'ascii' codec 
can't encode character u'\xe9' in position 19: ordinal not in range(128)
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi Traceback (most recent 
call last):
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/common/wsgi.py, line 223, in 
__call__
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi result = 
method(context, **params)
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/controllers.py, line 48, 
in get_users
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi 
CONF.identity.default_domain_id)
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/common/manager.py, line 47, in 
wrapper
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi return f(self, 
*args, **kwargs)
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/core.py, line 202, in 
wrapper
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi return f(self, 
*args, **kwargs)
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/core.py, line 213, in 
wrapper
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi return f(self, 
*args, **kwargs)
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/core.py, line 620, in 
list_users
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi ref_list, 
domain_scope, driver, mapping.EntityType.USER)
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/core.py, line 328, in 
_set_domain_id_and_mapping
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi x, domain_id, 
driver, entity_type) for x in ref]
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/core.py, line 325, in 
_set_domain_id_and_mapping
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi ref, domain_id, 
driver, entity_type, conf)
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/core.py, line 359, in 
_set_domain_id_and_mapping_for_single_ref
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi local_entity, 
public_id)
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/mapping_backends/sql.py, 
line 70, in create_id_mapping
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi public_id = 
self.id_generator_api.generate_public_ID(entity)
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/id_generators/sha256.py, 
line 27, in generate_public_ID
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi 
m.update(mapping[key])
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi UnicodeEncodeError: 
'ascii' codec can't encode character u'\xe9' in position 19: ordinal not in 
range(128)
2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi
2015-02-06 14:52:21.959 27199 INFO eventlet.wsgi.server [-] 172.20.96.65 - - 
[06/Feb/2015 14:52:21] GET /v2.0/users HTTP/1.1 500 291 23.150229


'local_entity' is here: 
https://github.com/openstack/keystone/blob/c4c8d0b99a0404f4dcdb2f87c48fe15ee1526197/keystone/identity/mapping_backends/sql.py#L66

its: {'local_id': u'^PNNL TQ Communiqu\xe9', 'domain_id': 
  'default', 'entity_type': 'user'}

** Affects: keystone
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1419187

Title:
  ldap unicode issue

Status in OpenStack Identity (Keystone):
  New

Bug description:
  exception when listing users in ldap:

  2015-02-06 14:52:21.934 27199 ERROR keystone.common.wsgi [-] 'ascii' codec 
can't encode character u'\xe9' in position 19: ordinal not in range(128)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi Traceback (most 
recent call last):
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/common/wsgi.py, line 223, in 
__call__
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi result = 
method(context, **params)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/controllers.py, line 48, 
in get_users
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi 
CONF.identity.default_domain_id)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 

[Yahoo-eng-team] [Bug 1419043] Re: Conflict on isolated credential setup

[Morgan Fainberg]

** Changed in: keystone
Milestone: None = kilo-3

** Also affects: keystone/icehouse
   Importance: Undecided
   Status: New

** Also affects: keystone/juno
   Importance: Undecided
   Status: New

** Changed in: keystone/icehouse
   Importance: Undecided = Critical

** Changed in: keystone/juno
   Importance: Undecided = Critical

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1419043

Title:
  Conflict on isolated credential setup

Status in OpenStack Identity (Keystone):
  In Progress
Status in Keystone icehouse series:
  New
Status in Keystone juno series:
  New
Status in Tempest:
  Invalid

Bug description:
  From the following run (in progress) -
  http://logs.openstack.org/26/153426/2/gate/gate-tempest-dsvm-
  nova-v21-full/c80cf2c//console.html

  2015-02-06 15:50:27.935 | ==
  2015-02-06 15:50:27.935 | Failed 1 tests - output below:
  2015-02-06 15:50:27.935 | ==
  2015-02-06 15:50:27.935 | 
  2015-02-06 15:50:27.935 | setUpClass 
(tempest.api.compute.admin.test_aggregates_negative.AggregatesAdminNegativeTestJSON)
  2015-02-06 15:50:27.936 | 
---
  2015-02-06 15:50:27.936 | 
  2015-02-06 15:50:27.936 | Captured traceback:
  2015-02-06 15:50:27.936 | ~~~
  2015-02-06 15:50:27.936 | Traceback (most recent call last):
  2015-02-06 15:50:27.936 |   File tempest/test.py, line 273, in 
setUpClass
  2015-02-06 15:50:27.936 | cls.resource_setup()
  2015-02-06 15:50:27.936 |   File 
tempest/api/compute/admin/test_aggregates_negative.py, line 31, in 
resource_setup
  2015-02-06 15:50:27.936 | super(AggregatesAdminNegativeTestJSON, 
cls).resource_setup()
  2015-02-06 15:50:27.936 |   File tempest/api/compute/base.py, line 341, 
in resource_setup
  2015-02-06 15:50:27.936 | super(BaseComputeAdminTest, 
cls).resource_setup()
  2015-02-06 15:50:27.936 |   File tempest/api/compute/base.py, line 44, 
in resource_setup
  2015-02-06 15:50:27.937 | cls.os = cls.get_client_manager()
  2015-02-06 15:50:27.937 |   File tempest/test.py, line 407, in 
get_client_manager
  2015-02-06 15:50:27.937 | creds = 
cls.isolated_creds.get_primary_creds()
  2015-02-06 15:50:27.937 |   File tempest/common/isolated_creds.py, line 
273, in get_primary_creds
  2015-02-06 15:50:27.937 | return self.get_credentials('primary')
  2015-02-06 15:50:27.937 |   File tempest/common/isolated_creds.py, line 
257, in get_credentials
  2015-02-06 15:50:27.937 | credentials = 
self._create_creds(admin=is_admin)
  2015-02-06 15:50:27.937 |   File tempest/common/isolated_creds.py, line 
119, in _create_creds
  2015-02-06 15:50:27.937 | tenant, email)
  2015-02-06 15:50:27.937 |   File tempest/common/isolated_creds.py, line 
65, in _create_user
  2015-02-06 15:50:27.937 | username, password, tenant['id'], email)
  2015-02-06 15:50:27.937 |   File 
tempest/services/identity/json/identity_client.py, line 168, in create_user
  2015-02-06 15:50:27.938 | resp, body = self.post('users', post_body)
  2015-02-06 15:50:27.938 |   File 
/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py,
 line 169, in post
  2015-02-06 15:50:27.938 | return self.request('POST', url, 
extra_headers, headers, body)
  2015-02-06 15:50:27.938 |   File tempest/common/service_client.py, line 
69, in request
  2015-02-06 15:50:27.938 | raise exceptions.Conflict(ex)
  2015-02-06 15:50:27.938 | Conflict: An object with that identifier 
already exists
  2015-02-06 15:50:27.938 | Details: An object with that identifier already 
exists
  2015-02-06 15:50:27.938 | Details: {u'title': u'Conflict', u'message': 
u'Conflict occurred attempting to store role - Duplicate Entry', u'code': 409}
  2015-02-06 15:50:27.938 | 

  
  Some how isolated_credential calls are failing.

  It appears that this might be racing on creating identical roles on
  multiple users - http://logs.openstack.org/26/153426/2/gate/gate-
  tempest-dsvm-
  nova-v21-full/c80cf2c//logs/apache/keystone.txt.gz#_2015-02-06_15_27_17_988

  That's about the time of the failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1419043/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419175] [NEW] DVR qrouter created without OVS qr device

[Zengfa Gao]

Public bug reported:

We have running stable/juno with DVR enabled.
During tests, we created router, gateway and instance.

There is one qrouter on one compute node was created with RuntimeError:

Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 
'ip', 'netns', 'exec', 'qrouter-086cf9e6-4c43-4b65-b623-fbd5d593f687', 'ip', 
'-4', 'neigh', 'replace', '10.100.100.13', 'lladdr', 'fa:16:3e:84:fe:e4', 
'nud', 'permanent', 'dev', 'qr-00d7d90b-01']
Exit code: 1
Stdout: ''
Stderr: 'Cannot find device qr-00d7d90b-01\n'
2015-02-05 20:48:11.834 27031 ERROR neutron.agent.l3_agent 
[req-2c71f61b-c036-4d90-bcfd-75ffdd5340ff None] DVR: Failed updating arp entry
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent Traceback (most 
recent call last):
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent   File 
/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/l3_agent.py,
 line 1719, in _update_arp_entry
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent 
device.neigh.add(net.version, ip, mac)
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent   File 
/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/linux/ip_lib.py,
 line 515, in add
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent 
options=[ip_version])
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent   File 
/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/linux/ip_lib.py,
 line 247, in _as_root
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent 
kwargs.get('use_root_namespace', False))
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent   File 
/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/linux/ip_lib.py,
 line 79, in _as_root
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent 
log_fail_as_error=self.log_fail_as_error)
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent   File 
/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/linux/ip_lib.py,
 line 91, in _execute
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent 
log_fail_as_error=log_fail_as_error)
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent   File 
/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/linux/utils.py,
 line 82, in execute
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent raise 
RuntimeError(m)
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent RuntimeError:

As the result, all future router update failed as well. When the router was 
removed, the qrouter namespace was left on the compute node as well because of 
error:
2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent Stderr: 'Cannot find 
device qr-00d7d90b-01\n'

Logs also can be read at: http://paste.openstack.org/show/168348/

** Affects: neutron
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1419175

Title:
  DVR qrouter created without OVS qr device

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  We have running stable/juno with DVR enabled.
  During tests, we created router, gateway and instance.

  There is one qrouter on one compute node was created with
  RuntimeError:

  Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 
'ip', 'netns', 'exec', 'qrouter-086cf9e6-4c43-4b65-b623-fbd5d593f687', 'ip', 
'-4', 'neigh', 'replace', '10.100.100.13', 'lladdr', 'fa:16:3e:84:fe:e4', 
'nud', 'permanent', 'dev', 'qr-00d7d90b-01']
  Exit code: 1
  Stdout: ''
  Stderr: 'Cannot find device qr-00d7d90b-01\n'
  2015-02-05 20:48:11.834 27031 ERROR neutron.agent.l3_agent 
[req-2c71f61b-c036-4d90-bcfd-75ffdd5340ff None] DVR: Failed updating arp entry
  2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent Traceback (most 
recent call last):
  2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent   File 
/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/l3_agent.py,
 line 1719, in _update_arp_entry
  2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent 
device.neigh.add(net.version, ip, mac)
  2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent   File 
/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/linux/ip_lib.py,
 line 515, in add
  2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent 
options=[ip_version])
  2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent   File 
/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/linux/ip_lib.py,
 line 247, in _as_root
  2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent 
kwargs.get('use_root_namespace', False))
  2015-02-05 20:48:11.834 27031 TRACE neutron.agent.l3_agent   File 

[Yahoo-eng-team] [Bug 1419156] [NEW] Upload Image page is not displayed properly when large_name image is uploaded

[Amogh]

Public bug reported:

1. Login as an admin/tenant user
2. Upload large name images through image file browse, preferable the name 
mentioned below:

SW_DVD5_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_Core_MLF_X19-05182.iso

Observe that upload images page is not displayed correctly.

** Affects: horizon
 Importance: Undecided
 Status: New

** Attachment added: upload_image.PNG
   
https://bugs.launchpad.net/bugs/1419156/+attachment/4313989/+files/upload_image.PNG

** Summary changed:

- Image page is not displayed properly when the large_name image is uploaded
+ Upload Image page is not displayed properly when large_name image is uploaded

-- 
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/1419156

Title:
  Upload Image page is not displayed properly when large_name image is
  uploaded

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  1. Login as an admin/tenant user
  2. Upload large name images through image file browse, preferable the name 
mentioned below:

  
SW_DVD5_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_Core_MLF_X19-05182.iso

  Observe that upload images page is not displayed correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1419156/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419225] [NEW] horizon unit tests report acturally does not generate like others , such as nova, ceilometer...

[guomin.lizte]

Public bug reported:

horizon unit tests report acturally does not generate like others ,such as 
nova,ceilometer..
in nova ,ceilometer,when run the unit tests, it will generate a folder 
.testrepository ; in the folder, I can find the steam messages, the latest 
unittest report can be find in it ;but, when I run horizon unit test, it 
acturally does not  generate a folder .testrepository ;
so anyone can tell me how to generate the report ,thanks.

** 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/1419225

Title:
  horizon unit tests report acturally does not generate like others
  ,such as nova,ceilometer...

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  horizon unit tests report acturally does not generate like others ,such as 
nova,ceilometer..
  in nova ,ceilometer,when run the unit tests, it will generate a folder 
.testrepository ; in the folder, I can find the steam messages, the latest 
unittest report can be find in it ;but, when I run horizon unit test, it 
acturally does not  generate a folder .testrepository ;
  so anyone can tell me how to generate the report ,thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1419225/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419235] [NEW] nova-compute service fails to startup after reboot kvm

[yuxingw]

Public bug reported:

Fail to start  nova-compute service after reboot kvm, here are steps
1: reboot kvm
2:# /etc/init.d/openstack-nova-compute restart

Openstack Version
icehouse
openstack-nova-compute-2014.1.2

Result
Fails to start nova-service and throws the following errors
2015-02-06 15:16:44.761 30137 AUDIT nova.service [-] Starting compute node 
(version 2014.1.2-201408122139.ibm.el6.169)
2015-02-06 15:16:44.998 30137 ERROR nova.openstack.common.threadgroup [-] 
vif_type parameter must be present for this vif_driver implementation
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup Traceback 
(most recent call last):
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.6/site-packages/nova/openstack/common/threadgroup.py, line 
117, in wait
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup 
x.wait()
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.6/site-packages/nova/openstack/common/threadgroup.py, line 
49, in wait
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup 
return self.thread.wait()
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.6/site-packages/eventlet/greenthread.py, line 168, in wait
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup 
return self._exit_event.wait()
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.6/site-packages/eventlet/event.py, line 116, in wait
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup 
return hubs.get_hub().switch()
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.6/site-packages/eventlet/hubs/hub.py, line 187, in switch
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup 
return self.greenlet.switch()
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.6/site-packages/eventlet/greenthread.py, line 194, in main
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup 
result = function(*args, **kwargs)
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.6/site-packages/nova/openstack/common/service.py, line 483, 
in run_service
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup 
service.start()
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.6/site-packages/nova/service.py, line 166, in start
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup 
self.manager.init_host()
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.6/site-packages/nova/compute/manager.py, line 1030, in 
init_host
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup 
self._init_instance(context, instance)
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.6/site-packages/nova/compute/manager.py, line 888, in 
_init_instance
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup 
self.driver.plug_vifs(instance, net_info)
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py, line 861, in 
plug_vifs
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup 
self.vif_driver.plug(instance, vif)
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.6/site-packages/nova/virt/libvirt/vif.py, line 596, in plug
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup 
_(vif_type parameter must be present 
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup 
NovaException: vif_type parameter must be present for this vif_driver 
implementation
2015-02-06 15:16:44.998 30137 TRACE nova.openstack.common.threadgroup

** 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/1419235

Title:
  nova-compute service fails to startup after reboot kvm

Status in OpenStack Compute (Nova):
  New

Bug description:
  Fail to start  nova-compute service after reboot kvm, here are steps
  1: reboot kvm
  2:# /etc/init.d/openstack-nova-compute restart

  Openstack Version
  icehouse
  openstack-nova-compute-2014.1.2

  Result
  Fails to start nova-service and throws the following errors
  2015-02-06 15:16:44.761 30137 AUDIT nova.service [-] Starting compute node 
(version 2014.1.2-201408122139.ibm.el6.169)
  2015-02-06 15:16:44.998 30137 ERROR nova.openstack.common.threadgroup [-] 
vif_type parameter must be present for this vif_driver implementation
  2015-02-06 15:16:44.998 30137 TRACE 

[Yahoo-eng-team] [Bug 1419204] [NEW] edit pencil icon in Users table not aligned

[Cindy Lu]

Public bug reported:

Identity  Users table

It seems that if the cell is empty (e.g. in the email column), the edit
pencil icon gets shifted down - not centered.  See image.

** Affects: horizon
 Importance: Undecided
 Status: New

** Attachment added: Untitled.png
   
https://bugs.launchpad.net/bugs/1419204/+attachment/4314030/+files/Untitled.png

-- 
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/1419204

Title:
  edit pencil icon in Users table not aligned

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Identity  Users table

  It seems that if the cell is empty (e.g. in the email column), the
  edit pencil icon gets shifted down - not centered.  See image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1419204/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1399065] Re: Quota updated through nova api not refelected in Horizon

[Sumanth]

** Changed in: horizon
   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/1399065

Title:
  Quota updated through nova api not refelected in Horizon

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  I am trying to update the quota of the user using the
  nova.quota.update( ... ), when i do this the quota is reflected in the
  commmond line but the same updated values are not reflected in the
  horizon dashboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1399065/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419193] [NEW] missing ceilometer policy support

[David Lyle]

Public bug reported:

Ceilometer recently in Kilo added support for policy checks. This should
be supported in Horizon.

** Affects: horizon
 Importance: Medium
 Assignee: David Lyle (david-lyle)
 Status: New


** Tags: ceilometer

-- 
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/1419193

Title:
  missing ceilometer policy support

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Ceilometer recently in Kilo added support for policy checks. This
  should be supported in Horizon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1419193/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419187] Re: ldap unicode issue

[Morgan Fainberg]

This bug is with the mapping id generator not properly handling encoding
for text strings.

** Changed in: keystone
   Importance: Undecided = Critical

** Changed in: keystone
   Status: New = Triaged

** Also affects: keystone/juno
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1419187

Title:
  ldap unicode issue

Status in OpenStack Identity (Keystone):
  Triaged
Status in Keystone juno series:
  Triaged

Bug description:
  exception when listing users in ldap:

  2015-02-06 14:52:21.934 27199 ERROR keystone.common.wsgi [-] 'ascii' codec 
can't encode character u'\xe9' in position 19: ordinal not in range(128)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi Traceback (most 
recent call last):
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/common/wsgi.py, line 223, in 
__call__
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi result = 
method(context, **params)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/controllers.py, line 48, 
in get_users
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi 
CONF.identity.default_domain_id)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/common/manager.py, line 47, in 
wrapper
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi return f(self, 
*args, **kwargs)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/core.py, line 202, in 
wrapper
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi return f(self, 
*args, **kwargs)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/core.py, line 213, in 
wrapper
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi return f(self, 
*args, **kwargs)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/core.py, line 620, in 
list_users
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi ref_list, 
domain_scope, driver, mapping.EntityType.USER)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/core.py, line 328, in 
_set_domain_id_and_mapping
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi x, domain_id, 
driver, entity_type) for x in ref]
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/core.py, line 325, in 
_set_domain_id_and_mapping
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi ref, domain_id, 
driver, entity_type, conf)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/core.py, line 359, in 
_set_domain_id_and_mapping_for_single_ref
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi local_entity, 
public_id)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/mapping_backends/sql.py, 
line 70, in create_id_mapping
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi public_id = 
self.id_generator_api.generate_public_ID(entity)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi   File 
/usr/lib/python2.7/site-packages/keystone/identity/id_generators/sha256.py, 
line 27, in generate_public_ID
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi 
m.update(mapping[key])
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi UnicodeEncodeError: 
'ascii' codec can't encode character u'\xe9' in position 19: ordinal not in 
range(128)
  2015-02-06 14:52:21.934 27199 TRACE keystone.common.wsgi
  2015-02-06 14:52:21.959 27199 INFO eventlet.wsgi.server [-] 172.20.96.65 - - 
[06/Feb/2015 14:52:21] GET /v2.0/users HTTP/1.1 500 291 23.150229

  
  'local_entity' is here: 
  
https://github.com/openstack/keystone/blob/c4c8d0b99a0404f4dcdb2f87c48fe15ee1526197/keystone/identity/mapping_backends/sql.py#L66

  its: {'local_id': u'^PNNL TQ Communiqu\xe9', 'domain_id': 
'default', 'entity_type': 'user'}

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1419187/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1418871] [NEW] Add styling to password field validation message during create user

[Nikunj Aggarwal]

Public bug reported:

While creating or editing a user in the Users panel, if user enters the
different Confirm Password then it shows a message saying Passwords
do not match..

But it should show this message with a error background.

** Affects: horizon
 Importance: Undecided
 Assignee: Nikunj Aggarwal (nikunj2512)
 Status: New

** Attachment added: edit_user.PNG
   
https://bugs.launchpad.net/bugs/1418871/+attachment/4313750/+files/edit_user.PNG

** Changed in: horizon
 Assignee: (unassigned) = Nikunj Aggarwal (nikunj2512)

-- 
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/1418871

Title:
  Add styling to password field validation message during create user

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  While creating or editing a user in the Users panel, if user enters
  the different Confirm Password then it shows a message saying
  Passwords do not match..

  But it should show this message with a error background.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1418871/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1396854] Re: fail to create an instance with specific ip

[Jerry Zhao]

https://review.openstack.org/#/c/149905/
fixed the bug.

** Changed in: tripleo
   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/1396854

Title:
  fail to create an instance with specific ip

Status in OpenStack Compute (Nova):
  In Progress
Status in tripleo - openstack on openstack:
  Fix Released

Bug description:
  When I using below command to create an instance with specific ip, it
  failed.

  nova boot --image cirros-0.3.2-x86_64-uec --flavor m1.nano --nic net-
  id=5b7930ae-ff24-4dcf-a429-e039cb7502dd,v4-fixed-ip=10.0.0.5 test

  My env is latest devstack on fedora20.



  Here is trace log from nova-compute.
  2014-11-27 11:15:09.565 ERROR nova.compute.manager [-] [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] Instance failed to spawn
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] Traceback (most recent call last):
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9]   File 
/opt/stack/nova/nova/compute/manager.py, line 2247, in _build_resources
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] yield resources
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9]   File 
/opt/stack/nova/nova/compute/manager.py, line 2117, in _build_and_run_instance
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] instance_type=instance_type)
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9]   File 
/opt/stack/nova/nova/virt/libvirt/driver.py, line 2634, in spawn
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] admin_pass=admin_password)
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9]   File 
/opt/stack/nova/nova/virt/libvirt/driver.py, line 3095, in _create_image
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] content=files, extra_md=extra_md, 
network_info=network_info)
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9]   File 
/opt/stack/nova/nova/api/metadata/base.py, line 167, in __init__
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] 
ec2utils.get_ip_info_for_instance_from_nw_info(network_info)
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9]   File 
/opt/stack/nova/nova/api/ec2/ec2utils.py, line 152, in 
get_ip_info_for_instance_from_nw_info
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] fixed_ips = nw_info.fixed_ips()
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9]   File 
/opt/stack/nova/nova/network/model.py, line 450, in _sync_wrapper
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] self.wait()
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9]   File 
/opt/stack/nova/nova/network/model.py, line 482, in wait
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] self[:] = self._gt.wait()
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9]   File 
/usr/lib/python2.7/site-packages/eventlet/greenthread.py, line 173, in wait
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] return self._exit_event.wait()
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9]   File 
/usr/lib/python2.7/site-packages/eventlet/event.py, line 125, in wait
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] current.throw(*self._exc)
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9]   File 
/usr/lib/python2.7/site-packages/eventlet/greenthread.py, line 212, in main
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] result = function(*args, **kwargs)
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9]   File 
/opt/stack/nova/nova/compute/manager.py, line 1647, in _allocate_network_async
  2014-11-27 11:15:09.565 TRACE nova.compute.manager [instance: 
1a8295a2-80b5-4f5c-81bb-414aa832f6b9] dhcp_options=dhcp_options)
  2014-11-27 11:15:09.565 TRACE nova.compute.manager 

[Yahoo-eng-team] [Bug 1419002] [NEW] nova do not compain if 'my_ip' is wrong

[George Shuklin]

Public bug reported:

If my_ip in nova config do not exit on any interface of the compute
host, nova-compute silently accepts it and failing cold migration.

Expected behaviour: error or warning if my_ip can not be found on any
interface.

Nova version: 1:2014.2.1-0ubuntu1~cloud0

** 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/1419002

Title:
  nova do not compain if 'my_ip' is wrong

Status in OpenStack Compute (Nova):
  New

Bug description:
  If my_ip in nova config do not exit on any interface of the compute
  host, nova-compute silently accepts it and failing cold migration.

  Expected behaviour: error or warning if my_ip can not be found on any
  interface.

  Nova version: 1:2014.2.1-0ubuntu1~cloud0

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1419002/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1418994] [NEW] Project was disabled without doing explicit changes to it by user

[Kyrylo Romanenko]

Public bug reported:

Project was disabled without doing explicit changes to it by user.

Steps:
1. Login to Horizon as admin.
2. Create TESTPROJECT project.
3. Create testuser user (with TESTPROJECT as primary project).
4. Assign testuser into TESTPROJECT as _member_ and admin roles.
5. Logout
6. Go to Identity - Projects.
7. Click Edit Project or Manage Members menu for TESTPROJECT, Edit Project 
dialog will open.

8. Do nothing, just view. And then click Save.

Got red error popups on page:
Error: Unauthorized: Failed to modify 0 project members and update project 
quotas.
Error: Unable to modify project TESTPROJECT.
Error: Unauthorized: Unable to retrieve project list.

9. Logout. Now you can not login back as testuser: 
Unable to authenticate to any available projects.

10. Login back as admin. 
11. Go to Identity - Projects. 
12. Look at row of TESTPROJECT, column Enabled:
Enabled=False
Open Edit Project dialog. 
Checkbox Enabled is set OFF also.

Horizon and Keystone logs fragments attached.

Environment
Devstack:
os|distro=trusty
os|vendor=Ubuntu
os|release=14.04
git|cinder|master[2079b0f]
git|glance|master[8d21220]
git|heat|master[6d6e417]
git|heat-cfntools|master[a7ffb71]
git|heat-templates|master[35e6837]
git|horizon|master[680488d]
git|keystone|master[e54c323]
git|nova|master[422b22e]

Browser:  Chrome Version 40.0.2214.95 (64-bit)

** Affects: horizon
 Importance: Undecided
 Status: New


** Tags: horizon-core keystone

** Attachment added: log_snippets.zip
   
https://bugs.launchpad.net/bugs/1418994/+attachment/4313885/+files/log_snippets.zip

-- 
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/1418994

Title:
  Project was disabled without doing explicit changes to it by user

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Project was disabled without doing explicit changes to it by user.

  Steps:
  1. Login to Horizon as admin.
  2. Create TESTPROJECT project.
  3. Create testuser user (with TESTPROJECT as primary project).
  4. Assign testuser into TESTPROJECT as _member_ and admin roles.
  5. Logout
  6. Go to Identity - Projects.
  7. Click Edit Project or Manage Members menu for TESTPROJECT, Edit 
Project dialog will open.

  8. Do nothing, just view. And then click Save.

  Got red error popups on page:
  Error: Unauthorized: Failed to modify 0 project members and update project 
quotas.
  Error: Unable to modify project TESTPROJECT.
  Error: Unauthorized: Unable to retrieve project list.

  9. Logout. Now you can not login back as testuser: 
  Unable to authenticate to any available projects.

  10. Login back as admin. 
  11. Go to Identity - Projects. 
  12. Look at row of TESTPROJECT, column Enabled:
  Enabled=False
  Open Edit Project dialog. 
  Checkbox Enabled is set OFF also.

  Horizon and Keystone logs fragments attached.

  Environment
  Devstack:
  os|distro=trusty
  os|vendor=Ubuntu
  os|release=14.04
  git|cinder|master[2079b0f]
  git|glance|master[8d21220]
  git|heat|master[6d6e417]
  git|heat-cfntools|master[a7ffb71]
  git|heat-templates|master[35e6837]
  git|horizon|master[680488d]
  git|keystone|master[e54c323]
  git|nova|master[422b22e]

  Browser:  Chrome Version 40.0.2214.95 (64-bit)

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1418994/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1418868] [NEW] duplicate operations when deleting tokens

[wanghong]

Public bug reported:

In token.persistence.core:PersistenceManager.delete_tokens method, we would:
1. List tokens that going to be deleted
2. Delete tokens, note that here we wouldn't use the data got before
3. Loop the tokens got before and invalidate token cache
There are two issues here:
1. Tokens got before may not equal with tokens that deleted
2. According to current code, we do list twice both in sql and kvs backends
Refer to:
https://github.com/openstack/keystone/blob/master/keystone/token/persistence/core.py#L116

** Affects: keystone
 Importance: Undecided
 Assignee: wanghong (w-wanghong)
 Status: New

** Changed in: keystone
 Assignee: (unassigned) = wanghong (w-wanghong)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1418868

Title:
  duplicate operations when deleting tokens

Status in OpenStack Identity (Keystone):
  New

Bug description:
  In token.persistence.core:PersistenceManager.delete_tokens method, we would:
  1. List tokens that going to be deleted
  2. Delete tokens, note that here we wouldn't use the data got before
  3. Loop the tokens got before and invalidate token cache
  There are two issues here:
  1. Tokens got before may not equal with tokens that deleted
  2. According to current code, we do list twice both in sql and kvs backends
  Refer to:
  
https://github.com/openstack/keystone/blob/master/keystone/token/persistence/core.py#L116

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1418868/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1418675] Re: libvirt utils doesn't canonicalize the image architecture property

[Markus Zoeller]

** Also affects: glance
   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/1418675

Title:
  libvirt utils doesn't canonicalize the image architecture property

Status in OpenStack Image Registry and Delivery Service (Glance):
  New
Status in OpenStack Compute (Nova):
  New

Bug description:
  If the image has an architecture property, the libvirt utils do *not*
  canonicalize that.

  ``utils.get_arch(image_meta)`` can possibly return S390X (= upper
  case). The canonicalized version should be s390x (= lower case).

  This will be an issue when a user adds the property
  architecture=S390X on an image.

  I used S390X as an arbitrary example. The real issue here is the
  lower case and upper case thing.

  See method ``get_arch(image_meta)`` in 
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/utils.py#L557
  See method ``canonicalize(name)`` in 
https://github.com/openstack/nova/blob/master/nova/compute/arch.py#L147

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1418675/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1418923] [NEW] The logger WatchedFileHandler don't write to nova.log

[Wu Hong Guang]

Public bug reported:

The following is the change i made to  /etc/nova/logging.conf ,

[logger_nova]
level = DEBUG
handlers = watchedfile
qualname = nova

[handler_watchedfile]
class = handlers.WatchedFileHandler
args = ('/var/log/nova/nova.log',)
formatter = context

 there is no nova.log after restart nova* service and all service are up

** Affects: nova
 Importance: Undecided
 Status: New

** Description changed:

- The following is the /etc/nova/logging.conf ,  there is no nova.log
- after restart nova* service
- 
- [loggers]
- keys = root, nova
- 
- [handlers]
- keys = stderr, stdout, watchedfile, syslog, null
- 
- [formatters]
- keys = context, default
- 
- [logger_root]
- level = INFO
- handlers = null
+ The following is the change i made to  /etc/nova/logging.conf ,
  
  [logger_nova]
  level = DEBUG
  handlers = watchedfile
  qualname = nova
  
- [logger_amqp]
- level = WARNING
- handlers = stderr
- qualname = amqp
- 
- [logger_amqplib]
- level = WARNING
- handlers = stderr
- qualname = amqplib
- 
- [logger_sqlalchemy]
- level = WARNING
- handlers = stderr
- qualname = sqlalchemy
- # level = INFO logs SQL queries.
- # level = DEBUG logs SQL queries and results.
- # level = WARNING logs neither.  (Recommended for production systems.)
- 
- [logger_boto]
- level = WARNING
- handlers = stderr
- qualname = boto
- 
- [logger_suds]
- level = INFO
- handlers = stderr
- qualname = suds
- 
- [logger_eventletwsgi]
- level = WARNING
- handlers = stderr
- qualname = eventlet.wsgi.server
- 
- [handler_stderr]
- class = StreamHandler
- args = (sys.stderr,)
- formatter = context
- 
- [handler_stdout]
- class = StreamHandler
- args = (sys.stdout,)
- formatter = context
  
  [handler_watchedfile]
  class = handlers.WatchedFileHandler
  args = ('/var/log/nova/nova.log',)
  formatter = context
  
- [handler_syslog]
- class = handlers.SysLogHandler
- args = ('/dev/log', handlers.SysLogHandler.LOG_USER)
- formatter = context
- 
- [handler_null]
- class = nova.openstack.common.log.NullHandler
- formatter = default
- args = ()
- 
- [formatter_context]
- class = nova.openstack.common.log.ContextFormatter
- 
- [formatter_default]
- format = %(message)s
+  there is no nova.log after restart nova* service

** Description changed:

  The following is the change i made to  /etc/nova/logging.conf ,
  
  [logger_nova]
  level = DEBUG
  handlers = watchedfile
  qualname = nova
  
- 
  [handler_watchedfile]
  class = handlers.WatchedFileHandler
  args = ('/var/log/nova/nova.log',)
  formatter = context
  
-  there is no nova.log after restart nova* service
+  there is no nova.log after restart nova* service and all service are up

-- 
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/1418923

Title:
  The logger WatchedFileHandler don't write to nova.log

Status in OpenStack Compute (Nova):
  New

Bug description:
  The following is the change i made to  /etc/nova/logging.conf ,

  [logger_nova]
  level = DEBUG
  handlers = watchedfile
  qualname = nova

  [handler_watchedfile]
  class = handlers.WatchedFileHandler
  args = ('/var/log/nova/nova.log',)
  formatter = context

   there is no nova.log after restart nova* service and all service are
  up

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1418923/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419040] [NEW] Add copy_from upload option to image creation in v2

[Julie Pichon]

Public bug reported:

Horizon relies heavily on the copy_from attribute when creating new
images, for example from feedback from deployers we even offer the
option to entirely disallow direct file uploads [1] [2] and only let
end-user create new images by indicating a URL.

It is my understanding that the copy_from attribute isn't currently
implemented in Glance v2. As we slowly add proper support for v2 to
Horizon [3] it would be really helpful if there was a way to create an
image given a URL when using v2 also. If this is already tracked
somewhere else, please me know! Thank you.

[1] 
http://docs.openstack.org/developer/horizon/topics/deployment.html#file-uploads
[2] 
http://docs.openstack.org/developer/horizon/topics/settings.html#horizon-images-allow-upload
[3] https://blueprints.launchpad.net/horizon/+spec/horizon-glance-v2

** Affects: glance
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1419040

Title:
  Add copy_from upload option to image creation in v2

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  Horizon relies heavily on the copy_from attribute when creating new
  images, for example from feedback from deployers we even offer the
  option to entirely disallow direct file uploads [1] [2] and only let
  end-user create new images by indicating a URL.

  It is my understanding that the copy_from attribute isn't currently
  implemented in Glance v2. As we slowly add proper support for v2 to
  Horizon [3] it would be really helpful if there was a way to create an
  image given a URL when using v2 also. If this is already tracked
  somewhere else, please me know! Thank you.

  [1] 
http://docs.openstack.org/developer/horizon/topics/deployment.html#file-uploads
  [2] 
http://docs.openstack.org/developer/horizon/topics/settings.html#horizon-images-allow-upload
  [3] https://blueprints.launchpad.net/horizon/+spec/horizon-glance-v2

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1419040/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419016] [NEW] New project in dropdown list becomes visible after logout

[Kyrylo Romanenko]

Public bug reported:

There is projects selection dropdown on top of Horizon, right from OpenStack 
logo.
New project in dropdown list becomes visible only after logout and re-login.

Steps:
1) Login to Horizon as admin
2) Go to Identity - Project
3) Create new project NEW .
4) Add admin as _member_ to this project.
5) Click on project selector dropdown (screenshot part 1).

Expected to see NEW project there.
Actually it`s not present there.

Now you have to log-out and log-in  to see NEW project there
(screenshot part 2).

Environment:
MOS 6.1 build:
{build_id: 2015-02-01_22-55-01, ostf_sha: 
c9100263140008abfcc2704732e98fbdfd644068, build_number: 92, 
release_versions: {2014.2-6.1: {VERSION: {build_id: 
2015-02-01_22-55-01, ostf_sha: c9100263140008abfcc2704732e98fbdfd644068, 
build_number: 92, api: 1.0, nailgun_sha: 
c0932eb5c2aa7fd1e13a999cb1b4bf5aff101c3b, production: docker, 
python-fuelclient_sha: 2ea7b3e91c1d2ff85110bf5abb161a6f4e537358, 
astute_sha: ed5270bf9c6c1234797e00bd7d4dd3213253a413, feature_groups: 
[mirantis], release: 6.1, fuelmain_sha: , fuellib_sha: 
c5e4a0410ba66f9e9911f62b3b71c0b9c29aed6e}}}, auth_required: true, api: 
1.0, nailgun_sha: c0932eb5c2aa7fd1e13a999cb1b4bf5aff101c3b, production: 
docker, python-fuelclient_sha: 2ea7b3e91c1d2ff85110bf5abb161a6f4e537358, 
astute_sha: ed5270bf9c6c1234797e00bd7d4dd3213253a413, feature_groups: 
[mirantis], release: 6.1, fuelmain_sha: , fuellib_sha: 
c5e4a0410ba66f9e9911f62b3b71c0b9c2
 9aed6e}

Also on Devstack:
Devstack:
os|distro=trusty
os|vendor=Ubuntu
os|release=14.04
git|cinder|master[2079b0f]
git|glance|master[8d21220]
git|heat|master[6d6e417]
git|heat-cfntools|master[a7ffb71]
git|heat-templates|master[35e6837]
git|horizon|master[680488d]
git|keystone|master[e54c323]
git|nova|master[422b22e]

Browsers: Chrome Version 40.0.2214.95 (64-bit), Firefox 35.0.1.

** Affects: horizon
 Importance: Undecided
 Status: New

** Affects: mos
 Importance: Undecided
 Status: New


** Tags: horizon

** Attachment added: NEW_Project.png
   
https://bugs.launchpad.net/bugs/1419016/+attachment/4313892/+files/NEW_Project.png

** Description changed:

  There is projects selection dropdown on top of Horizon, right from OpenStack 
logo.
  New project in dropdown list becomes visible only after logout and re-login.
  
- Steps: 
+ Steps:
  1) Login to Horizon as admin
  2) Go to Identity - Project
  3) Create new project NEW .
  4) Add admin as _member_ to this project.
  5) Click on project selector dropdown (screenshot part 1).
  
- Expected to see NEW project there. 
- Actually it`s not present there. 
+ Expected to see NEW project there.
+ Actually it`s not present there.
  
  Now you have to log-out and log-in  to see NEW project there
  (screenshot part 2).
  
- Environment: 
- MOS 6.1 build: 
+ Environment:
+ MOS 6.1 build:
  {build_id: 2015-02-01_22-55-01, ostf_sha: 
c9100263140008abfcc2704732e98fbdfd644068, build_number: 92, 
release_versions: {2014.2-6.1: {VERSION: {build_id: 
2015-02-01_22-55-01, ostf_sha: c9100263140008abfcc2704732e98fbdfd644068, 
build_number: 92, api: 1.0, nailgun_sha: 
c0932eb5c2aa7fd1e13a999cb1b4bf5aff101c3b, production: docker, 
python-fuelclient_sha: 2ea7b3e91c1d2ff85110bf5abb161a6f4e537358, 
astute_sha: ed5270bf9c6c1234797e00bd7d4dd3213253a413, feature_groups: 
[mirantis], release: 6.1, fuelmain_sha: , fuellib_sha: 
c5e4a0410ba66f9e9911f62b3b71c0b9c29aed6e}}}, auth_required: true, api: 
1.0, nailgun_sha: c0932eb5c2aa7fd1e13a999cb1b4bf5aff101c3b, production: 
docker, python-fuelclient_sha: 2ea7b3e91c1d2ff85110bf5abb161a6f4e537358, 
astute_sha: ed5270bf9c6c1234797e00bd7d4dd3213253a413, feature_groups: 
[mirantis], release: 6.1, fuelmain_sha: , fuellib_sha: 
c5e4a0410ba66f9e9911f62b3b71c0b9
 c29aed6e}
  
+ Also on Devstack:
+ Devstack:
+ os|distro=trusty
+ os|vendor=Ubuntu
+ os|release=14.04
+ git|cinder|master[2079b0f]
+ git|glance|master[8d21220]
+ git|heat|master[6d6e417]
+ git|heat-cfntools|master[a7ffb71]
+ git|heat-templates|master[35e6837]
+ git|horizon|master[680488d]
+ git|keystone|master[e54c323]
+ git|nova|master[422b22e]
+ 
  Browsers: Chrome Version 40.0.2214.95 (64-bit), Firefox 35.0.1.

** Project changed: mos = horizon

** Also affects: mos
   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/1419016

Title:
  New project in dropdown list becomes visible after logout

Status in OpenStack Dashboard (Horizon):
  New
Status in Mirantis OpenStack:
  New

Bug description:
  There is projects selection dropdown on top of Horizon, right from OpenStack 
logo.
  New project in dropdown list becomes visible only after logout and re-login.

  Steps:
  1) Login to Horizon as admin
  2) Go to Identity - Project
  3) Create new project NEW .
  4) Add admin as _member_ to this project.
  5) Click on project selector dropdown (screenshot part 

[Yahoo-eng-team] [Bug 1419047] [NEW] Error on nova compute on Power

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm trying to deploy OpenStack in a Power 8 server on a single node.

I've created 1 VM for MAAS, 1 VM for juju bootstrap and 4 VMs to use
them as compute, ceph and to hold all the OpenStack services.

I've deployed OpenStack and everything seemed to work fine, however, I
don't see any hypervisor. When I check into the nova logs I find:

2015-02-06 11:36:25.499 54731 TRACE nova.openstack.common.threadgroup 
libvirtError: XML error: Missing CPU model name
2015-02-06 13:08:29.419 66757 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 2885, in 
get_host_capabilities
2015-02-06 13:08:29.419 66757 TRACE nova.openstack.common.threadgroup 
libvirt.VIR_CONNECT_BASELINE_CPU_EXPAND_FEATURES)

** Affects: nova
 Importance: Undecided
 Status: New

-- 
Error on nova compute on Power
https://bugs.launchpad.net/bugs/1419047
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to OpenStack Compute (nova).

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419047] [NEW] Error on nova compute on Power

[Victor Estival]

Public bug reported:

I'm trying to deploy OpenStack in a Power 8 server on a single node.

I've created 1 VM for MAAS, 1 VM for juju bootstrap and 4 VMs to use
them as compute, ceph and to hold all the OpenStack services.

I've deployed OpenStack and everything seemed to work fine, however, I
don't see any hypervisor. When I check into the nova logs I find:

2015-02-06 11:36:25.499 54731 TRACE nova.openstack.common.threadgroup 
libvirtError: XML error: Missing CPU model name
2015-02-06 13:08:29.419 66757 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 2885, in 
get_host_capabilities
2015-02-06 13:08:29.419 66757 TRACE nova.openstack.common.threadgroup 
libvirt.VIR_CONNECT_BASELINE_CPU_EXPAND_FEATURES)

** Affects: nova
 Importance: Undecided
 Status: New

** Project changed: barbican = 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/1419047

Title:
  Error on nova compute on Power

Status in OpenStack Compute (Nova):
  New

Bug description:
  I'm trying to deploy OpenStack in a Power 8 server on a single node.

  I've created 1 VM for MAAS, 1 VM for juju bootstrap and 4 VMs to use
  them as compute, ceph and to hold all the OpenStack services.

  I've deployed OpenStack and everything seemed to work fine, however, I
  don't see any hypervisor. When I check into the nova logs I find:

  2015-02-06 11:36:25.499 54731 TRACE nova.openstack.common.threadgroup 
libvirtError: XML error: Missing CPU model name
  2015-02-06 13:08:29.419 66757 TRACE nova.openstack.common.threadgroup   File 
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 2885, in 
get_host_capabilities
  2015-02-06 13:08:29.419 66757 TRACE nova.openstack.common.threadgroup 
libvirt.VIR_CONNECT_BASELINE_CPU_EXPAND_FEATURES)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1419047/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419016] Re: New project in dropdown list

[Timur Sufiev]

Thank you for the detailed description, but this issue has been already
fixed in https://bugs.launchpad.net/horizon/+bug/1393659 K-1 milestone.
So it makes sense to backport the change to other MOS branches as well.

** No longer affects: horizon

** Changed in: mos
Milestone: None = 6.1

** Changed in: mos
 Assignee: (unassigned) = MOS Sustaining (mos-sustaining)

** Changed in: mos
   Importance: Undecided = Medium

** Also affects: mos/5.1.x
   Importance: Undecided
   Status: New

** Also affects: mos/6.0.x
   Importance: Undecided
   Status: New

** Changed in: mos/5.1.x
   Importance: Undecided = Medium

** Changed in: mos/6.0.x
   Importance: Undecided = Medium

** Changed in: mos/5.1.x
Milestone: None = 5.1.2

** Changed in: mos/5.1.x
 Assignee: (unassigned) = MOS Sustaining (mos-sustaining)

** Changed in: mos/6.0.x
 Assignee: (unassigned) = MOS Sustaining (mos-sustaining)

** Changed in: mos/6.0.x
Milestone: None = 6.0.1

-- 
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/1419016

Title:
  New project in dropdown list

Status in Mirantis OpenStack:
  New
Status in Mirantis OpenStack 5.1.x series:
  New
Status in Mirantis OpenStack 6.0.x series:
  New

Bug description:
  There is projects selection dropdown on top of Horizon, right from OpenStack 
logo.
  New project in dropdown list becomes visible only after logout and re-login.

  Steps:
  1) Login to Horizon as admin
  2) Go to Identity - Project
  3) Create new project NEW .
  4) Add admin as _member_ to this project.
  5) Click on project selector dropdown (screenshot part 1).

  Expected to see NEW project there.
  Actually it`s not present there.

  Now you have to log-out and log-in  to see NEW project there
  (screenshot part 2).

  Environment:
  MOS 6.1 build:
  {build_id: 2015-02-01_22-55-01, ostf_sha: 
c9100263140008abfcc2704732e98fbdfd644068, build_number: 92, 
release_versions: {2014.2-6.1: {VERSION: {build_id: 
2015-02-01_22-55-01, ostf_sha: c9100263140008abfcc2704732e98fbdfd644068, 
build_number: 92, api: 1.0, nailgun_sha: 
c0932eb5c2aa7fd1e13a999cb1b4bf5aff101c3b, production: docker, 
python-fuelclient_sha: 2ea7b3e91c1d2ff85110bf5abb161a6f4e537358, 
astute_sha: ed5270bf9c6c1234797e00bd7d4dd3213253a413, feature_groups: 
[mirantis], release: 6.1, fuelmain_sha: , fuellib_sha: 
c5e4a0410ba66f9e9911f62b3b71c0b9c29aed6e}}}, auth_required: true, api: 
1.0, nailgun_sha: c0932eb5c2aa7fd1e13a999cb1b4bf5aff101c3b, production: 
docker, python-fuelclient_sha: 2ea7b3e91c1d2ff85110bf5abb161a6f4e537358, 
astute_sha: ed5270bf9c6c1234797e00bd7d4dd3213253a413, feature_groups: 
[mirantis], release: 6.1, fuelmain_sha: , fuellib_sha: 
c5e4a0410ba66f9e9911f62b3b71c0b9
 c29aed6e}

  Also on Devstack:
  Devstack:
  os|distro=trusty
  os|vendor=Ubuntu
  os|release=14.04
  git|cinder|master[2079b0f]
  git|glance|master[8d21220]
  git|heat|master[6d6e417]
  git|heat-cfntools|master[a7ffb71]
  git|heat-templates|master[35e6837]
  git|horizon|master[680488d]
  git|keystone|master[e54c323]
  git|nova|master[422b22e]

  Browsers: Chrome Version 40.0.2214.95 (64-bit), Firefox 35.0.1.

  UPD: 
  It looks possible to update  dropdown list without re-login. 
  For that you have to choose another project in drop-down list. 
  Then our NEW project gets into list too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mos/+bug/1419016/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419043] Re: Conflict on isolated credential setup

[Matthew Treinish]

Looking through the failure logs this doesn't appear to be a tempest
issue. Tempest is just triggering a race in keystone.

** Changed in: tempest
   Importance: High = Undecided

** Changed in: tempest
   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/1419043

Title:
  Conflict on isolated credential setup

Status in OpenStack Identity (Keystone):
  Confirmed
Status in Tempest:
  Invalid

Bug description:
  From the following run (in progress) -
  http://logs.openstack.org/26/153426/2/gate/gate-tempest-dsvm-
  nova-v21-full/c80cf2c//console.html

  2015-02-06 15:50:27.935 | ==
  2015-02-06 15:50:27.935 | Failed 1 tests - output below:
  2015-02-06 15:50:27.935 | ==
  2015-02-06 15:50:27.935 | 
  2015-02-06 15:50:27.935 | setUpClass 
(tempest.api.compute.admin.test_aggregates_negative.AggregatesAdminNegativeTestJSON)
  2015-02-06 15:50:27.936 | 
---
  2015-02-06 15:50:27.936 | 
  2015-02-06 15:50:27.936 | Captured traceback:
  2015-02-06 15:50:27.936 | ~~~
  2015-02-06 15:50:27.936 | Traceback (most recent call last):
  2015-02-06 15:50:27.936 |   File tempest/test.py, line 273, in 
setUpClass
  2015-02-06 15:50:27.936 | cls.resource_setup()
  2015-02-06 15:50:27.936 |   File 
tempest/api/compute/admin/test_aggregates_negative.py, line 31, in 
resource_setup
  2015-02-06 15:50:27.936 | super(AggregatesAdminNegativeTestJSON, 
cls).resource_setup()
  2015-02-06 15:50:27.936 |   File tempest/api/compute/base.py, line 341, 
in resource_setup
  2015-02-06 15:50:27.936 | super(BaseComputeAdminTest, 
cls).resource_setup()
  2015-02-06 15:50:27.936 |   File tempest/api/compute/base.py, line 44, 
in resource_setup
  2015-02-06 15:50:27.937 | cls.os = cls.get_client_manager()
  2015-02-06 15:50:27.937 |   File tempest/test.py, line 407, in 
get_client_manager
  2015-02-06 15:50:27.937 | creds = 
cls.isolated_creds.get_primary_creds()
  2015-02-06 15:50:27.937 |   File tempest/common/isolated_creds.py, line 
273, in get_primary_creds
  2015-02-06 15:50:27.937 | return self.get_credentials('primary')
  2015-02-06 15:50:27.937 |   File tempest/common/isolated_creds.py, line 
257, in get_credentials
  2015-02-06 15:50:27.937 | credentials = 
self._create_creds(admin=is_admin)
  2015-02-06 15:50:27.937 |   File tempest/common/isolated_creds.py, line 
119, in _create_creds
  2015-02-06 15:50:27.937 | tenant, email)
  2015-02-06 15:50:27.937 |   File tempest/common/isolated_creds.py, line 
65, in _create_user
  2015-02-06 15:50:27.937 | username, password, tenant['id'], email)
  2015-02-06 15:50:27.937 |   File 
tempest/services/identity/json/identity_client.py, line 168, in create_user
  2015-02-06 15:50:27.938 | resp, body = self.post('users', post_body)
  2015-02-06 15:50:27.938 |   File 
/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py,
 line 169, in post
  2015-02-06 15:50:27.938 | return self.request('POST', url, 
extra_headers, headers, body)
  2015-02-06 15:50:27.938 |   File tempest/common/service_client.py, line 
69, in request
  2015-02-06 15:50:27.938 | raise exceptions.Conflict(ex)
  2015-02-06 15:50:27.938 | Conflict: An object with that identifier 
already exists
  2015-02-06 15:50:27.938 | Details: An object with that identifier already 
exists
  2015-02-06 15:50:27.938 | Details: {u'title': u'Conflict', u'message': 
u'Conflict occurred attempting to store role - Duplicate Entry', u'code': 409}
  2015-02-06 15:50:27.938 | 

  
  Some how isolated_credential calls are failing.

  It appears that this might be racing on creating identical roles on
  multiple users - http://logs.openstack.org/26/153426/2/gate/gate-
  tempest-dsvm-
  nova-v21-full/c80cf2c//logs/apache/keystone.txt.gz#_2015-02-06_15_27_17_988

  That's about the time of the failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1419043/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1418956] [NEW] Test utilities assume use of assignment api

[Henry Nash]

Public bug reported:

Our test fixtures and v3 test utils call the assignment API under the
hood to create assignments. This is normally absolutely fine, although
for developers looking to replace the assignments engine with their own,
such APIs might fail. While a fuller solution would be to allow the
disabling of all existing assignments tests, a simple thing we can do to
let out-of-tree experimentation to at least use our test fixtures/utils
is not to error out if the assignment APIs return NotImplemented.

** Affects: keystone
 Importance: Wishlist
 Assignee: Henry Nash (henry-nash)
 Status: New


** Tags: test-improvement

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1418956

Title:
  Test utilities assume use of assignment api

Status in OpenStack Identity (Keystone):
  New

Bug description:
  Our test fixtures and v3 test utils call the assignment API under the
  hood to create assignments. This is normally absolutely fine, although
  for developers looking to replace the assignments engine with their
  own, such APIs might fail. While a fuller solution would be to allow
  the disabling of all existing assignments tests, a simple thing we can
  do to let out-of-tree experimentation to at least use our test
  fixtures/utils is not to error out if the assignment APIs return
  NotImplemented.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1418956/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419010] [NEW] Thin the ML2 Cisco Nexus Driver

[Sam Betts]

Public bug reported:

Cisco vendor code is now moving out of the neutron tree and this bug
tracks the thinning of the Cisco nexus ml2 driver.

** Affects: neutron
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1419010

Title:
  Thin the ML2 Cisco Nexus Driver

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Cisco vendor code is now moving out of the neutron tree and this bug
  tracks the thinning of the Cisco nexus ml2 driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1419010/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1418990] Re: Conflict between global-requirements and keystone/nova-requirements

[Sergey Vilgelm]

I'm sorry. This bug touched only our modified version of devstack.

** Changed in: keystone
   Status: New = Invalid

** Changed in: nova
   Status: New = 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/1418990

Title:
  Conflict between global-requirements and keystone/nova-requirements

Status in OpenStack Identity (Keystone):
  Invalid
Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  At 5th of February was merged the patch 
https://review.openstack.org/#/c/153171/ changed the global requirements.
  The error in the devstack installation process:

  2015-02-06 13:35:47.117 | + /usr/local/bin/nova-manage db sync
  2015-02-06 13:35:47.218 | Traceback (most recent call last):
  2015-02-06 13:35:47.218 |   File /usr/local/bin/nova-manage, line 5, in 
module
  2015-02-06 13:35:47.218 | from pkg_resources import load_entry_point
  2015-02-06 13:35:47.219 |   File 
/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 3018, 
in module
  2015-02-06 13:35:47.219 | working_set = WorkingSet._build_master()
  2015-02-06 13:35:47.219 |   File 
/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 614, 
in _build_master
  2015-02-06 13:35:47.219 | return 
cls._build_from_requirements(__requires__)
  2015-02-06 13:35:47.219 |   File 
/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 627, 
in _build_from_requirements
  2015-02-06 13:35:47.220 | dists = ws.resolve(reqs, Environment())
  2015-02-06 13:35:47.220 |   File 
/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 805, 
in resolve
  2015-02-06 13:35:47.220 | raise DistributionNotFound(req)
  2015-02-06 13:35:47.220 | pkg_resources.DistributionNotFound: 
pycadf0.6.0,=0.4.1

  The installed version of pycadf is 0.6.0.

  This problem related to icehouse version. We have to run the OpenStack
  Proposal Bot to update the keystone and nova requirements for
  stable/icehouse branch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1418990/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419070] [NEW] Dropdown for Domains and Projects always shows Default for Domains

[Brad Pokorny]

Public bug reported:

After logging into Horizon with a domain other than Default, the
dropdown for Domains and Projects always shows Default for the
Domains.  It would make more sense to users if it showed the domain
they logged in with.

I've been doing some testing with
https://review.openstack.org/#/c/141153/ and
https://review.openstack.org/#/c/148082/ , and this situation still
exists - even though we can now get a token scoped to the domain the
user logged in with.

** 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/1419070

Title:
  Dropdown for Domains and Projects always shows Default for Domains

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  After logging into Horizon with a domain other than Default, the
  dropdown for Domains and Projects always shows Default for the
  Domains.  It would make more sense to users if it showed the domain
  they logged in with.

  I've been doing some testing with
  https://review.openstack.org/#/c/141153/ and
  https://review.openstack.org/#/c/148082/ , and this situation still
  exists - even though we can now get a token scoped to the domain the
  user logged in with.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1419070/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1418994] Re: Project was disabled without doing explicit changes to it by user

[Timur Sufiev]

*** This bug is a duplicate of bug 1413068 ***
https://bugs.launchpad.net/bugs/1413068

** This bug has been marked a duplicate of bug 1413068
   Edit current project will disable it

-- 
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/1418994

Title:
  Project was disabled without doing explicit changes to it by user

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Project was disabled without doing explicit changes to it by user.

  Steps:
  1. Login to Horizon as admin.
  2. Create TESTPROJECT project.
  3. Create testuser user (with TESTPROJECT as primary project).
  4. Assign testuser into TESTPROJECT as _member_ and admin roles.
  5. Logout
  6. Go to Identity - Projects.
  7. Click Edit Project or Manage Members menu for TESTPROJECT, Edit 
Project dialog will open.

  8. Do nothing, just view. And then click Save.

  Got red error popups on page:
  Error: Unauthorized: Failed to modify 0 project members and update project 
quotas.
  Error: Unable to modify project TESTPROJECT.
  Error: Unauthorized: Unable to retrieve project list.

  9. Logout. Now you can not login back as testuser: 
  Unable to authenticate to any available projects.

  10. Login back as admin. 
  11. Go to Identity - Projects. 
  12. Look at row of TESTPROJECT, column Enabled:
  Enabled=False
  Open Edit Project dialog. 
  Checkbox Enabled is set OFF also.

  Horizon and Keystone logs fragments attached.

  Environment
  Devstack:
  os|distro=trusty
  os|vendor=Ubuntu
  os|release=14.04
  git|cinder|master[2079b0f]
  git|glance|master[8d21220]
  git|heat|master[6d6e417]
  git|heat-cfntools|master[a7ffb71]
  git|heat-templates|master[35e6837]
  git|horizon|master[680488d]
  git|keystone|master[e54c323]
  git|nova|master[422b22e]

  Browser:  Chrome Version 40.0.2214.95 (64-bit)

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1418994/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419043] [NEW] Conflict on isolated credential setup

[Sean Dague]

Public bug reported:

From the following run (in progress) -
http://logs.openstack.org/26/153426/2/gate/gate-tempest-dsvm-
nova-v21-full/c80cf2c//console.html

2015-02-06 15:50:27.935 | ==
2015-02-06 15:50:27.935 | Failed 1 tests - output below:
2015-02-06 15:50:27.935 | ==
2015-02-06 15:50:27.935 | 
2015-02-06 15:50:27.935 | setUpClass 
(tempest.api.compute.admin.test_aggregates_negative.AggregatesAdminNegativeTestJSON)
2015-02-06 15:50:27.936 | 
---
2015-02-06 15:50:27.936 | 
2015-02-06 15:50:27.936 | Captured traceback:
2015-02-06 15:50:27.936 | ~~~
2015-02-06 15:50:27.936 | Traceback (most recent call last):
2015-02-06 15:50:27.936 |   File tempest/test.py, line 273, in setUpClass
2015-02-06 15:50:27.936 | cls.resource_setup()
2015-02-06 15:50:27.936 |   File 
tempest/api/compute/admin/test_aggregates_negative.py, line 31, in 
resource_setup
2015-02-06 15:50:27.936 | super(AggregatesAdminNegativeTestJSON, 
cls).resource_setup()
2015-02-06 15:50:27.936 |   File tempest/api/compute/base.py, line 341, 
in resource_setup
2015-02-06 15:50:27.936 | super(BaseComputeAdminTest, 
cls).resource_setup()
2015-02-06 15:50:27.936 |   File tempest/api/compute/base.py, line 44, in 
resource_setup
2015-02-06 15:50:27.937 | cls.os = cls.get_client_manager()
2015-02-06 15:50:27.937 |   File tempest/test.py, line 407, in 
get_client_manager
2015-02-06 15:50:27.937 | creds = cls.isolated_creds.get_primary_creds()
2015-02-06 15:50:27.937 |   File tempest/common/isolated_creds.py, line 
273, in get_primary_creds
2015-02-06 15:50:27.937 | return self.get_credentials('primary')
2015-02-06 15:50:27.937 |   File tempest/common/isolated_creds.py, line 
257, in get_credentials
2015-02-06 15:50:27.937 | credentials = 
self._create_creds(admin=is_admin)
2015-02-06 15:50:27.937 |   File tempest/common/isolated_creds.py, line 
119, in _create_creds
2015-02-06 15:50:27.937 | tenant, email)
2015-02-06 15:50:27.937 |   File tempest/common/isolated_creds.py, line 
65, in _create_user
2015-02-06 15:50:27.937 | username, password, tenant['id'], email)
2015-02-06 15:50:27.937 |   File 
tempest/services/identity/json/identity_client.py, line 168, in create_user
2015-02-06 15:50:27.938 | resp, body = self.post('users', post_body)
2015-02-06 15:50:27.938 |   File 
/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py,
 line 169, in post
2015-02-06 15:50:27.938 | return self.request('POST', url, 
extra_headers, headers, body)
2015-02-06 15:50:27.938 |   File tempest/common/service_client.py, line 
69, in request
2015-02-06 15:50:27.938 | raise exceptions.Conflict(ex)
2015-02-06 15:50:27.938 | Conflict: An object with that identifier already 
exists
2015-02-06 15:50:27.938 | Details: An object with that identifier already 
exists
2015-02-06 15:50:27.938 | Details: {u'title': u'Conflict', u'message': 
u'Conflict occurred attempting to store role - Duplicate Entry', u'code': 409}
2015-02-06 15:50:27.938 | 


Some how isolated_credential calls are failing.

It appears that this might be racing on creating identical roles on
multiple users - http://logs.openstack.org/26/153426/2/gate/gate-
tempest-dsvm-
nova-v21-full/c80cf2c//logs/apache/keystone.txt.gz#_2015-02-06_15_27_17_988

That's about the time of the failure.

** Affects: keystone
 Importance: Critical
 Status: New

** Affects: tempest
 Importance: High
 Status: New

** Changed in: tempest
   Importance: Undecided = High

** Also affects: keystone
   Importance: Undecided
   Status: New

** Changed in: keystone
   Importance: Undecided = Critical

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1419043

Title:
  Conflict on isolated credential setup

Status in OpenStack Identity (Keystone):
  New
Status in Tempest:
  New

Bug description:
  From the following run (in progress) -
  http://logs.openstack.org/26/153426/2/gate/gate-tempest-dsvm-
  nova-v21-full/c80cf2c//console.html

  2015-02-06 15:50:27.935 | ==
  2015-02-06 15:50:27.935 | Failed 1 tests - output below:
  2015-02-06 15:50:27.935 | ==
  2015-02-06 15:50:27.935 | 
  2015-02-06 15:50:27.935 | setUpClass 
(tempest.api.compute.admin.test_aggregates_negative.AggregatesAdminNegativeTestJSON)
  2015-02-06 15:50:27.936 | 
---
  2015-02-06 15:50:27.936 | 
  2015-02-06 15:50:27.936 | Captured traceback:
  2015-02-06 15:50:27.936 | ~~~
  2015-02-06 15:50:27.936 | Traceback 

[Yahoo-eng-team] [Bug 1407685] Re: New eventlet library breaks nova-manage

[Jesse Pretorius]

** Also affects: openstack-ansible
   Importance: Undecided
   Status: New

** Also affects: openstack-ansible/juno
   Importance: Undecided
   Status: New

** Also affects: openstack-ansible/icehouse
   Importance: Undecided
   Status: New

** Also affects: openstack-ansible/trunk
   Importance: Undecided
   Status: New

** Changed in: openstack-ansible/icehouse
   Importance: Undecided = High

** Changed in: openstack-ansible/juno
   Importance: Undecided = High

** Changed in: openstack-ansible/trunk
   Importance: Undecided = High

** Changed in: openstack-ansible/icehouse
Milestone: None = next

** Changed in: openstack-ansible/juno
Milestone: None = 10.1.2

-- 
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/1407685

Title:
  New eventlet library breaks nova-manage

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) juno series:
  Fix Released
Status in Ansible playbooks for deploying OpenStack:
  New
Status in openstack-ansible icehouse series:
  New
Status in openstack-ansible juno series:
  New
Status in openstack-ansible trunk series:
  New

Bug description:
  This only affects stable/juno and stable/icehouse, which still use the
  deprecated eventlet.util module:

  ~# nova-manage service list
  2015-01-05 13:13:11.202 29016 ERROR stevedore.extension [-] Could not load 
'file': cannot import name util
  2015-01-05 13:13:11.202 29016 ERROR stevedore.extension [-] cannot import 
name util
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension Traceback (most 
recent call last):
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension   File 
/opt/cloudbau/nova-virtualenv/lib/python2.7/site-packages/stevedore/extension.py,
 line 162, in _load_plugins
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension 
verify_requirements,
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension   File 
/opt/cloudbau/nova-virtualenv/lib/python2.7/site-packages/stevedore/extension.py,
 line 178, in _load_one_plugin
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension plugin = 
ep.load(require=verify_requirements)
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension   File 
/opt/cloudbau/nova-virtualenv/lib/python2.7/site-packages/pkg_resources/__init__.py,
 line 2306, in load
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension return 
self._load()
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension   File 
/opt/cloudbau/nova-virtualenv/lib/python2.7/site-packages/pkg_resources/__init__.py,
 line 2309, in _load
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension module = 
__import__(self.module_name, fromlist=['__name__'], level=0)
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension   File 
/opt/cloudbau/nova-virtualenv/lib/python2.7/site-packages/nova/image/download/file.py,
 line 23, in module
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension import 
nova.virt.libvirt.utils as lv_utils
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension   File 
/opt/cloudbau/nova-virtualenv/lib/python2.7/site-packages/nova/virt/libvirt/__init__.py,
 line 15, in module
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension from 
nova.virt.libvirt import driver
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension   File 
/opt/cloudbau/nova-virtualenv/lib/python2.7/site-packages/nova/virt/libvirt/driver.py,
 line 59, in module
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension from eventlet 
import util as eventlet_util
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension ImportError: cannot 
import name util
  2015-01-05 13:13:11.202 29016 TRACE stevedore.extension

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1407685/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419042] [NEW] os.makedirs with 0o7755 was repeated several places in agent code

[Zengfa Gao]

Public bug reported:

For agent code,  os.makedirs(dir, 0o755) was repeated in several places.
First it will be difficult if we want to modify file permission such as 0o555 
in the future.
It will be easier to just to agent.linux.utils.ensure_dir method in other 
plances.
Second, there is no unit test for utils.os.ensure_dir method. We need to add 
unit testing.

** Affects: neutron
 Importance: Undecided
 Assignee: Zengfa Gao (zfgao)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) = Zengfa Gao (zfgao)

** Summary changed:

- os.makedirs with 0o7755 was repeated several plances in agent code
+ os.makedirs with 0o7755 was repeated several places in agent code

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1419042

Title:
  os.makedirs with 0o7755 was repeated several places in agent code

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  For agent code,  os.makedirs(dir, 0o755) was repeated in several places.
  First it will be difficult if we want to modify file permission such as 0o555 
in the future.
  It will be easier to just to agent.linux.utils.ensure_dir method in other 
plances.
  Second, there is no unit test for utils.os.ensure_dir method. We need to add 
unit testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1419042/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1274137] Re: Libvirt driver suspend returns before completion of the task

[Loganathan Parthipan]

I hadn't reproduced since then. Closing it.

** 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/1274137

Title:
  Libvirt driver suspend returns before completion of the task

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  The suspend() function in libvirt driver issues a managedsave() call
  and returns immediately. This will result in the compute manager
  setting task_state to None from 'suspending'.

  This is not good. It's possible for a host to be set to reboot
  assuming all VMs are in stable states or other Operations on the VM
  itself may get through for task_state is None.

  It would be good if driver suspend() actually wait for the power_state
  to move from PAUSED to SHUTOFF and then return control to the manager.
  This would make sure there are no inconsistent task_states reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1274137/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419106] [NEW] potential race condition with member role creation

[Guang Yee]

Public bug reported:

See

https://github.com/openstack/keystone/blob/master/keystone/assignment/core.pyhttps://github.com/openstack/keystone/blob/master/keystone/assignment/core.py#L256-L261

In a multi-worker environment, the second role creation call could
result in conflict.

** Affects: keystone
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1419106

Title:
  potential race condition with member role creation

Status in OpenStack Identity (Keystone):
  New

Bug description:
  See

  
https://github.com/openstack/keystone/blob/master/keystone/assignment/core.pyhttps://github.com/openstack/keystone/blob/master/keystone/assignment/core.py#L256-L261

  In a multi-worker environment, the second role creation call could
  result in conflict.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1419106/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp