[Yahoo-eng-team] [Bug 1339564] [NEW] glance image-delete on an image with the status "saving" doesn't delete the image's file from store
Public bug reported: Description of problem: After running the the scenario described in bugs.launchpad.net/cinder/+bug/1339545 , I've deleted two images with that were stuck in "saving" status with # glance image-delete both of the image's files were still in the store: #ls -l /var/lib/glance/images -rw-r-. 1 glance glance 2158362624 Jul 9 10:18 d4da7dea-c94d-4c9e-a987-955a905a7fed -rw-r-. 1 glance glance 1630994432 Jul 9 10:09 8532ef07-3dfa-4d63-8537-033c31b16814 Version-Release number of selected component (if applicable): python-glanceclient-0.12.0-1.el7ost.noarch python-glance-2014.1-4.el7ost.noarch openstack-glance-2014.1-4.el7ost.noarch How reproducible: Steps to Reproduce: 1. Run the scenario from bugs.launchpad.net/cinder/+bug/1339545 2. Delete the image: # glance image-delete Actual results: The file is still in the store. Expected results: The file has been deleted from the store. Additional info: The logs are attached - images uid's: d4da7dea-c94d-4c9e-a987-955a905a7fed 8532ef07-3dfa-4d63-8537-033c31b16814 ** Affects: glance Importance: Undecided Status: New ** Attachment added: "delete_images.log" https://bugs.launchpad.net/bugs/1339564/+attachment/4148612/+files/delete_images.log -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1339564 Title: glance image-delete on an image with the status "saving" doesn't delete the image's file from store Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Description of problem: After running the the scenario described in bugs.launchpad.net/cinder/+bug/1339545 , I've deleted two images with that were stuck in "saving" status with # glance image-delete both of the image's files were still in the store: #ls -l /var/lib/glance/images -rw-r-. 1 glance glance 2158362624 Jul 9 10:18 d4da7dea-c94d-4c9e-a987-955a905a7fed -rw-r-. 1 glance glance 1630994432 Jul 9 10:09 8532ef07-3dfa-4d63-8537-033c31b16814 Version-Release number of selected component (if applicable): python-glanceclient-0.12.0-1.el7ost.noarch python-glance-2014.1-4.el7ost.noarch openstack-glance-2014.1-4.el7ost.noarch How reproducible: Steps to Reproduce: 1. Run the scenario from bugs.launchpad.net/cinder/+bug/1339545 2. Delete the image: # glance image-delete Actual results: The file is still in the store. Expected results: The file has been deleted from the store. Additional info: The logs are attached - images uid's: d4da7dea-c94d-4c9e-a987-955a905a7fed 8532ef07-3dfa-4d63-8537-033c31b16814 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1339564/+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 1337821] Re: VMDK Volume attach fails while attaching to an instance that is booted from VMDK volume
Removing the VMWare tag as looking at the code it seems to affect all drivers. Also marking as invalid for Nova - Horizon should not be making assumptions about the device name for attach. ** Also affects: horizon Importance: Undecided Status: New ** Changed in: nova Status: New => Invalid ** Tags removed: vmware -- 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/1337821 Title: VMDK Volume attach fails while attaching to an instance that is booted from VMDK volume Status in OpenStack Dashboard (Horizon): New Status in OpenStack Compute (Nova): Invalid Bug description: I have booted an instance from a volume, successfully booted, now another volume, i try to attach to same instance, it is failing. see the stack trace.. 2014-07-04 08:56:11.391 TRACE oslo.messaging.rpc.dispatcher raise exception.InvalidDevicePath(path=root_device_name) 2014-07-04 08:56:11.391 TRACE oslo.messaging.rpc.dispatcher InvalidDevicePath: The supplied device path (vda) is invalid. 2014-07-04 08:56:11.391 TRACE oslo.messaging.rpc.dispatcher 2014-07-04 08:56:11.396 ERROR oslo.messaging._drivers.common [req-648122d5-fd39-495b-a3a7-a96bd32091d6 admin admin] Returning exception The supplied device path (vda) is invalid. to caller 2014-07-04 08:56:11.396 ERROR oslo.messaging._drivers.common [req-648122d5-fd39-495b-a3a7-a96bd32091d6 admin admin] ['Traceback (most recent call last):\n', ' File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 134, in _dispatch_and_reply\nincoming.message))\n', ' File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 177, in _dispatch\nreturn self._do_dispatch(endpoint, method, ctxt, args)\n', ' File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 123, in _do_dispatch\nresult = getattr(endpoint, method)(ctxt, **new_args)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 401, in decorated_function\nreturn function(self, context, *args, **kwargs)\n', ' File "/opt/stack/nova/nova/exception.py", line 88, in wrapped\npayload)\n', ' File "/opt/stack/nova/nova/openstack/common/excutils.py", line 82, in __exit__\nsix.reraise(self.type_, self.value, self.tb) \n', ' File "/opt/stack/nova/nova/exception.py", line 71, in wrapped\n return f(self, context, *args, **kw)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 286, in decorated_function\n pass\n', ' File "/opt/stack/nova/nova/openstack/common/excutils.py", line 82, in __exit__\nsix.reraise(self.type_, self.value, self.tb)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 272, in decorated_function\n return function(self, context, *args, **kwargs)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 314, in decorated_function\n kwargs[\'instance\'], e, sys.exc_info())\n', ' File "/opt/stack/nova/nova/openstack/common/excutils.py", line 82, in __exit__\n six.reraise(self.type_, self.value, self.tb)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 302, in decorated_function\n return function(self, context, *args, **kwargs)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 4201, in reserve_block_device_name\nret urn do_reserve()\n', ' File "/opt/stack/nova/nova/openstack/common/lockutils.py", line 249, in inner\n return f(*args, **kwargs)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 4188, in do_reserve\n context, instance, bdms, device)\n', ' File "/opt/stack/nova/nova/compute/utils.py", line 106, in get_device_name_for_instance\nmappings[\'root\'], device)\n', ' File "/opt/stack/nova/nova/compute/utils.py", line 155, in get_next_device_name\n raise exception.InvalidDevicePath(path=root_device_name)\n', 'InvalidDevicePath: The supplied device path (vda) is invalid.\n'] To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1337821/+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 1337821] Re: VMDK Volume attach fails while attaching to an instance that is booted from VMDK volume
** Changed in: horizon Status: New => Invalid ** Changed in: nova Status: Invalid => In Progress ** Changed in: horizon Assignee: Chinmaya Bharadwaj (acbharadwaj) => (unassigned) -- 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/1337821 Title: VMDK Volume attach fails while attaching to an instance that is booted from VMDK volume Status in OpenStack Dashboard (Horizon): Invalid Status in OpenStack Compute (Nova): In Progress Bug description: I have booted an instance from a volume, successfully booted, now another volume, i try to attach to same instance, it is failing. see the stack trace.. 2014-07-04 08:56:11.391 TRACE oslo.messaging.rpc.dispatcher raise exception.InvalidDevicePath(path=root_device_name) 2014-07-04 08:56:11.391 TRACE oslo.messaging.rpc.dispatcher InvalidDevicePath: The supplied device path (vda) is invalid. 2014-07-04 08:56:11.391 TRACE oslo.messaging.rpc.dispatcher 2014-07-04 08:56:11.396 ERROR oslo.messaging._drivers.common [req-648122d5-fd39-495b-a3a7-a96bd32091d6 admin admin] Returning exception The supplied device path (vda) is invalid. to caller 2014-07-04 08:56:11.396 ERROR oslo.messaging._drivers.common [req-648122d5-fd39-495b-a3a7-a96bd32091d6 admin admin] ['Traceback (most recent call last):\n', ' File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 134, in _dispatch_and_reply\nincoming.message))\n', ' File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 177, in _dispatch\nreturn self._do_dispatch(endpoint, method, ctxt, args)\n', ' File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 123, in _do_dispatch\nresult = getattr(endpoint, method)(ctxt, **new_args)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 401, in decorated_function\nreturn function(self, context, *args, **kwargs)\n', ' File "/opt/stack/nova/nova/exception.py", line 88, in wrapped\npayload)\n', ' File "/opt/stack/nova/nova/openstack/common/excutils.py", line 82, in __exit__\nsix.reraise(self.type_, self.value, self.tb) \n', ' File "/opt/stack/nova/nova/exception.py", line 71, in wrapped\n return f(self, context, *args, **kw)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 286, in decorated_function\n pass\n', ' File "/opt/stack/nova/nova/openstack/common/excutils.py", line 82, in __exit__\nsix.reraise(self.type_, self.value, self.tb)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 272, in decorated_function\n return function(self, context, *args, **kwargs)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 314, in decorated_function\n kwargs[\'instance\'], e, sys.exc_info())\n', ' File "/opt/stack/nova/nova/openstack/common/excutils.py", line 82, in __exit__\n six.reraise(self.type_, self.value, self.tb)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 302, in decorated_function\n return function(self, context, *args, **kwargs)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 4201, in reserve_block_device_name\nret urn do_reserve()\n', ' File "/opt/stack/nova/nova/openstack/common/lockutils.py", line 249, in inner\n return f(*args, **kwargs)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 4188, in do_reserve\n context, instance, bdms, device)\n', ' File "/opt/stack/nova/nova/compute/utils.py", line 106, in get_device_name_for_instance\nmappings[\'root\'], device)\n', ' File "/opt/stack/nova/nova/compute/utils.py", line 155, in get_next_device_name\n raise exception.InvalidDevicePath(path=root_device_name)\n', 'InvalidDevicePath: The supplied device path (vda) is invalid.\n'] The reason behind this issue is: because of the root device_name being set 'vda' in the case of boot from volume, The future volume attaches to the VM fail saying "The supplied device path (vda) is invalid" To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1337821/+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 1317100] Re: User data should be redacted when logging request spec
The change to drive provisioning from conductor now avoids the code path that was logging user data, so the immediate concern has gone away. Not carrying user data in the instance object would still be a useful optimization - but that's a different task. ** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1317100 Title: User data should be redacted when logging request spec Status in OpenStack Compute (Nova): Invalid Bug description: The filter scheduler has a Debug level log for the request spec, which includes in the instance properties the base64 encoded user_data. Since this may be used by the user to pass credentials into the VM this field should be redacted in the log enrty. User data is an opaque data blob as far as Nova is concerned (and hence of no practical use for debugging). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1317100/+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 1337821] Re: VMDK Volume attach fails while attaching to an instance that is booted from VMDK volume
** No longer affects: horizon -- 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/1337821 Title: VMDK Volume attach fails while attaching to an instance that is booted from VMDK volume Status in OpenStack Compute (Nova): In Progress Bug description: I have booted an instance from a volume, successfully booted, now another volume, i try to attach to same instance, it is failing. see the stack trace.. 2014-07-04 08:56:11.391 TRACE oslo.messaging.rpc.dispatcher raise exception.InvalidDevicePath(path=root_device_name) 2014-07-04 08:56:11.391 TRACE oslo.messaging.rpc.dispatcher InvalidDevicePath: The supplied device path (vda) is invalid. 2014-07-04 08:56:11.391 TRACE oslo.messaging.rpc.dispatcher 2014-07-04 08:56:11.396 ERROR oslo.messaging._drivers.common [req-648122d5-fd39-495b-a3a7-a96bd32091d6 admin admin] Returning exception The supplied device path (vda) is invalid. to caller 2014-07-04 08:56:11.396 ERROR oslo.messaging._drivers.common [req-648122d5-fd39-495b-a3a7-a96bd32091d6 admin admin] ['Traceback (most recent call last):\n', ' File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 134, in _dispatch_and_reply\nincoming.message))\n', ' File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 177, in _dispatch\nreturn self._do_dispatch(endpoint, method, ctxt, args)\n', ' File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 123, in _do_dispatch\nresult = getattr(endpoint, method)(ctxt, **new_args)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 401, in decorated_function\nreturn function(self, context, *args, **kwargs)\n', ' File "/opt/stack/nova/nova/exception.py", line 88, in wrapped\npayload)\n', ' File "/opt/stack/nova/nova/openstack/common/excutils.py", line 82, in __exit__\nsix.reraise(self.type_, self.value, self.tb) \n', ' File "/opt/stack/nova/nova/exception.py", line 71, in wrapped\n return f(self, context, *args, **kw)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 286, in decorated_function\n pass\n', ' File "/opt/stack/nova/nova/openstack/common/excutils.py", line 82, in __exit__\nsix.reraise(self.type_, self.value, self.tb)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 272, in decorated_function\n return function(self, context, *args, **kwargs)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 314, in decorated_function\n kwargs[\'instance\'], e, sys.exc_info())\n', ' File "/opt/stack/nova/nova/openstack/common/excutils.py", line 82, in __exit__\n six.reraise(self.type_, self.value, self.tb)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 302, in decorated_function\n return function(self, context, *args, **kwargs)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 4201, in reserve_block_device_name\nret urn do_reserve()\n', ' File "/opt/stack/nova/nova/openstack/common/lockutils.py", line 249, in inner\n return f(*args, **kwargs)\n', ' File "/opt/stack/nova/nova/compute/manager.py", line 4188, in do_reserve\n context, instance, bdms, device)\n', ' File "/opt/stack/nova/nova/compute/utils.py", line 106, in get_device_name_for_instance\nmappings[\'root\'], device)\n', ' File "/opt/stack/nova/nova/compute/utils.py", line 155, in get_next_device_name\n raise exception.InvalidDevicePath(path=root_device_name)\n', 'InvalidDevicePath: The supplied device path (vda) is invalid.\n'] The reason behind this issue is: because of the root device_name being set 'vda' in the case of boot from volume, The future volume attaches to the VM fail saying "The supplied device path (vda) is invalid" To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1337821/+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 1292142] Re: Fix some swift based scrubber functional tests
I re-tested with the latest 'master' and these seem to run ok now: It looks like these run ok now: test_delayed_delete 22.34 test_scrubber_app 25.90 test_scrubber_app_against_swift 27.17 test_scrubber_delete_handles_exception26.20 test_scrubber_handles_swift_missing 26.73 test_scrubber_with_metadata_enc 19.67 ** Changed in: glance Status: Triaged => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1292142 Title: Fix some swift based scrubber functional tests Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: Three of the scrubber tests which rely on swift (glance.tests.functional.test_scrubber.TestScrubber) are currently failing. glance.tests.functional.test_scrubber.TestScrubber test_delayed_delete OK 20.17 test_scrubber_app OK 24.21 test_scrubber_app_against_swift FAIL test_scrubber_delete_handles_exceptionOK 24.02 test_scrubber_handles_swift_missing FAIL test_scrubber_with_metadata_enc FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1292142/+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 1280055] Re: Replace nova.db.sqlalchemy.utils with openstack.common.db.sqlalchemy.utils
** Changed in: oslo Status: Fix Committed => 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/1280055 Title: Replace nova.db.sqlalchemy.utils with openstack.common.db.sqlalchemy.utils Status in OpenStack Compute (Nova): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: Most of the code in nova.db.sqlalchemy.utils is also in oslo- incubator.openstack.common.db.sqlalchemy.utils, except for the modify_indexes method which is not actually even used in the nova db migration code anymore now that it's been compacted in icehouse. Also, the oslo.db code has been getting synced over to nova more frequently lately so rather than keep all of this duplicate code around we should move nova to using the oslo utils code and drop the internal nova one, with maybe moving the modify_indexes method to oslo first, then sync back to nova and then drop nova.db.sqlalchemy.utils from nova. We will have to make sure that there are no behavior differences in the oslo code such that it would change the nova db schema, but we should be able to use Dan Prince's nova/tools/db/schema_diff.py script to validate that. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1280055/+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 1322197] Re: [OSSA 2014-023] Persistent XSS in OpenStack Havana UI for Network Name (CVE-2014-3474)
** Changed in: ossa Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1322197 Title: [OSSA 2014-023] Persistent XSS in OpenStack Havana UI for Network Name (CVE-2014-3474) Status in OpenStack Dashboard (Horizon): Fix Committed Status in OpenStack Security Advisories: Fix Released Bug description: Received 2014-05-20 18:52:34 UTC via encrypted E-mail from "Craig Lorentzen (crlorent)" : Hello Jeremy, This is Craig Lorentzen from the Product Security Incident Response Team (PSIRT) at Cisco Systems. The purpose of this email is to disclose to you a vulnerability that was found during testing of a Cisco Product using OpenStack. Below please find the original discoverer's notes. Please let us know if there is anything else you need regarding this. Please also provide a tracking number for our records. - Headline: Persistent XSS in OpenStack Havana UI for Network Name Platforms:OpenStack Horizon Versions: Havana CVSS Score: 9.0 CVSS Vector: AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:U/RC:C CWE Tags: The Openstack Horizon user interface is vulnerable to XSS. The Network Name parameter is not properly sanitized to prevent javascript injection, leading to persistent XSS. Steps to reproduce: 1) Create a new network. Use: alert(1); for the network name. Disable both Subnet -> Create Subnet and Subnet Detail -> Enable DHCP. Choose Create. 2) Select Instances -> Launch Instance. Receive alert. Recommendations: - Sanitize the rendering of "Network Name" string to prevent XSS. - Consider utilizing Content Security Policy (CSP). This can be used to prevent inline javascript from executing & only load Javascript files from approved domains. This would prevent XSS, even in scenarios where user input is not properly sanitized. - Thank You, Craig Lorentzen Incident Manager Cisco Product Security Incident Response Team Security Research and Operations Office: 919.574.5680 Email: crlor...@cisco.com SIO: http://www.cisco.com/security PGP: 0x30A6C8ED To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1322197/+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 1320235] Re: [OSSA 2014-023] Stored XSS for /admin/users/ (CVE-2014-3475)
** Changed in: ossa Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1320235 Title: [OSSA 2014-023] Stored XSS for /admin/users/ (CVE-2014-3475) Status in OpenStack Dashboard (Horizon): Fix Committed Status in OpenStack Security Advisories: Fix Released Bug description: The /admin/users/ page does not output encode users' email addresses correctly. Since there is no user input validation for the users' email address during creation process. It is possible to inject script tag into the email address. This is a stored cross site scripting issue. The issue can be abused to hijack user's session and implant malware, etc. For example, attached is a screen copy of Horizon for users with stored XSS in action. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1320235/+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 1270725] Re: Quota Deadlock when creating >200 servers at once under Psql
** Changed in: oslo Status: Fix Committed => 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/1270725 Title: Quota Deadlock when creating >200 servers at once under Psql Status in OpenStack Compute (Nova): In Progress Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: When you create >200 servers at once under psql, it's easier to meet a deadlock exception in quota process(reserve/commit). Like this: http://paste.openstack.org/show/61534/ The '@retry_on_dead_lock' function, is not available for matching psql. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1270725/+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 1252693] Re: Running of unit tests fails if SQLAlchemy >= 0.8.3 is used
** Changed in: oslo Status: Fix Committed => 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/1252693 Title: Running of unit tests fails if SQLAlchemy >= 0.8.3 is used Status in OpenStack Compute (Nova): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: If SQLAlchemy >= 0.8.3 is used, running of unit tests fails. The following error is printed to stderr multiple times: DBError: (IntegrityError) constraint failed u'UPDATE instance_system_metadata SET updated_at=?, deleted_at=?, deleted=? WHERE instance_system_metadata.id = ?' ('2013- 11-19 10:37:44.378444', '2013-11-19 10:37:44.377819', 11, 11) A few of our migrations change the type of deleted column from boolean to int. MySQL and SQLite don't have native boolean data type. SQLAlchemy uses int columns (e.g. in case of MySQL - tinyint) + CHECK constraint (something like CHECK (deleted in (0, 1))) to emulate boolean data type. In our migrations when the type of column `deleted` is changed from boolean to int, the corresponding CHECK constraint is dropped too. But starting from SQLAlchemy version 0.8.3, those CHECK constraints aren't dropped anymore. So despite the fact that column deleted is of type int now, we still restrict its values to be either 0 or 1. Migrations changing the data type of deleted columns rely on SQL rendered for CHECK constraints (e.g. https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/migrate_repo/versions/152_change_type_of_deleted_column.py#L172). There was a patch in SQLAlchemy 0.8.3 release that slightly changed the way DDL statements are rendered ((http://docs.sqlalchemy.org/en/latest/changelog/changelog_08.html #change-487183f04e6da9aa27d8817bca9906d1)). Unfortunately, due to the fact that nova migrations depend on such implementation details, this change to SQLAlchemy broke our code. We must fix our migrations to work properly with new SQLAlchemy versions too (0.8.3+). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1252693/+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 1339735] [NEW] Deadlock updating image properties in glance-registry daemon
Public bug reported: Glance Registry is now regularly deadlocking when trying to update image properties. This causes gate failures. Example Log: http://logs.openstack.org/33/100933/3/gate/gate-tempest- dsvm-full/e21d71a/logs/screen-g-reg.txt.gz#_2014-07-09_00_27_38_261 Logstash query: message:'Deadlock found when trying to get lock; try restarting transaction' AND tags:screen-g-reg.txt ** Affects: glance Importance: High 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/1339735 Title: Deadlock updating image properties in glance-registry daemon Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Glance Registry is now regularly deadlocking when trying to update image properties. This causes gate failures. Example Log: http://logs.openstack.org/33/100933/3/gate/gate-tempest- dsvm-full/e21d71a/logs/screen-g-reg.txt.gz#_2014-07-09_00_27_38_261 Logstash query: message:'Deadlock found when trying to get lock; try restarting transaction' AND tags:screen-g-reg.txt To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1339735/+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 1339739] [NEW] test_cidr_repr race fail with "AttributeError: 'PostgreSQLOpportunisticFixture' object has no attribute '_details'"
Public bug reported: message:"AttributeError: 'PostgreSQLOpportunisticFixture' object has no attribute '_details'" AND tags:console AND project:"openstack/nova" http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiQXR0cmlidXRlRXJyb3I6ICdQb3N0Z3JlU1FMT3Bwb3J0dW5pc3RpY0ZpeHR1cmUnIG9iamVjdCBoYXMgbm8gYXR0cmlidXRlICdfZGV0YWlscydcIiBBTkQgdGFnczpjb25zb2xlIEFORCBwcm9qZWN0Olwib3BlbnN0YWNrL25vdmFcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQwNDkxNjY0NDYxMywibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIifQ== ** Affects: nova Importance: Undecided Status: New ** Tags: db testing -- 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/1339739 Title: test_cidr_repr race fail with "AttributeError: 'PostgreSQLOpportunisticFixture' object has no attribute '_details'" Status in OpenStack Compute (Nova): New Bug description: message:"AttributeError: 'PostgreSQLOpportunisticFixture' object has no attribute '_details'" AND tags:console AND project:"openstack/nova" http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiQXR0cmlidXRlRXJyb3I6ICdQb3N0Z3JlU1FMT3Bwb3J0dW5pc3RpY0ZpeHR1cmUnIG9iamVjdCBoYXMgbm8gYXR0cmlidXRlICdfZGV0YWlscydcIiBBTkQgdGFnczpjb25zb2xlIEFORCBwcm9qZWN0Olwib3BlbnN0YWNrL25vdmFcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQwNDkxNjY0NDYxMywibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIifQ== To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1339739/+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 1339760] [NEW] Launch instance: volume device name should be optional
Public bug reported: >From comment 9 on Nova bug 1337821, the device name should be optional and can cause issues if we force the user to select one and they enter an incorrect value. We should make the field optional (and make sure we still create the instance correctly in these cases.) ** Affects: horizon Importance: Medium Status: New ** Tags: nova -- 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/1339760 Title: Launch instance: volume device name should be optional Status in OpenStack Dashboard (Horizon): New Bug description: From comment 9 on Nova bug 1337821, the device name should be optional and can cause issues if we force the user to select one and they enter an incorrect value. We should make the field optional (and make sure we still create the instance correctly in these cases.) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1339760/+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 1339775] [NEW] Some v2 exceptions raise unicodeError
Public bug reported: In v2, for some exceptions the exception is not converted to a string properly resulting in: 2014-07-09 15:36:38,714 INFO msg = _("Image exceeds the storage quota: %s") % e 2014-07-09 15:36:38,714 INFO File "glance/openstack/common/gettextutils.py", line 333, in __str__ 2014-07-09 15:36:38,714 INFO raise UnicodeError(msg) in some cases 'utils.exception_to_str' is used to cast the exception. We should do this in all cases for consistency/to avoid the stack trace ** 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/1339775 Title: Some v2 exceptions raise unicodeError Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: In v2, for some exceptions the exception is not converted to a string properly resulting in: 2014-07-09 15:36:38,714 INFO msg = _("Image exceeds the storage quota: %s") % e 2014-07-09 15:36:38,714 INFO File "glance/openstack/common/gettextutils.py", line 333, in __str__ 2014-07-09 15:36:38,714 INFO raise UnicodeError(msg) in some cases 'utils.exception_to_str' is used to cast the exception. We should do this in all cases for consistency/to avoid the stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1339775/+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 1339789] [NEW] Horizon should redirect to the last used window after using Setting or Change Password
Public bug reported: Description of problem: === Horizon should redirect to the last used window after using 'Setting' or 'Change Password' Version-Release number of selected component: = openstack-dashboard-2014.1-7.el7ost.noarch How reproducible: = 100% Steps to Reproduce: === Change settings or password Actual results: === Horizons doesn't redirect to the last used window Expected results: = After click 'Save' or 'Change' Horizon should redirect to the last used window ** Affects: horizon Importance: Undecided Status: New ** Tags: ux -- 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/1339789 Title: Horizon should redirect to the last used window after using Setting or Change Password Status in OpenStack Dashboard (Horizon): New Bug description: Description of problem: === Horizon should redirect to the last used window after using 'Setting' or 'Change Password' Version-Release number of selected component: = openstack-dashboard-2014.1-7.el7ost.noarch How reproducible: = 100% Steps to Reproduce: === Change settings or password Actual results: === Horizons doesn't redirect to the last used window Expected results: = After click 'Save' or 'Change' Horizon should redirect to the last used window To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1339789/+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 1333587] Re: VMware: ExtendVirtualDisk_Task fails due to locked file
** Also affects: openstack-vmwareapi-team 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/1333587 Title: VMware: ExtendVirtualDisk_Task fails due to locked file Status in OpenStack Compute (Nova): Fix Committed Status in The OpenStack VMwareAPI subTeam: New Bug description: Extending a disk during spawn races, which can result in failure. It is possible to hit this bug by launching a large number of instances of an image which isn't already cached, simultaneously. Some of them will race to extend the cached image, ultimately resulting in an error such as: 2014-06-17 10:49:26.006 9177 WARNING nova.virt.vmwareapi.driver [-] Task [ExtendVirtualDisk_Task] value = "task-12073" _type = "Task" } status: error Unable to access file [datastore1] 172.16.0.13_base/326153d2-1226-415a-a194-2ca47ac3c48b/326153d2-1226-415a-a194-2ca47ac3c48b.1.vmdk since it is locked To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1333587/+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 1031493] Re: Default Quotas still lists "Cores" when should be VCPUs
** Changed in: nova Status: In Progress => Opinion ** Changed in: nova Assignee: Srinivas Reddy (srinivasreddy-j) => (unassigned) -- 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/1031493 Title: Default Quotas still lists "Cores" when should be VCPUs Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Compute (Nova): Opinion Bug description: Default Quotas still lists "Cores" when should be VCPUs to match term in the rest of the UI. ENV: Devstack trunk (Folsom) / Horizon 6b3545ef7021f6ed437ff1889d79485a65380fc8 (Mon Jul 30 03:56:18 2012) http://x.x.x.x/syspanel/quotas/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1031493/+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 1018566] Re: vm_state and task_state changes contained no DB migration
As per Chris Behrens, marking this as invalid ** Changed in: nova Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1018566 Title: vm_state and task_state changes contained no DB migration Status in OpenStack Compute (Nova): Invalid Bug description: As an example, the old state of vm_state of "rebuilding" is now a vm_state of "active" and a task_state of "rebuilding". There's no DB migration to update the columns based on the change in Change ID: I3c5a97508a6dad7175fba12828bd3fa6ef1e50ee (https://review.openstack.org/#/c/8254/) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1018566/+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 1337472] Re: UnboundLocalError: local variable 'domain' referenced before assignment
This bug isn't invalid. The whole point of this test is that it uses old code. We start with an icehouse deployment and test that. Then we upgrade everything to master except for nova cpu and test that. So nova cpu is running old code and will always run old code in this test. One way to fix this bug would be to backport 5a98983e87e5020626db2e319f7b00ae547ae8e1 to icehouse. There may be other approaches that are simpler, but I am not familiar enough with nova to know. ** Changed in: nova Status: Invalid => Confirmed ** Changed in: grenade Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1337472 Title: UnboundLocalError: local variable 'domain' referenced before assignment Status in Grenade - OpenStack upgrade testing: Invalid Status in OpenStack Compute (Nova): Confirmed Bug description: This unbound local error happens when running the grenade test that does not upgrade nova-cpu. In this test grenade upgrades all services but n-cpu then runs some tempest tests. Could be a backward compat issue? In any case domain is an unbound local variable in _create_domain_and_network() and seems to lead to the failure of instance creation. Logs for the node that failed can be seen starting at http://logs.openstack.org/48/104448/5/check/check-grenade-dsvm- partial- ncpu/6b93538/logs/old/screen-n-cpu.txt.gz?level=TRACE#_2014-07-03_17_15_26_819 To manage notifications about this bug go to: https://bugs.launchpad.net/grenade/+bug/1337472/+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 1160749] Re: nova quota-update command is executed without checking if the quota exceed
Not sure how the client can solve this. ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1160749 Title: nova quota-update command is executed without checking if the quota exceed Status in OpenStack Compute (Nova): Fix Released Bug description: 1. Changed number of the cores from 100 to 15 with the following command: [root@firstbox11-1 ˜]# nova quota-update --cores 15 2bff6058d6454dc0859cc545c2dc6d4f [root@firstbox11-1 ˜]# nova quota-show 2bff6058d6454dc0859cc545c2dc6d4f +-++ | Property| Value | +-++ | cores | 15 | | floating_ips| 40 | | gigabytes | 1000 | | injected_file_content_bytes | 10240 | | injected_files | 5 | | instances | 100| | metadata_items | 128| | ram | 204800 | | volumes | 10 | +-++ 2. Perform a deploy using a flavor with 8 CPUs like this: tm_fl: Memory: 2048MB, VCPUS: 8, Root: 8GB, Ephemeral: 0Gb, FlavorID: 69, Swap: 0MB, RXTX Factor: 1.0, public, ExtraSpecs {} the deploy fails with the following message: 'Quota exceeded for cores: Requested 8, but already used 47 of 15 cores' This is an issue, because 47 cores are already used, but the nova quota-update does not check and permits to decrease the cores value under 47.in alternative if it is possible have a number of cores already used greater than of the cores defined on quotait is an usability issue because minimum a warning should be issued when nova quota-update is issued. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1160749/+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 1304593] Re: VMware: waste of disk datastore when root disk size of instance is 0
** Also affects: openstack-vmwareapi-team 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/1304593 Title: VMware: waste of disk datastore when root disk size of instance is 0 Status in OpenStack Compute (Nova): In Progress Status in The OpenStack VMwareAPI subTeam: New Bug description: When an instance has 0 root disk size an extra image is created on the datastore (uuid.0.vmdk that is identical to uuid.vmdk). This is only in the case of a linked clone image and wastes space on the datastore. The original image that is cached can be used. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1304593/+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 1291617] Re: guest vm hostname is not set to the instance name
The hostname is usually set by the config_drive. You have to set "force_config_drive = always" in /etc/nova/nova.conf. I have tried this with the latest devstack and using the ubuntu cloud image. ** Changed in: nova Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1291617 Title: guest vm hostname is not set to the instance name Status in OpenStack Compute (Nova): Invalid Bug description: Create a new VM with a name like "testvm1" with the default cirros image Wait for it to be acitve and SSH able. ssh to the guest VM just created. check the hostname - it is "cirros" instead of the expected hostname "testvm1" To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1291617/+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 1339823] [NEW] Nova compute process crash doesn't reset task state 'migrating'
Public bug reported: When a live migration (task state = migrating) task is running, and the compute service goes down, the instance remains in migrating state when the compute service restarts. The compute/manager.py _init_instance method seems to handle all states except migrating. It handles inactive migration (resize_migrating), but not live migration. ** 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/1339823 Title: Nova compute process crash doesn't reset task state 'migrating' Status in OpenStack Compute (Nova): New Bug description: When a live migration (task state = migrating) task is running, and the compute service goes down, the instance remains in migrating state when the compute service restarts. The compute/manager.py _init_instance method seems to handle all states except migrating. It handles inactive migration (resize_migrating), but not live migration. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1339823/+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 1338745] Re: Add healthcheck middleware
** Changed in: keystone Status: In Progress => 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/1338745 Title: Add healthcheck middleware Status in OpenStack Identity (Keystone): Invalid Bug description: Would be useful for keystone to support a healthcheck URL for consumption by load balancers. This middleware should provide the ability to manually disable the service via the existence of a file on the system's local disk. This middleware should also perform a basic application functionality [1] check prior to reporting OK. Having this middleware would give us some flexibility around LB health checks we do not have today, and IMO would be beneficial. This is fairly similar to what swift [2] is doing as well. [1] https://github.com/CiscoSystems/puppet-monit/blob/a459a7314ac4f0250ad8b9c6956a872b949840f1/files/healthcheck.py#L37 [2] https://github.com/openstack/swift/blob/0b594bc3afbffe942edebe9cdf02f60c06e627ab/swift/common/middleware/healthcheck.py To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1338745/+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 977738] Re: iptables-save command executed by "nova-manage network create" command with QuantumManager
I do not believe this is an issue anymore. Please re-open if it is. ** Changed in: nova Status: Triaged => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/977738 Title: iptables-save command executed by "nova-manage network create" command with QuantumManager Status in OpenStack Compute (Nova): Invalid Bug description: Scenario : when "nova-manage network create" is executed, it internally executes "iptables-save" Here is a stack trace obtained by putting a breakpoint in nova/network/linux_net.py : apply() method /usr/local/bin/nova-manage(7)() -> execfile(__file__) /opt/stack/nova/bin/nova-manage(1746)() -> main() /opt/stack/nova/bin/nova-manage(1733)main() -> fn(*fn_args, **fn_kwargs) /opt/stack/nova/bin/nova-manage(812)create() -> fixed_cidr=fixed_cidr) /opt/stack/nova/nova/network/quantum/manager.py(223)create_networks() -> self.l3driver.initialize_network(cidr) /opt/stack/nova/nova/network/l3.py(93)initialize_network() -> linux_net.add_snat_rule(cidr) /opt/stack/nova/nova/network/linux_net.py(434)add_snat_rule() -> iptables_manager.apply() /opt/stack/nova/nova/utils.py(945)inner() -> retval = f(*args, **kwargs) > /opt/stack/nova/nova/network/linux_net.py(327)apply() -> current_table, _err = self.execute('%s-save' % (cmd,), Expected Behavior : nova-manage should only touch database, because nova-manage is not always executed on nova-network node. So nova-manage should NOT execute iptables-save command To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/977738/+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 1338841] Re: EC2KeysTest fails in tearDownClass with InvalidKeyPair.Duplicate
Multiple trove workers also merged on 7/8: https://review.openstack.org/#/c/103239/ And glance api/registry workers to use number of CPUs by default merged on 7/3: https://review.openstack.org/102665 So maybe the cinder api workers change just tipped it over. ** Also affects: cinder Importance: Undecided Status: New ** Summary changed: - EC2KeysTest fails in tearDownClass with InvalidKeyPair.Duplicate + asynchronous connection failed in postgresql jobs -- 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/1338841 Title: asynchronous connection failed in postgresql jobs Status in Cinder: New Status in OpenStack Compute (Nova): New Bug description: The trace for the failure is here: http://logs.openstack.org/57/105257/4/check/check-tempest-dsvm- postgres- full/f72b818/logs/tempest.txt.gz?level=TRACE#_2014-07-07_23_43_37_250 This is the console error: 2014-07-07 23:44:59.590 | tearDownClass (tempest.thirdparty.boto.test_ec2_keys.EC2KeysTest) 2014-07-07 23:44:59.590 | - 2014-07-07 23:44:59.590 | 2014-07-07 23:44:59.590 | Captured traceback: 2014-07-07 23:44:59.590 | ~~~ 2014-07-07 23:44:59.590 | Traceback (most recent call last): 2014-07-07 23:44:59.590 | File "tempest/thirdparty/boto/test.py", line 272, in tearDownClass 2014-07-07 23:44:59.590 | raise exceptions.TearDownException(num=fail_count) 2014-07-07 23:44:59.590 | TearDownException: 1 cleanUp operation failed There isn't much in the n-api logs, just the 400 response. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1338841/+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 1308727] Re: [OSSA 2014-023] XSS in Horizon Heat template - resource name (CVE-2014-3473)
** Also affects: horizon/havana Importance: Undecided Status: New ** Also affects: horizon/icehouse 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/1308727 Title: [OSSA 2014-023] XSS in Horizon Heat template - resource name (CVE-2014-3473) Status in OpenStack Dashboard (Horizon): Fix Committed Status in OpenStack Dashboard (Horizon) havana series: New Status in OpenStack Dashboard (Horizon) icehouse series: New Status in OpenStack Security Advisories: Fix Committed Bug description: The attached yaml will result in a Cross Site Script when viewing the resources or events of an Orchestration stack in the following paths: /project/stacks/stack/{stack_id}/?tab=stack_details__resources /project/stacks/stack/{stack_id}/?tab=stack_details__events The A tag's href attribute does not properly URL encode the name of the resource string resulting in escaping out of the attribute and arbitrary HTML written to the page. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1308727/+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 1163569] Re: security groups don't work with vip and ovs plugin
** Information type changed from Public to Public Security ** Also affects: ossa 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/1163569 Title: security groups don't work with vip and ovs plugin Status in OpenStack Neutron (virtual network service): Triaged Status in OpenStack Security Advisories: New Bug description: http://codepad.org/xU8G4s00 I pinged nachi and he suggested to try using: interface_driver = quantum.agent.linux.interface.BridgeInterfaceDriver But after setting this it seems like the vip does not work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1163569/+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 1339849] [NEW] Cleanup dict.update(single elem dict)
Public bug reported: There's several places in the code where this type of thing exists: form_data.update({'vpnservice_id': vpnservice.id}) better would be this: form_data['vpnservice_id'] = vpnservice.id This type of thing bothers me, so I'm going to clean it up. ** Affects: horizon Importance: Undecided Assignee: Matthew D. Wood (woodm1979) Status: New ** Changed in: horizon Assignee: (unassigned) => Matthew D. Wood (woodm1979) -- 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/1339849 Title: Cleanup dict.update(single elem dict) Status in OpenStack Dashboard (Horizon): New Bug description: There's several places in the code where this type of thing exists: form_data.update({'vpnservice_id': vpnservice.id}) better would be this: form_data['vpnservice_id'] = vpnservice.id This type of thing bothers me, so I'm going to clean it up. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1339849/+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 1338841] Re: asynchronous connection failed in postgresql jobs
https://review.openstack.org/#/c/105854/ ** Also affects: devstack Importance: Undecided Status: New ** Changed in: cinder Status: New => Invalid ** Changed in: devstack Status: New => In Progress ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1338841 Title: asynchronous connection failed in postgresql jobs Status in Cinder: Invalid Status in devstack - openstack dev environments: In Progress Status in OpenStack Compute (Nova): Invalid Bug description: The trace for the failure is here: http://logs.openstack.org/57/105257/4/check/check-tempest-dsvm- postgres- full/f72b818/logs/tempest.txt.gz?level=TRACE#_2014-07-07_23_43_37_250 This is the console error: 2014-07-07 23:44:59.590 | tearDownClass (tempest.thirdparty.boto.test_ec2_keys.EC2KeysTest) 2014-07-07 23:44:59.590 | - 2014-07-07 23:44:59.590 | 2014-07-07 23:44:59.590 | Captured traceback: 2014-07-07 23:44:59.590 | ~~~ 2014-07-07 23:44:59.590 | Traceback (most recent call last): 2014-07-07 23:44:59.590 | File "tempest/thirdparty/boto/test.py", line 272, in tearDownClass 2014-07-07 23:44:59.590 | raise exceptions.TearDownException(num=fail_count) 2014-07-07 23:44:59.590 | TearDownException: 1 cleanUp operation failed There isn't much in the n-api logs, just the 400 response. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1338841/+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 1339855] [NEW] Raise NotImplementedError instead of NotImplemented
Public bug reported: NotImplementedError is the name of the exception (https://docs.python.org/2/library/exceptions.html). NotImplemented is the name of a constant (https://docs.python.org/2/library/constants.html). It makes no sense to raise a constant. The exception should be raised instead. ** Affects: fuel Importance: Undecided Status: New ** Affects: neutron Importance: Undecided Assignee: Christian Berendt (berendt) Status: In Progress ** Affects: warm 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/1339855 Title: Raise NotImplementedError instead of NotImplemented Status in Fuel: OpenStack installer that works: New Status in OpenStack Neutron (virtual network service): In Progress Status in Warm: New Bug description: NotImplementedError is the name of the exception (https://docs.python.org/2/library/exceptions.html). NotImplemented is the name of a constant (https://docs.python.org/2/library/constants.html). It makes no sense to raise a constant. The exception should be raised instead. To manage notifications about this bug go to: https://bugs.launchpad.net/fuel/+bug/1339855/+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 1339855] Re: Raise NotImplementedError instead of NotImplemented
** Also affects: warm 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/1339855 Title: Raise NotImplementedError instead of NotImplemented Status in Fuel: OpenStack installer that works: New Status in OpenStack Neutron (virtual network service): In Progress Status in Warm: New Bug description: NotImplementedError is the name of the exception (https://docs.python.org/2/library/exceptions.html). NotImplemented is the name of a constant (https://docs.python.org/2/library/constants.html). It makes no sense to raise a constant. The exception should be raised instead. To manage notifications about this bug go to: https://bugs.launchpad.net/fuel/+bug/1339855/+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 1339855] Re: Raise NotImplementedError instead of NotImplemented
** Also affects: fuel 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/1339855 Title: Raise NotImplementedError instead of NotImplemented Status in CloudCafe: New Status in Fuel: OpenStack installer that works: In Progress Status in OpenStack Neutron (virtual network service): In Progress Status in Warm: New Bug description: NotImplementedError is the name of the exception (https://docs.python.org/2/library/exceptions.html). NotImplemented is the name of a constant (https://docs.python.org/2/library/constants.html). It makes no sense to raise a constant. The exception should be raised instead. To manage notifications about this bug go to: https://bugs.launchpad.net/cloudcafe/+bug/1339855/+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 1339855] Re: Raise NotImplementedError instead of NotImplemented
** Also affects: cloudcafe 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/1339855 Title: Raise NotImplementedError instead of NotImplemented Status in CloudCafe: New Status in Fuel: OpenStack installer that works: In Progress Status in OpenStack Neutron (virtual network service): In Progress Status in Warm: New Bug description: NotImplementedError is the name of the exception (https://docs.python.org/2/library/exceptions.html). NotImplemented is the name of a constant (https://docs.python.org/2/library/constants.html). It makes no sense to raise a constant. The exception should be raised instead. To manage notifications about this bug go to: https://bugs.launchpad.net/cloudcafe/+bug/1339855/+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 1339882] [NEW] OperationalError 'Unknown error occurred' during tempest EC2 tests
Public bug reported: e.g. http://logs.openstack.org/71/105671/1/gate/gate-tempest-dsvm- postgres-full/e38bc0c/console.html 2014-07-09 18:53:15.055 | tempest.thirdparty.boto.test_ec2_volumes.EC2VolumesTest.test_create_volume_from_snapshot 2014-07-09 18:53:15.055 | 2014-07-09 18:53:15.056 | 2014-07-09 18:53:15.056 | Captured traceback: 2014-07-09 18:53:15.056 | ~~~ 2014-07-09 18:53:15.056 | Traceback (most recent call last): 2014-07-09 18:53:15.056 | File "tempest/thirdparty/boto/test_ec2_volumes.py", line 56, in test_create_volume_from_snapshot 2014-07-09 18:53:15.056 | volume = self.client.create_volume(1, self.zone) 2014-07-09 18:53:15.056 | File "tempest/services/botoclients.py", line 82, in func 2014-07-09 18:53:15.056 | return getattr(conn, name)(*args, **kwargs) 2014-07-09 18:53:15.056 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/boto/ec2/connection.py", line 2288, in create_volume 2014-07-09 18:53:15.056 | return self.get_object('CreateVolume', params, Volume, verb='POST') 2014-07-09 18:53:15.056 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/boto/connection.py", line 1164, in get_object 2014-07-09 18:53:15.057 | response = self.make_request(action, params, path, verb) 2014-07-09 18:53:15.057 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/boto/connection.py", line 1090, in make_request 2014-07-09 18:53:15.057 | return self._mexe(http_request) 2014-07-09 18:53:15.057 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/boto/connection.py", line 1003, in _mexe 2014-07-09 18:53:15.057 | raise BotoServerError(response.status, response.reason, body) 2014-07-09 18:53:15.057 | BotoServerError: BotoServerError: 500 Internal Server Error 2014-07-09 18:53:15.057 | 2014-07-09 18:53:15.057 | OperationalErrorUnknown error occurred.req-6642eacb-3628-420a-bac8-82ab58332383 but it's not just a volumes test - also security groups and keypairs ** Affects: nova Importance: Undecided Status: New ** Tags: ec2 testing ** Tags added: ec2 testing -- 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/1339882 Title: OperationalError 'Unknown error occurred' during tempest EC2 tests Status in OpenStack Compute (Nova): New Bug description: e.g. http://logs.openstack.org/71/105671/1/gate/gate-tempest-dsvm- postgres-full/e38bc0c/console.html 2014-07-09 18:53:15.055 | tempest.thirdparty.boto.test_ec2_volumes.EC2VolumesTest.test_create_volume_from_snapshot 2014-07-09 18:53:15.055 | 2014-07-09 18:53:15.056 | 2014-07-09 18:53:15.056 | Captured traceback: 2014-07-09 18:53:15.056 | ~~~ 2014-07-09 18:53:15.056 | Traceback (most recent call last): 2014-07-09 18:53:15.056 | File "tempest/thirdparty/boto/test_ec2_volumes.py", line 56, in test_create_volume_from_snapshot 2014-07-09 18:53:15.056 | volume = self.client.create_volume(1, self.zone) 2014-07-09 18:53:15.056 | File "tempest/services/botoclients.py", line 82, in func 2014-07-09 18:53:15.056 | return getattr(conn, name)(*args, **kwargs) 2014-07-09 18:53:15.056 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/boto/ec2/connection.py", line 2288, in create_volume 2014-07-09 18:53:15.056 | return self.get_object('CreateVolume', params, Volume, verb='POST') 2014-07-09 18:53:15.056 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/boto/connection.py", line 1164, in get_object 2014-07-09 18:53:15.057 | response = self.make_request(action, params, path, verb) 2014-07-09 18:53:15.057 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/boto/connection.py", line 1090, in make_request 2014-07-09 18:53:15.057 | return self._mexe(http_request) 2014-07-09 18:53:15.057 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/boto/connection.py", line 1003, in _mexe 2014-07-09 18:53:15.057 | raise BotoServerError(response.status, response.reason, body) 2014-07-09 18:53:15.057 | BotoServerError: BotoServerError: 500 Internal Server Error 2014-07-09 18:53:15.057 | 2014-07-09 18:53:15.057 | OperationalErrorUnknown error occurred.req-6642eacb-3628-420a-bac8-82ab58332383 but it's not just a volumes test - also security groups and keypairs To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1339882/+subscriptions -- Mailing list: https:
[Yahoo-eng-team] [Bug 1339884] [NEW] Variable initialization missing in db_base_plugin_v2 class
Public bug reported: In the update_port method of class neutron/db/db_base_plugin_v2.py, the variable "changed_device_id" is not initialized, but it is getting tested in the if condition which causes python error. ** Affects: neutron Importance: Undecided Assignee: Karthik Natarajan (natarajk) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Karthik Natarajan (natarajk) ** Changed in: neutron Status: New => In Progress ** Description changed: - In the update_port method of neutron/db/db_base_plugin_v2.py, the + In the update_port method of class neutron/db/db_base_plugin_v2.py, the variable "changed_device_id" is not initialized, but it is getting tested in the if condition which causes python error. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1339884 Title: Variable initialization missing in db_base_plugin_v2 class Status in OpenStack Neutron (virtual network service): In Progress Bug description: In the update_port method of class neutron/db/db_base_plugin_v2.py, the variable "changed_device_id" is not initialized, but it is getting tested in the if condition which causes python error. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1339884/+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 1339885] [NEW] exceptions.check_message does not work
Public bug reported: When using exceptions.check_message to check it a connection was refused by an API, check_message will check to see if the exception's message contains "Connection" and "refused". When a connection is refused, the message does not contain exactly "Connection" and "refused", but rather "Connection" and "refused)". In this situation check_message does nothing and the exception is re-raised. To reproduce: Stop the Nova API Navigate to http:///admin/info/ Other notes: 1. Even if the error message contains "Connection" and "refused" exactly, the same error screen is shown, because the exception is re-raised in both situations, and is not being handled properly higher up. 2. The exception being raised when a connection is refused is ConnectionError, a Python built-in exception. 3. The only other situation where check_message is used is within Horizon is in https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/volumes/volumes/tables.py when a volume is deleted. When this occurs, the re-raised exception is properly handled, and a red error message is shown correctly. 4. The current use of check_message is not compatible with localization. The keywords checked for are not translated, so if the exception message is translated, the words will never match. ** 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/1339885 Title: exceptions.check_message does not work Status in OpenStack Dashboard (Horizon): New Bug description: When using exceptions.check_message to check it a connection was refused by an API, check_message will check to see if the exception's message contains "Connection" and "refused". When a connection is refused, the message does not contain exactly "Connection" and "refused", but rather "Connection" and "refused)". In this situation check_message does nothing and the exception is re-raised. To reproduce: Stop the Nova API Navigate to http:///admin/info/ Other notes: 1. Even if the error message contains "Connection" and "refused" exactly, the same error screen is shown, because the exception is re-raised in both situations, and is not being handled properly higher up. 2. The exception being raised when a connection is refused is ConnectionError, a Python built-in exception. 3. The only other situation where check_message is used is within Horizon is in https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/volumes/volumes/tables.py when a volume is deleted. When this occurs, the re-raised exception is properly handled, and a red error message is shown correctly. 4. The current use of check_message is not compatible with localization. The keywords checked for are not translated, so if the exception message is translated, the words will never match. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1339885/+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 1339879] Re: gate tests fail due to intermittent failures
This appears to be a failure in either glance or nova. If you have reason to believe this is an infrastructure bug please add additional info and I can reevaluate the status of the bug against infra. ** Changed in: openstack-ci Status: New => Incomplete ** Also affects: glance Importance: Undecided Status: New ** Also affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1339879 Title: gate tests fail due to intermittent failures Status in OpenStack Image Registry and Delivery Service (Glance): New Status in OpenStack Compute (Nova): New Status in OpenStack Core Infrastructure: Incomplete Bug description: Tests in the Glance gate seem to be failing due to the following error:- Details: The server has either erred or is incapable of performing the requested operation. 2014-07-09 16:38:38.863 | == 2014-07-09 16:38:38.863 | Failed 1 tests - output below: 2014-07-09 16:38:38.863 | == 2014-07-09 16:38:38.863 | 2014-07-09 16:38:38.863 | tempest.api.compute.images.test_images.ImagesTestXML.test_delete_saving_image[gate] 2014-07-09 16:38:38.864 | --- 2014-07-09 16:38:38.864 | 2014-07-09 16:38:38.864 | Captured traceback: 2014-07-09 16:38:38.864 | ~~~ 2014-07-09 16:38:38.864 | Traceback (most recent call last): 2014-07-09 16:38:38.864 | File "tempest/api/compute/images/test_images.py", line 42, in test_delete_saving_image 2014-07-09 16:38:38.864 | resp, body = self.client.delete_image(image['id']) 2014-07-09 16:38:38.864 | File "tempest/services/compute/xml/images_client.py", line 136, in delete_image 2014-07-09 16:38:38.864 | return self.delete("images/%s" % str(image_id)) 2014-07-09 16:38:38.864 | File "tempest/common/rest_client.py", line 224, in delete 2014-07-09 16:38:38.864 | return self.request('DELETE', url, extra_headers, headers, body) 2014-07-09 16:38:38.865 | File "tempest/common/rest_client.py", line 430, in request 2014-07-09 16:38:38.865 | resp, resp_body) 2014-07-09 16:38:38.865 | File "tempest/common/rest_client.py", line 526, in _error_checker 2014-07-09 16:38:38.865 | raise exceptions.ServerFault(message) 2014-07-09 16:38:38.865 | ServerFault: Got server fault 2014-07-09 16:38:38.865 | Details: The server has either erred or is incapable of performing the requested operation. 2014-07-09 16:38:38.865 | ref. http://logs.openstack.org/51/105751/1/check/check-tempest-dsvm- full/5f646ca/console.html#_2014-07-09_16_38_38_863 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1339879/+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 1339888] [NEW] Fix whitespace for interfaces file with two interfaces and IPv6
Public bug reported: If you have more than one interface and IPv6 is enabled, then the interfaces file will be broken: the 'auto` line will be on the same line as the previous stanza's gateway: auto eth0 iface eth0 inet static address 192.168.0.2 netmask 255.255.255.0 gateway 192.168.0.1 auto eth1 iface eth1 inet static ... vs auto eth0 iface eth0 inet static address 192.168.0.2 netmask 255.255.255.0 gateway 192.168.0.1 auto eth1 iface eth1 inet static ... The solution is fix the Jinja whitespace control in the template. ** Affects: nova Importance: Undecided Assignee: Rick Harris (rconradharris) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Rick Harris (rconradharris) ** Changed in: nova Status: New => In Progress -- 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/1339888 Title: Fix whitespace for interfaces file with two interfaces and IPv6 Status in OpenStack Compute (Nova): In Progress Bug description: If you have more than one interface and IPv6 is enabled, then the interfaces file will be broken: the 'auto` line will be on the same line as the previous stanza's gateway: auto eth0 iface eth0 inet static address 192.168.0.2 netmask 255.255.255.0 gateway 192.168.0.1 auto eth1 iface eth1 inet static ... vs auto eth0 iface eth0 inet static address 192.168.0.2 netmask 255.255.255.0 gateway 192.168.0.1 auto eth1 iface eth1 inet static ... The solution is fix the Jinja whitespace control in the template. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1339888/+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 1339882] Re: OperationalError 'Unknown error occurred' during tempest EC2 tests
*** This bug is a duplicate of bug 1338841 *** https://bugs.launchpad.net/bugs/1338841 Looks like a dup of bug #1338841 ** This bug has been marked a duplicate of bug 1338841 asynchronous connection failed in postgresql jobs -- 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/1339882 Title: OperationalError 'Unknown error occurred' during tempest EC2 tests Status in OpenStack Compute (Nova): New Bug description: e.g. http://logs.openstack.org/71/105671/1/gate/gate-tempest-dsvm- postgres-full/e38bc0c/console.html 2014-07-09 18:53:15.055 | tempest.thirdparty.boto.test_ec2_volumes.EC2VolumesTest.test_create_volume_from_snapshot 2014-07-09 18:53:15.055 | 2014-07-09 18:53:15.056 | 2014-07-09 18:53:15.056 | Captured traceback: 2014-07-09 18:53:15.056 | ~~~ 2014-07-09 18:53:15.056 | Traceback (most recent call last): 2014-07-09 18:53:15.056 | File "tempest/thirdparty/boto/test_ec2_volumes.py", line 56, in test_create_volume_from_snapshot 2014-07-09 18:53:15.056 | volume = self.client.create_volume(1, self.zone) 2014-07-09 18:53:15.056 | File "tempest/services/botoclients.py", line 82, in func 2014-07-09 18:53:15.056 | return getattr(conn, name)(*args, **kwargs) 2014-07-09 18:53:15.056 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/boto/ec2/connection.py", line 2288, in create_volume 2014-07-09 18:53:15.056 | return self.get_object('CreateVolume', params, Volume, verb='POST') 2014-07-09 18:53:15.056 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/boto/connection.py", line 1164, in get_object 2014-07-09 18:53:15.057 | response = self.make_request(action, params, path, verb) 2014-07-09 18:53:15.057 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/boto/connection.py", line 1090, in make_request 2014-07-09 18:53:15.057 | return self._mexe(http_request) 2014-07-09 18:53:15.057 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/boto/connection.py", line 1003, in _mexe 2014-07-09 18:53:15.057 | raise BotoServerError(response.status, response.reason, body) 2014-07-09 18:53:15.057 | BotoServerError: BotoServerError: 500 Internal Server Error 2014-07-09 18:53:15.057 | 2014-07-09 18:53:15.057 | OperationalErrorUnknown error occurred.req-6642eacb-3628-420a-bac8-82ab58332383 but it's not just a volumes test - also security groups and keypairs To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1339882/+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 1339918] [NEW] Requirements should django should be with hyphen
Public bug reported: Currently requirements uses "_" for django_pyscss Actually, it should be "-" django-pyscss ** Affects: horizon Importance: Undecided Assignee: Edgar Magana (emagana) Status: New ** Changed in: horizon Assignee: (unassigned) => Edgar Magana (emagana) -- 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/1339918 Title: Requirements should django should be with hyphen Status in OpenStack Dashboard (Horizon): New Bug description: Currently requirements uses "_" for django_pyscss Actually, it should be "-" django-pyscss To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1339918/+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 1225191] Re: add qpid-python to requirements.txt
There was a discussion about this a while back and the consensus was to create a requirements.d directory to better reflect the nuances in requirements ** Changed in: nova Status: In Progress => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1225191 Title: add qpid-python to requirements.txt Status in Orchestration API (Heat): Fix Released Status in OpenStack Compute (Nova): Opinion Bug description: If one tries using qpid instead of rabbitmq with heat, when heat- engine starts up it will complain that the qpid.messaging library is missing. To fix this, qpid-python should be included in requirements.txt. 2013-09-13 20:47:51.624 7031 INFO heat.engine.environment [-] Registering AWS::CloudFormation::WaitCondition -> 2013-09-13 20:47:51.634 7031 ERROR heat.openstack.common.threadgroup [-] Failed to import qpid.messaging 2013-09-13 20:47:51.634 7031 TRACE heat.openstack.common.threadgroup Traceback (most recent call last): 2013-09-13 20:47:51.634 7031 TRACE heat.openstack.common.threadgroup File "/opt/stack/venvs/heat/local/lib/python2.7/site-pa ckages/heat/openstack/common/threadgroup.py", line 117, in wait 2013-09-13 20:47:51.634 7031 TRACE heat.openstack.common.threadgroup x.wait() 2013-09-13 20:47:51.634 7031 TRACE heat.openstack.common.threadgroup File "/opt/stack/venvs/heat/local/lib/python2.7/site-pa ckages/heat/openstack/common/threadgroup.py", line 49, in wait 2013-09-13 20:47:51.634 7031 TRACE heat.openstack.common.threadgroup return self.thread.wait() 2013-09-13 20:47:51.634 7031 TRACE heat.openstack.common.threadgroup File "/opt/stack/venvs/heat/local/lib/python2.7/site-pa ckages/eventlet/greenthread.py", line 168, in wait 2013-09-13 20:47:51.634 7031 TRACE heat.openstack.common.threadgroup return self._exit_event.wait() 2013-09-13 20:47:51.634 7031 TRACE heat.openstack.common.threadgroup File "/opt/stack/venvs/heat/local/lib/python2.7/site-pa ckages/eventlet/event.py", line 116, in wait 2013-09-13 20:47:51.634 7031 TRACE heat.openstack.common.threadgroup return hubs.get_hub().switch() 2013-09-13 20:47:51.634 7031 TRACE heat.openstack.common.threadgroup File "/opt/stack/venvs/heat/local/lib/python2.7/site-pa ckages/eventlet/hubs/hub.py", line 187, in switch To manage notifications about this bug go to: https://bugs.launchpad.net/heat/+bug/1225191/+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 1265561] Re: Log message printed for unhandled exception is not very helpful.
** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1265561 Title: Log message printed for unhandled exception is not very helpful. Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in OpenStack Compute (Nova): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: Currently, on an unhandled exception, the error message logged through sys.excepthook is not very helpful. Currently it prints only the exception_value. https://github.com/openstack/oslo-incubator/blob/master/openstack/common/log.py#L396 Fix: Make the log message print both the exception_type and exception_value of the unhandled exception. PS: Currently the traceback is printed only when the VERBOSE is ON. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1265561/+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 1266875] Re: First spawn of docker image starts with "sh" command instead of image CMD
docker isn't in the nova tree currently. ** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1266875 Title: First spawn of docker image starts with "sh" command instead of image CMD Status in OpenStack Compute (Nova): Invalid Bug description: Hello On spawning instance firstly after uploading image to registry, docker container runs with command "sh", instead of command, written in image. Next spawns work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1266875/+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 1187397] Re: nova-network allows all outgoing traffic
not in progress anymore, this is more of a feature request then a bug ** Changed in: nova Status: In Progress => Opinion ** Changed in: nova Assignee: Bernhard M. Wiedemann (ubuntubmw) => (unassigned) -- 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/1187397 Title: nova-network allows all outgoing traffic Status in OpenStack Compute (Nova): Opinion Bug description: Having a cloud running with nova-network by default allows all outgoing traffic. While you can restrict access to the internet, there is no easy way to restrict VM access to private cloud infrastructure IP addresses. For reference, this was tracked for essex-based SUSE Cloud 1.0 https://bugzilla.novell.com/show_bug.cgi?id=777488 filed on 2012-08-27 VMs route all their traffic through their host's IP in the nova_fixed network Since we have asymmetric routing, it is not enough to disable forwarding on the interface used for the admin network because replies come in through a different interface. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1187397/+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 1231848] Re: vmware driver: issues reducing code coverage
this isn't really a bug per se, but rather just a cleanup. Previous patch was abandoned. ** Changed in: nova Status: In Progress => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1231848 Title: vmware driver: issues reducing code coverage Status in OpenStack Compute (Nova): Opinion Bug description: There are few issues affecting the test coverage of vmware driver code. 1. Remove unnecessary event object in wait_for_task. It also causes the coverage tool to miss reporting statements hits after wait_for_task is invoked. 2. Remove the following unused private methods in vmops.py. None of them are utility functions that are referred elsewhere. _get_res_pool_ref get_console_output _delete To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1231848/+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 1172764] Re: quota usage includes instances that are in task_state=deleting and vm_state=active
as per discussion on the patch, marking as invalid ** Changed in: nova Status: In Progress => Invalid ** Changed in: nova Assignee: Aleksander Korzynski (a-korzynski) => (unassigned) -- 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/1172764 Title: quota usage includes instances that are in task_state=deleting and vm_state=active Status in OpenStack Compute (Nova): Invalid Bug description: Consider a scenario where a user issues a request to delete an instance but the instance doesn't disappear because of a problem with the infrastructure (e.g. a libvirt error). The instance then stays in vm_state=active and task_state=deleting. In that case, it is not the user's fault that the instance doesn't go away. However, the user is penalized for it, because that instance gets counted in the user's quota. The problem was confirmed to exist on the trunk version of Nova: 2013.2.a332.g18d9a8b. One way to reproduce this problem is to start an instance then shut down nova-compute and then try to delete the instance. Check the instance in the instances table in the data base. It will have vm_state=active and task_state=deleting. Then check the quota usage with "nova absolute-limits". The totalInstancesUsed variable will include that instance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1172764/+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 1146945] Re: Failed rescue request sets instance state to ERROR
As per comments on the patch, marking as invalid ** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1146945 Title: Failed rescue request sets instance state to ERROR Status in OpenStack Compute (Nova): Invalid Bug description: If a "rescue()" call on the virtualization driver for an instance throws an exception, the instance's state is set to ERROR. The example that uncovered this issue goes something like this: 1. Create an instance of a specific flavor 2. Delete the flavor 3. Call "nova rescue" on the aforementioned instance . While it is arguably reasonable for the request to fail in this case, it does not seem necessary to alter the state of the instance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1146945/+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 1240374] Re: some times availability-zone not take effect after it created
** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1240374 Title: some times availability-zone not take effect after it created Status in OpenStack Compute (Nova): Fix Released Bug description: 1. create a availability-zone: second_zone, add ns17 to the aggregate [root@ns11 nova]# nova availability-zone-list +--++ | Name | Status | +--++ | first_zone | available | | |- ns11.sce.cn.ibm.com || | | |- nova-compute| enabled :-) 2013-09-25T09:51:54.352341 | | second_zone | available | | |- ns17-osee.cn.ibm.com || | | |- nova-compute| enabled :-) 2013-09-25T09:51:58.283034 | +--++ 2. nova boot with the zone: [root@ns11 ˜]# nova boot --image d7c64f67-3de7-4aa0-88fb-1292ff520404 --flavor 1 --availability-zone second_zone:ns17-osee.cn.ibm.com test_zone17_2 3. [root@ns11 nova]# nova list +--+-+-+-+-++ | ID | Name| Status | Task State | Power State | Networks | +--+-+-+-+-++ | 6f3ec942-6c8e-46fa-ad7e-d2c900921f65 | test_zone17 | ACTIVE | None | Running | flat_net01=172.10.0.16 | | 7273973d-a9e1-4917-ad59-c54ece9b0765 | test_zone17_1 | ACTIVE | None | Running | flat_net01=172.10.0.18 | | 27f71b26-b775-4516-ba2a-13d9e91e96dd | test_zone17_2 | ACTIVE | None | Running | flat_net01=172.10.0.19 | | 6350a439-2dd3-4b14-b99e-219fad27111b | zhikun_testvm | ACTIVE | None | Running | flat_net01=172.10.0.13 | +--+-+-+-+-++ 4. but the zone of the vm is: nova [root@ns11 nova]# nova show 27f71b26-b775-4516-ba2a-13d9e91e96dd +--+--+ | Property | Value | +--+--+ | status | ACTIVE | | flat_net01 network | 172.10.0.19 | | updated | 2013-09-25T09:50:23Z | | OS-EXT-STS:task_state| None | | OS-EXT-SRV-ATTR:host | ns17-osee.cn.ibm.com | | key_name | None | | image| cirros_kvm (d7c64f67-3de7-4aa0-88fb-1292ff520404)| | accessIPv6 | | | progress | 0 | | OS-EXT-STS:power_state | 1 | | OS-EXT-AZ:availability_zone | nova | | config_drive | | +--+--+ [root@ns11 nova]# date Wed Sep 25 18:05:26 CST 2013 5. I did not configure default_zone in nova.conf 6. It is very strange that this problem could not always been recreated. usually it happens when we create a new AZ, and then use the AZ boot instance. Seems wait for some time, may be one night or sooner, the AZ will become to correct one. I'm confused. # Expected results The AZ should take effect any time if we did not set default AZ in nova.conf To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1240374/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launc
[Yahoo-eng-team] [Bug 1194739] Re: Keypairs does not take action-level policies into consideration
** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1194739 Title: Keypairs does not take action-level policies into consideration Status in OpenStack Compute (Nova): Fix Released Bug description: Right now the way the authorizer is used in the keypairs extension the ":create/delete/index/show" suffixes in policy.json don't work. Action should be passed while authorizing. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1194739/+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 1100366] Re: Fix the default for libvirt_cpu_model
marked invalid per discussions in the linked reviews above. ** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1100366 Title: Fix the default for libvirt_cpu_model Status in OpenStack Compute (Nova): Invalid Bug description: It could be possible to remove the need for manually selecting qemu vs kvm by using some introspection to determine which to use. It'd be possible to either completely remove this config variable or have a None value for it that tells nova to determine cpu model and features itself. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1100366/+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 1199875] Re: Make XML in API Samples Test Easier to Work With
marking invalid as per discussion on patch ** Changed in: nova Status: In Progress => Incomplete ** Changed in: nova Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1199875 Title: Make XML in API Samples Test Easier to Work With Status in OpenStack Compute (Nova): Won't Fix Bug description: Right now the XML pretty-printed in the API Sample tests has lines that are 1500 characters long. This makes them difficult to review and even harder to resolve conflicts against if (heaven forbid) you're holding a patch against it. Long term it would be nice to make these 'expected-value' declarations more extensible. In the mean time, just having one-attr per line would make it easier to review and make conflicts much easier to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1199875/+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 1168610] Re: nova-compute fails to start if is_power_on raises exception
since we are in the process of deprecating and removing nova baremetal and the patch is abandoned, closing this bug. ** Changed in: nova Status: In Progress => Won't Fix ** Changed in: nova Assignee: Tim Miller (tim-miller-0) => (unassigned) -- 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/1168610 Title: nova-compute fails to start if is_power_on raises exception Status in OpenStack Compute (Nova): Won't Fix Bug description: During startup of nova-compute, if virtual_power_driver is_power_on() raises an exception, it will prevent nova-compute from starting. This can happen when a compute instance exists in the database but the SSH credentials that vpd uses are wrong. I think a solution is for vpd to convert exception.PowerVMConnectionFailed into an error and log it. Here is a trace of this error: 2013-04-13 06:52:02,213.213 4164 TRACE nova File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/service.py", line 147, in run_server 2013-04-13 06:52:02,213.213 4164 TRACE nova server.start() 2013-04-13 06:52:02,213.213 4164 TRACE nova File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/service.py", line 429, in start 2013-04-13 06:52:02,213.213 4164 TRACE nova self.manager.init_host() 2013-04-13 06:52:02,213.213 4164 TRACE nova File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/compute/manager.py", line 630, in init_host 2013-04-13 06:52:02,213.213 4164 TRACE nova self._init_instance(context, instance) 2013-04-13 06:52:02,213.213 4164 TRACE nova File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/compute/manager.py", line 539, in _init_instance 2013-04-13 06:52:02,213.213 4164 TRACE nova drv_state = self._get_power_state(context, instance) 2013-04-13 06:52:02,213.213 4164 TRACE nova File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/compute/manager.py", line 649, in _get_power_state 2013-04-13 06:52:02,213.213 4164 TRACE nova return self.driver.get_info(instance)["state"] 2013-04-13 06:52:02,213.213 4164 TRACE nova File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/virt/baremetal/driver.py", line 363, in get_info 2013-04-13 06:52:02,213.213 4164 TRACE nova if pm.is_power_on(): 2013-04-13 06:52:02,213.213 4164 TRACE nova File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/virt/baremetal/virtual_power_driver.py", line 198, in is_power_on 2013-04-13 06:52:02,213.213 4164 TRACE nova if not self._check_for_node(): 2013-04-13 06:52:02,213.213 4164 TRACE nova File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/virt/baremetal/virtual_power_driver.py", line 147, in _check_for_node 2013-04-13 06:52:02,213.213 4164 TRACE nova full_node_list = self._get_full_node_list() 2013-04-13 06:52:02,213.213 4164 TRACE nova File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/virt/baremetal/virtual_power_driver.py", line 141, in _get_full_node_list 2013-04-13 06:52:02,213.213 4164 TRACE nova full_list = self._run_command(cmd) 2013-04-13 06:52:02,213.213 4164 TRACE nova File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/virt/baremetal/virtual_power_driver.py", line 225, in _run_command 2013-04-13 06:52:02,213.213 4164 TRACE nova self._set_connection() 2013-04-13 06:52:02,213.213 4164 TRACE nova File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/virt/baremetal/virtual_power_driver.py", line 136, in _set_connection 2013-04-13 06:52:02,213.213 4164 TRACE nova self._connection = connection.ssh_connect(self.connection_data) 2013-04-13 06:52:02,213.213 4164 TRACE nova File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/virt/powervm/common.py", line 62, in ssh_connect 2013-04-13 06:52:02,213.213 4164 TRACE nova raise exception.PowerVMConnectionFailed() 2013-04-13 06:52:02,213.213 4164 TRACE nova PowerVMConnectionFailed: Connection to PowerVM manager failed 2013-04-13 06:52:02,213.213 4164 TRACE nova 2013-04-13 06:52:02,648.648 4217 INFO nova.manager [-] Skipping periodic task _periodic_update_dns because its interval is negative 2013-04-13 06:52:02,705.705 4217 INFO nova.virt.driver [-] Loading compute driver 'baremetal.driver.BareMetalDriver' 2013-04-13 06:52:02,754.754 INFO nova.openstack.common.rpc.common [req-235af7f1-4c57-42b8-8cc7-cbdd1327f12a None None] Connected to AMQP server on 127.0.0.1:5672 2013-04-13 06:52:02,839.839 4217 AUDIT nova.service [-] Starting compute node (version 2013.2) 2013-04-13 06:52:03,176.176 ERROR nova.compute.manager [req-e06f7f34-a2df-44f2-b3f2-ac299d4087d6 None None] Instance bmtest found in the hypervisor, but not in the database To manage notifications about this bug go to: https://bugs.launchpa
[Yahoo-eng-team] [Bug 1160982] Re: List servers with a request body should return 400 Bad Request
closing bug as per discussion on patch ** Changed in: nova Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1160982 Title: List servers with a request body should return 400 Bad Request Status in OpenStack Compute (Nova): Won't Fix Bug description: A GET /servers/detail request containing a body does not return a BadRequest. Request: curl -i http://176.78.165.15:8774/v2/339822f0d748407fb69b678cc80c2496/servers/detail -X GET -H "X-Auth-Project-Id: demo" -H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: MIIKpAYJKoZIhZw==" -d "{}" Response: {"servers": []} Since nova would not use a request body in this case it should give a bad request. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1160982/+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 1216060] Re: Notifiers needed when starting the attaching/detaching of volumes
closing bug as per comments on patch ** Changed in: nova Status: In Progress => Invalid ** Changed in: nova Assignee: Jim Sayer (jim-sayer) => (unassigned) -- 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/1216060 Title: Notifiers needed when starting the attaching/detaching of volumes Status in OpenStack Compute (Nova): Invalid Bug description: Nova only provides a notification when the attach/detach of a volume has been completed. Need to add additional notifiers to provide when the attaching/detaching of a volume has been started. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1216060/+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 1222334] Re: Failed to GET & UPDATE A Cell
*** This bug is a duplicate of bug 1198796 *** https://bugs.launchpad.net/bugs/1198796 ** This bug has been marked a duplicate of bug 1198796 update cell error -- 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/1222334 Title: Failed to GET & UPDATE A Cell Status in OpenStack Compute (Nova): In Progress Bug description: I built my environment by DevStack on Sep 5th, 2013. I can List all cells as normal, but when I Get One cell, the problem will occur. Due to this issue, "Update cell" is also influenced, and the problem is also involved in the new V3-api. Plz see the detailed info here: http://paste.openstack.org/show/46150/ Thanks~ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1222334/+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 1244043] Re: Can't delete the flavor by name which name is used in other flavor as id
as per discussion on patch, closing this bug. ** Changed in: nova Status: In Progress => Won't Fix ** Changed in: nova Assignee: Tiago Rodrigues de Mello (timello) => (unassigned) -- 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/1244043 Title: Can't delete the flavor by name which name is used in other flavor as id Status in OpenStack Compute (Nova): Won't Fix Bug description: # DETAILS 1. create 2 flavors like below nova flavor-create duplicateName duplicateID 10 10 10 nova flavor-create duplicateID duplicateName 10 10 10 [root@ns11 nova]# nova flavor-list +-+-+++---+--++-+---+ | ID | Name| Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | +-+-+++---+--++-+---+ | 1 | m1.tiny | 512| 1 | 0 | | 1 | 1.0 | True | | 2 | m1.small| 2048 | 20 | 0 | | 1 | 1.0 | True | | 3 | m1.medium | 4096 | 40 | 0 | | 2 | 1.0 | True | | 4 | m1.large| 8192 | 80 | 0 | | 4 | 1.0 | True | | 5 | m1.xlarge | 16384 | 160| 0 | | 8 | 1.0 | True | | duplicateID | duplicateName | 10 | 10 | 0 | | 10 | 1.0 | True | | duplicateName | duplicateID | 10 | 10 | 0 | | 10 | 1.0 | True | 2. Delete the flavor which id is duplicateID nova flavor-delete duplicateID 3. Delete the flavor which name is duplicateID nova flavor-delete duplicateID # EXPECTED RESULTS The flavor which name is duplicateID can be delete successfully # Actual Result [root@ns11 nova]# nova flavor-delete duplicateID ERROR: NV-88FBE2E Flavor duplicateID could not be found. (HTTP 404) (Request-ID: req-08c7f398-e76a-48ac-b2a8-5e452dd97782) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1244043/+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 1258055] Re: Inappropriate exception for flavorRef
see discussion at https://review.openstack.org/#/c/60177/ ** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1258055 Title: Inappropriate exception for flavorRef Status in OpenStack Compute (Nova): Invalid Bug description: There is an Inappropriate exception for flavorRef in nova boot API try: flavor_id = self._flavor_id_from_req_data(body) except ValueError as error: msg = _("Invalid flavorRef provided.") raise exc.HTTPBadRequest(explanation=msg) I think it will be better for: try: flavor_id = self._flavor_id_from_req_data(body) except ValueError as error: raise exc.HTTPBadRequest(explanation=error.format_message()) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1258055/+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 1272815] Re: Remove unused code in cleanup method
this isn't really a bug, but rather a cleanup. Patch was abandoned. ** Changed in: nova Status: In Progress => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1272815 Title: Remove unused code in cleanup method Status in OpenStack Compute (Nova): Opinion Bug description: Remove unused code "retry = False" in cleanup method To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1272815/+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 1194497] Re: xrange incompatible with py3. range bad in py2.
patch abandoned. ** Changed in: nova Status: In Progress => Opinion ** Changed in: nova Assignee: Kevin Conway (kevinconway) => (unassigned) -- 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/1194497 Title: xrange incompatible with py3. range bad in py2. Status in OpenStack Compute (Nova): Opinion Bug description: The nova code has a mixed usage of `range` and `xrange`. The `xrange` usage is preferred on py2 environments because it makes use of a generator rather than attempting to construct an entire list in memory. In py3, however, the `xrange` built-in no longer exists because it has been renamed `range`. This could cause several problems. The use of `range` in py2 for any significant size input will have a noticeable impact on performance. The use of `xrange` in py3 will cause a `NameError`. This is a case where the most appropriate solution is to break from the HACKING.rst guidelines and shadow a built-in and make `range` and alias for `xrange` in py2 environments. This would allow us to normalize the usage of `range` vs `xrange` as well as ensure that all calls to `range` are using the version with the best performance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1194497/+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 1076521] Re: host-list should print state of service
** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1076521 Title: host-list should print state of service Status in OpenStack Compute (Nova): Invalid Bug description: Using "host-list" I can't see if a service is up and running or if it's offline. For example the compute service on fig is stopped. admin:~ # nova host-list ++---+ | host_name | service | ++---+ | fig| compute | | nova-scheduler | scheduler | | plum | compute | ++---+ Would be nice to have the same output as of nova-manage service list. There I can see the last contact of the service and the zone. Binary Host Zone Status State Updated_At nova-compute fig internal enabledXXX 2012-11-08 19:15:57 nova-scheduler nova-scheduler internal enabled:-) 2012-11-08 19:19:10 nova-compute plum internal enabled:-) 2012-11-08 19:19:07 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1076521/+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 1238910] Re: nova boot operation with servers greater then 63 characters don't get DHCP address
see discussion at https://review.openstack.org/#/c/51390/ ** Changed in: nova Status: In Progress => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1238910 Title: nova boot operation with servers greater then 63 characters don't get DHCP address Status in OpenStack Compute (Nova): Opinion Bug description: If a server with greater then 63 characters is attempted to be booted, the servers will boot but fail to obtain DHCP addresses with nova networking and neutron. dnsmsq is fully configured for the full server name, however, Linux has a 64 character hostname limit. [sdake@bigiron ~]$ getconf HOST_NAME_MAX 64 Recommend a nova exception if a server greater then 63 characters is created so the user is aware of the problem at the api level rather then wondering why their vm doesn't appear to work. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1238910/+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 1175483] Re: use socket.getfqdn() to replace gethostname() for param host
See discussion at https://review.openstack.org/#/c/28015/ ** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1175483 Title: use socket.getfqdn() to replace gethostname() for param host Status in OpenStack Compute (Nova): Invalid Bug description: We have a openstack cluster which run with nova-network in mulit-host mode and the version is Folsom. Yesterday, our server shutdown cause of power failure and boot after the power recovered. Then we find one compute node ymy-r1-9 didn't bring up the bridge br100 and /var/lib/nova/networks/br100.conf is blank. Then I reboot the nova-network and find the br100's ip has changed from 192.168.2.14 to 192.168.2.29. In ordinary,it should not be changed. We look up in the nova/db/sqlalchemy/api.py:network_get_associated_fixed_ips, it has a param named host, if it's not None, then the function will return all the fix_ip of the vm on that host. We have 8 vm running on that host, but actually it return None. After we look up the database,we find the hostname has changed: mysql> select * from services; +-+-++-++-+--+-+--+--+---+ | created_at | updated_at | deleted_at | deleted | id | host| binary | topic | report_count | disabled | availability_zone | +-+-++-++-+--+-+--+--+---+ | 2013-04-22 11:43:13 | 2013-04-29 09:14:59 | NULL | 0 | 1 | ymy-r1-9| nova-consoleauth | consoleauth |62059 |0 | nova | | 2013-04-22 11:43:15 | 2013-04-29 09:14:59 | NULL | 0 | 2 | ymy-r1-9| nova-scheduler | scheduler |62058 |0 | nova | | 2013-04-22 11:43:21 | 2013-04-29 09:14:59 | NULL | 0 | 3 | ymy-r1-9| nova-network | network |61926 |0 | nova | | 2013-04-22 11:43:26 | 2013-04-29 09:14:59 | NULL | 0 | 4 | ymy-r1-9| nova-cert| cert|62060 |0 | nova | | 2013-04-22 06:26:08 | 2013-05-02 07:11:14 | NULL | 0 | 5 | ymy-r1-7.production.com | nova-compute | compute |86015 | 0 | nova | | 2013-04-22 06:26:09 | 2013-05-02 07:11:12 | NULL | 0 | 6 | ymy-r1-7.production.com | nova-network | network |86009 | 0 | nova | | 2013-04-22 06:32:44 | 2013-05-02 07:11:18 | NULL | 0 | 7 | ymy-r1-8| nova-compute | compute |85855 |0 | nova | | 2013-04-22 06:32:46 | 2013-05-02 07:11:14 | NULL | 0 | 8 | ymy-r1-8| nova-network | network |85856 |0 | nova | | 2013-04-22 06:55:25 | 2013-04-29 09:14:59 | NULL | 0 | 9 | ymy-r1-9| nova-console | console |60956 |0 | nova | | 2013-04-23 07:07:42 | 2013-04-29 09:15:00 | NULL | 0 | 10 | ymy-r1-9| nova-compute | compute |52116 |0 | nova | | 2013-04-29 09:28:57 | 2013-05-02 07:11:12 | NULL | 0 | 11 | ymy-r1-9.production.com | nova-consoleauth | consoleauth |24905 | 0 | nova | | 2013-04-29 09:28:57 | 2013-05-02 07:11:14 | NULL | 0 | 12 | ymy-r1-9.production.com | nova-cert| cert|24906 | 0 | nova | | 2013-04-29 09:28:57 | 2013-05-02 07:11:13 | NULL | 0 | 13 | ymy-r1-9.production.com | nova-scheduler | scheduler |24907 | 0 | nova | | 2013-04-29 09:28:57 | 2013-05-02 07:11:12 | NULL | 0 | 14 | ymy-r1-9.production.com | nova-compute | compute |24886 | 0 | nova | | 2013-04-29 09:28:59 | 2013-05-02 07:11:13 | NULL | 0 | 15 | ymy-r1-9.production.com | nova-network | network |24863 | 0 | nova | +-+-++-++-+--+-+--+--+---+ The hostname has changed from ymy-r1-9 to ymy-r1-9.production.com. Now if we search the host by name 'ymy-r1-9': mysql> select * from instances where host='ymy-r1-9'; 37 rows in set (0.00 sec) But if we search the host by name 'ymy-r1-9.production.com': select * fro
[Yahoo-eng-team] [Bug 1262480] Re: All API controllers inherit from wsgi.Controller
as per https://review.openstack.org/#/c/63048/, closing ** Changed in: nova Status: In Progress => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1262480 Title: All API controllers inherit from wsgi.Controller Status in OpenStack Compute (Nova): Opinion Bug description: Most of the Nova Public API Controllers inherit from wsgi.Controller, but still some Nova Public APIs controllers directly inherit from object. So it's necessary to unify all the Nova Public API Controllers inherit from wsgi.Controller. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1262480/+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 1254769] Re: Wrong instance action events updated in re-scheduling case
as per comments on patch, closing bug ** Changed in: nova Status: In Progress => Opinion ** Changed in: nova Status: Opinion => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1254769 Title: Wrong instance action events updated in re-scheduling case Status in OpenStack Compute (Nova): Invalid Bug description: Event logs in "nova instance-action" is always updated based on request id and event name. However, for re-scheduling case (instance failed to spin up and rescheduled to another host), multiple event records with the same name could be generated under same request id. In such case, event details could not be trusted, because it is always the first event record got updated. nova instance-action 461e1aae-6eae-4172-b2fe-2984dab34a1f req-18c907ac-dbd7-4898-a6ed-e5dbb5c8da91 +---+--+ | Property | Value| +---+--+ | instance_uuid | 461e1aae-6eae-4172-b2fe-2984dab34a1f | | user_id | 30d8f5a8deaf446ba51131b751ab8b46 | | start_time| 2013-11-25T14:26:18.00 | | request_id| req-18c907ac-dbd7-4898-a6ed-e5dbb5c8da91 | | action| create | | message | None | | project_id| 5bd1b3ec18b84b8ea3403bdc662983fb | | events| [{u'event': u'schedule', | | | u'finish_time': None, | | | u'result': None, | | | u'start_time': u'2013-11-25T14:26:49.00', | | | u'traceback': None}, | | | {u'event': u'schedule', | | | u'finish_time': None, | | | u'result': None, | | | u'start_time': u'2013-11-25T14:26:46.00', | | | u'traceback': None}, | | | {u'event': u'compute_run_instance', | | | u'finish_time': None, | | | u'result': None, | | | u'start_time': u'2013-11-25T14:26:46.00', | | | u'traceback': None}, | | | {u'event': u'schedule', | | | u'finish_time': u'2013-11-25T14:26:49.00', | | | u'result': u'Success', | | | u'start_time': u'2013-11-25T14:26:19.00', | | | u'traceback': None}, | | | {u'event': u'compute_run_instance', | | | u'finish_time': u'2013-11-25T14:26:47.00', | | | u'result': u'Success', | | | u'start_time': u'2013-11-25T14:27:35.00', | | | u'traceback': None}] | +---+--+ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1254769/+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 1207250] Re: no paramter to specify cinder and glance request timeout
** Changed in: nova Status: In Progress => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1207250 Title: no paramter to specify cinder and glance request timeout Status in OpenStack Compute (Nova): Opinion Bug description: nova doesn't support cinder and glance request timeout To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1207250/+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 1242233] Re: nova resize revert will be failed when using lvm
see discussion at https://review.openstack.org/#/c/52807/ ** Changed in: nova Status: In Progress => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1242233 Title: nova resize revert will be failed when using lvm Status in OpenStack Compute (Nova): Opinion Bug description: With following configuration: libvirt_images_type=lvm libvirt_images_volume_group=stack-volumes allow_resize_to_same_host = True liugya@liugya-ubuntu:~$ nova flavor-list ++---+---+--+---+--+---+-+---+ | ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | ++---+---+--+---+--+---+-+---+ | 1 | m1.tiny | 512 | 1| 0 | | 1 | 1.0 | True | | 2 | m1.small | 2048 | 20 | 0 | | 1 | 1.0 | True | | 3 | m1.medium | 4096 | 40 | 0 | | 2 | 1.0 | True | | 4 | m1.large | 8192 | 80 | 0 | | 4 | 1.0 | True | | 42 | m1.nano | 64| 0| 0 | | 1 | 1.0 | True | | 5 | m1.xlarge | 16384 | 160 | 0 | | 8 | 1.0 | True | | 6 | m1.test | 256 | 1| 0 | | 2 | 1.0 | True | | 84 | m1.micro | 128 | 0| 0 | | 1 | 1.0 | True | ++---+---+--+---+--+---+-+---+ 1) Create a VM based on flavor 1 2) resize to flavor 6 3) resize revert the VM, compute report error 2013-10-20 10:19:15.677 DEBUG amqp [-] Channel open from (pid=21759) _open_ok /usr/local/lib/python2.7/dist-packages/amqp-1.0.12-py2.7.egg/amqp/channel.py:420 2013-10-20 10:19:15.678 ERROR nova.openstack.common.rpc.amqp [req-2bb3187b-6555-4c6c-826d-0917c91aba97 admin admin] Exception during message handling 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp Traceback (most recent call last): 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 461, in _process_data 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp **args) 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/openstack/common/rpc/dispatcher.py", line 172, in dispatch 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp result = getattr(proxyobj, method)(ctxt, **kwargs) 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 354, in decorated_function 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/exception.py", line 90, in wrapped 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp payload) 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/exception.py", line 73, in wrapped 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp return f(self, context, *args, **kw) 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 244, in decorated_function 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp pass 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 230, in decorated_function 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 295, in decorated_function 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp function(self, context, *args, **kwargs) 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 272, in decorated_function 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp e, sys.exc_info()) 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 259, in decorated_function 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 2827, in finish_revert_resize 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp block_device_info, power_on) 2013-10-20 10:19:15.678 TRACE nova.openstack.common.rpc.amqp Fil
[Yahoo-eng-team] [Bug 1339968] [NEW] duplicate dhcp port when deleting original dhcp port and restart dhcp-agent
Public bug reported: my use case is as follows: 1.delete dhcp port 2.restart dhcp-agent then, there will be two dhcp ports. ** 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/1339968 Title: duplicate dhcp port when deleting original dhcp port and restart dhcp- agent Status in OpenStack Neutron (virtual network service): New Bug description: my use case is as follows: 1.delete dhcp port 2.restart dhcp-agent then, there will be two dhcp ports. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1339968/+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 1339974] [NEW] return full version console log
Public bug reported: Currently , there is no way to get the entire console log via API. It would be great to have an offset parameter which users can specify where to read from the top of file and the API response should contain the current reading byte position. This will give users the ability to read the entire console log chunk by chunk. ** Affects: nova Importance: Undecided Status: New ** Description changed: Currently , there is no way to get the entire console log via API. - It would be great to have an offset parameter which users can specify - where to read from the top of file and the API response should contain - the current reading byte position. This will give uses the ability to read + It would be great to have an offset parameter which users can specify + where to read from the top of file and the API response should contain + the current reading byte position. This will give users the ability to read the entire console log chunk by chunk. -- 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/1339974 Title: return full version console log Status in OpenStack Compute (Nova): New Bug description: Currently , there is no way to get the entire console log via API. It would be great to have an offset parameter which users can specify where to read from the top of file and the API response should contain the current reading byte position. This will give users the ability to read the entire console log chunk by chunk. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1339974/+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 1265731] Re: Need change instance's property updated_at when swap volume
because the patch suggested is rejected and reviewers don't think it's a valid bug ** Changed in: nova Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1265731 Title: Need change instance's property updated_at when swap volume Status in OpenStack Compute (Nova): Invalid Bug description: https://bugs.launchpad.net/nova/+bug/1250066 updated the updated_at for attach/detach volume swap volume also should need same update because it also did the attach/detach and from user perspective, the content is changed To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1265731/+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 1340002] [NEW] Some exceptions raise unicodeError
Public bug reported: Thie bug is a generic case for bug 1339775 [0], there are a lot same cases in codebase which are outside of v2 stuff, but the result is smimilar, UnicodeError exception will be raised. [0] https://bugs.launchpad.net/glance/+bug/1339775 ** 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/1340002 Title: Some exceptions raise unicodeError Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Thie bug is a generic case for bug 1339775 [0], there are a lot same cases in codebase which are outside of v2 stuff, but the result is smimilar, UnicodeError exception will be raised. [0] https://bugs.launchpad.net/glance/+bug/1339775 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1340002/+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 1340040] [NEW] Can't able to delete pseudo folder under container
Public bug reported: Hi all, I can't able to delete pseudo folders created under Container. I installed openstack using packstack all-in-one in a CentOS machine. I can create multiple containers and upload objects in to it without a problem, but when I create a pseudo folder, I click on that dashboard goes to "something went wrong". I fix that temporarily using the fix here https://bugs.launchpad.net/horizon/+bug/131 Now I can create subfolders and upload objects in to that file, but I can't able to delete any of these pseudo folders. When I try to delete pseudo folder named (for eg test), I'm getting error Error: You are not allowed to delete object:test. When using cli, I get this [root@icestack ~(keystone_admin)]# swift list test test1/ [root@icestack ~(keystone_admin)]# [root@icestack ~(keystone_admin)]# [root@icestack ~(keystone_admin)]# swift delete test test1 Object 'test/test1' not found I think it is a known issue, any workaround for this problem. Thanks & Regards, Anand TS ** Affects: horizon Importance: Undecided Status: New ** Tags: dashboard horizon rdo swift -- 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/1340040 Title: Can't able to delete pseudo folder under container Status in OpenStack Dashboard (Horizon): New Bug description: Hi all, I can't able to delete pseudo folders created under Container. I installed openstack using packstack all-in-one in a CentOS machine. I can create multiple containers and upload objects in to it without a problem, but when I create a pseudo folder, I click on that dashboard goes to "something went wrong". I fix that temporarily using the fix here https://bugs.launchpad.net/horizon/+bug/131 Now I can create subfolders and upload objects in to that file, but I can't able to delete any of these pseudo folders. When I try to delete pseudo folder named (for eg test), I'm getting error Error: You are not allowed to delete object:test. When using cli, I get this [root@icestack ~(keystone_admin)]# swift list test test1/ [root@icestack ~(keystone_admin)]# [root@icestack ~(keystone_admin)]# [root@icestack ~(keystone_admin)]# swift delete test test1 Object 'test/test1' not found I think it is a known issue, any workaround for this problem. Thanks & Regards, Anand TS To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1340040/+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 1340041] [NEW] user-role-add not working with OpenLDAP - slapd 2.3.43
Public bug reported: My keystone server is hosted on RHEL 6.4 The keystone version from rpm -qa is openstack- keystone-2014.1-0.3.b2.el6.noarch I have defined following: - a user: authadmin (objectclass: Inetorgperson) - a tenant: authentication (objectclass: groupOfNames) - a role: admin (objectclass: organizationalRole) My keystone.conf snippet is: user_tree_dn = ou=Users,ou=OpenStack,dc=sonasldap,dc=com user_objectclass = inetOrgPerson user_id_attribute = uid user_name_attribute = uid tenant_tree_dn = ou=Customers,ou=OpenStack,dc=sonasldap,dc=com tenant_objectclass = groupOfNames tenant_id_attribute = cn tenant_name_attribute = cn role_tree_dn = ou=Roles,ou=OpenStack,dc=sonasldap,dc=com role_objectclass = organizationalRole role_id_attribute = cn role_name_attribute = cn While assigning 'admin' role to 'authadmin' user under tenant 'authentication' I get the following error keystone user-role-add --user authadmin --role admin --tenant authentication An unexpected error prevented the server from fulfilling your request. {'info': "naming attribute 'cn' is not present in entry", 'desc': 'Naming violation'} (HTTP 500) Looking at the network traffic I could see that ldapadd request is for the dn: cn=admin,ou=authentication,ou=openstack,dc=ldap,dc=com with 2 attributes: objectclass: organizationalRole roleOccupant: uid=authadmin,ou=users,ou=openstack,dc=ldap,dc=com And since the 'cn' is missing which is the mandatory attribute for organizationalRole objectclass, I am observing this failure. If I use a new OpenLDAP server, say slapd 2.4.23, this works fine. The LDAP server automatically adds the 'cn' attribute which is mentioned in the 'dn'. Active Directory is also behaving in the similar way Now I am unable to conclude if this is an OpenLDAP bug or a keystone bug. Why is keystone not adding the 'cn' attribute in the ldapadd request ? ** 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/1340041 Title: user-role-add not working with OpenLDAP - slapd 2.3.43 Status in OpenStack Identity (Keystone): New Bug description: My keystone server is hosted on RHEL 6.4 The keystone version from rpm -qa is openstack- keystone-2014.1-0.3.b2.el6.noarch I have defined following: - a user: authadmin (objectclass: Inetorgperson) - a tenant: authentication (objectclass: groupOfNames) - a role: admin (objectclass: organizationalRole) My keystone.conf snippet is: user_tree_dn = ou=Users,ou=OpenStack,dc=sonasldap,dc=com user_objectclass = inetOrgPerson user_id_attribute = uid user_name_attribute = uid tenant_tree_dn = ou=Customers,ou=OpenStack,dc=sonasldap,dc=com tenant_objectclass = groupOfNames tenant_id_attribute = cn tenant_name_attribute = cn role_tree_dn = ou=Roles,ou=OpenStack,dc=sonasldap,dc=com role_objectclass = organizationalRole role_id_attribute = cn role_name_attribute = cn While assigning 'admin' role to 'authadmin' user under tenant 'authentication' I get the following error keystone user-role-add --user authadmin --role admin --tenant authentication An unexpected error prevented the server from fulfilling your request. {'info': "naming attribute 'cn' is not present in entry", 'desc': 'Naming violation'} (HTTP 500) Looking at the network traffic I could see that ldapadd request is for the dn: cn=admin,ou=authentication,ou=openstack,dc=ldap,dc=com with 2 attributes: objectclass: organizationalRole roleOccupant: uid=authadmin,ou=users,ou=openstack,dc=ldap,dc=com And since the 'cn' is missing which is the mandatory attribute for organizationalRole objectclass, I am observing this failure. If I use a new OpenLDAP server, say slapd 2.4.23, this works fine. The LDAP server automatically adds the 'cn' attribute which is mentioned in the 'dn'. Active Directory is also behaving in the similar way Now I am unable to conclude if this is an OpenLDAP bug or a keystone bug. Why is keystone not adding the 'cn' attribute in the ldapadd request ? To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1340041/+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