[Yahoo-eng-team] [Bug 1411525] [NEW] Nova boot from volume functionallity stop working
Public bug reported: Rally benchmarks related to booting from volume functionality stopped working. Like: NovaServers.boot_server_from_volume We are getting such errors: Resource has ERROR status: No valid host was found. There are not enough hosts available. All patches in Rally are facing it. For example this one: https://review.openstack.org/#/c/147394/ ** Affects: nova Importance: Undecided Assignee: Boris Pavlovic (boris-42) Status: In Progress ** Affects: rally Importance: Critical Assignee: Boris Pavlovic (boris-42) Status: Triaged ** Description changed: Rally benchmarks related to booting from volume functionality stopped working. - - Like: + Like: NovaServers.boot_server_from_volume We are getting such errors: - Traceback (most recent call last): - File "/opt/stack/new/rally/rally/benchmark/runners/base.py", line 77, in _run_scenario_once - method_name)(**kwargs) or scenario_output - File "/opt/stack/new/rally/rally/benchmark/scenarios/nova/servers.py", line 248, in boot_server_from_volume - **kwargs) - File "/opt/stack/new/rally/rally/benchmark/scenarios/base.py", line 261, in func_atomic_actions - f = func(self, *args, **kwargs) - File "/opt/stack/new/rally/rally/benchmark/scenarios/nova/utils.py", line 126, in _boot_server - check_interval=CONF.benchmark.nova_server_boot_poll_interval - File "/opt/stack/new/rally/rally/benchmark/utils.py", line 104, in wait_for - resource = update_resource(resource) - File "/opt/stack/new/rally/rally/benchmark/utils.py", line 67, in _get_from_manager - status=status, fault=msg) - GetResourceErrorStatus: Resource has ERROR status: No valid host was found. There are not enough hosts available. + Resource has ERROR status: + No valid host was found. There are not enough hosts available. ** Changed in: rally Status: New => Triaged ** Changed in: rally Importance: Undecided => Critical ** Also affects: nova Importance: Undecided Status: New ** Description changed: Rally benchmarks related to booting from volume functionality stopped working. Like: NovaServers.boot_server_from_volume We are getting such errors: Resource has ERROR status: No valid host was found. There are not enough hosts available. + + All patches in Rally are facing it. For example this one: + https://review.openstack.org/#/c/147394/ -- 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/1411525 Title: Nova boot from volume functionallity stop working Status in OpenStack Compute (Nova): In Progress Status in Rally: Triaged Bug description: Rally benchmarks related to booting from volume functionality stopped working. Like: NovaServers.boot_server_from_volume We are getting such errors: Resource has ERROR status: No valid host was found. There are not enough hosts available. All patches in Rally are facing it. For example this one: https://review.openstack.org/#/c/147394/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1411525/+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 1411517] [NEW] add schema for endpoint group
Public bug reported: Like other keystone objects, endpoint group also needs a schema to check parameters. ** 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/1411517 Title: add schema for endpoint group Status in OpenStack Identity (Keystone): New Bug description: Like other keystone objects, endpoint group also needs a schema to check parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1411517/+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 1411495] [NEW] Failed sending gratuitous ARP errors
Public bug reported: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRmFpbGVkIHNlbmRpbmcgZ3JhdHVpdG91cyBBUlAgdG8gMjAwMzo6XCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjE3MjgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MjEzNzkwMjA5NDV9 Possible culprit is https://review.openstack.org/#/c/146597/ ** Affects: neutron Importance: Medium Assignee: Carl Baldwin (carl-baldwin) Status: Confirmed ** Changed in: neutron Importance: Undecided => Medium ** Changed in: neutron Assignee: (unassigned) => Carl Baldwin (carl-baldwin) ** Changed in: neutron Status: New => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1411495 Title: Failed sending gratuitous ARP errors Status in OpenStack Neutron (virtual network service): Confirmed Bug description: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRmFpbGVkIHNlbmRpbmcgZ3JhdHVpdG91cyBBUlAgdG8gMjAwMzo6XCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjE3MjgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MjEzNzkwMjA5NDV9 Possible culprit is https://review.openstack.org/#/c/146597/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1411495/+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 1411467] Re: l3 agent periodic sync does not respect the fuzzy delay
misunderstood the code ** Changed in: neutron Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1411467 Title: l3 agent periodic sync does not respect the fuzzy delay Status in OpenStack Neutron (virtual network service): Invalid Bug description: The L3 agent does not honor the configuration value from l3_agent.ini for the periodic router sync fuzzy delay so it runs immediately after start. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1411467/+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 1411489] [NEW] ValueError: Tables "task_info, tasks" have non utf8 collation, please make sure all tables are CHARSET=utf8
Public bug reported: When upgrading to Juno and running DB migrations I get the following error: glance-manage db version 34 glance-manage db sync 2015-01-16 13:42:08.647 6746 CRITICAL glance [-] ValueError: Tables "task_info,tasks" have non utf8 collation, please make sure all tables are CHARSET=utf8 2015-01-16 13:42:08.647 6746 TRACE glance Traceback (most recent call last): 2015-01-16 13:42:08.647 6746 TRACE glance File "/usr/bin/glance-manage", line 10, in 2015-01-16 13:42:08.647 6746 TRACE glance sys.exit(main()) 2015-01-16 13:42:08.647 6746 TRACE glance File "/usr/lib/python2.7/dist-packages/glance/cmd/manage.py", line 290, in main 2015-01-16 13:42:08.647 6746 TRACE glance return CONF.command.action_fn(*func_args, **func_kwargs) 2015-01-16 13:42:08.647 6746 TRACE glance File "/usr/lib/python2.7/dist-packages/glance/cmd/manage.py", line 115, in sync 2015-01-16 13:42:08.647 6746 TRACE glance version) 2015-01-16 13:42:08.647 6746 TRACE glance File "/usr/lib/python2.7/dist-packages/oslo/db/sqlalchemy/migration.py", line 77, in db_sync 2015-01-16 13:42:08.647 6746 TRACE glance _db_schema_sanity_check(engine) 2015-01-16 13:42:08.647 6746 TRACE glance File "/usr/lib/python2.7/dist-packages/oslo/db/sqlalchemy/migration.py", line 110, in _db_schema_sanity_check 2015-01-16 13:42:08.647 6746 TRACE glance ) % ','.join(table_names)) 2015-01-16 13:42:08.647 6746 TRACE glance ValueError: Tables "task_info,tasks" have non utf8 collation, please make sure all tables are CHARSET=utf8 2015-01-16 13:42:08.647 6746 TRACE glance ** 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/1411489 Title: ValueError: Tables "task_info,tasks" have non utf8 collation, please make sure all tables are CHARSET=utf8 Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: When upgrading to Juno and running DB migrations I get the following error: glance-manage db version 34 glance-manage db sync 2015-01-16 13:42:08.647 6746 CRITICAL glance [-] ValueError: Tables "task_info,tasks" have non utf8 collation, please make sure all tables are CHARSET=utf8 2015-01-16 13:42:08.647 6746 TRACE glance Traceback (most recent call last): 2015-01-16 13:42:08.647 6746 TRACE glance File "/usr/bin/glance-manage", line 10, in 2015-01-16 13:42:08.647 6746 TRACE glance sys.exit(main()) 2015-01-16 13:42:08.647 6746 TRACE glance File "/usr/lib/python2.7/dist-packages/glance/cmd/manage.py", line 290, in main 2015-01-16 13:42:08.647 6746 TRACE glance return CONF.command.action_fn(*func_args, **func_kwargs) 2015-01-16 13:42:08.647 6746 TRACE glance File "/usr/lib/python2.7/dist-packages/glance/cmd/manage.py", line 115, in sync 2015-01-16 13:42:08.647 6746 TRACE glance version) 2015-01-16 13:42:08.647 6746 TRACE glance File "/usr/lib/python2.7/dist-packages/oslo/db/sqlalchemy/migration.py", line 77, in db_sync 2015-01-16 13:42:08.647 6746 TRACE glance _db_schema_sanity_check(engine) 2015-01-16 13:42:08.647 6746 TRACE glance File "/usr/lib/python2.7/dist-packages/oslo/db/sqlalchemy/migration.py", line 110, in _db_schema_sanity_check 2015-01-16 13:42:08.647 6746 TRACE glance ) % ','.join(table_names)) 2015-01-16 13:42:08.647 6746 TRACE glance ValueError: Tables "task_info,tasks" have non utf8 collation, please make sure all tables are CHARSET=utf8 2015-01-16 13:42:08.647 6746 TRACE glance To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1411489/+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 1411480] [NEW] remain "BUILD" status when instance with force-host failed to create
Public bug reported: The state "BUILD" remained when instance with force-host failed to create. Till the period task "_check_instance_build_time" change the state "BUILD" to "ERROR". # nova list +--+---+++-+---+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+---+ | 2d14b1b3-fa57-4953-b226-40076f78e9ac | instanceA | ACTIVE | - | Running | net-test=192.168.0.23 | | fcc745de-a15d-47c4-9167-153eb73a4c9b | instanceB | BUILD | - | NOSTATE | | +--+---+++-+---+ reproduce: 1. create one instance group with policy "anti-affinity", named "group-anti-affinity"; 2. create one instance with "--hint group=group-anti-affinity", hosted on hostA; 3. create another instance with "--hint group=group-anti-affinity", force it to hostA; ** 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/1411480 Title: remain "BUILD" status when instance with force-host failed to create Status in OpenStack Compute (Nova): New Bug description: The state "BUILD" remained when instance with force-host failed to create. Till the period task "_check_instance_build_time" change the state "BUILD" to "ERROR". # nova list +--+---+++-+---+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+---+ | 2d14b1b3-fa57-4953-b226-40076f78e9ac | instanceA | ACTIVE | - | Running | net-test=192.168.0.23 | | fcc745de-a15d-47c4-9167-153eb73a4c9b | instanceB | BUILD | - | NOSTATE | | +--+---+++-+---+ reproduce: 1. create one instance group with policy "anti-affinity", named "group-anti-affinity"; 2. create one instance with "--hint group=group-anti-affinity", hosted on hostA; 3. create another instance with "--hint group=group-anti-affinity", force it to hostA; To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1411480/+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 1411478] [NEW] Any attribute that is equal to 'TRUE' or 'FALSE' is treated as boolean by LDAP drivers
Public bug reported:
Our core LDAP driver makes a dangerous assumption that any attribute
that is equal to the string 'TRUE' or 'FALSE' must be a boolean and will
covert the value accordingly. For instance the following test:
def test_hn1(self):
ref = {
'name': 'TRUE',
'domain_id': CONF.identity.default_domain_id}
ref = self.identity_api.create_user(ref)
ref1 = self.identity_api.get_user(ref['id'])
self.assertEqual(ref ,ref1)
will fail (on an LDAP backend) with:
MismatchError: !=:
reference = {'domain_id': 'default', 'enabled': True, 'id':
'd4202d8717104d2bb2ab49fec5e7fe70', 'name': 'TRUE'}
actual= {'domain_id': 'default', 'enabled': True, 'id':
u'd4202d8717104d2bb2ab49fec5e7fe70', 'name': True}
Ouch!
Now that we have a schema for our models, perhaps we should use that to
determine whether something is a boolean or not? e.g. for projects, we
have:
_project_properties = {
'description': validation.nullable(parameter_types.description),
# NOTE(lbragstad): domain_id isn't nullable according to some backends.
# The identity-api should be updated to be consistent with the
# implementation.
'domain_id': parameter_types.id_string,
'enabled': parameter_types.boolean,
'parent_id': validation.nullable(parameter_types.id_string),
'name': {
'type': 'string',
'minLength': 1,
'maxLength': 64
}
}
For some reason the user/group ones don't exist yet, but we can fix
that.
** Affects: keystone
Importance: High
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/1411478
Title:
Any attribute that is equal to 'TRUE' or 'FALSE' is treated as boolean
by LDAP drivers
Status in OpenStack Identity (Keystone):
New
Bug description:
Our core LDAP driver makes a dangerous assumption that any attribute
that is equal to the string 'TRUE' or 'FALSE' must be a boolean and
will covert the value accordingly. For instance the following test:
def test_hn1(self):
ref = {
'name': 'TRUE',
'domain_id': CONF.identity.default_domain_id}
ref = self.identity_api.create_user(ref)
ref1 = self.identity_api.get_user(ref['id'])
self.assertEqual(ref ,ref1)
will fail (on an LDAP backend) with:
MismatchError: !=:
reference = {'domain_id': 'default', 'enabled': True, 'id':
'd4202d8717104d2bb2ab49fec5e7fe70', 'name': 'TRUE'}
actual= {'domain_id': 'default', 'enabled': True, 'id':
u'd4202d8717104d2bb2ab49fec5e7fe70', 'name': True}
Ouch!
Now that we have a schema for our models, perhaps we should use that
to determine whether something is a boolean or not? e.g. for projects,
we have:
_project_properties = {
'description': validation.nullable(parameter_types.description),
# NOTE(lbragstad): domain_id isn't nullable according to some backends.
# The identity-api should be updated to be consistent with the
# implementation.
'domain_id': parameter_types.id_string,
'enabled': parameter_types.boolean,
'parent_id': validation.nullable(parameter_types.id_string),
'name': {
'type': 'string',
'minLength': 1,
'maxLength': 64
}
}
For some reason the user/group ones don't exist yet, but we can fix
that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1411478/+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 1411467] [NEW] l3 agent periodic sync does not respect the fuzzy delay
Public bug reported: The L3 agent does not honor the configuration value from l3_agent.ini for the periodic router sync fuzzy delay so it runs immediately after start. ** Affects: neutron Importance: Undecided Assignee: Kevin Benton (kevinbenton) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Kevin Benton (kevinbenton) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1411467 Title: l3 agent periodic sync does not respect the fuzzy delay Status in OpenStack Neutron (virtual network service): In Progress Bug description: The L3 agent does not honor the configuration value from l3_agent.ini for the periodic router sync fuzzy delay so it runs immediately after start. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1411467/+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 1194451] Re: Prefetcher should validate image data transfer
Closing due to inactivity. ** Changed in: glance Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1194451 Title: Prefetcher should validate image data transfer Status in OpenStack Image Registry and Delivery Service (Glance): Won't Fix Bug description: The prefetcher is somewhat exposed to the equivalent of this bug: https://bugs.launchpad.net/glance/+bug/882585 We should raise an exception in the case of an aborted download. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1194451/+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 1411138] Re: Incorrect response code for show-subnet
** Project changed: neutron => openstack-api-site -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1411138 Title: Incorrect response code for show-subnet Status in OpenStack API documentation site: New Bug description: In http://developer.openstack.org/api-ref-networking-v2.html, the response code for show-subnet is described 201. However, the correct response code is 200. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-api-site/+bug/1411138/+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 1202178] Re: Glance-replicator doesn't copy anmore if you stop and restart it
Closing due to incompleteness and Thibaut's lack of response. ** Changed in: glance Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1202178 Title: Glance-replicator doesn't copy anmore if you stop and restart it Status in OpenStack Image Registry and Delivery Service (Glance): Won't Fix Bug description: hello, I've noticed a little bug/lacks of feature with glance-replicator. if you stop the copy and restart it, Glance-replicator doesn't copy anything. It's because instances are tagged "killed" in the DB and glance replicator lacks a condition for this use case (ligne 473) (i suppose) if headers['status'] == 'active': Regards, Thibaut To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1202178/+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 1411462] Re: Some floatingIP parameters are incorrect
** Project changed: neutron => openstack-api-site
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1411462
Title:
Some floatingIP parameters are incorrect
Status in OpenStack API documentation site:
New
Bug description:
In http://developer.openstack.org/api-ref-networking-v2.html,
following contents need to be fixed in "floatingIP".
---
A. Incorrect description of "id".
B. Response parameter "router_id" does not exist.
C. "status" does not exist in Response parameters matrix.
D. "status" does not exist in JSON parameters.
E. "floatingip" does not exist in Request parameters matrix.
F. Normal response codes is not "200", but "201"
---
POST: /v2.0/floatingips
-> fix A, B, C, D, F
PUT: /v2.0/floatingips/{floatingip_id}
-> fix A, B, C, D, E
GET: /v2.0/floatingips/{floatingip_id}
-> fix A, B, C, D,
To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-api-site/+bug/1411462/+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 1411464] [NEW] list-floatingip does not exist in API-ref
Public bug reported: In http://developer.openstack.org/api-ref-networking-v2.html, LIST floatingIP does not exist. Following API needs to describe on API reference. --- List floating IP Lists all floating IP. --- ** Affects: openstack-api-site Importance: Undecided Status: New ** Project changed: neutron => openstack-api-site -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1411464 Title: list-floatingip does not exist in API-ref Status in OpenStack API documentation site: New Bug description: In http://developer.openstack.org/api-ref-networking-v2.html, LIST floatingIP does not exist. Following API needs to describe on API reference. --- List floating IP Lists all floating IP. --- To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-api-site/+bug/1411464/+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 1411462] [NEW] Some floatingIP parameters are incorrect
Public bug reported:
In http://developer.openstack.org/api-ref-networking-v2.html,
following contents need to be fixed in "floatingIP".
---
A. Incorrect description of "id".
B. Response parameter "router_id" does not exist.
C. "status" does not exist in Response parameters matrix.
D. "status" does not exist in JSON parameters.
E. "floatingip" does not exist in Request parameters matrix.
F. Normal response codes is not "200", but "201"
---
POST: /v2.0/floatingips
-> fix A, B, C, D, F
PUT: /v2.0/floatingips/{floatingip_id}
-> fix A, B, C, D, E
GET: /v2.0/floatingips/{floatingip_id}
-> fix A, B, C, D,
** Affects: neutron
Importance: Undecided
Assignee: Yushiro FURUKAWA (y-furukawa-2)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Yushiro FURUKAWA (y-furukawa-2)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1411462
Title:
Some floatingIP parameters are incorrect
Status in OpenStack Neutron (virtual network service):
New
Bug description:
In http://developer.openstack.org/api-ref-networking-v2.html,
following contents need to be fixed in "floatingIP".
---
A. Incorrect description of "id".
B. Response parameter "router_id" does not exist.
C. "status" does not exist in Response parameters matrix.
D. "status" does not exist in JSON parameters.
E. "floatingip" does not exist in Request parameters matrix.
F. Normal response codes is not "200", but "201"
---
POST: /v2.0/floatingips
-> fix A, B, C, D, F
PUT: /v2.0/floatingips/{floatingip_id}
-> fix A, B, C, D, E
GET: /v2.0/floatingips/{floatingip_id}
-> fix A, B, C, D,
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1411462/+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 1410622] Re: nova is still broken with boto==2.35*
Aha, the signature nova is passing to keystone:
1c314a588a431c92d83b00ca7450195c461857fb78018147065e43089af10788
is different from the generated signature in the keystone code:
8189a643a8669802f5e9e09bc835558cc8521b7edebb43d166e6b60469509d11
** Also affects: keystone
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/1410622
Title:
nova is still broken with boto==2.35*
Status in OpenStack Identity (Keystone):
New
Status in OpenStack Compute (Nova):
Triaged
Bug description:
Bug 1408987 fixed one auth issue with the signature handling:
https://review.openstack.org/#/c/146124/
But when trying to uncap the requirement on master we hit two new
failures when trying to create a security group, we get auth failures
(401 failures to be exact).
Copied from comment 14 of bug 1408987:
This is still broken on master, when I tried to uncap the boto version
on master I get new auth failures:
http://logs.openstack.org/92/146592/1/check/check-tempest-dsvm-
full/7c375f8/console.html#_2015-01-12_19_11_36_102
2015-01-12 19:11:36.102 |
tempest.thirdparty.boto.test_ec2_security_groups.EC2SecurityGroupTest.test_create_authorize_security_group
2015-01-12 19:11:36.102 |
--
2015-01-12 19:11:36.102 |
2015-01-12 19:11:36.102 | Captured traceback:
2015-01-12 19:11:36.102 | ~~~
2015-01-12 19:11:36.103 | Traceback (most recent call last):
2015-01-12 19:11:36.103 | _StringException: Empty attachments:
2015-01-12 19:11:36.103 | stderr
2015-01-12 19:11:36.103 | stdout
2015-01-12 19:11:36.103 |
2015-01-12 19:11:36.103 | pythonlogging:'': {{{
2015-01-12 19:11:36.103 | 2015-01-12 19:07:12,279 27381 DEBUG
[keystoneclient.auth.identity.v2] Making authentication request to
http://127.0.0.1:5000/v2.0/tokens
2015-01-12 19:11:36.103 | 2015-01-12 19:07:13,359 27381 ERROR [boto] 401
Unauthorized
2015-01-12 19:11:36.103 | 2015-01-12 19:07:13,359 27381 ERROR [boto]
2015-01-12 19:11:36.103 |
AuthFailureUnauthorizedreq-81391f74-7caf-42a6-a3b8-ccd2c7d1cbdf
2015-01-12 19:11:36.104 | }}}
2015-01-12 19:11:36.104 |
2015-01-12 19:11:36.104 | Traceback (most recent call last):
2015-01-12 19:11:36.104 | File
"tempest/thirdparty/boto/test_ec2_security_groups.py", line 32, in
test_create_authorize_security_group
2015-01-12 19:11:36.104 | group_description)
2015-01-12 19:11:36.104 | File "tempest/services/botoclients.py", line 84, in
func
2015-01-12 19:11:36.104 | return getattr(conn, name)(*args, **kwargs)
2015-01-12 19:11:36.104 | File
"/usr/local/lib/python2.7/dist-packages/boto/ec2/connection.py", line 3003, in
create_security_group
2015-01-12 19:11:36.104 | SecurityGroup, verb='POST')
2015-01-12 19:11:36.105 | File
"/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1207, in
get_object
2015-01-12 19:11:36.105 | raise self.ResponseError(response.status,
response.reason, body)
2015-01-12 19:11:36.105 | EC2ResponseError: EC2ResponseError: 401 Unauthorized
2015-01-12 19:11:36.105 |
2015-01-12 19:11:36.105 |
AuthFailureUnauthorizedreq-81391f74-7caf-42a6-a3b8-ccd2c7d1cbdf
It's something to do with security groups this time.
http://logs.openstack.org/92/146592/1/check/check-tempest-dsvm-
full/7c375f8/logs/screen-n-api.txt.gz#_2015-01-12_19_07_13_357
2015-01-12 19:07:13.357 24624 DEBUG nova.api.ec2.faults [-] EC2 error
response: AuthFailure: Unauthorized ec2_error_response
/opt/stack/new/nova/nova/api/ec2/faults.py:29
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1410622/+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 1411441] [NEW] Missing spaces in error messages
Public bug reported: In several places there are error messages that span multiple lines that are missing spaces ** Affects: neutron Importance: Undecided Assignee: Bradley Jones (bradjones) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Bradley Jones (bradjones) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1411441 Title: Missing spaces in error messages Status in OpenStack Neutron (virtual network service): In Progress Bug description: In several places there are error messages that span multiple lines that are missing spaces To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1411441/+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 1310815] Re: bad django conf example
The fix for openstack-manuals is the only applicable fix for this, I believe. Closing as wontfix on the Horizon side since there's no change needed. ** Changed in: horizon Status: Confirmed => Won't Fix ** Changed in: horizon Assignee: (unassigned) => Gabriel Hurley (gabriel-hurley) -- 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/1310815 Title: bad django conf example Status in OpenStack Dashboard (Horizon): Won't Fix Status in OpenStack Manuals: Fix Released Bug description: With Django 1.6, the setting is wrong. You need to use SESSION_ENGINE = 'django.contrib.sessions.backends.db' as described on: https://docs.djangoproject.com/en/1.6/ref/settings/#std:setting- SESSION_ENGINE If i use the one described on this page (SESSION_ENGINE = 'django.core.cache.backends.db.DatabaseCache'), i got a 500 error and i have this in logs: File ".../django-1.6/django/core/handlers/base.py", line 90, in get_response response = middleware_method(request) File ".../django-1.6/django/contrib/sessions/middleware.py", line 10, in process_request engine = import_module(settings.SESSION_ENGINE) File ".../django-1.6/django/utils/importlib.py", line 40, in import_module __import__(name) ImportError: No module named DatabaseCache greetings, Thomas --- Built: 2014-04-07T07:45:00 00:00 git SHA: b7557a0bb682410c86f8022eb07980840d82c8cf URL: http://docs.openstack.org/havana/install-guide/install/apt/content/dashboard-session-database.html source File: file:/home/jenkins/workspace/openstack-install-deploy-guide-ubuntu/doc/common/section_dashboard_sessions.xml xml:id: dashboard-session-database To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1310815/+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 1411427] [NEW] Misconfiguration of OPENSTACK_API_VERSIONS is hard to debug
Public bug reported: In local_settings.py we allow operators to specify the preferred API versions for their service endpoints. The values provided are then fed directly into a dict key lookup in the APIVersionManager code. Any misconfiguration here results in a KeyError which provides no guidance as to what an acceptable value might be. Instead, we can: 1. Verify that the value provided is of the right type (currently all version keys are ints or floats, not strings as one might expect). 2. Provide a list of the keys which would be acceptable if an invalid key is provided. 3. Raise a useful and explanatory exception if these values are incorrect. As a correlated issue, it also turns out that the way the metadata_defs panel checks for the Glance active version triggers an error since Glance (and other APIs for which only one version is supported) don't actually bother to declare their supported versions. ** Affects: horizon Importance: Undecided Assignee: Gabriel Hurley (gabriel-hurley) Status: New ** Changed in: horizon Assignee: (unassigned) => Gabriel Hurley (gabriel-hurley) ** Changed in: horizon Milestone: None => kilo-2 -- 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/1411427 Title: Misconfiguration of OPENSTACK_API_VERSIONS is hard to debug Status in OpenStack Dashboard (Horizon): New Bug description: In local_settings.py we allow operators to specify the preferred API versions for their service endpoints. The values provided are then fed directly into a dict key lookup in the APIVersionManager code. Any misconfiguration here results in a KeyError which provides no guidance as to what an acceptable value might be. Instead, we can: 1. Verify that the value provided is of the right type (currently all version keys are ints or floats, not strings as one might expect). 2. Provide a list of the keys which would be acceptable if an invalid key is provided. 3. Raise a useful and explanatory exception if these values are incorrect. As a correlated issue, it also turns out that the way the metadata_defs panel checks for the Glance active version triggers an error since Glance (and other APIs for which only one version is supported) don't actually bother to declare their supported versions. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1411427/+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 1411411] [NEW] keystone sample config is out of date
Public bug reported: A recent change [1] change the keystone config, but didn't update the sample. [1] https://review.openstack.org/#/c/126897/ ** Affects: keystone Importance: High Assignee: Henry Nash (henry-nash) 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/1411411 Title: keystone sample config is out of date Status in OpenStack Identity (Keystone): New Bug description: A recent change [1] change the keystone config, but didn't update the sample. [1] https://review.openstack.org/#/c/126897/ To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1411411/+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 1411347] Re: Missing space in error message in neutron/db/l3_db.py
Filed in Horizon by mistake, will reopen in Neutron.
** Changed in: horizon
Status: Triaged => Invalid
** Project changed: horizon => neutron
** Changed in: neutron
Milestone: kilo-2 => None
** Changed in: neutron
Status: Invalid => In Progress
--
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/1411347
Title:
Missing space in error message in neutron/db/l3_db.py
Status in OpenStack Neutron (virtual network service):
In Progress
Bug description:
Error message on line 746 is missing a space between lines:
msg = (_('Cannot add floating IP to port %s that has'
'no fixed IP addresses') % internal_port['id'])
Should be:
msg = (_('Cannot add floating IP to port %s that has '
'no fixed IP addresses') % internal_port['id'])
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1411347/+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 1411396] [NEW] Missing space in error message in neutron/db/l3_db.py
*** This bug is a duplicate of bug 1411347 ***
https://bugs.launchpad.net/bugs/1411347
Public bug reported:
Error message on line 746 is missing a space between lines:
msg = (_('Cannot add floating IP to port %s that has'
'no fixed IP addresses') % internal_port['id'])
Should be:
msg = (_('Cannot add floating IP to port %s that has '
'no fixed IP addresses') % internal_port['id'])
** Affects: neutron
Importance: Undecided
Status: New
** This bug has been marked a duplicate of bug 1411347
Missing space in error message in neutron/db/l3_db.py
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1411396
Title:
Missing space in error message in neutron/db/l3_db.py
Status in OpenStack Neutron (virtual network service):
New
Bug description:
Error message on line 746 is missing a space between lines:
msg = (_('Cannot add floating IP to port %s that has'
'no fixed IP addresses') % internal_port['id'])
Should be:
msg = (_('Cannot add floating IP to port %s that has '
'no fixed IP addresses') % internal_port['id'])
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1411396/+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 1411383] [NEW] Arista ML2 plugin incorrectly syncs with EOS
Public bug reported: The Arista ML2 plugin periodically compares the data in the Neutron DB with EOS to ensure that they are in sync. If EOS reboots, then the data might be out of sync and the plugin needs to push data from Neutron DB to EOS. As an optimization, the plugin gets and stores the time at which the data on EOS was modified. Just before a sync, the plugin compares the stored time with the timestamp on EOS and performs the sync only if the timestamps differ. Due to a bug, the timestamp is incorrectly stored in the plugin because of which the sync never takes place and the only way to force a sync is to restart the neutron server. ** Affects: neutron Importance: Undecided Assignee: Shashank Hegde (hegde-shashank) Status: New ** Changed in: neutron Assignee: (unassigned) => Shashank Hegde (hegde-shashank) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1411383 Title: Arista ML2 plugin incorrectly syncs with EOS Status in OpenStack Neutron (virtual network service): New Bug description: The Arista ML2 plugin periodically compares the data in the Neutron DB with EOS to ensure that they are in sync. If EOS reboots, then the data might be out of sync and the plugin needs to push data from Neutron DB to EOS. As an optimization, the plugin gets and stores the time at which the data on EOS was modified. Just before a sync, the plugin compares the stored time with the timestamp on EOS and performs the sync only if the timestamps differ. Due to a bug, the timestamp is incorrectly stored in the plugin because of which the sync never takes place and the only way to force a sync is to restart the neutron server. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1411383/+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 1295876] Re: libvirtError: internal error unable to add domain xxx to cgroup: No space left on device
** Changed in: libvirt (Ubuntu)
Status: Confirmed => 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/1295876
Title:
libvirtError: internal error unable to add domain xxx to cgroup: No
space left on device
Status in OpenStack Compute (Nova):
Invalid
Status in libvirt package in Ubuntu:
Fix Released
Bug description:
logstash query: message:"cgroup\: No space left on device" AND
filename:logs*screen-n-cpu.txt
http://logs.openstack.org/12/80412/8/check/check-tempest-dsvm-
postgres-
full/f9f6158/logs/screen-n-cpu.txt.gz?level=TRACE#_2014-03-21_17_45_12_490
ERROR nova.compute.manager [req-630b71d6-0fbe-4e9e-99fe-019da7d29a3a
FixedIPsNegativeTestJson-475659359 FixedIPsNegativeTestJson-265680949]
[instance: 3f281136-ed69-4bfb-bf36-a7d4aa1c0640] Error: internal error unable
to add domain instance-0002 task 3057 to cgroup: No space left on device
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] Traceback (most recent call last):
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] File
"/opt/stack/new/nova/nova/compute/manager.py", line 1304, in _build_instance
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] set_access_ip=set_access_ip)
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] File
"/opt/stack/new/nova/nova/compute/manager.py", line 394, in decorated_function
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] return function(self, context, *args,
**kwargs)
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] File
"/opt/stack/new/nova/nova/compute/manager.py", line 1716, in _spawn
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] LOG.exception(_('Instance failed to
spawn'), instance=instance)
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] File
"/opt/stack/new/nova/nova/openstack/common/excutils.py", line 68, in __exit__
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] six.reraise(self.type_, self.value,
self.tb)
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] File
"/opt/stack/new/nova/nova/compute/manager.py", line 1713, in _spawn
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] block_device_info)
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] File
"/opt/stack/new/nova/nova/virt/libvirt/driver.py", line 2241, in spawn
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] block_device_info)
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] File
"/opt/stack/new/nova/nova/virt/libvirt/driver.py", line 3621, in
_create_domain_and_network
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] power_on=power_on)
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] File
"/opt/stack/new/nova/nova/virt/libvirt/driver.py", line 3531, in _create_domain
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] domain.XMLDesc(0))
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] File
"/opt/stack/new/nova/nova/openstack/common/excutils.py", line 68, in __exit__
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] six.reraise(self.type_, self.value,
self.tb)
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] File
"/opt/stack/new/nova/nova/virt/libvirt/driver.py", line 3526, in _create_domain
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] domain.createWithFlags(launch_flags)
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] File
"/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 179, in doit
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] result = proxy_call(self._autowrap,
f, *args, **kwargs)
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] File
"/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 139, in
proxy_call
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] rv = execute(f,*args,**kwargs)
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] File
"/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 77, in tworker
26028 TRACE nova.compute.manager [instance:
3f281136-ed69-4bfb-bf36-a7d4aa1c0640] rv = meth(*args,**kwargs)
2
[Yahoo-eng-team] [Bug 1328501] Re: start of keystone not possible when use_syslog=True but syslog is not accessible/running
** Changed in: oslo.log
Status: Fix Committed => Fix Released
** Changed in: oslo.log
Milestone: None => 0.1.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1328501
Title:
start of keystone not possible when use_syslog=True but syslog is not
accessible/running
Status in OpenStack Identity (Keystone):
Fix Released
Status in Logging configuration library for OpenStack:
Fix Released
Bug description:
[ 101s] msg: Traceback (most recent call last):
[ 101s] File "/usr/bin/keystone-manage", line 51, in
[ 101s] cli.main(argv=sys.argv, config_files=config_files)
[ 101s] File "/usr/lib64/python2.6/site-packages/keystone/cli.py", line
190, in main
[ 101s] config.setup_logging()
[ 101s] File "/usr/lib64/python2.6/site-packages/keystone/config.py", line
56, in setup_logging
[ 101s] log.setup('keystone')
[ 101s] File
"/usr/lib64/python2.6/site-packages/keystone/openstack/common/log.py", line
461, in setup
[ 101s] _setup_logging_from_conf(product_name, version)
[ 101s] File
"/usr/lib64/python2.6/site-packages/keystone/openstack/common/log.py", line
520, in _setup_logging_from_conf
[ 101s] facility=facility)
[ 101s] File "/usr/lib64/python2.6/logging/handlers.py", line 715, in
__init__
[ 101s] self._connect_unixsocket(address)
[ 101s] File "/usr/lib64/python2.6/logging/handlers.py", line 730, in
_connect_unixsocket
[ 101s] self.socket.connect(address)
[ 101s] File "", line 1, in connect
[ 101s] socket.error: [Errno 2] No such file or directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1328501/+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 1210261] Re: remove openstack.common.context
** Changed in: oslo.log Status: Fix Committed => Fix Released ** Changed in: oslo.log Milestone: None => 0.1.0 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1210261 Title: remove openstack.common.context Status in Cinder: Fix Committed Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): Confirmed Status in Logging configuration library for OpenStack: Fix Released Bug description: relates to https://bugs.launchpad.net/neutron/+bug/1208734, and according to https://github.com/openstack/oslo- incubator/blob/master/MAINTAINERS#L87, i think we'd better remove openstack/comon/context To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1210261/+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 1411351] [NEW] Fix static strings in DVR config with LABELs
Public bug reported: There are couple of static strings in DVR that are used for checking the configuration modes of the L3-agent such as "dvr_snat", "dvr", "legacy", "agent_mode" and "distributed". We need to replace those with LABELs. ** Affects: neutron Importance: Undecided Assignee: Swaminathan Vasudevan (swaminathan-vasudevan) Status: In Progress ** Tags: l3-dvr-backlog ** Changed in: neutron Assignee: (unassigned) => Swaminathan Vasudevan (swaminathan-vasudevan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1411351 Title: Fix static strings in DVR config with LABELs Status in OpenStack Neutron (virtual network service): In Progress Bug description: There are couple of static strings in DVR that are used for checking the configuration modes of the L3-agent such as "dvr_snat", "dvr", "legacy", "agent_mode" and "distributed". We need to replace those with LABELs. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1411351/+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 1411347] [NEW] Missing space in error message in neutron/db/l3_db.py
Public bug reported:
Error message on line 746 is missing a space between lines:
msg = (_('Cannot add floating IP to port %s that has'
'no fixed IP addresses') % internal_port['id'])
Should be:
msg = (_('Cannot add floating IP to port %s that has '
'no fixed IP addresses') % internal_port['id'])
** Affects: horizon
Importance: Undecided
Assignee: John Davidge (john-davidge)
Status: New
** Changed in: horizon
Assignee: (unassigned) => John Davidge (john-davidge)
** Description changed:
Error message on line 746 is missing a space between lines:
msg = (_('Cannot add floating IP to port %s that has'
- 'no fixed IP addresses') % internal_port['id'])
+ 'no fixed IP addresses') % internal_port['id'])
Should be:
msg = (_('Cannot add floating IP to port %s that has '
- 'no fixed IP addresses') % internal_port['id'])
+ 'no fixed IP addresses') % internal_port['id'])
--
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/1411347
Title:
Missing space in error message in neutron/db/l3_db.py
Status in OpenStack Dashboard (Horizon):
New
Bug description:
Error message on line 746 is missing a space between lines:
msg = (_('Cannot add floating IP to port %s that has'
'no fixed IP addresses') % internal_port['id'])
Should be:
msg = (_('Cannot add floating IP to port %s that has '
'no fixed IP addresses') % internal_port['id'])
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1411347/+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 1411316] [NEW] "Attempted to remove chain which does not exist" probably shouldn't be a warning
Public bug reported: Noticed this here: http://logs.openstack.org/36/147336/1/gate/gate-tempest-dsvm-neutron- full/a695425/logs/screen-q-agt.txt.gz?level=TRACE So running the query: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiQXR0ZW1wdGVkIHRvIHJlbW92ZSBjaGFpblwiIEFORCBtZXNzYWdlOlwid2hpY2ggZG9lcyBub3QgZXhpc3RcIiBBTkQgdGFnczpcInNjcmVlbi1xLWFndC50eHRcIiBBTkQgbG9nbGV2ZWw6XCJXQVJOSU5HXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MjEzNDAyMTgyMDgsIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0= We have about 7.4 million hits of that warning in a week in the check/gate queue. For something that gets logged that much, it's probably not a valid warning level message, probably more debug. ** 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/1411316 Title: "Attempted to remove chain which does not exist" probably shouldn't be a warning Status in OpenStack Neutron (virtual network service): New Bug description: Noticed this here: http://logs.openstack.org/36/147336/1/gate/gate-tempest-dsvm-neutron- full/a695425/logs/screen-q-agt.txt.gz?level=TRACE So running the query: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiQXR0ZW1wdGVkIHRvIHJlbW92ZSBjaGFpblwiIEFORCBtZXNzYWdlOlwid2hpY2ggZG9lcyBub3QgZXhpc3RcIiBBTkQgdGFnczpcInNjcmVlbi1xLWFndC50eHRcIiBBTkQgbG9nbGV2ZWw6XCJXQVJOSU5HXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MjEzNDAyMTgyMDgsIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0= We have about 7.4 million hits of that warning in a week in the check/gate queue. For something that gets logged that much, it's probably not a valid warning level message, probably more debug. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1411316/+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 1411312] [NEW] tempest.api.compute.servers.test_create_server.ServersTestManualDisk.test_verify_multiple_nics_order intermittent fails in the gate
Public bug reported: http://logs.openstack.org/36/147336/1/gate/gate-tempest-dsvm-neutron- full/a695425/console.html#_2015-01-15_01_13_40_304 2015-01-15 01:40:06.862 | Traceback (most recent call last): 2015-01-15 01:40:06.862 | File "tempest/api/compute/servers/test_create_server.py", line 181, in test_verify_multiple_nics_order 2015-01-15 01:40:06.863 | self.assertEqual(expected_addr, addr) 2015-01-15 01:40:06.863 | File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 348, in assertEqual 2015-01-15 01:40:06.863 | self.assertThat(observed, matcher, message) 2015-01-15 01:40:06.863 | File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 433, in assertThat 2015-01-15 01:40:06.863 | raise mismatch_error 2015-01-15 01:40:06.863 | MismatchError: ['19.80.0.2', '19.86.0.2'] != [u'19.80.0.3', u'19.86.0.3'] http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwidGVtcGVzdC5hcGkuY29tcHV0ZS5zZXJ2ZXJzLnRlc3RfY3JlYXRlX3NlcnZlci5TZXJ2ZXJzVGVzdE1hbnVhbERpc2sudGVzdF92ZXJpZnlfbXVsdGlwbGVfbmljc19vcmRlclwiIEFORCBtZXNzYWdlOlwiRkFJTEVEXCIgQU5EIHRhZ3M6XCJjb25zb2xlXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNS0wMS0wMVQxNjozNjowOSswMDowMCIsInRvIjoiMjAxNS0wMS0xNVQxNjozNjowOSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxNDIxMzM5ODE0ODE5fQ== 14 hits in the last 10 days, going back to 1/8 for the first one. check, gate and experimental queues, all failures, looks like neutronv2 API only. ** Affects: nova Importance: Undecided Status: Confirmed ** Changed in: nova Status: New => Confirmed -- 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/1411312 Title: tempest.api.compute.servers.test_create_server.ServersTestManualDisk.test_verify_multiple_nics_order intermittent fails in the gate Status in OpenStack Compute (Nova): Confirmed Bug description: http://logs.openstack.org/36/147336/1/gate/gate-tempest-dsvm-neutron- full/a695425/console.html#_2015-01-15_01_13_40_304 2015-01-15 01:40:06.862 | Traceback (most recent call last): 2015-01-15 01:40:06.862 | File "tempest/api/compute/servers/test_create_server.py", line 181, in test_verify_multiple_nics_order 2015-01-15 01:40:06.863 | self.assertEqual(expected_addr, addr) 2015-01-15 01:40:06.863 | File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 348, in assertEqual 2015-01-15 01:40:06.863 | self.assertThat(observed, matcher, message) 2015-01-15 01:40:06.863 | File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 433, in assertThat 2015-01-15 01:40:06.863 | raise mismatch_error 2015-01-15 01:40:06.863 | MismatchError: ['19.80.0.2', '19.86.0.2'] != [u'19.80.0.3', u'19.86.0.3'] http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwidGVtcGVzdC5hcGkuY29tcHV0ZS5zZXJ2ZXJzLnRlc3RfY3JlYXRlX3NlcnZlci5TZXJ2ZXJzVGVzdE1hbnVhbERpc2sudGVzdF92ZXJpZnlfbXVsdGlwbGVfbmljc19vcmRlclwiIEFORCBtZXNzYWdlOlwiRkFJTEVEXCIgQU5EIHRhZ3M6XCJjb25zb2xlXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNS0wMS0wMVQxNjozNjowOSswMDowMCIsInRvIjoiMjAxNS0wMS0xNVQxNjozNjowOSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxNDIxMzM5ODE0ODE5fQ== 14 hits in the last 10 days, going back to 1/8 for the first one. check, gate and experimental queues, all failures, looks like neutronv2 API only. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1411312/+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 1411074] Re: Move
** Changed in: horizon Status: New => Invalid -- 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/1411074 Title: Move Status in OpenStack Dashboard (Horizon): Invalid Bug description: Both PageObject and it's child BasePage all have go_to_login_page method, and they are same. To keep logic clear , remove go_to_login_page from PageObject To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1411074/+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 1383794] Re: [SRU] GCE datasource should use the short hostname
fix-committed in revno 1049. ** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Fix Committed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1383794 Title: [SRU] GCE datasource should use the short hostname Status in Init scripts for use on cloud images: Fix Committed Status in cloud-init package in Ubuntu: New Status in cloud-init source package in Precise: New Status in cloud-init source package in Trusty: New Status in cloud-init source package in Utopic: New Bug description: [IMPACT] Since GCE FQDN are usually longer than 64-characters, several hi-profile tools like Java and Hadoop may break. [FIX] Per GCE's recommendation, Linux instances should use the short hostname over the FQDN. This change sets the system hostname to the short name. [VERIFICATION] 1. Install new cloud-init from proposed 2. Re-run cloud-config: * 14.04/14.10: cloud-init single -n set_hostname --frequency=always * 12.04: cloud-init-cfg set_hostname always 3. Check to make sure that the short name is used for /etc/hostname [RISK] This is a very low risk change. The actual change is a single line, and has test cases for 14.04 and 14.10. Further, since this change is only in the GCE datasource, it only affects GCE instances. [ORIGINAL REPORT] The GCE datasource uses the long hostname. Hostnames longer than 64 characters can break several tools. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1383794/+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 1411239] [NEW] policy checks for get_image, get_images not working
Public bug reported: I'm trying to prevent a user to boot from a glance image (for whatever reason) I went ahead and changed glance_policy: "get_image": "role:admin", "get_images": "role:admin", still a normal user can see and apparently boot from glance. Shouldn't that be prevented by policy checks? ** 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/1411239 Title: policy checks for get_image, get_images not working Status in OpenStack Dashboard (Horizon): New Bug description: I'm trying to prevent a user to boot from a glance image (for whatever reason) I went ahead and changed glance_policy: "get_image": "role:admin", "get_images": "role:admin", still a normal user can see and apparently boot from glance. Shouldn't that be prevented by policy checks? To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1411239/+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 1368599] Re: instance create failed due to the deffirence services between regions
@Justin Pomeroy (jpomero) You are right! ** Changed in: horizon Status: New => Fix Released -- 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/1368599 Title: instance create failed due to the deffirence services between regions Status in OpenStack Dashboard (Horizon): Fix Released Bug description: region 1 deploys nova(includes nova-network) and glance service. region 2 deploys nova, neutron and glance service. keystone is shared by region 1 and region 2 However, instance creation failed when switches to region 1 in the dashboard. [Fri Sep 12 03:35:10 2014] [error] Internal Server Error: /dashboard/project/instances/launch [Fri Sep 12 03:35:10 2014] [error] Traceback (most recent call last): [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/core/handlers/base.py", line 134, in get_response [Fri Sep 12 03:35:10 2014] [error] response = response.render() [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/response.py", line 104, in render [Fri Sep 12 03:35:10 2014] [error] self._set_content(self.rendered_content) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/response.py", line 81, in rendered_content [Fri Sep 12 03:35:10 2014] [error] content = template.render(context) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/base.py", line 140, in render [Fri Sep 12 03:35:10 2014] [error] return self._render(context) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/base.py", line 134, in _render [Fri Sep 12 03:35:10 2014] [error] return self.nodelist.render(context) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/base.py", line 823, in render [Fri Sep 12 03:35:10 2014] [error] bit = self.render_node(node, context) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/debug.py", line 74, in render_node [Fri Sep 12 03:35:10 2014] [error] return node.render(context) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/defaulttags.py", line 478, in render [Fri Sep 12 03:35:10 2014] [error] output = self.nodelist.render(context) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/base.py", line 823, in render [Fri Sep 12 03:35:10 2014] [error] bit = self.render_node(node, context) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/debug.py", line 74, in render_node [Fri Sep 12 03:35:10 2014] [error] return node.render(context) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/loader_tags.py", line 53, in render [Fri Sep 12 03:35:10 2014] [error] result = self.nodelist.render(context) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/debug.py", line 74, in render_node [Fri Sep 12 03:35:10 2014] [error] return node.render(context) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/defaulttags.py", line 186, in render [Fri Sep 12 03:35:10 2014] [error] nodelist.append(node.render(context)) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/defaulttags.py", line 275, in render [Fri Sep 12 03:35:10 2014] [error] match = condition.eval(context) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/defaulttags.py", line 825, in eval [Fri Sep 12 03:35:10 2014] [error] return self.value.resolve(context, ignore_failures=True) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/base.py", line 571, in resolve [Fri Sep 12 03:35:10 2014] [error] obj = self.var.resolve(context) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/base.py", line 721, in resolve [Fri Sep 12 03:35:10 2014] [error] value = self._resolve_lookup(context) [Fri Sep 12 03:35:10 2014] [error] File "/usr/lib/python2.6/site-packages/django/template/base.py", line 772, in _resolve_lookup [Fri Sep 12 03:35:10 2014] [error] current = current() [Fri Sep 12 03:35:10 2014] [error] File "/opt/stack/horizon/horizon/workflows/base.py", line 454, in has_required_fields [Fri Sep 12 03:35:10 2014] [error] field = self.action.fields.get(key, None) [Fri Sep 12 03:35:10 2014] [error] File "/opt/stack/horizon/horizon/workflows/base.py", line 376, in action [Fri Sep 12 03:35:10 2014] [error] context) [Fri Sep 12 03:35:10 2014] [error] File "/opt
[Yahoo-eng-team] [Bug 1411215] [NEW] Add an option to replicator to select which images to compare/copy
Public bug reported: It would be nice to add some sort of filter to images considered by glance-replicator. Two types of a filters would be nice : * a list of ids * a list of names (and maybe some sort of regexp on the names, for example --filter "ubuntu-*") A quick look at the code makes me think this can easily be added in the def get_images just before the yield. For interfacing I would add : --filter-by-name 'item1,item2,item3" --filter-by-name 'ubuntu-*' --filter-by-id 'id1,id2,id3' Am willing to contribute a patch if feature request is adopted (we are going to implement it anyway). ** 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/1411215 Title: Add an option to replicator to select which images to compare/copy Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: It would be nice to add some sort of filter to images considered by glance-replicator. Two types of a filters would be nice : * a list of ids * a list of names (and maybe some sort of regexp on the names, for example --filter "ubuntu-*") A quick look at the code makes me think this can easily be added in the def get_images just before the yield. For interfacing I would add : --filter-by-name 'item1,item2,item3" --filter-by-name 'ubuntu-*' --filter-by-id 'id1,id2,id3' Am willing to contribute a patch if feature request is adopted (we are going to implement it anyway). To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1411215/+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 1411163] [NEW] No fdb entries added when failover dhcp and l3 agent together
Public bug reported: [Env] OpenStack: icehouse OS: ubuntu enable l2 population enable gre tunnel [Description] If the dhcp and l3 agent on the same host, then after this host is down, then there will be a probability that scheduled to other same host, then sometimes the ovs tunnel can't be created on the new scheduled host. [Root cause] After debugging, we found below log: 2015-01-14 13:44:18.284 9815 INFO neutron.plugins.ml2.drivers.l2pop.db [req-e36fe1fe-a08c-43c9-9d9c-75fe714d6f91 None] query:[, ] Above shows there will be a probability that two ACTIVE ports shows up in db together, but from l2 pop mech_driver: " if agent_active_ports == 1 or ( self.get_agent_uptime(agent) < cfg.CONF.l2pop.agent_boot_time): " only in above condition the fdb entry will be added and notified to agent, so failures are pop up. ** 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/1411163 Title: No fdb entries added when failover dhcp and l3 agent together Status in OpenStack Neutron (virtual network service): New Bug description: [Env] OpenStack: icehouse OS: ubuntu enable l2 population enable gre tunnel [Description] If the dhcp and l3 agent on the same host, then after this host is down, then there will be a probability that scheduled to other same host, then sometimes the ovs tunnel can't be created on the new scheduled host. [Root cause] After debugging, we found below log: 2015-01-14 13:44:18.284 9815 INFO neutron.plugins.ml2.drivers.l2pop.db [req-e36fe1fe-a08c-43c9-9d9c-75fe714d6f91 None] query:[, ] Above shows there will be a probability that two ACTIVE ports shows up in db together, but from l2 pop mech_driver: " if agent_active_ports == 1 or ( self.get_agent_uptime(agent) < cfg.CONF.l2pop.agent_boot_time): " only in above condition the fdb entry will be added and notified to agent, so failures are pop up. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1411163/+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 1410841] Re: Cast unnecessary notification over l3_agent with admin_state_up False
The meaning of admin_state_up is under discussion now. See this thread.[1] If we go the way of admin_state_up only indicating scheduling candidacy, then this is behaving just as we would want it. 1. http://lists.openstack.org/pipermail/openstack- dev/2015-January/053782.html ** Changed in: neutron Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1410841 Title: Cast unnecessary notification over l3_agent with admin_state_up False Status in OpenStack Neutron (virtual network service): Opinion Bug description: When users update router hosted by l3_agent, neutron server casts unnecessary notification even if the l3_agent is set admin_state_up False . $ neutron --os-username admin --os-password openstack l3-agent-list-hosting-router router1 +--+--++---+ | id | host | admin_state_up | alive | +--+--++---+ | 25991a37-5f6c-41bb-a80f-c2e41cdc3a0f | vagrant-ubuntu-trusty-64 | False | :-) | +--+--++---+ $ neutron router-interface-add router1 subnet Added interface d0985c72-08d0-4f87-b825-9dba1d257823 to router router1. l3_agent log: 2015-01-14 15:18:46.937 DEBUG neutron.agent.l3.agent [req-1ecc6f52-49c7-4e3a-aa98-a949aefc65cd demo e7f0cdeb333c4b21a9acdacbe9b50a86] Got routers updated notification :[u'154aa9bd-4950-4ccc-a26f-c9278f9da0c4'] from (pid=11845) routers_updated /opt/stack/neutron/neutron/agent/l3/agent.py:977 2015-01-14 15:18:46.937 DEBUG neutron.agent.l3.agent [req-1ecc6f52-49c7-4e3a-aa98-a949aefc65cd demo e7f0cdeb333c4b21a9acdacbe9b50a86] Starting router update for 154aa9bd-4950-4ccc-a26f-c9278f9da0c4 from (pid=11845) _process_router_update /opt/stack/neutron/neutron/agent/l3/agent.py:1051 2015-01-14 15:18:46.953 WARNING neutron.agent.l3.agent [req-1ecc6f52-49c7-4e3a-aa98-a949aefc65cd demo e7f0cdeb333c4b21a9acdacbe9b50a86] Info for router 154aa9bd-4950-4ccc-a26f-c9278f9da0c4 were not found. Skipping router removal To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1410841/+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 1411138] [NEW] Incorrect response code for show-subnet
Public bug reported: In http://developer.openstack.org/api-ref-networking-v2.html, the response code for show-subnet is described 201. However, the correct response code is 200. ** Affects: neutron Importance: Undecided Assignee: Yushiro FURUKAWA (y-furukawa-2) Status: New ** Changed in: neutron Assignee: (unassigned) => Yushiro FURUKAWA (y-furukawa-2) ** Description changed: In http://developer.openstack.org/api-ref-networking-v2.html, the response code for show-subnet is described 201. - However, correct responst code is 200. + However, correct respons code is 200. ** Description changed: In http://developer.openstack.org/api-ref-networking-v2.html, the response code for show-subnet is described 201. - However, correct respons code is 200. + However, the correct response code is 200. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1411138 Title: Incorrect response code for show-subnet Status in OpenStack Neutron (virtual network service): New Bug description: In http://developer.openstack.org/api-ref-networking-v2.html, the response code for show-subnet is described 201. However, the correct response code is 200. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1411138/+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 1399788] Re: neutron doesn't log tenant_id and user_id along side req-id in logs
** Project changed: neutron => devstack -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1399788 Title: neutron doesn't log tenant_id and user_id along side req-id in logs Status in devstack - openstack dev environments: In Progress Bug description: neutron logs: [req-94a39f87-e470-4032-82af-9a6b429b60fa None] while nova logs: [req-c0b4dfb9-8af3-40eb-b0dd-7b576cfd1d55 AggregatesAdminTestJSON-917687995 AggregatesAdminTestJSON-394398414] Nova uses the format: #logging_context_format_string=%(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s Without knowing the user and tenant its hard to understand what the logs are doing when multiple tenants are using the cloud. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1399788/+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 1410951] Re: Devstack does not set the "gateway_external_netword_id" to null when "external_network_bridge" is set to null. They both should be set to null in the l3_agent.ini wh
** Project changed: neutron => devstack -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1410951 Title: Devstack does not set the "gateway_external_netword_id" to null when "external_network_bridge" is set to null. They both should be set to null in the l3_agent.ini when a single agent supports multiple external network Status in devstack - openstack dev environments: New Bug description: When multiple external networks are set for the provider network, the l3_agent.ini should have external_network_bridge = "" gateway_external_network_id = "" if a single agent is hosting all the multiple external networks. In devstack today, when there is no 'br-ex' configured, the devstack "stack.sh" script only configures external_network_bridge="" and not gateway_external_network_id. This causes some issues in validation. Because there is a check to make sure if the "gateway_external_network" is null or not. If the key is not found, the action varies. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1410951/+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 1411137] [NEW] Cann't use extra-dhcp-opt to set networking parameters on stateless-dhcp network
Public bug reported: when using slaac+stateless dhcpv6 to configure ipv6 address and networking configurations on OpenStack， if the network only consist one ipv6 subnet with ipv6-address-mode setted as stateless-dhcpv6，the dhcp agent will filter this subnet in its _iter_hosts() function, at this time, even you use extr-dhcp-opt to set network configuration on ports of this subnet, they will not be included in the host file of the dnsmasq, and can not be got through dhcpv6 protocal. The stateless dhcpv6 will fail on this situation! ** 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/1411137 Title: Cann't use extra-dhcp-opt to set networking parameters on stateless- dhcp network Status in OpenStack Neutron (virtual network service): New Bug description: when using slaac+stateless dhcpv6 to configure ipv6 address and networking configurations on OpenStack， if the network only consist one ipv6 subnet with ipv6-address-mode setted as stateless-dhcpv6，the dhcp agent will filter this subnet in its _iter_hosts() function, at this time, even you use extr-dhcp-opt to set network configuration on ports of this subnet, they will not be included in the host file of the dnsmasq, and can not be got through dhcpv6 protocal. The stateless dhcpv6 will fail on this situation! To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1411137/+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
