[Yahoo-eng-team] [Bug 1472936] [NEW] External flat network show out iof the tenant.
Public bug reported: Hi guys! I found problem in neutron. When I create a new network and I set external and the tenant is i.e demo, then I saw the network form other (not admin) tenant as well. I can get floating IP address, router etc. It is a problem because I can't assign external network to tenant. Here is an example: ext-pub1 is an external network, owned by demo tenant. If I list the networks in the demo2 tenant I see the ext-pub1 network as well :( root@controller01:~# source demo-openrc.sh root@controller01:~# neutron net-list +--+---+-+ | id | name | subnets | +--+---+-+ | 0c034b21-4e79-45c0-8f63-48b58dbd29f9 | demo-net | 24ad19d9-7967-42da-8457-bde999558bca 10.0.2.0/24| | 3a647d2a-3386-4104-8fbc-0deacac5f0f2 | demo-net2 | ffe02388-45d5-431d-967d-625344410081 10.0.3.0/24| | 807c842e-2b99-40cc-bbcc-3d74990de142 | ext-net | d6d52683-7dba-432d-adf6-7c582ca0f527| | 938c2abb-dfcb-4627-8626-3618c189d4de | ext-pub1 | 791b8764-a5ab-4b16-a7b0-2b883c4f0e1e 193.225.212.128/27 | +--+---+-+ root@controller01:~# source demo2-openrc.sh root@controller01:~# neutron net-list +--++--+ | id | name | subnets | +--++--+ | 7b362a28-4bbd-42a3-b99f-81861905b136 | demo2-net | abd5d600-2f54-4a27-8d6b-23d690c18e3a 10.0.4.0/24 | | 807c842e-2b99-40cc-bbcc-3d74990de142 | ext-net| d6d52683-7dba-432d-adf6-7c582ca0f527 | | 938c2abb-dfcb-4627-8626-3618c189d4de | ext-pub1 | 791b8764-a5ab-4b16-a7b0-2b883c4f0e1e | +--++--+ The database seems be okay: root@controller01:~# openstack project list +--+-+ | ID | Name| +--+-+ | 0d693b62fb2941a381faf68f348f68f8 | service | | 1437d72da6e64b2785e04c3e2e73d6a7 | demo2 | | 15371d3015b24005a33536a95a750a62 | admin | | 60800c67e5a94d9c90c462283ea3ad0a | demo| +--+-+ Database: MariaDB [neutron]> select * from networks; +--+--+++++--+--+ | tenant_id| id | name | status | admin_state_up | shared | mtu | vlan_transparent | +--+--+++++--+--+ | 60800c67e5a94d9c90c462283ea3ad0a | 0c034b21-4e79-45c0-8f63-48b58dbd29f9 | demo-net | ACTIVE | 1 | 0 |0 | NULL | | 60800c67e5a94d9c90c462283ea3ad0a | 3a647d2a-3386-4104-8fbc-0deacac5f0f2 | demo-net2 | ACTIVE | 1 | 0 |0 | NULL | | | 57646215-ad08-465e-9b14-bc00023bd685 | HA network tenant 60800c67e5a94d9c90c462283ea3ad0a | ACTIVE | 1 | 0 |0 | NULL | | 15371d3015b24005a33536a95a750a62 | 5a0db313-a44e-41ea-8d45-e6742f0ab608 | admin-net | ACTIVE | 1 | 0 |0 | NULL | | 1437d72da6e64b2785e04c3e2e73d6a7 | 7b362a28-4bbd-42a3-b99f-81861905b136 | demo2-net | ACTIVE | 1 | 0 |0 | NULL | | 15371d3015b24005a33536a95a750a62 | 807c842e-2b99-40cc-bbcc-3d74990de142 | ext-net| ACTIVE | 1 | 0 |0 | NULL | | 60800c67e5a94d9c90c462283ea3ad0a | 938c2abb-dfcb-4627-8626-3618c189d4de | ext-pub1 | ACTIVE | 1 | 0 |0 | NULL | +--+--+++++--+--+ 7 rows in set (0.00 sec) The stored tenant id in networks table is equal with the demo tenant id. I think maybe it is a fi
[Yahoo-eng-team] [Bug 1472948] [NEW] when click edit pencil icon in the table cell in projects and users panel will display css error when login timeout
Public bug reported: Reproduce the bug: 1 Click the pencil icon in table cell in users and projects panel in identity panel group 2 When login time out it will redirect to login page 3 Login successfully and it will return to the previous page, and it will display css style error ** Affects: horizon Importance: Undecided Status: New ** Attachment added: "U$C7@FC_059U$V`[555JC0O.jpg" https://bugs.launchpad.net/bugs/1472948/+attachment/4426816/+files/U%24C7%40FC_059U%24V%60%5B555JC0O.jpg -- 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/1472948 Title: when click edit pencil icon in the table cell in projects and users panel will display css error when login timeout Status in OpenStack Dashboard (Horizon): New Bug description: Reproduce the bug: 1 Click the pencil icon in table cell in users and projects panel in identity panel group 2 When login time out it will redirect to login page 3 Login successfully and it will return to the previous page, and it will display css style error To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1472948/+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 1472946] [NEW] _poll_shelved_instances periodic task is offloading instances even if shelved_offload_time is -1
Public bug reported: shelved_offload_time -1 means instance will remain in the SHELVED state until user unshelves it. Current behavior of _poll_shelved_instances periodic task is not considering shelved_offload_time is configured as -1 and offloading all the instances which are in 'SHELVED' state. Stpes to reproduce: 1. set shelved_offload_time to -1 and restart nova-compute service. 2. create instance and shelve it using command, "nova shelve " 3. verify instance is in SHELVED state and instance files are present in instance path. 4. wait until _poll_shelved_instances periodic task executes (default is 3600 seconds, you can change it to 120 seconds) 5. Once _poll_shelved_instances periodic task is executed, instance state changes to SHELVED_OFFLOADED and instance files are deleted from instance path. ** Affects: nova Importance: Undecided Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: nova Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) -- 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/1472946 Title: _poll_shelved_instances periodic task is offloading instances even if shelved_offload_time is -1 Status in OpenStack Compute (Nova): New Bug description: shelved_offload_time -1 means instance will remain in the SHELVED state until user unshelves it. Current behavior of _poll_shelved_instances periodic task is not considering shelved_offload_time is configured as -1 and offloading all the instances which are in 'SHELVED' state. Stpes to reproduce: 1. set shelved_offload_time to -1 and restart nova-compute service. 2. create instance and shelve it using command, "nova shelve " 3. verify instance is in SHELVED state and instance files are present in instance path. 4. wait until _poll_shelved_instances periodic task executes (default is 3600 seconds, you can change it to 120 seconds) 5. Once _poll_shelved_instances periodic task is executed, instance state changes to SHELVED_OFFLOADED and instance files are deleted from instance path. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1472946/+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 1472955] [NEW] Fail to boot with snapshot image in vmware driver
Public bug reported: branch: master/kilo When using nova VMwareVCDriver, nova boot failed with instance snapshot image. This error is found from tempest failure: tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_shelve_shelved_server Steps to reproduce the failure(command line): 1. Boot an instance using a vmdk image, for example, the instance is named with test1 2. Take a snapshot of the instance: nova image_create test1 test1_snapshot 3. Boot an instance using the snapshot image, with same disk size flavor in step 1 Expected result: Instance should boot up successfully Actual result: Instance boots up with ERROR and following error is found in compute.log: VMwareDriverException: A specified parameter was not correct. capacity Full log is available here: http://paste.openstack.org/show/358046/ ** 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/1472955 Title: Fail to boot with snapshot image in vmware driver Status in OpenStack Compute (Nova): New Bug description: branch: master/kilo When using nova VMwareVCDriver, nova boot failed with instance snapshot image. This error is found from tempest failure: tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_shelve_shelved_server Steps to reproduce the failure(command line): 1. Boot an instance using a vmdk image, for example, the instance is named with test1 2. Take a snapshot of the instance: nova image_create test1 test1_snapshot 3. Boot an instance using the snapshot image, with same disk size flavor in step 1 Expected result: Instance should boot up successfully Actual result: Instance boots up with ERROR and following error is found in compute.log: VMwareDriverException: A specified parameter was not correct. capacity Full log is available here: http://paste.openstack.org/show/358046/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1472955/+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 1472956] [NEW] Wrong line python-ldap>=2.4; python_version=='2.7' in test_requirements
Public bug reported: Line 16 python-ldap>=2.4;python_version=='2.7' will block the keystone from installing via devstack. Should it be python-ldap>=2.4 # python_version=='2.7'? ** 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/1472956 Title: Wrong line python-ldap>=2.4;python_version=='2.7' in test_requirements Status in OpenStack Identity (Keystone): New Bug description: Line 16 python-ldap>=2.4;python_version=='2.7' will block the keystone from installing via devstack. Should it be python-ldap>=2.4 # python_version=='2.7'? To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1472956/+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 1472957] [NEW] BFV server with wrong bdm syntax leads to wrong volume status
Public bug reported: When booting a server from a volume with the wrong following bdm syntax: --block-device-mapping vda=vol_uuid::0 (instead of --block-device-mapping vda=vol_uuid:::0) the volume status will be reported as available. Steps to reproduce: - create a bootable volume - create a server from this volume with wrong bdm syntax - show volume status ** 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/1472957 Title: BFV server with wrong bdm syntax leads to wrong volume status Status in OpenStack Compute (Nova): New Bug description: When booting a server from a volume with the wrong following bdm syntax: --block-device-mapping vda=vol_uuid::0 (instead of --block-device-mapping vda=vol_uuid:::0) the volume status will be reported as available. Steps to reproduce: - create a bootable volume - create a server from this volume with wrong bdm syntax - show volume status To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1472957/+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 1470740] Re: swiftclient disclose token in debug logs
** No longer affects: glance -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1470740 Title: swiftclient disclose token in debug logs Status in OpenStack Security Notes: New Status in Python client library for Swift: New Bug description: Setup: juno. Nova, glance + swiftclient. glance-api.conf (important parts): [DEFAULT] debug = true logging_context_format_string=%(name)s[%(process)d]: %(levelname)s %(instance)s%(message)s [%(request_id)s %(user)s %(tenant)s] logging_default_format_string=%(name)s[%(process)d]: %(levelname)s %(instance)s%(message)s logging_debug_format_suffix=%(funcName)s %(pathname)s:%(lineno)d logging_exception_prefix=%(name)s[%(process)d]: TRACE %(instance)s default_store = swift use_syslog = True syslog_log_facility = LOG_LOCAL2 swift_store_auth_address = https://my.hand.disclosing.corporte.url:5000/v2.0 swift_store_user = tenant:user swift_store_key = sexgodqwerty123456love Result in remote syslog: DEBUG REQ: curl -i https://my.hand.disclosing.corporte.url:8080/v1/OMG_47e02d5a461148ef9f9dab62ea0ba64b/region/6a66d8dc-5748-4cb5-9db5-b12ab0d1c698-7 -X PUT -H "X-Auth-Token: 6f64276e2074726461650a6d" http_log /usr/lib/python2.7/dist-packages/swiftclient/client.py:95 Versions: ii python-swift2.2.0-0ubuntu1~cloud0 all distributed virtual object store - Python libraries ii python-swiftclient 1:2.3.0-0ubuntu1~cloud0 all Client library for Openstack Swift API. ii glance-api 1:2014.2.3-0-ownbuild all OpenStack Image Registry and Delivery Service - API ii glance-common 1:2014.2.3-ownbuild all OpenStack Image Registry and Delivery Service - Common ii python-glance 1:2014.2.3-0ownbuild all OpenStack Image Registry and Delivery Service - Python library ii python-glance-store 0.1.8-1ubuntu2~cloud0 all OpenStack Image Service store library - Python 2.x ii python-glanceclient 1:0.14.0-0ubuntu1~cloud0 all Client library for Openstack glance server. Impact: 1) Unprivileged employee with access to logging facility may get access to glance images, including snapshots of the tenants. 2) Syslog transmitted unencrypted in UDP or TCP and it may be viewed by unauthorized person. Expected behavior: Complete or partial token masking in logs, f.e.: DEBUG REQ: curl -i https://my.hand.disclosing.corporte.url:8080/v1/OMG_47e02d5a461148ef9f9dab62ea0ba64b/region/6a66d8dc-5748-4cb5-9db5-b12ab0d1c698-7 -X PUT -H "X-Auth-Token: 6d" http_log /usr/lib/python2.7/dist-packages/swiftclient/client.py:95 To manage notifications about this bug go to: https://bugs.launchpad.net/ossn/+bug/1470740/+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 1472987] [NEW] helpless exception message
Public bug reported: When there is an invalid token in use, keystone will throw exception.UnsupportedTokenVersionException, but currently, there is no useful information provided and user don't know what's happened, see the following error message. CLI, /usr/local/lib/python2.7/dist-packages/keystoneclient/shell.py:64: DeprecationWarning: The keystone CLI is deprecated in favor of python-openstackclient. For a Python library, continue using python-keystoneclient. 'python-keystoneclient.', DeprecationWarning) An unexpected error prevented the server from fulfilling your request: (Disable debug mode to suppress these details.) (HTTP 500) (Request-ID: req-b116d6e4-336a-48d0-9a00-939249ac5b1a) keystone.log, 2015-07-09 17:19:27.034038 14283 ERROR keystone.common.wsgi [-] 2015-07-09 17:19:27.034047 14283 TRACE keystone.common.wsgi Traceback (most recent call last): 2015-07-09 17:19:27.034049 14283 TRACE keystone.common.wsgi File "/opt/stack/keystone/keystone/common/wsgi.py", line 463, in __call__ 2015-07-09 17:19:27.034051 14283 TRACE keystone.common.wsgi response = self.process_request(request) 2015-07-09 17:19:27.034053 14283 TRACE keystone.common.wsgi File "/opt/stack/keystone/keystone/middleware/core.py", line 209, in process_request 2015-07-09 17:19:27.034055 14283 TRACE keystone.common.wsgi auth_context = self._build_auth_context(request) 2015-07-09 17:19:27.034057 14283 TRACE keystone.common.wsgi File "/opt/stack/keystone/keystone/middleware/core.py", line 189, in _build_auth_context 2015-07-09 17:19:27.034059 14283 TRACE keystone.common.wsgi token_data=self.token_provider_api.validate_token(token_id)) 2015-07-09 17:19:27.034061 14283 TRACE keystone.common.wsgi File "/opt/stack/keystone/keystone/models/token_model.py", line 59, in __init__ 2015-07-09 17:19:27.034063 14283 TRACE keystone.common.wsgi raise exception.UnsupportedTokenVersionException() 2015-07-09 17:19:27.034065 14283 TRACE keystone.common.wsgi UnsupportedTokenVersionException 2015-07-09 17:19:27.034067 14283 TRACE keystone.common.wsgi We can provide some unformation to end user, so the user knows what's happened and going to fix it. ** Affects: keystone Importance: Undecided Assignee: Dave Chen (wei-d-chen) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1472987 Title: helpless exception message Status in OpenStack Identity (Keystone): In Progress Bug description: When there is an invalid token in use, keystone will throw exception.UnsupportedTokenVersionException, but currently, there is no useful information provided and user don't know what's happened, see the following error message. CLI, /usr/local/lib/python2.7/dist-packages/keystoneclient/shell.py:64: DeprecationWarning: The keystone CLI is deprecated in favor of python-openstackclient. For a Python library, continue using python-keystoneclient. 'python-keystoneclient.', DeprecationWarning) An unexpected error prevented the server from fulfilling your request: (Disable debug mode to suppress these details.) (HTTP 500) (Request-ID: req-b116d6e4-336a-48d0-9a00-939249ac5b1a) keystone.log, 2015-07-09 17:19:27.034038 14283 ERROR keystone.common.wsgi [-] 2015-07-09 17:19:27.034047 14283 TRACE keystone.common.wsgi Traceback (most recent call last): 2015-07-09 17:19:27.034049 14283 TRACE keystone.common.wsgi File "/opt/stack/keystone/keystone/common/wsgi.py", line 463, in __call__ 2015-07-09 17:19:27.034051 14283 TRACE keystone.common.wsgi response = self.process_request(request) 2015-07-09 17:19:27.034053 14283 TRACE keystone.common.wsgi File "/opt/stack/keystone/keystone/middleware/core.py", line 209, in process_request 2015-07-09 17:19:27.034055 14283 TRACE keystone.common.wsgi auth_context = self._build_auth_context(request) 2015-07-09 17:19:27.034057 14283 TRACE keystone.common.wsgi File "/opt/stack/keystone/keystone/middleware/core.py", line 189, in _build_auth_context 2015-07-09 17:19:27.034059 14283 TRACE keystone.common.wsgi token_data=self.token_provider_api.validate_token(token_id)) 2015-07-09 17:19:27.034061 14283 TRACE keystone.common.wsgi File "/opt/stack/keystone/keystone/models/token_model.py", line 59, in __init__ 2015-07-09 17:19:27.034063 14283 TRACE keystone.common.wsgi raise exception.UnsupportedTokenVersionException() 2015-07-09 17:19:27.034065 14283 TRACE keystone.common.wsgi UnsupportedTokenVersionException 2015-07-09 17:19:27.034067 14283 TRACE keystone.common.wsgi We can provide some unformation to end user, so the user knows what's happened and going to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1472987/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launc
[Yahoo-eng-team] [Bug 1472999] [NEW] filter doesn't handle unicode charaters
Public bug reported: 1 go to project/instances 2. insert 'ölk' into filter field 3. enter filter 4. UnicodeEncodeError at /project/instances/ 'ascii' codec can't encode character u'\xf6' in position 0: ordinal not in range(128) Request Method: GET Request URL:http://localhost:8000/project/instances/ Django Version: 1.8.2 Exception Type: UnicodeEncodeError Exception Value: 'ascii' codec can't encode character u'\xf6' in position 0: ordinal not in range(128) Exception Location: /usr/lib64/python2.7/urllib.py in urlencode, line 1347 Python Executable: /usr/bin/python Python Version: 2.7.10 Python Path: ['/home/mrunge/work/horizon', '/usr/lib64/python27.zip', '/usr/lib64/python2.7', '/usr/lib64/python2.7/plat-linux2', '/usr/lib64/python2.7/lib-tk', '/usr/lib64/python2.7/lib-old', '/usr/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7/site-packages', '/usr/lib64/python2.7/site-packages/gtk-2.0', '/usr/lib/python2.7/site-packages', '/home/mrunge/work/horizon/openstack_dashboard'] ** Affects: horizon Importance: High Status: New ** Changed in: horizon Importance: Undecided => High -- 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/1472999 Title: filter doesn't handle unicode charaters Status in OpenStack Dashboard (Horizon): New Bug description: 1 go to project/instances 2. insert 'ölk' into filter field 3. enter filter 4. UnicodeEncodeError at /project/instances/ 'ascii' codec can't encode character u'\xf6' in position 0: ordinal not in range(128) Request Method: GET Request URL: http://localhost:8000/project/instances/ Django Version: 1.8.2 Exception Type: UnicodeEncodeError Exception Value: 'ascii' codec can't encode character u'\xf6' in position 0: ordinal not in range(128) Exception Location: /usr/lib64/python2.7/urllib.py in urlencode, line 1347 Python Executable:/usr/bin/python Python Version: 2.7.10 Python Path: ['/home/mrunge/work/horizon', '/usr/lib64/python27.zip', '/usr/lib64/python2.7', '/usr/lib64/python2.7/plat-linux2', '/usr/lib64/python2.7/lib-tk', '/usr/lib64/python2.7/lib-old', '/usr/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7/site-packages', '/usr/lib64/python2.7/site-packages/gtk-2.0', '/usr/lib/python2.7/site-packages', '/home/mrunge/work/horizon/openstack_dashboard'] To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1472999/+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 1473009] [NEW] HTTP external sources are not supported
Public bug reported:
Trying to define a new image from an external source keeps failing with 400 Bad
Request External source are not supported.
In my specific case I have tryed to define an image via Heat:
# heat stack-create image-test -f cirros.yaml
cirros.yaml:
heat_template_version: 2013-05-23
description: Glance image provider
parameters:
image_name:
type: string
default: heat_cirros
resources:
glance_image:
type: OS::Glance::Image
properties:
container_format: bare
disk_format: qcow2
is_public: true
location:
http://download.cirros-cloud.net/0.3.3/cirros-0.3.3-x86_64-disk.img
min_disk: 1
min_ram: 64
name: {get_param: image_name}
protected: false
Note that the URL is well formatted should be valid as an external
source.
** 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/1473009
Title:
HTTP external sources are not supported
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
Trying to define a new image from an external source keeps failing with 400
Bad Request External source are not supported.
In my specific case I have tryed to define an image via Heat:
# heat stack-create image-test -f cirros.yaml
cirros.yaml:
heat_template_version: 2013-05-23
description: Glance image provider
parameters:
image_name:
type: string
default: heat_cirros
resources:
glance_image:
type: OS::Glance::Image
properties:
container_format: bare
disk_format: qcow2
is_public: true
location:
http://download.cirros-cloud.net/0.3.3/cirros-0.3.3-x86_64-disk.img
min_disk: 1
min_ram: 64
name: {get_param: image_name}
protected: false
Note that the URL is well formatted should be valid as an external
source.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1473009/+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 1473030] [NEW] JS load failing due to Identity
Public bug reported: Uncaught Error: [$injector:modulerr] Failed to instantiate module horizon.app due to: Error: [$injector:modulerr] Failed to instantiate module hz.dashboard.identity due to: Error: [$injector:nomod] Module 'hz.dashboard.identity' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument. ** 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/1473030 Title: JS load failing due to Identity Status in OpenStack Dashboard (Horizon): New Bug description: Uncaught Error: [$injector:modulerr] Failed to instantiate module horizon.app due to: Error: [$injector:modulerr] Failed to instantiate module hz.dashboard.identity due to: Error: [$injector:nomod] Module 'hz.dashboard.identity' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1473030/+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 1473038] [NEW] func test ovs agent KeyError: 'ofport'
Public bug reported: >From time to time I see this error: 2015-07-07 16:32:03.667 | 2015-07-07 16:32:03.600 | Traceback (most recent call last): 2015-07-07 16:32:03.667 | 2015-07-07 16:32:03.601 | File "neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py", line 1550, in rpc_loop 2015-07-07 16:32:03.667 | 2015-07-07 16:32:03.603 | port_info = self.scan_ports(reg_ports, updated_ports_copy) 2015-07-07 16:32:03.667 | 2015-07-07 16:32:03.604 | File "neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py", line 1075, in scan_ports 2015-07-07 16:32:03.668 | 2015-07-07 16:32:03.605 | cur_ports = self.int_br.get_vif_port_set() 2015-07-07 16:32:03.668 | 2015-07-07 16:32:03.607 | File "neutron/agent/common/ovs_lib.py", line 372, in get_vif_port_set 2015-07-07 16:32:03.668 | 2015-07-07 16:32:03.608 | if result['ofport'] == UNASSIGNED_OFPORT: 2015-07-07 16:32:03.668 | 2015-07-07 16:32:03.609 | KeyError: 'ofport' 2015-07-07 16:32:03.668 | 2015-07-07 16:32:03.610 | 2015-07-07 16:30:31,332 INFO [neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent] Agent out of sync with plugin! http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiS2V5RXJyb3I6ICdvZnBvcnQnXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjE3MjgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MzY0NDQwNTczMDksIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0= ** Affects: neutron Importance: Undecided Assignee: Rossella Sblendido (rossella-o) Status: New ** Changed in: neutron Assignee: (unassigned) => Rossella Sblendido (rossella-o) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1473038 Title: func test ovs agent KeyError: 'ofport' Status in OpenStack Neutron (virtual network service): New Bug description: From time to time I see this error: 2015-07-07 16:32:03.667 | 2015-07-07 16:32:03.600 | Traceback (most recent call last): 2015-07-07 16:32:03.667 | 2015-07-07 16:32:03.601 | File "neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py", line 1550, in rpc_loop 2015-07-07 16:32:03.667 | 2015-07-07 16:32:03.603 | port_info = self.scan_ports(reg_ports, updated_ports_copy) 2015-07-07 16:32:03.667 | 2015-07-07 16:32:03.604 | File "neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py", line 1075, in scan_ports 2015-07-07 16:32:03.668 | 2015-07-07 16:32:03.605 | cur_ports = self.int_br.get_vif_port_set() 2015-07-07 16:32:03.668 | 2015-07-07 16:32:03.607 | File "neutron/agent/common/ovs_lib.py", line 372, in get_vif_port_set 2015-07-07 16:32:03.668 | 2015-07-07 16:32:03.608 | if result['ofport'] == UNASSIGNED_OFPORT: 2015-07-07 16:32:03.668 | 2015-07-07 16:32:03.609 | KeyError: 'ofport' 2015-07-07 16:32:03.668 | 2015-07-07 16:32:03.610 | 2015-07-07 16:30:31,332 INFO [neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent] Agent out of sync with plugin! http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiS2V5RXJyb3I6ICdvZnBvcnQnXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjE3MjgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MzY0NDQwNTczMDksIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0= To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1473038/+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 1473049] [NEW] test_port_creation_and_deletion fails with "Row removed from DB during listing"
Public bug reported:
I see it failing once in feature/qos:
ft1.57:
neutron.tests.functional.agent.test_l2_ovs_agent.TestOVSAgent.test_port_creation_and_deletion(native)_StringException:
Empty attachments:
pythonlogging:'neutron.api.extensions'
stderr
stdout
pythonlogging:'': {{{
2015-07-09 10:50:55,923 INFO
[neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent] Mapping
physical network physnet to bridge br-int790964659
2015-07-09 10:50:55,949 WARNING
[neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent] Creating an
interface named br-int790964659 exceeds the 15 character limitation. It was
shortened to int-br-inad9e8d to fit.
2015-07-09 10:50:55,949 WARNING
[neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent] Creating an
interface named br-int790964659 exceeds the 15 character limitation. It was
shortened to phy-br-inad9e8d to fit.
2015-07-09 10:50:56,466ERROR [neutron.agent.ovsdb.impl_idl] Traceback (most
recent call last):
File "neutron/agent/ovsdb/native/connection.py", line 84, in run
txn.results.put(txn.do_commit())
File "neutron/agent/ovsdb/impl_idl.py", line 92, in do_commit
ctx.reraise = False
File
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 119, in __exit__
six.reraise(self.type_, self.value, self.tb)
File "neutron/agent/ovsdb/impl_idl.py", line 87, in do_commit
command.run_idl(txn)
File "neutron/agent/ovsdb/native/commands.py", line 413, in run_idl
"Records=%(records)s.") % self.requested_info)
RuntimeError: Row removed from DB during listing. Request info: Table=Port.
Columns=['name', 'other_config', 'tag']. Records=None.
2015-07-09 10:50:56,466ERROR [neutron.agent.ovsdb.native.commands] Error
executing command
Traceback (most recent call last):
File "neutron/agent/ovsdb/native/commands.py", line 35, in execute
txn.add(self)
File "neutron/agent/ovsdb/api.py", line 70, in __exit__
self.result = self.commit()
File "neutron/agent/ovsdb/impl_idl.py", line 70, in commit
raise result.ex
RuntimeError: Row removed from DB during listing. Request info: Table=Port.
Columns=['name', 'other_config', 'tag']. Records=None.
}}}
Traceback (most recent call last):
File "neutron/tests/functional/agent/test_l2_ovs_agent.py", line 245, in
test_port_creation_and_deletion
agent = self.create_agent()
File "neutron/tests/functional/agent/test_l2_ovs_agent.py", line 112, in
create_agent
conf=self.config)
File "neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
line 281, in __init__
self._restore_local_vlan_map()
File "neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
line 316, in _restore_local_vlan_map
"Port", columns=["name", "other_config", "tag"])
File "neutron/agent/common/ovs_lib.py", line 148, in db_list
execute(check_error=check_error, log_errors=log_errors))
File "neutron/agent/ovsdb/native/commands.py", line 42, in execute
ctx.reraise = False
File
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 119, in __exit__
six.reraise(self.type_, self.value, self.tb)
File "neutron/agent/ovsdb/native/commands.py", line 35, in execute
txn.add(self)
File "neutron/agent/ovsdb/api.py", line 70, in __exit__
self.result = self.commit()
File "neutron/agent/ovsdb/impl_idl.py", line 70, in commit
raise result.ex
RuntimeError: Row removed from DB during listing. Request info: Table=Port.
Columns=['name', 'other_config', 'tag']. Records=None.
** Affects: neutron
Importance: Undecided
Assignee: Assaf Muller (amuller)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Assaf Muller (amuller)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1473049
Title:
test_port_creation_and_deletion fails with "Row removed from DB during
listing"
Status in OpenStack Neutron (virtual network service):
New
Bug description:
I see it failing once in feature/qos:
ft1.57:
neutron.tests.functional.agent.test_l2_ovs_agent.TestOVSAgent.test_port_creation_and_deletion(native)_StringException:
Empty attachments:
pythonlogging:'neutron.api.extensions'
stderr
stdout
pythonlogging:'': {{{
2015-07-09 10:50:55,923 INFO
[neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent] Mapping
physical network physnet to bridge br-int790964659
2015-07-09 10:50:55,949 WARNING
[neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent] Creating an
interface named br-int790964659 exceeds the 15 character limitation. It was
shortened to int-br-inad9e8d to fit.
2015-07-09 10:50:55,949 WARNING
[neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent] Creating an
interface named br-int790964659 exceeds the 15 character lim
[Yahoo-eng-team] [Bug 1304409] Re: VMs can't be booted with networks without subnet
Fix proposed to branch: master
Review: https://review.openstack.org/200046
** Changed in: nova
Status: Expired => In Progress
** Changed in: nova
Assignee: (unassigned) => Bence Romsics (bence-romsics)
--
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/1304409
Title:
VMs can't be booted with networks without subnet
Status in OpenStack Compute (Nova):
In Progress
Bug description:
Recently a change in the nova/network/neutronv2/api.py file is causing
nova boots to fail for networks that do not have a subnet associated
with them.
The following line in the api.py file is causing the issue:
for net in nets:
if not net.get('subnets'):
raise exception.NetworkRequiresSubnet(
network_uuid=net['id'])
This has to be fixed to allow users to do boots with networks that do
not have a subnet associated with them.
The issue seems to be occuring post the commit done here:
https://review.openstack.org/gitweb?p=openstack%2Fnova.git;a=commitdiff;h=45e2398f0c01c327db46ce92fb9dda886455db9d
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1304409/+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 1473030] Re: JS load failing due to Identity
** Changed in: horizon Status: In Progress => 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/1473030 Title: JS load failing due to Identity Status in OpenStack Dashboard (Horizon): Invalid Bug description: Uncaught Error: [$injector:modulerr] Failed to instantiate module horizon.app due to: Error: [$injector:modulerr] Failed to instantiate module hz.dashboard.identity due to: Error: [$injector:nomod] Module 'hz.dashboard.identity' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1473030/+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 1473073] [NEW] Example local.conf doesn't use newer plugin system
Public bug reported: The local_conf.rst uses an old configuration: # enable Sahara (data-processing) Service enable_service sahara # enable Trove (database) Service enable_service trove tr-api tr-tmgr tr-cond This should now use the enable_plugin functions. ** Affects: horizon Importance: Low Assignee: Rob Cresswell (robcresswell) Status: 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/1473073 Title: Example local.conf doesn't use newer plugin system Status in OpenStack Dashboard (Horizon): In Progress Bug description: The local_conf.rst uses an old configuration: # enable Sahara (data-processing) Service enable_service sahara # enable Trove (database) Service enable_service trove tr-api tr-tmgr tr-cond This should now use the enable_plugin functions. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1473073/+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 1457551] Re: Another Horizon login page vulnerability to a DoS attack
We normally don't increase upper bounds on requirements in stable
branches. Does horizon 2014.2.x actually work with Django 1.8? If not,
is it possible to modify it to work without significant risk of
introducing new regressions and behavior changes? This is primarily a
concern for people continuously deploying stable/juno from source. Any
distributions which packaged 2014.2 will almost certainly have security
fixes backported to the release of Django they're shipping rather than
upgrading to a later Django release.
Anyway, these are conversations which can be had in public now that we
won't be disclosing the Django vulnerability by opening this bug report.
** Information type changed from Private Security to Public
** Changed in: ossa
Status: Incomplete => Won't Fix
** Tags added: security
--
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/1457551
Title:
Another Horizon login page vulnerability to a DoS attack
Status in OpenStack Dashboard (Horizon):
New
Status in OpenStack Security Advisories:
Won't Fix
Bug description:
This bug is very similar to: https://bugs.launchpad.net/bugs/1394370
Steps to reproduce:
1) Setup Horizon to use db as session engine (using this doc:
http://docs.openstack.org/admin-guide-cloud/content/dashboard-session-database.html).
I've used MySQL.
2) Run 'for i in {1..100}; do curl -b "sessionid=a;"
http://HORIZON__IP/auth/login/ &> /dev/null; done' from your terminal.
I've got 100 rows in django_session after this.
I've used devstack installation just with updated master branch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1457551/+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 1470635] Re: endpoints added with v3 are not visible with v2
I can confirm that this is a problem, and I agree that endpoints created using the v3 api really should be available via the v2 api. ** Changed in: keystone Status: New => Confirmed ** Also affects: openstack-ansible 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/1470635 Title: endpoints added with v3 are not visible with v2 Status in OpenStack Identity (Keystone): Confirmed Status in Ansible playbooks for deploying OpenStack: New Status in Puppet module for Keystone: Confirmed Bug description: Create an endpoint with v3:: # openstack --os-identity-api-version 3 [--admin credentials] endpoint create try to list endpoints with v2:: # openstack --os-identity-api-version 2 [--admin credentials] endpoint list nothing. We are in the process of trying to convert puppet-keystone to v3 with the goal of maintaining backwards compatibility. That means, we want admins/operators not to have to change any existing workflow. This bug causes openstack endpoint list to return nothing which breaks existing workflows and backwards compatibility. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1470635/+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 1440762] Re: Rebuild an instance with attached volume fails
This bug has has also been impacting openstack-ansible. We have been tracking it here: https://bugs.launchpad.net/openstack- ansible/+bug/1400881 ** Also affects: openstack-ansible 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/1440762 Title: Rebuild an instance with attached volume fails Status in OpenStack Compute (Nova): In Progress Status in Ansible playbooks for deploying OpenStack: New Bug description: When trying to rebuild an instance with attached volume, it fails with the errors: 2015-02-04 08:41:27.477 22000 TRACE oslo.messaging.rpc.dispatcher libvirtError: Failed to terminate process 22913 with SIGKILL: Device or resource busy 2015-02-04 08:41:27.477 22000 TRACE oslo.messaging.rpc.dispatcher <180>Feb 4 08:43:12 node-2 nova-compute Periodic task is updating the host stats, it is trying to get disk info for instance-0003, but the backing volume block device was removed by concurrent operations such as resize. Error: No volume Block Device Mapping at path: /dev/disk/by-path/ip-192.168.0.4:3260-iscsi-iqn.2010-10.org.openstack:volume-82ba5653-3e07-4f0f-b44d-a946f4dedde9-lun-1 <182>Feb 4 08:43:13 node-2 nova-compute VM Stopped (Lifecycle Event) The full log of rebuild process is here: http://paste.openstack.org/show/166892/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1440762/+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 1469865] Re: oslo.versionedobjects breaks nova/cinder tests
The revert https://review.openstack.org/#/c/196926/ was released in ovo 0.5.1. ** No longer affects: nova ** No longer affects: cinder ** Changed in: oslo.versionedobjects Assignee: Alexander Tivelkov (ativelkov) => Davanum Srinivas (DIMS) (dims-v) ** Changed in: oslo.versionedobjects 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/1469865 Title: oslo.versionedobjects breaks nova/cinder tests Status in Oslo Versioned Objects: Fix Released Bug description: Version 0.5.0 cut today broke Nova: http://logs.openstack.org/40/193240/3/check/gate-nova- python27/98212cb/testr_results.html.gz To manage notifications about this bug go to: https://bugs.launchpad.net/oslo.versionedobjects/+bug/1469865/+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 1411582] Re: Azure data source should auto-detect ephemeral disk location
** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Status: New => In Progress ** Changed in: cloud-init Assignee: (unassigned) => Dan Watkins (daniel-thewatkins) -- 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/1411582 Title: Azure data source should auto-detect ephemeral disk location Status in Init scripts for use on cloud images: In Progress Status in cloud-init package in Ubuntu: New Status in walinuxagent package in Ubuntu: Fix Released Status in cloud-init source package in Precise: New Status in walinuxagent source package in Precise: Fix Released Status in cloud-init source package in Trusty: New Status in walinuxagent source package in Trusty: Fix Released Status in cloud-init source package in Utopic: New Status in walinuxagent source package in Utopic: Fix Released Status in cloud-init source package in Vivid: New Status in walinuxagent source package in Vivid: Fix Released Bug description: Currently we assume it will be /dev/sdb, but this may change. There is an example of how to handle this in the Azure Linux agent. To quote stevez in a comment on bug 1410835: Device names are not persistent in Linux and could change, so it is not guaranteed that the ephemeral disk will be called /dev/sdb. Ideally this should be auto-detected in cloud-init at runtime (for example, see DeviceForIdePort() in the Azure Linux agent). To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1411582/+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 1472957] Re: BFV server with wrong bdm syntax leads to wrong volume status
this is parsing of client , nova API should not have this problem ** Project changed: nova => python-novaclient -- 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/1472957 Title: BFV server with wrong bdm syntax leads to wrong volume status Status in Python client library for Nova: New Bug description: When booting a server from a volume with the wrong following bdm syntax: --block-device-mapping vda=vol_uuid::0 (instead of --block-device-mapping vda=vol_uuid:::0) the volume status will be reported as available. Steps to reproduce: - create a bootable volume - create a server from this volume with wrong bdm syntax - show volume status To manage notifications about this bug go to: https://bugs.launchpad.net/python-novaclient/+bug/1472957/+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 1473110] [NEW] Can't declare service providers both in neutron.conf and in neutron_*aas.conf
Public bug reported: Neutron server behavior is to load service providers from neutron.conf or neutron_*aas.conf but not both. [1] If we have a case of a service provider that does not belong to any of neutron_(lbaas|fwaas|vpnaas).conf (e.g. bgpvpn from networking-bgpvpn project) we would enable it through neutron.conf. But of course we want to be able to enable both bgpvpn and other services defined through neutron_*aas.conf at the same time. Example error where both neutron.conf and neutron_lbaas.conf are used: root@devstack-juno-compute02:/etc/neutron# grep service_provider neutron*.conf |grep -v :# neutron.conf:[service_providers] neutron.conf:service_provider=BGPVPN:BaGPipe:networking_bgpvpn.neutron.services.bgpvpn.service_drivers.bagpipe.bagpipe.BaGPipeBGPVPNDriver:default neutron_lbaas.conf:[service_providers] neutron_lbaas.conf:service_provider=LOADBALANCER:Haproxy:neutron_lbaas.services.loadbalancer.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default 2015-07-09 16:56:39.778 INFO neutron.manager [req-0d5c679c-d9de-42eb-8aa3-c889869486d4 None None] Loading Plugin: networking_bgpvpn.neutron.services.bgpvpn.plugin.BGPVPNPlugin 2015-07-09 16:56:39.992 WARNING neutron.services.provider_configuration [req-0d5c679c-d9de-42eb-8aa3-c889869486d4 None None] Reading service_providers from legacy location in neutron.conf, and ignoring values in neutron_*aas.conf files; this override will be going away soon. 2015-07-09 16:56:39.993 DEBUG neutron.services.provider_configuration [req-0d5c679c-d9de-42eb-8aa3-c889869486d4 None None] Service providers = ['BGPVPN:BaGPipe:networking_bgpvpn.neutron.services.bgpvpn.service_drivers.bagpipe.bagpipe.BaGPipeBGPVPNDriver:default'] parse_service_provider_opt /opt/stack/neutron/neutron/services/provider_configuration.py:93 2015-07-09 16:56:39.998 DEBUG neutron.services.service_base [req-0d5c679c-d9de-42eb-8aa3-c889869486d4 None None] Loaded 'networking_bgpvpn.neutron.services.bgpvpn.service_drivers.bagpipe.bagpipe.BaGPipeBGPVPNDriver' provider for service BGPVPN load_drivers /opt/stack/neutron/neutron/services/service_base.py:85 2015-07-09 16:56:39.999 INFO networking_bgpvpn.neutron.services.bgpvpn.plugin [req-0d5c679c-d9de-42eb-8aa3-c889869486d4 None None] BGP VPN Service Plugin using Service Driver: bagpipe 2015-07-09 16:56:40.000 DEBUG neutron.manager [req-0d5c679c-d9de-42eb-8aa3-c889869486d4 None None] Successfully loaded BGPVPN plugin. Description: Neutron BGP VPN connection Service Plugin _load_service_plugins /opt/stack/neutron/neutron/manager.py:196 2015-07-09 16:56:40.001 INFO neutron.manager [req-0d5c679c-d9de-42eb-8aa3-c889869486d4 None None] Loading Plugin: neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPlugin 2015-07-09 16:56:40.536 ERROR neutron.services.service_base [req-0d5c679c-d9de-42eb-8aa3-c889869486d4 None None] No providers specified for 'LOADBALANCER' service, exiting The solution could consist in extending the harcoded list of neutron_*.conf files that neutron reads to load service_providers [2], but this may or may not be the most sensible approach. [1] https://review.openstack.org/gitweb?p=openstack%2Fneutron.git;a=commitdiff;h=fb3138c8d718be67505f247ca776abf15ba1504a [2] https://github.com/openstack/neutron/blob/master/neutron/common/repos.py#L80 ** 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/1473110 Title: Can't declare service providers both in neutron.conf and in neutron_*aas.conf Status in OpenStack Neutron (virtual network service): New Bug description: Neutron server behavior is to load service providers from neutron.conf or neutron_*aas.conf but not both. [1] If we have a case of a service provider that does not belong to any of neutron_(lbaas|fwaas|vpnaas).conf (e.g. bgpvpn from networking-bgpvpn project) we would enable it through neutron.conf. But of course we want to be able to enable both bgpvpn and other services defined through neutron_*aas.conf at the same time. Example error where both neutron.conf and neutron_lbaas.conf are used: root@devstack-juno-compute02:/etc/neutron# grep service_provider neutron*.conf |grep -v :# neutron.conf:[service_providers] neutron.conf:service_provider=BGPVPN:BaGPipe:networking_bgpvpn.neutron.services.bgpvpn.service_drivers.bagpipe.bagpipe.BaGPipeBGPVPNDriver:default neutron_lbaas.conf:[service_providers] neutron_lbaas.conf:service_provider=LOADBALANCER:Haproxy:neutron_lbaas.services.loadbalancer.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default 2015-07-09 16:56:39.778 INFO neutron.manager [req-0d5c679c-d9de-42eb-8aa3-c889869486d4 None None] Loading Plugin: networking_bgpvpn.neutron.services.bgpvpn.plugin.BGPVPNPlugin 2015-07-09 16:56:39.992 WARNING neutron.services.provider_configuration [req-0d5c679c-d9de-42eb-8a
[Yahoo-eng-team] [Bug 1473117] [NEW] Sort using column work only for the dataset on one page
Public bug reported: When I open admin dashboard: /dashboard/admin/instances/ I see 20 items (in my case I have 50 records in total). Now I want to sort the data using hypervisor, so I click on "Host" column and it indeed sort it using hypervisor. However it sort just the data of that one page. E.g if I have in host column those names (using just 5 rows instead of 20 to make things simplier): machine1 machine5 machine3 machine4 machine2 When I click on Host column I got correctly machine1 machine2 machine3 machine4 machine5 But then I notice the link "More >>>" at the bottom. And when I click on it I get machine1 machine2 machine1 and when I click on Host column I get: machine1 machine1 machine2 However this is totaly wrong as I expect the sorting to work across whole dataset. So after clicking on the first page on "host" column I am expecting to see: machine1 machine1 machine1 machine2 machine2 and when I click on "More>>>" machine3 machine4 machine5 Note: I'm using OpenStack Icehouse release ** 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/1473117 Title: Sort using column work only for the dataset on one page Status in OpenStack Dashboard (Horizon): New Bug description: When I open admin dashboard: /dashboard/admin/instances/ I see 20 items (in my case I have 50 records in total). Now I want to sort the data using hypervisor, so I click on "Host" column and it indeed sort it using hypervisor. However it sort just the data of that one page. E.g if I have in host column those names (using just 5 rows instead of 20 to make things simplier): machine1 machine5 machine3 machine4 machine2 When I click on Host column I got correctly machine1 machine2 machine3 machine4 machine5 But then I notice the link "More >>>" at the bottom. And when I click on it I get machine1 machine2 machine1 and when I click on Host column I get: machine1 machine1 machine2 However this is totaly wrong as I expect the sorting to work across whole dataset. So after clicking on the first page on "host" column I am expecting to see: machine1 machine1 machine1 machine2 machine2 and when I click on "More>>>" machine3 machine4 machine5 Note: I'm using OpenStack Icehouse release To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1473117/+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 1472503] Re: python-ldap 2.4.20 causing install issues
** Changed in: keystone Status: Incomplete => 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/1472503 Title: python-ldap 2.4.20 causing install issues Status in OpenStack Identity (Keystone): Invalid Status in pbr package in Ubuntu: Confirmed Bug description: I use the lastest devstack and lastest keystone, and the install error from devstack is like this: 2015-07-08 07:15:36.238 | + local name=keystone 2015-07-08 07:15:36.238 | + /opt/stack/requirements/.venv/bin/edit-constraints /opt/stack/requirements/upper-constraints.txt -- keystone '-e file:///opt/stack/keystone#egg=keystone' 2015-07-08 07:15:36.315 | + setup_package /opt/stack/keystone -e 2015-07-08 07:15:36.315 | + local project_dir=/opt/stack/keystone 2015-07-08 07:15:36.315 | + local flags=-e 2015-07-08 07:15:36.315 | + pip_install -e /opt/stack/keystone 2015-07-08 07:15:36.592 | + sudo -H http_proxy=http://proxy01.cd.intel.com:911 https_proxy=http://proxy01.cd.intel.com:911 'no_proxy=intel.com,*.intel.com,10.0.0.0/8,192.168.0.0/16,127.0.0.0/8,localhost,127.0.0.1,192.168.140.145' PIP_FIND_LINKS=file:///opt/stack/.wheelhouse /usr/local/bin/pip install -e /opt/stack/keystone 2015-07-08 07:15:37.358 | Obtaining file:///opt/stack/keystone 2015-07-08 07:15:38.004 | Complete output from command python setup.py egg_info: 2015-07-08 07:15:38.004 | error in setup command: 'tests_require' must be a string or list of strings containing valid project/version requirement specifiers; Expected ',' or end-of-list in python-ldap>=2.4;python_version=='2.7' at ;python_version=='2.7' 2015-07-08 07:15:38.004 | 2015-07-08 07:15:38.004 | 2015-07-08 07:15:38.004 | Command "python setup.py egg_info" failed with error code 1 in /opt/stack/keystone 2015-07-08 07:15:38.015 | + exit_trap 2015-07-08 07:15:38.015 | + local r=1 2015-07-08 07:15:38.016 | ++ jobs -p 2015-07-08 07:15:38.016 | + jobs= 2015-07-08 07:15:38.016 | + [[ -n '' ]] 2015-07-08 07:15:38.016 | + kill_spinner 2015-07-08 07:15:38.016 | + '[' '!' -z '' ']' 2015-07-08 07:15:38.016 | + [[ 1 -ne 0 ]] 2015-07-08 07:15:38.016 | + echo 'Error on exit' 2015-07-08 07:15:38.017 | Error on exit 2015-07-08 07:15:38.017 | + [[ -z /opt/stack/logs ]] 2015-07-08 07:15:38.017 | + /home/stack/devstack/devstack/tools/worlddump.py -d /opt/stack/logs 2015-07-08 07:15:38.051 | df: '/run/user/112/gvfs': Permission denied 2015-07-08 07:15:38.484 | + exit 1 stack@stack-PC44-8000:~/devstack/devstack$ 2015-07-08 07:15:38.490 | /bin/sh: 1: kill: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or 2015-07-08 07:15:38.490 | kill -l [exitstatus] seems this line in https://review.openstack.org/#/c/197773/2/test-requirements.txt python-ldap>=2.4;python_version=='2.7' To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1472503/+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 1457551] Re: Another Horizon login page vulnerability to a DoS attack
OSSN seems appropriate for this once we have guidance for a proper
approach to mitigating this.
** Also affects: ossn
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/1457551
Title:
Another Horizon login page vulnerability to a DoS attack
Status in OpenStack Dashboard (Horizon):
New
Status in OpenStack Security Advisories:
Won't Fix
Status in OpenStack Security Notes:
New
Bug description:
This bug is very similar to: https://bugs.launchpad.net/bugs/1394370
Steps to reproduce:
1) Setup Horizon to use db as session engine (using this doc:
http://docs.openstack.org/admin-guide-cloud/content/dashboard-session-database.html).
I've used MySQL.
2) Run 'for i in {1..100}; do curl -b "sessionid=a;"
http://HORIZON__IP/auth/login/ &> /dev/null; done' from your terminal.
I've got 100 rows in django_session after this.
I've used devstack installation just with updated master branch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1457551/+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 1473138] [NEW] Autodiscovery tests and documentation needed
Public bug reported: See this patch. https://review.openstack.org/#/c/183364/ There was discussion in IRC room today asking for more info and saying there wasn't documentation. So we need that. ** 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/1473138 Title: Autodiscovery tests and documentation needed Status in OpenStack Dashboard (Horizon): New Bug description: See this patch. https://review.openstack.org/#/c/183364/ There was discussion in IRC room today asking for more info and saying there wasn't documentation. So we need that. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1473138/+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 1473143] [NEW] Vandelay Match-Only with blank match set Cause Duplicate records in Acquisitions
Public bug reported: Issue: It is easy to create duplicate records using the Vandelay loader for Acquisitions with the following conditions: 1. Import Non-Matching – selected 2. Match-Only Merge – selected 3. Match Set Field – blank The load will load all the incoming records as Match Set Field is blank and the system does not match on anything. This creates duplicate records. Solution: Add validation / error or user warning before loading match- only records with a blank match set. The workaround is to set up the library’s profiles for a match set. The settings are sticky so when they return to that screen they should have the proper parameters in place which would prevent the duplicates from happening. ** Affects: evergreen Importance: Wishlist Status: Confirmed ** Project changed: horizon => evergreen -- 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/1473143 Title: Vandelay Match-Only with blank match set Cause Duplicate records in Acquisitions Status in Evergreen - Open ILS: Confirmed Bug description: Issue: It is easy to create duplicate records using the Vandelay loader for Acquisitions with the following conditions: 1.Import Non-Matching – selected 2.Match-Only Merge – selected 3.Match Set Field – blank The load will load all the incoming records as Match Set Field is blank and the system does not match on anything. This creates duplicate records. Solution: Add validation / error or user warning before loading match-only records with a blank match set. The workaround is to set up the library’s profiles for a match set. The settings are sticky so when they return to that screen they should have the proper parameters in place which would prevent the duplicates from happening. To manage notifications about this bug go to: https://bugs.launchpad.net/evergreen/+bug/1473143/+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 1472060] Re: websso callback is in the wrong place
** Tags added: federation
** Changed in: keystone
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1472060
Title:
websso callback is in the wrong place
Status in OpenStack Identity (Keystone):
Opinion
Bug description:
We have all this infrastructure in /OS-
FEDERATION/identity_providers/{id}/protocol/{id} to uniquely identify
the relationship between an identity provider and a protocol for
interacting with that provider so we can apply mappings. With websso
we then hard code a route of /OS-FEDERATION/websso/{protocol}. Because
we have just stripped the identity_provider from the URL we then have
to add remote_ids to the identity_providers so that the
websso/protocol route can figure out which idp we are talking about
and lookup the idp.
We have a route that includes the idp id and protocol and if we had
put the websso route at /OS-
FEDERATION/identity_providers/{id}/protocol/{id}/websso (next to where
/auth) lives we wouldn't need the multiple s in the httpd
config and we wouldn't need to add remote_ids to the idp (because
we've already established this once in httpd).
I'm sure there are advantages to this too but what was the point of
/identity_providers/{id}/protocol/{id} if we're going to have to
establish remote_id relationships back to and IDP?
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1472060/+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 1471943] Re: KeystoneClient OS-FEDERATION needs to handle EmptyCatalog
** Tags added: federation ** Project changed: keystone => python-keystoneclient ** Changed in: python-keystoneclient Importance: Undecided => Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1471943 Title: KeystoneClient OS-FEDERATION needs to handle EmptyCatalog Status in Python client library for Keystone: In Progress Bug description: When listing federated projects using unscoped token an EmptyCatalog Exception is thrown. KeystoneClient should handle this exception. Line 36 in [1] [1] https://github.com/openstack/python-keystoneclient/blob/feature/keystoneauth_integration/keystoneclient/v3/contrib/federation/base.py To manage notifications about this bug go to: https://bugs.launchpad.net/python-keystoneclient/+bug/1471943/+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 1471787] Re: policies defined for the neutron extension resource attributes are not enforced
** 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/1471787 Title: policies defined for the neutron extension resource attributes are not enforced Status in OpenStack Neutron (virtual network service): Invalid Bug description: Policies defined for the neutron extension resource attributes are not enforced. In the case of address scopes, even though the policy.json has the below rules, neutron is allowing the tenant user to create a shared address scope. "create_subnetpool": "", "create_subnetpool:shared": "rule:admin_only" To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1471787/+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 1473169] [NEW] 'django-babel' is not in global-requirements.txt
Public bug reported:
Hi. I'm trying to install Devstack for Openstack Juno on Ubuntu 14.10,
I'm getting this error: "'django-babel' is not in global-
requirements.txt". I tried pip install django-babel, but it did not
change the error. Please see below for more information.
2015-07-09 17:39:28.145 | + cd /opt/stack/requirements
2015-07-09 17:39:28.146 | + ./.venv/bin/python update.py /opt/stack/horizon
2015-07-09 17:39:28.297 | _sync_requirements_file({'glance-store':
'glance_store>=0.1.1,<=0.1.10 # Apache-2.0', 'doc8': 'doc8
# Apache-2.0', 'sockjs-tornado': 'sockjs-tornado>=1.0.0,<2.0.0',
'xstatic-angular-mock': 'XStatic-angular-mock>=1.2.1.1 # MIT
License', 'prettytable': 'PrettyTable>=0.7,<0.8', 'pystache': 'pystache',
'cffi': 'cffi<=0.9.2', 'requests-mock': 'requests-moc
k>=0.4.0 # Apache-2.0', 'pyeclib': 'pyeclib>=0.9.2 #
BSD', 'networkx': 'networkx>=1.8,<=1.9.1', 'disk
image-builder': 'diskimage-builder>=0.1.20', 'openstack.nose-plugin':
'openstack.nose_plugin>=0.7', 'pyparsing': 'pyparsing>=2.
0.1,<=2.0.3', 'tempest-lib': 'tempest-lib', 'python-glanceclient':
'python-glanceclient>=0.14.0,<=0.15.0', 'oslo.concurrency':
'oslo.concurrency>=0.3.0,<=1.8.0 # Apache-2.0', 'python-ldap':
'python-ldap==2.3.13', 'oauthlib': 'oauthlib>=0.6,<=0.7.2', 'pyt
hon-ironicclient': 'python-ironicclient>=0.2.1,<=0.3.3', 'wrapt': 'wrapt>=1.7.0
# BSD License', 'flask': 'Flask>=0.10,<1.0', 'p
sycopg2': 'psycopg2<=2.6', 'selenium': 'selenium',
'xstatic-bootstrap-datepicker': 'XStatic-bootstrap-datepicker>=1.3.1.0 # Ap
ache 2.0 License', 'feedparser': 'feedparser<=5.1.3', 'nosexcover':
'nosexcover', 'python-troveclient': 'python-troveclient>=1.
0.4,<=1.0.8', 'xstatic-spin': 'XStatic-spin>=1.2.5.2 # MIT License',
'libvirt-python': 'libvirt-python>=1.2.5
# LGPLv2+', 'django-nose': 'django-nose', 'mox': 'mox>=0.5.3,<=0.5.3',
'cryptography': 'cryptography>=0.4,<=0.8.1 # Apache-2.
0', 'python-cinderclient': 'python-cinderclient>=1.1.0,<=1.1.1', 'jinja2':
'Jinja2<=2.7.2', 'jsonpath-rw': 'jsonpath-rw>=1.2.0,
<2.0', 'django-pyscss': 'django-pyscss>=1.0.3,<=1.0.6 # BSD License (2
clause)', 'happybase': 'happybase>=0.5,!=0.7,<=0.9', 'fa
lcon': 'falcon>=0.1.6,<0.2.0', 'decorator': 'decorator>=3.4.0,<=3.4.0', 'pbr':
'pbr>=0.6,!=0.7,<1.0', 'webob': 'WebOb>=1.2.3,<=
1.3.1', 'python-openstackclient': 'python-openstackclient>=0.3.0,<=1.0.1',
'redis': 'redis<=2.10.3', 'passlib': 'passlib<=1.6.2
', 'psutil': 'psutil>=1.1.1,<2.0.0', 'oslotest': 'oslotest>=1.1.0,<1.4.0 #
Apache-2.0', 'greenlet': 'greenlet>=0.3.2,<=0.4.2',
'mock': 'mock>=1.0,<=1.0.1', 'keystonemiddleware':
'keystonemiddleware>=1.0.0,<1.4.0', 'xstatic-jquery.bootstrap.wizard': 'XSt
atic-jquery.bootstrap.wizard>=1.0.0.1 # MIT License', 'requests':
'requests>=2.1.0,!=2.4.0,<=2.2.1', 'python-swiftclient': 'py
thon-swiftclient>=2.2.0,<=2.3.1', 'discover': 'discover<=0.4.0',
'nosehtmloutput': 'nosehtmloutput>=0.0.3', 'jsonschema': 'json
schema>=2.0.0,<3.0.0', 'os-apply-config': 'os-apply-config', 'qpid-python':
'qpid-python<=0.26.1', 'fixtures': 'fixtures>=0.3.1
4,<=1.0.0', 'boto': 'boto>=2.32.1,<2.35.0', 'os-refresh-config':
'os-refresh-config', 'nose-exclude': 'nose-exclude', 'eventlet
': 'eventlet>=0.15.1,<=0.15.2', 'pyopenssl': 'pyOpenSSL>=0.11,<=0.13',
'pastedeploy': 'PasteDeploy>=1.5.0,<=1.5.2', 'xstatic-js
encrypt': 'XStatic-jsencrypt>=2.0.0.2 # MIT License',
'tripleo-image-elements': 'tripleo-image-elements', 'ddt': 'ddt>=0.4.0',
'django-openstack-auth': 'django_openstack_auth>=1.1.7,!=1.1.8,<=1.1.9',
'python-designateclient': 'python-designateclient>=1.
0.0,<=1.1.1', 'oslo.serialization': 'oslo.serialization>=1.0.0,<=1.2.0 #
Apache-2.0', 'python-saharaclient': 'python-saharaclie
nt>=0.7.3,<=0.7.6', 'pysqlite': 'pysqlite<=2.6.3', 'nose': 'nose<=1.3.1',
'python-neutronclient': 'python-neutronclient>=2.3.6,
<2.4.0', 'sphinxcontrib-httpdomain': 'sphinxcontrib-httpdomain<=1.3.0',
'pysaml2': 'pysaml2', 'xstatic-jasmine': 'XStatic-jasmi
ne>=1.3.1.1,<2 # MIT License', 'msgpack-python':
'msgpack-python>=0.4.0,<=0.4.5', 'lockfile': 'lockfile>=0.8,<=0.8', 'paste':
'Paste<=1.7.5.1', 'python-barbicanclient':
'python-barbicanclient>=2.1.0,!=3.0.0,<3.0.2', 'oslo.i18n':
'oslo.i18n>=1.0.0,<=1.3.
1 # Apache-2.0', 'pyyaml': 'PyYAML>=3.1.0,<=3.10', 'sqlalchemy-migrate':
'sqlalchemy-migrate==0.9.1', 'oslo.utils': 'oslo.utils
>=1.4.0,<1.5.0 # Apache-2.0', 'cliff-tablib': 'cliff-tablib>=1.0,<=1.1',
>'xvfbwrapper': 'xvfbwrapper>=0.1.3 #license: MIT', 're
quests-kerberos': 'requests-kerberos>=0.5 # MIT', 'wsgiref': 'wsgiref>=0.1.2',
'xstatic-angular': 'XStatic-angular>=1.2.1.1,<1.
3.0 # MIT License', 'pyscss': 'pyScss>=1.2.1,<1.3 # MIT License',
'xstatic-angular-cookies': 'XStatic-angular-cookies>=1.2.1.
1 # MIT License', 'mox3': 'mox3>=0.7.0,<=0.7.0', 'routes':
'Routes>=1.12.
[Yahoo-eng-team] [Bug 1473176] [NEW] Dashboard karma is missing framework files
Public bug reported: We currently have two Karma files: one for horizon and one for dashboard. Because dashboard code relies horizon, the karma conf in dashboard should include the needed files from framework. Links: https://github.com/openstack/horizon/blob/master/openstack_dashboard/karma.conf.js ** Affects: horizon Importance: High Assignee: Thai Tran (tqtran) Status: In Progress ** Tags: unittest -- 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/1473176 Title: Dashboard karma is missing framework files Status in OpenStack Dashboard (Horizon): In Progress Bug description: We currently have two Karma files: one for horizon and one for dashboard. Because dashboard code relies horizon, the karma conf in dashboard should include the needed files from framework. Links: https://github.com/openstack/horizon/blob/master/openstack_dashboard/karma.conf.js To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1473176/+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 1470898] Re: keystoneclient client doesn't install cleanly with pip
apt-get install python-dev
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1470898
Title:
keystoneclient client doesn't install cleanly with pip
Status in OpenStack Identity (Keystone):
Invalid
Bug description:
I've tried this on ubuntu 12.04, 14.04 and 15.04. All reported the
same problem as follows:
sudo apt-get update
sudo apt-get install -y python-pip
sudo pip install python-keystoneclient
the installation makes it almost to the end and reports this:
building 'netifaces' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-
prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-
protector-strong -Wformat -Werror=format-security -fPIC
-DNETIFACES_VERSION=0.10.4 -DHAVE_GETIFADDRS=1 -DHAVE_GETNAMEINFO=1
-DHAVE_NETASH_ASH_H=1 -DHAVE_NETATALK_AT_H=1 -DHAVE_NETAX25_AX25_H=1
-DHAVE_NETECONET_EC_H=1 -DHAVE_NETIPX_IPX_H=1
-DHAVE_NETPACKET_PACKET_H=1 -DHAVE_LINUX_IRDA_H=1 -DHAVE_LINUX_ATM_H=1
-DHAVE_LINUX_LLC_H=1 -DHAVE_LINUX_TIPC_H=1 -DHAVE_LINUX_DN_H=1
-DHAVE_SOCKADDR_AT=1 -DHAVE_SOCKADDR_AX25=1 -DHAVE_SOCKADDR_IN=1
-DHAVE_SOCKADDR_IN6=1 -DHAVE_SOCKADDR_IPX=1 -DHAVE_SOCKADDR_UN=1
-DHAVE_SOCKADDR_ASH=1 -DHAVE_SOCKADDR_EC=1 -DHAVE_SOCKADDR_LL=1
-DHAVE_SOCKADDR_ATMPVC=1 -DHAVE_SOCKADDR_ATMSVC=1 -DHAVE_SOCKADDR_DN=1
-DHAVE_SOCKADDR_IRDA=1 -DHAVE_SOCKADDR_LLC=1 -DHAVE_PF_NETLINK=1
-I/usr/include/python2.7 -c netifaces.c -o build/temp.linux-
x86_64-2.7/netifaces.o
netifaces.c:1:20: fatal error: Python.h: No such file or directory
#include
^
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
Cleaning up...
Command /usr/bin/python -c "import setuptools,
tokenize;__file__='/tmp/pip-build-gjivLQ/netifaces/setup.py';exec(compile(getattr(tokenize,
'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))"
install --record /tmp/pip-3ffENP-record/install-record.txt
--single-version-externally-managed --compile failed with error code 1 in
/tmp/pip-build-gjivLQ/netifaces
Traceback (most recent call last):
File "/usr/bin/pip", line 9, in
load_entry_point('pip==1.5.6', 'console_scripts', 'pip')()
File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 248, in main
return command.main(cmd_args)
File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 161, in
main
text = '\n'.join(complete_log)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 42:
ordinal not in range(128)
However, if I run the keystone command I get an error that debtcollector is
missing and if I then pip install it on 12.04 or 14.04 keystone then appears to
work correctly. On 15.04 this happens:
buntu@test-1504-raw:~$ sudo pip install debtcollector
sudo: unable to resolve host test-1504-raw
Traceback (most recent call last):
File "/usr/bin/pip", line 9, in
load_entry_point('pip==1.5.6', 'console_scripts', 'pip')()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line
521, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line
2632, in load_entry_point
return ep.load()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line
2312, in load
return self.resolve()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line
2318, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 74, in
from pip.vcs import git, mercurial, subversion, bazaar # noqa
File "/usr/lib/python2.7/dist-packages/pip/vcs/mercurial.py", line 9, in
from pip.download import path_to_url
File "/usr/lib/python2.7/dist-packages/pip/download.py", line 25, in
from requests.compat import IncompleteRead
ImportError: cannot import name IncompleteRead
-mark
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1470898/+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 1473194] [NEW] Grenade tests fail for *aaS migrations
Public bug reported: I found that when Grenade runs (check-grenade-dsvm-function), it runs the migration for *aaS repos BEFORE upgrade, but not part of upgrade. In my case, the migration modified a table and the migration never ran. This fails a bunch of tests as a result. http://logs.openstack.org/70/199670/2/check/check-grenade-dsvm- neutron/8000a62/ Applies to all the advanced services. ** Affects: neutron Importance: Undecided Assignee: Paul Michali (pcm) Status: New ** Tags: vpnaas ** Changed in: neutron Assignee: (unassigned) => Paul Michali (pcm) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1473194 Title: Grenade tests fail for *aaS migrations Status in OpenStack Neutron (virtual network service): New Bug description: I found that when Grenade runs (check-grenade-dsvm-function), it runs the migration for *aaS repos BEFORE upgrade, but not part of upgrade. In my case, the migration modified a table and the migration never ran. This fails a bunch of tests as a result. http://logs.openstack.org/70/199670/2/check/check-grenade-dsvm- neutron/8000a62/ Applies to all the advanced services. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1473194/+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 1473179] Re: neutron-ovs-cleanup fails if there is a bond on br-ex
** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Status: New => In Progress ** Changed in: neutron Assignee: (unassigned) => Dan Prince (dan-prince) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1473179 Title: neutron-ovs-cleanup fails if there is a bond on br-ex Status in OpenStack Neutron (virtual network service): In Progress Status in tripleo - openstack on openstack: In Progress Bug description: Using some of the TripleO network bond templates we've discoverd that having any sort of bond on the br-ex bridge causes neutron-ovs-cleanup to fail like this: 2015-07-09 17:51:07.080 8880 ERROR neutron Traceback (most recent call last): 2015-07-09 17:51:07.080 8880 ERROR neutron File "/bin/neutron-ovs-cleanup", line 10, in 2015-07-09 17:51:07.080 8880 ERROR neutron sys.exit(main()) 2015-07-09 17:51:07.080 8880 ERROR neutron File "/usr/lib/python2.7/site-packages/neutron/cmd/ovs_cleanup.py", line 100, in main 2015-07-09 17:51:07.080 8880 ERROR neutron ports = collect_neutron_ports(available_configuration_bridges) 2015-07-09 17:51:07.080 8880 ERROR neutron File "/usr/lib/python2.7/site-packages/neutron/cmd/ovs_cleanup.py", line 60, in collect_neutron_ports 2015-07-09 17:51:07.080 8880 ERROR neutron ports += [port.port_name for port in ovs.get_vif_ports()] 2015-07-09 17:51:07.080 8880 ERROR neutron File "/usr/lib/python2.7/site-packages/neutron/agent/common/ovs_lib.py", line 324, in get_vif_ports 2015-07-09 17:51:07.080 8880 ERROR neutron check_error=True) 2015-07-09 17:51:07.080 8880 ERROR neutron File "/usr/lib/python2.7/site-packages/neutron/agent/common/ovs_lib.py", line 142, in db_get_val 2015-07-09 17:51:07.080 8880 ERROR neutron check_error=check_error, log_errors=log_errors) 2015-07-09 17:51:07.080 8880 ERROR neutron File "/usr/lib/python2.7/site-packages/neutron/agent/ovsdb/impl_vsctl.py", line 83, in execute 2015-07-09 17:51:07.080 8880 ERROR neutron txn.add(self) 2015-07-09 17:51:07.080 8880 ERROR neutron File "/usr/lib/python2.7/site-packages/neutron/agent/ovsdb/api.py", line 70, in __exit__ 2015-07-09 17:51:07.080 8880 ERROR neutron self.result = self.commit() 2015-07-09 17:51:07.080 8880 ERROR neutron File "/usr/lib/python2.7/site-packages/neutron/agent/ovsdb/impl_vsctl.py", line 50, in commit 2015-07-09 17:51:07.080 8880 ERROR neutron res = self.run_vsctl(args) 2015-07-09 17:51:07.080 8880 ERROR neutron File "/usr/lib/python2.7/site-packages/neutron/agent/ovsdb/impl_vsctl.py", line 70, in run_vsctl 2015-07-09 17:51:07.080 8880 ERROR neutron ctxt.reraise = False 2015-07-09 17:51:07.080 8880 ERROR neutron File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in __exit__ 2015-07-09 17:51:07.080 8880 ERROR neutron six.reraise(self.type_, self.value, self.tb) 2015-07-09 17:51:07.080 8880 ERROR neutron File "/usr/lib/python2.7/site-packages/neutron/agent/ovsdb/impl_vsctl.py", line 63, in run_vsctl 2015-07-09 17:51:07.080 8880 ERROR neutron log_fail_as_error=False).rstrip() 2015-07-09 17:51:07.080 8880 ERROR neutron File "/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py", line 138, in execute 2015-07-09 17:51:07.080 8880 ERROR neutron raise RuntimeError(m) 2015-07-09 17:51:07.080 8880 ERROR neutron RuntimeError: 2015-07-09 17:51:07.080 8880 ERROR neutron Command: ['sudo', 'ovs-vsctl', '--timeout=10', '--oneline', '--format=json', '--', '--columns=external_ids', 'list', 'Interface', 'bond1'] 2015-07-09 17:51:07.080 8880 ERROR neutron Exit code: 1 2015-07-09 17:51:07.080 8880 ERROR neutron Stdin: 2015-07-09 17:51:07.080 8880 ERROR neutron Stdout: 2015-07-09 17:51:07.080 8880 ERROR neutron Stderr: ovs-vsctl: no row "bond1" in table Interface 2015-07-09 17:51:07.080 8880 ERROR neutron 2015-07-09 17:51:07.080 8880 ERROR neutron To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1473179/+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 1473199] [NEW] OVSBridge.db_list should query only the ports belonging to the bridge
Public bug reported: This change introduced bulk operation for vif ports https://review.openstack.org/#/c/186734/ Anyway when calling self.int_br.db_list we query all the ports existing, not only the ports on the int_br ** Affects: neutron Importance: Undecided Assignee: Rossella Sblendido (rossella-o) Status: New ** Changed in: neutron Assignee: (unassigned) => Rossella Sblendido (rossella-o) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1473199 Title: OVSBridge.db_list should query only the ports belonging to the bridge Status in OpenStack Neutron (virtual network service): New Bug description: This change introduced bulk operation for vif ports https://review.openstack.org/#/c/186734/ Anyway when calling self.int_br.db_list we query all the ports existing, not only the ports on the int_br To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1473199/+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 1434152] Re: oslo.serialization should be moved to test-requirements.txt on stable
** Changed in: keystone/juno Status: In Progress => Confirmed ** Changed in: keystone/juno Status: Confirmed => 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/1434152 Title: oslo.serialization should be moved to test-requirements.txt on stable Status in OpenStack Identity (Keystone): Invalid Status in Keystone icehouse series: Fix Released Status in Keystone juno series: Invalid Bug description: This added oslo.serialization to requirements.txt on stable/icehouse, probably to fix a gate blocker: https://review.openstack.org/#/c/128850/ And that was cherry picked to stable/juno: https://review.openstack.org/#/c/129170/ Those should be in test-requirements.txt since it's a testing requirement for master keystoneclient and stable keystone. The keystone code on stable/juno and stable/icehouse doesn't directly use oslo.serialization so it shouldn't be in requirements.txt. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1434152/+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 1467919] Re: networking-macvtap ml2 driver and agent
Just set up my external repo along the guidlines and it's working perfeclty without any fixes into Neutron. Great work! ** Changed in: neutron Status: Confirmed => 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/1467919 Title: networking-macvtap ml2 driver and agent Status in OpenStack Neutron (virtual network service): Invalid Bug description: This defect is to track the integration of the stackforge networking- macvtap ml2 plugin + agent [1] into neutron [1] https://review.openstack.org/#/c/189644/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1467919/+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 1473217] [NEW] Cisco Nexus1000V: Remove support for the monolithic plugin
Public bug reported: Remove support for Cisco Meta plugin and the N1KV monolithic plugin. ** Affects: neutron Importance: Undecided Assignee: Abhishek Raut (abhraut) Status: New ** Tags: cisco ** Changed in: neutron Assignee: (unassigned) => Abhishek Raut (abhraut) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1473217 Title: Cisco Nexus1000V: Remove support for the monolithic plugin Status in OpenStack Neutron (virtual network service): New Bug description: Remove support for Cisco Meta plugin and the N1KV monolithic plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1473217/+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 1473267] [NEW] create endpoint with uuid string should be suppressing
Public bug reported: code location: tests.unit.test_v2_keystoneclient_sql.ClientDrivenSqlTestCase.test_endpoint_crud code: endpoint_publicurl = uuid.uuid4().hex endpoint_internalurl = uuid.uuid4().hex endpoint_adminurl = uuid.uuid4().hex result: can create endpoint success but endpoint_publicurl , endpoint_internalurl and endpoint_adminurl are invalid. related bug : https://bugs.launchpad.net/keystone/+bug/1471034 ,In fact, I was working on this bug.I think a url as a uuid string should be invalid. But the test tests.unit.test_v2_keystoneclient_sql.ClientDrivenSqlTestCase.test_endpoint_crud allow this uuid url.That' s annoying. ** Affects: keystone Importance: Undecided Assignee: jiaxi (tjxiter) Status: New ** Changed in: keystone Assignee: (unassigned) => jiaxi (tjxiter) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1473267 Title: create endpoint with uuid string should be suppressing Status in OpenStack Identity (Keystone): New Bug description: code location: tests.unit.test_v2_keystoneclient_sql.ClientDrivenSqlTestCase.test_endpoint_crud code: endpoint_publicurl = uuid.uuid4().hex endpoint_internalurl = uuid.uuid4().hex endpoint_adminurl = uuid.uuid4().hex result: can create endpoint success but endpoint_publicurl , endpoint_internalurl and endpoint_adminurl are invalid. related bug : https://bugs.launchpad.net/keystone/+bug/1471034 ,In fact, I was working on this bug.I think a url as a uuid string should be invalid. But the test tests.unit.test_v2_keystoneclient_sql.ClientDrivenSqlTestCase.test_endpoint_crud allow this uuid url.That' s annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1473267/+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 1473276] [NEW] dashboard conflict with php, which result in httpd.sevice restart failed
Public bug reported: When I install openstack into redhat 7, I find one strange thing. When I install dashboard firstly and then install php, httpd.sevice restart failed. error info: httpd[32735]: AH00526: Syntax error on line 31 of /etc/httpd/conf.d/php.conf: httpd[32735]: Invalid command 'php_value', perhaps misspelled or defined by a module not included in the server configuration When I install php firstly and then install dashboard, httpd.sevice still restart failed. error info: httpd[20260]: AH00526: Syntax error on line 1 of /etc/httpd/conf.d/openstack-dashboard.conf: httpd[20260]: Invalid command 'WSGIDaemonProcess', perhaps misspelled or defined by a module not included in the server configuration This is a very strange thing. I think it might be http's problem, but I don't know how to figure it out. ps:If I just only install php or dashboard, httpd.sevice could restart successfully. ** 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/1473276 Title: dashboard conflict with php,which result in httpd.sevice restart failed Status in OpenStack Dashboard (Horizon): New Bug description: When I install openstack into redhat 7, I find one strange thing. When I install dashboard firstly and then install php, httpd.sevice restart failed. error info: httpd[32735]: AH00526: Syntax error on line 31 of /etc/httpd/conf.d/php.conf: httpd[32735]: Invalid command 'php_value', perhaps misspelled or defined by a module not included in the server configuration When I install php firstly and then install dashboard, httpd.sevice still restart failed. error info: httpd[20260]: AH00526: Syntax error on line 1 of /etc/httpd/conf.d/openstack-dashboard.conf: httpd[20260]: Invalid command 'WSGIDaemonProcess', perhaps misspelled or defined by a module not included in the server configuration This is a very strange thing. I think it might be http's problem, but I don't know how to figure it out. ps:If I just only install php or dashboard, httpd.sevice could restart successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1473276/+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 1450438] Re: loopingcall: if a time drift to the future occurs, all timers will be blocked
** Also affects: oslo-incubator Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1450438 Title: loopingcall: if a time drift to the future occurs, all timers will be blocked Status in OpenStack Compute (Nova): In Progress Status in The Oslo library incubator: New Status in Library for running OpenStack services: Fix Released Bug description: Due to the fact that loopingcall.py uses time.time for recording wall- clock time which is not guaranteed to be monotonic, if a time drift to the future occurs, and then gets corrected, all the timers will get blocked until the actual time reaches the moment of the original drift. This can be pretty bad if the interval is not insignificant - in Nova's case - all services uses FixedIntervalLoopingCall for it's heartbeat periodic tasks - if a drift is on the order of magnitude of several hours, no heartbeats will happen. DynamicLoopingCall is affected by this as well but because it relies on eventlet which would also use a non-monotonic time.time function for it's internal timers. Solving this will require looping calls to start using a monotonic timer (for python 2.7 there is a monotonic package). Also all services that want to use timers and avoid this issue should doe something like import monotonic hub = eventlet.get_hub() hub.clock = monotonic.monotonic immediately after calling eventlet.monkey_patch() To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1450438/+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 1473278] [NEW] add vhost user constants to portbinding extention
Public bug reported: during the kilo development cycle a new vif type VIF_TYPE_VHOST_USER was added to the nova libvit driver. in parallel a ovs dpdk mechanism driver was also created which consumes this new VIF type. as humans are error prone when multitasking i forgot to introduce the pathset to add vhost_user constants for port binding to https://github.com/openstack/neutron/blob/master/neutron/extensions/portbindings.py the rfe bug captures the addtion of the following binding constants for the vhost user interface. # - vhost_user_ovs_plug: Boolean used to inform Nova that the ovs plug # method should be used when binding the # vhost user vif. VHOST_USER_OVS_PLUG = 'vhostuser_ovs_plug' # - vhost_user_mode: String value used to declare how the mode of a # vhost-user socket VHOST_USER_MODE = 'vhostuser_mode' # - server: socket created by hypervisor VHOST_USER_MODE_SERVER = 'server' # - client: socket created by vswitch VHOST_USER_MODE_CLIENT = 'client' # - vhostuser_socket String value used to declare the vhostuser socket name VHOST_USER_SOCKET = 'vhostuser_socket' # - vif_type_vhost_user: vif type to enable use of the qemu vhost-user vif VIF_TYPE_VHOST_USER = 'vhostuser' # default location for vhostuser sockets VHOSTUSER_SOCKET_DIR = '/var/run/openvswitch' ** Affects: neutron Importance: Undecided Assignee: sean mooney (sean-k-mooney) Status: New ** Tags: rfe ** Changed in: neutron Assignee: (unassigned) => sean mooney (sean-k-mooney) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1473278 Title: add vhost user constants to portbinding extention Status in OpenStack Neutron (virtual network service): New Bug description: during the kilo development cycle a new vif type VIF_TYPE_VHOST_USER was added to the nova libvit driver. in parallel a ovs dpdk mechanism driver was also created which consumes this new VIF type. as humans are error prone when multitasking i forgot to introduce the pathset to add vhost_user constants for port binding to https://github.com/openstack/neutron/blob/master/neutron/extensions/portbindings.py the rfe bug captures the addtion of the following binding constants for the vhost user interface. # - vhost_user_ovs_plug: Boolean used to inform Nova that the ovs plug # method should be used when binding the # vhost user vif. VHOST_USER_OVS_PLUG = 'vhostuser_ovs_plug' # - vhost_user_mode: String value used to declare how the mode of a # vhost-user socket VHOST_USER_MODE = 'vhostuser_mode' # - server: socket created by hypervisor VHOST_USER_MODE_SERVER = 'server' # - client: socket created by vswitch VHOST_USER_MODE_CLIENT = 'client' # - vhostuser_socket String value used to declare the vhostuser socket name VHOST_USER_SOCKET = 'vhostuser_socket' # - vif_type_vhost_user: vif type to enable use of the qemu vhost-user vif VIF_TYPE_VHOST_USER = 'vhostuser' # default location for vhostuser sockets VHOSTUSER_SOCKET_DIR = '/var/run/openvswitch' To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1473278/+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 1473277] [NEW] Create new project fail
Public bug reported: Creating new project fail with keystone V3. we get the message "Project name is already in use. Please use a different name." , although the name of project is not duplicated. ** Affects: horizon Importance: Undecided Assignee: Canh Truong (canh-v-truong) Status: New ** Changed in: horizon Assignee: (unassigned) => Canh Truong (canh-v-truong) -- 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/1473277 Title: Create new project fail Status in OpenStack Dashboard (Horizon): New Bug description: Creating new project fail with keystone V3. we get the message "Project name is already in use. Please use a different name." , although the name of project is not duplicated. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1473277/+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 1473291] [NEW] nova compute on hyperv don't wait for vif plugged event from neutron
Public bug reported: 1. Exact version of Nova/OpenStack you are running: Juno/stable 2. Reproduce steps: * Launch a VM on a Hyper-V cloud. * Note the boot time of the Virtual Machine in nova-compute.log. * Note the port up status time in neutron DB for the port of the VM. The boot time of the Virtual machine is earlier than the port UP status, which should not be the case. Expected result: * The boot time of the Virtual Machine should be later than port UP status. * All port rules are applied before the VM is booted and presented to the user. Actual result: * VM boots before the port rules are applied by neutron and it results in VM not getting IP, missing rules to communicate etc. 4. Description When the port binding is complete, neutron uses notifier to notify the port UP event to Nova, so that Nova could power ON or resume the VM instance. On Nova compute for hyper-v, Nova doesn't wait for the Port Up event from neutron and boots the instance immediately once the disk preparation is done. This causes VM instances to boot without proper security rules and hence would result in VMs not getting IP or connectivity as desired by the user. To prevent this, Nova compute should wait for the vif plugged event from neutron and then do power ON operation. ** 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/1473291 Title: nova compute on hyperv don't wait for vif plugged event from neutron Status in OpenStack Compute (Nova): New Bug description: 1. Exact version of Nova/OpenStack you are running: Juno/stable 2. Reproduce steps: * Launch a VM on a Hyper-V cloud. * Note the boot time of the Virtual Machine in nova-compute.log. * Note the port up status time in neutron DB for the port of the VM. The boot time of the Virtual machine is earlier than the port UP status, which should not be the case. Expected result: * The boot time of the Virtual Machine should be later than port UP status. * All port rules are applied before the VM is booted and presented to the user. Actual result: * VM boots before the port rules are applied by neutron and it results in VM not getting IP, missing rules to communicate etc. 4. Description When the port binding is complete, neutron uses notifier to notify the port UP event to Nova, so that Nova could power ON or resume the VM instance. On Nova compute for hyper-v, Nova doesn't wait for the Port Up event from neutron and boots the instance immediately once the disk preparation is done. This causes VM instances to boot without proper security rules and hence would result in VMs not getting IP or connectivity as desired by the user. To prevent this, Nova compute should wait for the vif plugged event from neutron and then do power ON operation. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1473291/+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 1473292] [NEW] Cannot delete trust with an expired date
Public bug reported: Using keystone V3 trusts (Kilo 2015.1.0) Deleting a non expired trust works as expected, meanwhile when trying to remove an expired trust, Keystone returns the trust doesn't exist. Also nothing in the documentation [1] indicates expired trusts cannot be removed or have to flushed from database (using a separate process): [1] http://specs.openstack.org/openstack/keystone-specs/api/v3/identity- api-v3-os-trust-ext.html --- Trust list --- # openstack --os-username adminv3 --os-password testing --os-auth-url http://192.168.64.11:5000/v3 --os-project-name openstackv3 --os-identity-api-version 3 --os-user-domain-name admin_domain --os-project-domain-name admin_domain trust list --format csv "ID","Expires At","Impersonation","Project ID","Trustee User ID","Trustor User ID" "38861fcd00594aa2ac4bfb6355833025","2018-01-01T00:00:00.00Z",True,"78e22bb71862481dbe8335b4ce4551e8","ac994e5701d644b6a3ac78c9dd1ad04a","24b047f52ff94029923f7f0ea982f03f" "3b98a91e56df4f4f879ae982083fdfd4","2015-01-01T00:00:00.00Z",False,"78e22bb71862481dbe8335b4ce4551e8","ac994e5701d644b6a3ac78c9dd1ad04a","24b047f52ff94029923f7f0ea982f03f" - --- Trust delete a non expired trust --- # openstack --os-username adminv3 --os-password testing --os-auth-url http://192.168.64.11:5000/v3 --os-project-name openstackv3 --os-identity-api-version 3 --os-user-domain-name admin_domain --os-project-domain-name admin_domain trust delete 38861fcd00594aa2ac4bfb6355833025 --- Trust delete a non expired trust --- # openstack --os-username adminv3 --os-password testing --os-auth-url http://192.168.64.11:5000/v3 --os-project-name openstackv3 --os-identity-api-version 3 --os-user-domain-name admin_domain --os-project-domain-name admin_domain trust delete 3b98a91e56df4f4f879ae982083fdfd4 ERROR: openstack No trust with a name or ID of '3b98a91e56df4f4f879ae982083fdfd4' exists. Keystone log file --- 2015-07-08 16:29:18.134 1635 WARNING keystone.common.wsgi [-] Could not find trust: 3b98a91e56df4f4f879ae982083fdfd4 -- ** 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/1473292 Title: Cannot delete trust with an expired date Status in OpenStack Identity (Keystone): New Bug description: Using keystone V3 trusts (Kilo 2015.1.0) Deleting a non expired trust works as expected, meanwhile when trying to remove an expired trust, Keystone returns the trust doesn't exist. Also nothing in the documentation [1] indicates expired trusts cannot be removed or have to flushed from database (using a separate process): [1] http://specs.openstack.org/openstack/keystone-specs/api/v3 /identity-api-v3-os-trust-ext.html --- Trust list --- # openstack --os-username adminv3 --os-password testing --os-auth-url http://192.168.64.11:5000/v3 --os-project-name openstackv3 --os-identity-api-version 3 --os-user-domain-name admin_domain --os-project-domain-name admin_domain trust list --format csv "ID","Expires At","Impersonation","Project ID","Trustee User ID","Trustor User ID" "38861fcd00594aa2ac4bfb6355833025","2018-01-01T00:00:00.00Z",True,"78e22bb71862481dbe8335b4ce4551e8","ac994e5701d644b6a3ac78c9dd1ad04a","24b047f52ff94029923f7f0ea982f03f" "3b98a91e56df4f4f879ae982083fdfd4","2015-01-01T00:00:00.00Z",False,"78e22bb71862481dbe8335b4ce4551e8","ac994e5701d644b6a3ac78c9dd1ad04a","24b047f52ff94029923f7f0ea982f03f" - --- Trust delete a non expired trust --- # openstack --os-username adminv3 --os-password testing --os-auth-url http://192.168.64.11:5000/v3 --os-project-name openstackv3 --os-identity-api-version 3 --os-user-domain-name admin_domain --os-project-domain-name admin_domain trust delete 38861fcd00594aa2ac4bfb6355833025 --- Trust delete a non expired trust --- # openstack --os-username adminv3 --os-password testing --os-auth-url http://192.168.64.11:5000/v3 --os-project-name openstackv3 --os-identity-api-version 3 --os-user-domain-name admin_domain --os-project-domain-name admin_domain trust delete 3b98a91e56df4f4f879ae982083fdfd4 ERROR: openstack No trust with a name or ID of '3b98a91e56df4f4f879ae982083fdfd4' exists. Keystone log file --- 2015-07-08 16:29:18.134 1635 WARNING keystone.common.wsgi [-] Could not find trust: 3b98a91e56df4f4f879ae982083fdfd4 -- To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1473292/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-
[Yahoo-eng-team] [Bug 1473298] [NEW] Cannot create keystone trust with python-openstackclient using trustor/trustee id
Public bug reported: Creating Keystone V3 trusts (Kilo 2015.1.0) with python-openstackclient (OSC) 1.5.0 works fine when using trustor user and trustee user names but doesn't when using IDs. Keystone log (verbose) doesn't return any error/warning, so that might be an OSC issue. # openstack user show adminv3 --format shell domain_id="43c0586acd1b48b5ad544600414700fb" email="t...@example.tld" enabled="True" id="24b047f52ff94029923f7f0ea982f03f" name="adminv3" # openstack trust create --format shell --role admin --project openstackv3 adminv3 foo deleted_at="None" expires_at="None" id="c42c31ac89a0465da6f23121a64570c1" impersonation="False" project_id="78e22bb71862481dbe8335b4ce4551e8" redelegation_count="0" remaining_uses="None" roles="admin " trustee_user_id="ac994e5701d644b6a3ac78c9dd1ad04a" trustor_user_id="24b047f52ff94029923f7f0ea982f03f" # openstack trust create --format shell --role admin --project openstackv3 24b047f52ff94029923f7f0ea982f03f foo ERROR: openstack No user with a name or ID of '24b047f52ff94029923f7f0ea982f03f' exists. ** 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/1473298 Title: Cannot create keystone trust with python-openstackclient using trustor/trustee id Status in OpenStack Identity (Keystone): New Bug description: Creating Keystone V3 trusts (Kilo 2015.1.0) with python- openstackclient (OSC) 1.5.0 works fine when using trustor user and trustee user names but doesn't when using IDs. Keystone log (verbose) doesn't return any error/warning, so that might be an OSC issue. # openstack user show adminv3 --format shell domain_id="43c0586acd1b48b5ad544600414700fb" email="t...@example.tld" enabled="True" id="24b047f52ff94029923f7f0ea982f03f" name="adminv3" # openstack trust create --format shell --role admin --project openstackv3 adminv3 foo deleted_at="None" expires_at="None" id="c42c31ac89a0465da6f23121a64570c1" impersonation="False" project_id="78e22bb71862481dbe8335b4ce4551e8" redelegation_count="0" remaining_uses="None" roles="admin " trustee_user_id="ac994e5701d644b6a3ac78c9dd1ad04a" trustor_user_id="24b047f52ff94029923f7f0ea982f03f" # openstack trust create --format shell --role admin --project openstackv3 24b047f52ff94029923f7f0ea982f03f foo ERROR: openstack No user with a name or ID of '24b047f52ff94029923f7f0ea982f03f' exists. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1473298/+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
