[Yahoo-eng-team] [Bug 1197025] Re: Hyper-V: Captured image size is 0
** 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/1197025 Title: Hyper-V: Captured image size is 0 Status in OpenStack Compute (Nova): Invalid Bug description: If the original image A size is 123456, then deploy an instance B based on the image A. Next capture an image C based on the instance B. As a result, the size of image C will be 0. After investigation, I think the root cause is the meta data is never updated during snapshot. See this: https://github.com/openstack/nova/blob/master/nova/virt/hyperv/snapshotops.py#L45 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1197025/+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 1172922] Re: Nova and quantum don't close qpid connections after certain error conditions
Fix merged to nova (master): https://github.com/openstack/nova/commit/b4826d85c25a56ad95ffb76c467cdb459daba0c4 ** Changed in: nova Status: Triaged = Fix Committed ** Changed in: nova Assignee: (unassigned) = Michael Still (mikalstill) ** Changed in: nova Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1172922 Title: Nova and quantum don't close qpid connections after certain error conditions Status in OpenStack Neutron (virtual network service): Fix Released Status in neutron grizzly series: Fix Released Status in OpenStack Compute (Nova): Fix Released Status in OpenStack Compute (nova) grizzly series: In Progress Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: In conditions where nova gets a connection to qpid but there is a problem at the application layer (such as a bad qpid password is specified), nova will continuously retry the connection without closing previous connections. Steps to reproduce: - Preconditions: At least 1 nova compute node using qpid for messaging, with authentication turned on. - Specify a wrong qpid password in nova.conf on the compute node - nova will continuously retry with the wrong password and print errors such as this to the compute log: 2013-04-25 16:37:52.269 ERROR nova.openstack.common.rpc.impl_qpid [req-1d15f33c-5b2d-4ee1-aaa1-ab0140a56608 None None] Unable to connect to AMQP server: connection-forced: Authentication failed(320). Sleeping 60 seconds - Each time nova retries the connection, it will create another connection to qpid and not close the previous connections. I think this exception case needs to be updated in https://github.com/openstack/nova/blob/master/nova/openstack/common/rpc/impl_qpid.py to close the connection: except qpid_exceptions.ConnectionError, e: msg_dict = dict(e=e, delay=delay) msg = _(Unable to connect to AMQP server: %(e)s. Sleeping %(delay)s seconds) % msg_dict LOG.error(msg) time.sleep(delay) delay = min(2 * delay, 60) Note that quantum uses the same code for qpid. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1172922/+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 1195357] Re: Unused variable uri
** Changed in: glance Status: In Progress = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1195357 Title: Unused variable uri Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: https://github.com/openstack/glance/blob/master/glance/store/swift.py#L278 the variable uri is defined but never used. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1195357/+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 1047695] Re: Fragile Test: glance.tests.functional.v1.test_api:TestApi.test_zero_initial_size
I have not seen this fail since some of the recent test enhancements
have been made.
** Changed in: glance
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1047695
Title:
Fragile Test:
glance.tests.functional.v1.test_api:TestApi.test_zero_initial_size
Status in OpenStack Image Registry and Delivery Service (Glance):
Invalid
Bug description:
As seen in http://logs.openstack.org/12465/4/check/gate-glance-
python27/1801/console.html:
20:56:15
==
20:56:15 FAIL: A test to ensure that an image with size explicitly set to
zero
20:56:15
--
20:56:15 Traceback (most recent call last):
20:56:15File
/home/jenkins/workspace/gate-glance-python27/glance/tests/utils.py, line 178,
in wrapped
20:56:15 func(*a, **kwargs)
20:56:15File
/home/jenkins/workspace/gate-glance-python27/glance/tests/functional/v1/test_api.py,
line 493, in test_zero_initial_size
20:56:15 self.assertEqual(response.status, 201)
20:56:15 AssertionError: 404 != 201
20:56:15 '404 != 201' = '%s != %s' % (safe_repr(404), safe_repr(201))
20:56:15 '404 != 201' = self._formatMessage('404 != 201', '404 != 201')
20:56:15raise self.failureException('404 != 201')
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1047695/+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 1108985] Re: Spurious ECONNREFUSED errors during Glance unit tests
I have not seen this problem since the test suite re-factors. I believe it is no longer valid. ** Changed in: glance Status: Confirmed = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1108985 Title: Spurious ECONNREFUSED errors during Glance unit tests Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Got weird errors in unit testing: ERROR: glance.tests.functional.v2.test_images.TestImageDirectURLVisibility.test_image_direct_url_visible requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection (1): 127.0.0.1 ConnectionError: [Errno 111] ECONNREFUSED (See https://jenkins.openstack.org/job/gate-glance-python26/2868/consoleFull) and ERROR: glance.tests.functional.v1.test_api.TestApi.test_mismatched_size error: [Errno 111] ECONNREFUSED (https://jenkins.openstack.org/job/gate-glance-python27/2881/consoleFull) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1108985/+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 1199442] Re: Allow forcing of requested networks
Not a lot of traction for this going in trunk: https://review.openstack.org/#/c/36293/ Leaving this out is probably the best course at this point. ** 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/1199442 Title: Allow forcing of requested networks Status in OpenStack Compute (Nova): Invalid Bug description: The blueprint disable-servers-extensions tied the handling of networks POST data to whether the `os-networks` extension was enabled. This is a sensible default. Providers however may want to run their own separate network extension. In order to do this, we need a way to 'force' the handling of requested-networks regardless of whether the `os-networks` extension is enabled. Adding a `enable_requested_networks` config with a default=False should do the trick. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1199442/+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 1199309] Re: Ambiguous exception class for validate_ec2_id
Duplicated bug of https://bugs.launchpad.net/nova/+bug/1199308 was created. Marked invalid as I couldn't see a duplicate option. ** Changed in: nova Assignee: Aswad Rangnekar (aswad-r) = (unassigned) ** 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/1199309 Title: Ambiguous exception class for validate_ec2_id Status in OpenStack Compute (Nova): Invalid Bug description: The validate_ec2_id() method is used to validate both the Instance ID as well as Volume ID for valid EC2 ID format. However the exception class raised in both cases, if the respective ID were invalid is InvalidInstanceIDMalformed. This is ambiguous and needs to be fixed such that a clearer exception is seen in the stack trace. The exception class InvalidInstanceIDMalformed in exception.py could be changed to something like InvalidEC2IDMalformed. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1199309/+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
