[Yahoo-eng-team] [Bug 1300607] [NEW] BigSwitch: async port create susceptible to deadlock
Public bug reported: In the async port creation function used by the Big Switch plugin and ML2 driver, the calls to _set_port_status are susceptible to the well- known eventlet/mysql deadlock. ** Affects: neutron Importance: Undecided Assignee: Kevin Benton (kevinbenton) Status: In Progress ** Tags: bigswitch ** Changed in: neutron Assignee: (unassigned) => Kevin Benton (kevinbenton) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1300607 Title: BigSwitch: async port create susceptible to deadlock Status in OpenStack Neutron (virtual network service): In Progress Bug description: In the async port creation function used by the Big Switch plugin and ML2 driver, the calls to _set_port_status are susceptible to the well- known eventlet/mysql deadlock. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1300607/+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 1300593] [NEW] db migration: portbindingport table missing for ml2
Public bug reported: The ML2 plugin is missing in the migration script to create the portbindingports table. This causes errors on drivers that reference port binding information. http://openstack-ci-gw.bigswitch.com/logs/refs- changes-13-84313-3/BSN_ML2/logs/screen/screen-q-svc.log.gz ** Affects: neutron Importance: Undecided Assignee: Kevin Benton (kevinbenton) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Kevin Benton (kevinbenton) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1300593 Title: db migration: portbindingport table missing for ml2 Status in OpenStack Neutron (virtual network service): In Progress Bug description: The ML2 plugin is missing in the migration script to create the portbindingports table. This causes errors on drivers that reference port binding information. http://openstack-ci-gw.bigswitch.com/logs/refs- changes-13-84313-3/BSN_ML2/logs/screen/screen-q-svc.log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1300593/+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 1300581] [NEW] test_revoke.RevokeTreeTests.test_cleanup fails
Public bug reported:
As seen in http://logs.openstack.org/69/83169/3/check/gate-keystone-
python27/160e2d4/console.html
Additional logs: http://logs.openstack.org/69/83169/3/check/gate-
keystone-python27/160e2d4/
The following test fails:
2014-04-01 03:37:31.236 |
==
2014-04-01 03:37:31.236 | FAIL:
keystone.tests.test_revoke.RevokeTreeTests.test_cleanup
2014-04-01 03:37:31.236 | tags: worker-3
2014-04-01 03:37:31.236 |
--
2014-04-01 03:37:31.236 | Empty attachments:
2014-04-01 03:37:31.236 | pythonlogging:''-1
2014-04-01 03:37:31.236 | stderr
2014-04-01 03:37:31.236 | stdout
2014-04-01 03:37:31.236 |
2014-04-01 03:37:31.237 | pythonlogging:'': {{{Adding cache-proxy
'keystone.tests.test_cache.CacheIsolatingProxy' to backend.}}}
2014-04-01 03:37:31.237 |
2014-04-01 03:37:31.237 | Traceback (most recent call last):
2014-04-01 03:37:31.237 | File "keystone/tests/test_revoke.py", line 457, in
test_cleanup
2014-04-01 03:37:31.237 | self._assertEventsMatchIteration(i + 1)
2014-04-01 03:37:31.237 | File "keystone/tests/test_revoke.py", line 418, in
_assertEventsMatchIteration
2014-04-01 03:37:31.237 | ['access_token_id=*']))
2014-04-01 03:37:31.237 | File
"/home/jenkins/workspace/gate-keystone-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 321, in assertEqual
2014-04-01 03:37:31.237 | self.assertThat(observed, matcher, message)
2014-04-01 03:37:31.237 | File
"/home/jenkins/workspace/gate-keystone-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 406, in assertThat
2014-04-01 03:37:31.237 | raise mismatch_error
2014-04-01 03:37:31.237 | MismatchError: 3 != 2
2014-04-01 03:37:31.238 |
==
2014-04-01 03:37:31.238 | FAIL: process-returncode
2014-04-01 03:37:31.238 | tags: worker-3
2014-04-01 03:37:31.238 |
--
** Affects: keystone
Importance: Undecided
Status: New
** Description changed:
As seen in http://logs.openstack.org/69/83169/3/check/gate-keystone-
python27/160e2d4/console.html
+
+ Additional logs: http://logs.openstack.org/69/83169/3/check/gate-
+ keystone-python27/160e2d4/
The following test fails:
2014-04-01 03:37:31.236 |
==
2014-04-01 03:37:31.236 | FAIL:
keystone.tests.test_revoke.RevokeTreeTests.test_cleanup
2014-04-01 03:37:31.236 | tags: worker-3
2014-04-01 03:37:31.236 |
--
2014-04-01 03:37:31.236 | Empty attachments:
2014-04-01 03:37:31.236 | pythonlogging:''-1
2014-04-01 03:37:31.236 | stderr
2014-04-01 03:37:31.236 | stdout
- 2014-04-01 03:37:31.236 |
+ 2014-04-01 03:37:31.236 |
2014-04-01 03:37:31.237 | pythonlogging:'': {{{Adding cache-proxy
'keystone.tests.test_cache.CacheIsolatingProxy' to backend.}}}
- 2014-04-01 03:37:31.237 |
+ 2014-04-01 03:37:31.237 |
2014-04-01 03:37:31.237 | Traceback (most recent call last):
2014-04-01 03:37:31.237 | File "keystone/tests/test_revoke.py", line 457,
in test_cleanup
2014-04-01 03:37:31.237 | self._assertEventsMatchIteration(i + 1)
2014-04-01 03:37:31.237 | File "keystone/tests/test_revoke.py", line 418,
in _assertEventsMatchIteration
2014-04-01 03:37:31.237 | ['access_token_id=*']))
2014-04-01 03:37:31.237 | File
"/home/jenkins/workspace/gate-keystone-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 321, in assertEqual
2014-04-01 03:37:31.237 | self.assertThat(observed, matcher, message)
2014-04-01 03:37:31.237 | File
"/home/jenkins/workspace/gate-keystone-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 406, in assertThat
2014-04-01 03:37:31.237 | raise mismatch_error
2014-04-01 03:37:31.237 | MismatchError: 3 != 2
2014-04-01 03:37:31.238 |
==
2014-04-01 03:37:31.238 | FAIL: process-returncode
2014-04-01 03:37:31.238 | tags: worker-3
2014-04-01 03:37:31.238 |
--
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1300581
Title:
test_revoke.RevokeTreeTests.test_cleanup fails
Status in OpenStack Identity (Keystone):
New
Bug description:
As seen in http://logs.openstack.org/69/83169/3/check/gate-keystone-
python27/160e2d4/console.html
Additional logs: http://logs.openstack.org/69/83169/3/check/gate-
keystone-python27/160e2d4/
The following test fails:
2014-04-01 03:37:31.236 |
==
[Yahoo-eng-team] [Bug 1300570] [NEW] dhcp_agent fails in RPC communication with neutron-server under Metaplugin
Public bug reported:
This problem occurs when ml2 plugin runs under Metaplugin.
error log of dhcp_agent is as follows:
---
2014-03-28 18:57:17.062 ERROR neutron.agent.dhcp_agent
[req-9c53d7a6-d850-42de-896f-184827b33bfd None None] Failed reporting state!
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent Traceback (most recent
call last):
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent File
"/opt/stack/neutron/neutron/agent/dhcp_agent.py", line 564, in _report_state
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent
self.state_rpc.report_state(ctx, self.agent_state, self.use_call)
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent File
"/opt/stack/neutron/neutron/agent/rpc.py", line 72, in report_state
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent return
self.call(context, msg, topic=self.topic)
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent File
"/opt/stack/neutron/neutron/openstack/common/rpc/proxy.py", line 129, in call
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent exc.info,
real_topic, msg.get('method'))
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent Timeout: Timeout while
waiting on RPC response - topic: "q-plugin", RPC method: "report_state" info:
""
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent
---
This problem is brought by the patch:
https://review.openstack.org/#/c/72565/
because ml2 plguin does not become to open RPC connection at plugin
initialization.
** Affects: neutron
Importance: Undecided
Assignee: Itsuro Oda (oda-g)
Status: New
** Tags: icehouse-rc-potential
** Changed in: neutron
Assignee: (unassigned) => Itsuro Oda (oda-g)
** Tags added: icehouse-rc-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1300570
Title:
dhcp_agent fails in RPC communication with neutron-server under
Metaplugin
Status in OpenStack Neutron (virtual network service):
New
Bug description:
This problem occurs when ml2 plugin runs under Metaplugin.
error log of dhcp_agent is as follows:
---
2014-03-28 18:57:17.062 ERROR neutron.agent.dhcp_agent
[req-9c53d7a6-d850-42de-896f-184827b33bfd None None] Failed reporting state!
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent Traceback (most recent
call last):
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent File
"/opt/stack/neutron/neutron/agent/dhcp_agent.py", line 564, in _report_state
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent
self.state_rpc.report_state(ctx, self.agent_state, self.use_call)
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent File
"/opt/stack/neutron/neutron/agent/rpc.py", line 72, in report_state
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent return
self.call(context, msg, topic=self.topic)
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent File
"/opt/stack/neutron/neutron/openstack/common/rpc/proxy.py", line 129, in call
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent exc.info,
real_topic, msg.get('method'))
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent Timeout: Timeout while
waiting on RPC response - topic: "q-plugin", RPC method: "report_state" info:
""
2014-03-28 18:57:17.062 TRACE neutron.agent.dhcp_agent
---
This problem is brought by the patch:
https://review.openstack.org/#/c/72565/
because ml2 plguin does not become to open RPC connection at plugin
initialization.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1300570/+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 1300563] [NEW] panel permission not working in multiple region environment
Public bug reported: When there are 2 Openstack Regions: 1.Using nova-network, name RegionOne 2.Using neutron, name RegionTwo Share horizon and keystone in two regions. Here is the problem: Login horizon with RegionOne, we can see that all neutron network related panels are still there... ** 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/1300563 Title: panel permission not working in multiple region environment Status in OpenStack Dashboard (Horizon): New Bug description: When there are 2 Openstack Regions: 1.Using nova-network, name RegionOne 2.Using neutron, name RegionTwo Share horizon and keystone in two regions. Here is the problem: Login horizon with RegionOne, we can see that all neutron network related panels are still there... To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1300563/+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 1289195] Re: Duplicate security group name cause fail to start instance
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1289195
Title:
Duplicate security group name cause fail to start instance
Status in OpenStack Compute (Nova):
In Progress
Bug description:
When create a security group, the duplicate name is allowed.
In create a instance, duplicate sg name will cause exception and the instance
will be started fail. So the duplicate name of sg should be not allowed.
In nova.network.neutronv2.API:allocate_for_instance
for security_group in security_groups:
name_match = None
uuid_match = None
for user_security_group in user_security_groups:
if user_security_group['name'] == security_group: # if have
duplicate sg name, the name_match will not be None for the second matching.
if name_match:
raise exception.NoUniqueMatch(
_("Multiple security groups found matching"
" '%s'. Use an ID to be more specific.") %
security_group)
name_match = user_security_group['id']
if user_security_group['id'] == security_group:
uuid_match = user_security_group['id']
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1289195/+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 1299349] Re: upstream-translation-update Jenkins job failing
** Also affects: openstack-manuals 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/1299349 Title: upstream-translation-update Jenkins job failing Status in OpenStack Telemetry (Ceilometer): In Progress Status in Cinder: In Progress Status in OpenStack Image Registry and Delivery Service (Glance): New Status in Orchestration API (Heat): In Progress Status in OpenStack Identity (Keystone): Fix Committed Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): In Progress Status in OpenStack Manuals: New Bug description: Various upstream-translation-update succeed apparently but looking into the file errors get ignored - and there are errors uploading the files to the translation site like: Error uploading file: There is a syntax error in your file. Line 1936: duplicate message definition... Line 7: ...this is the location of the first definition For keystone, see: http://logs.openstack.org/78/7882359da114079e8411bd3f97c5628f2cd1c098/post/keystone-upstream-translation-update/27cbb22/ This has been fixed on ironic with: https://review.openstack.org/#/c/83935 See also: http://lists.openstack.org/pipermail/openstack-i18n/2014-March/000479.html To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1299349/+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 1300553] [NEW] when using ldap driver to modify user's default tenantid, , keystone does not check if the tenantId exits in the system.
Public bug reported:
when using API driver to modify user's default tenantid, keystone does
not check if the tenantId exits in the system. I think if the tenant
does not exit,it need to return the error "The tenant id cannot be
found".
And the API I used is put: /v2.0/users/{userid},the request is :{"user":
{"id": "1535b2b9cafa419aa96141c445e5de7a", "name":
"abcd","password":"abcd", "email":
"b...@139.com","tenantId":"344d24ddce1643219d6c8c49c8cd9ded"}}
the tenantid does not exist.
** 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/1300553
Title:
when using ldap driver to modify user's default tenantid,,keystone
does not check if the tenantId exits in the system.
Status in OpenStack Identity (Keystone):
New
Bug description:
when using API driver to modify user's default tenantid, keystone
does not check if the tenantId exits in the system. I think if the
tenant does not exit,it need to return the error "The tenant id cannot
be found".
And the API I used is put: /v2.0/users/{userid},the request is
:{"user": {"id": "1535b2b9cafa419aa96141c445e5de7a", "name":
"abcd","password":"abcd", "email":
"b...@139.com","tenantId":"344d24ddce1643219d6c8c49c8cd9ded"}}
the tenantid does not exist.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1300553/+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 1269701] Re: log message level is unreasonable
** 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/1269701
Title:
log message level is unreasonable
Status in OpenStack Image Registry and Delivery Service (Glance):
Invalid
Bug description:
In method glance.api.v1.images.Controller#_reserve, if an duplicate image
uuid is specified, it will log the "debug" level message and raise error:
except exception.Duplicate:
msg = (_("An image with identifier %s already exists") %
image_meta['id'])
LOG.debug(msg)
raise HTTPConflict(explanation=msg,
In method glance.registry.api.v1.images.Controller#create,in the same case,
glance will log the "error" level message and return error:
except exception.Duplicate:
msg = _("Image with identifier %s already exists!") % image_id
LOG.error(msg)
return exc.HTTPConflict(msg)
I think it should log error message when raise or return exceptions.
there are many similar cases in glance code.
is it a bug?
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1269701/+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 1222682] Re: Live Migration does not work unless cache=none
The code itself is abandoned. The referring URLs are grizzly. Marking as won't fix. ** Changed in: openstack-manuals Status: Triaged => 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/1222682 Title: Live Migration does not work unless cache=none Status in OpenStack Compute (Nova): In Progress Status in OpenStack Manuals: Won't Fix Bug description: If O_DIRECT is not supported, 'cache=none' is not set. Thus, Live Migration gives the following error: "Live Migration failure: Unsafe migration: Migration may lead to data corruption if disks use cache != none" However, it is ok to migrate if the storage is "coherent" across nodes. So Nova's live-migration should support the Libvirt's unsafe=True flag. Ideally there should be a nova flag which can be set to pass through the libvirt 'unsafe=true' flag. My thinking is that if 'cache=writethrough' is set then the underlying storage should be safe, but perhaps it's best not to make that assumption and rather to have a nova.conf flag. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1222682/+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 1300527] [NEW] Nova rpc zmq has gone away
Public bug reported: It seems like the inclusion of the rpc zmq reciever has disappeared. This causes the build to fail on icehouse/master (not havana). The error that will happen during build phase: RPM build errors: File not found: /home/harlowja/openstack/deps/rpmbuild/openstack-nova-2014.2.dev1.g3265368-1.el6.src.rpm/BUILDROOT/openstack-nova-2014.2.dev1.g3265368-1.el6.x86_64/usr/bin/nova-rpc-zmq-receiver ** Affects: anvil Importance: High Status: New ** Changed in: anvil Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to anvil. https://bugs.launchpad.net/bugs/1300527 Title: Nova rpc zmq has gone away Status in ANVIL for forging OpenStack.: New Bug description: It seems like the inclusion of the rpc zmq reciever has disappeared. This causes the build to fail on icehouse/master (not havana). The error that will happen during build phase: RPM build errors: File not found: /home/harlowja/openstack/deps/rpmbuild/openstack-nova-2014.2.dev1.g3265368-1.el6.src.rpm/BUILDROOT/openstack-nova-2014.2.dev1.g3265368-1.el6.x86_64/usr/bin/nova-rpc-zmq-receiver To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1300527/+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 1288245] Re: mox is needed in requirements
This bug was fixed in the package horizon - 1:2014.1~rc1-0ubuntu1
---
horizon (1:2014.1~rc1-0ubuntu1) trusty; urgency=medium
* New upstream release candidate (LP: #1288245).
- d/static/*: Refreshed assets for new upstream release.
* d/theme/*: Refresh Ubuntu theme against Icehouse templates (LP: #1291653).
-- James PageMon, 31 Mar 2014 17:31:49 +0100
** Changed in: horizon (Ubuntu Trusty)
Status: Triaged => 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/1288245
Title:
mox is needed in requirements
Status in OpenStack Dashboard (Horizon):
Fix Released
Status in “horizon” package in Ubuntu:
Fix Released
Status in “horizon” source package in Trusty:
Fix Released
Bug description:
It appears that mox is needed in requirements.tst now:
Environment:
Request Method: GET
Request URL: http://localhost:8080/
Django Version: 1.5.5
Python Version: 2.7.3
Installed Applications:
['openstack_dashboard',
'django.contrib.contenttypes',
'django.contrib.auth',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'django.contrib.humanize',
'compressor',
'horizon',
'openstack_auth',
'openstack_dashboard.dashboards.project',
'openstack_dashboard.dashboards.admin',
'openstack_dashboard.dashboards.settings']
Installed Middleware:
('django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'horizon.middleware.HorizonMiddleware',
'django.middleware.doc.XViewMiddleware',
'django.middleware.locale.LocaleMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware')
Traceback:
File
"/home/vulcan/horizon/.venv/local/lib/python2.7/site-packages/django/core/handlers/base.py"
in get_response
92. response = middleware_method(request)
File
"/home/vulcan/horizon/.venv/local/lib/python2.7/site-packages/django/middleware/locale.py"
in process_request
21. check_path = self.is_language_prefix_patterns_used()
File
"/home/vulcan/horizon/.venv/local/lib/python2.7/site-packages/django/middleware/locale.py"
in is_language_prefix_patterns_used
56. for url_pattern in get_resolver(None).url_patterns:
File
"/home/vulcan/horizon/.venv/local/lib/python2.7/site-packages/django/core/urlresolvers.py"
in url_patterns
347. patterns = getattr(self.urlconf_module, "urlpatterns",
self.urlconf_module)
File
"/home/vulcan/horizon/.venv/local/lib/python2.7/site-packages/django/core/urlresolvers.py"
in urlconf_module
342. self._urlconf_module = import_module(self.urlconf_name)
File
"/home/vulcan/horizon/.venv/local/lib/python2.7/site-packages/django/utils/importlib.py"
in import_module
35. __import__(name)
File "/home/vulcan/horizon/openstack_dashboard/urls.py" in
38. url(r'', include(horizon.urls))
File
"/home/vulcan/horizon/.venv/local/lib/python2.7/site-packages/django/conf/urls/__init__.py"
in include
26. patterns = getattr(urlconf_module, 'urlpatterns', urlconf_module)
File
"/home/vulcan/horizon/.venv/local/lib/python2.7/site-packages/django/utils/functional.py"
in inner
204. self._setup()
File
"/home/vulcan/horizon/.venv/local/lib/python2.7/site-packages/django/utils/functional.py"
in _setup
270. self._wrapped = self._setupfunc()
File "/home/vulcan/horizon/horizon/base.py" in url_patterns
733. return self._urls()[0]
File "/home/vulcan/horizon/horizon/base.py" in _urls
739. urlpatterns = self._get_default_urlpatterns()
File "/home/vulcan/horizon/horizon/base.py" in _get_default_urlpatterns
82. mod = import_module(self.urls)
File
"/home/vulcan/horizon/.venv/local/lib/python2.7/site-packages/django/utils/importlib.py"
in import_module
35. __import__(name)
File "/home/vulcan/horizon/horizon/site_urls.py" in
26. from horizon.test.jasmine import jasmine
File "/home/vulcan/horizon/horizon/test/jasmine/jasmine.py" in
17. from horizon.test import helpers as test
File "/home/vulcan/horizon/horizon/test/helpers.py" in
50. import mox
Exception Type: ImportError at /
Exception Value: No module named mox
Addind mox to requirements solved this issue.
The latest commit in my checkout is:
commit 015aff26307ca619abc569404f82c6338239e628
Author: Jordan OMara
Date: Tue Jan 14 10:25:26 2014 -0500
Change-Id: I2854e9e4bb578be5187ef962808b93f11ac6b1f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1288245/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-
[Yahoo-eng-team] [Bug 1297512] Re: libvirt domain launch "Cannot find 'pm-is-supported' in path" error
** Also affects: devstack 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/1297512 Title: libvirt domain launch "Cannot find 'pm-is-supported' in path" error Status in devstack - openstack dev environments: New Status in OpenStack Compute (Nova): New Bug description: Seen here: http://logs.openstack.org/29/82829/1/check/check-tempest-dsvm- full/67c8984/logs/screen-n-cpu.txt.gz 2014-03-25 14:27:02.318 ERROR nova.virt.libvirt.driver [req-b485d6b2-cf63-468f-ae09-0c6ba31274db SecurityGroupsTestJSON-1020006517 SecurityGroupsTestJSON-1157433096] An error occurred while trying to launch a defined domain with xml: instance-0032 c3baa6cf-9127-4a69-af9a-58dbba0824cc 65536 65536 1 OpenStack Foundation OpenStack Nova 2014.1 44361562-54ff-5e7f-6c5b-ba157fe8645a c3baa6cf-9127-4a69-af9a-58dbba0824cc hvm /opt/stack/data/nova/instances/c3baa6cf-9127-4a69-af9a-58dbba0824cc/kernel /opt/stack/data/nova/instances/c3baa6cf-9127-4a69-af9a-58dbba0824cc/ramdisk root=/dev/vda console=tty0 console=ttyS0 destroy restart destroy /usr/bin/qemu-system-x86_64 Then: 2014-03-25 14:27:05.135 ERROR nova.compute.manager [req-b485d6b2-cf63-468f-ae09-0c6ba31274db SecurityGroupsTestJSON-1020006517 SecurityGroupsTestJSON-1157433096] [instance: c3baa6cf-9127-4a69-af9a-58dbba0824cc] Cannot reboot instance: internal error Process exited while reading console log output: char device redirected to /dev/pts/2 qemu-system-x86_64: -drive file=/opt/stack/data/nova/instances/c3baa6cf-9127-4a69-af9a-58dbba0824cc/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none: could not open disk image /opt/stack/data/nova/instances/c3baa6cf-9127-4a69-af9a-58dbba0824cc/disk: Invalid argument Looking in the libvirtd log: http://logs.openstack.org/29/82829/1/check/check-tempest-dsvm-full/67c8984/logs/libvirtd.txt.gz 2014-03-25 14:54:56.792+: 12413: warning : qemuCapsInit:856 : Failed to get host power management capabilities 2014-03-25 14:54:56.936+: 10184: error : virExecWithHook:327 : Cannot find 'pm-is-supported' in path: No such file or directory 2014-03-25 14:54:56.936+: 10184: warning : qemuCapsInit:856 : Failed to get host power management capabilities 2014-03-25 14:54:57.004+: 12413: error : virExecWithHook:327 : Cannot find 'pm-is-supported' in path: No such file or directory 2014-03-25 14:54:57.004+: 12413: warning : qemuCapsInit:856 : Failed to get host power management capabilities To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1297512/+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 1243718] Re: kill qemu pid will crash openstack-nova-compute
*** This bug is a duplicate of bug 1270304 *** https://bugs.launchpad.net/bugs/1270304 ** This bug has been marked a duplicate of bug 1270304 error in guestfs driver setup causes orphaned libguestfs processes -- 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/1243718 Title: kill qemu pid will crash openstack-nova-compute Status in OpenStack Compute (Nova): Incomplete Bug description: I am working with gluster as cinder backend. when I boot an instance I see two qemu pid's created, one for the instance and a second one for glusterfs (not sure what it is and why we run it) when I delete the instance the glusterfs pid remains. if I kill it openstack-nova-compute will be killed as well [root@cougar07 ~(keystone_admin)]# ps -elf |grep qemu 2 S nova 13775 13645 6 80 0 - 212831 poll_s 16:51 ? 00:00:02 /usr/libexec/qemu-kvm -global virtio-blk-pci.scsi=off -nodefconfig -nodefaults -nographic -machine accel=kvm:tcg -cpu host,+kvmclock -m 500 -no-reboot -kernel /var/tmp/.guestfs-162/kernel.13645 -initrd /var/tmp/.guestfs-162/initrd.13645 -device virtio-scsi-pci,id=scsi -drive file=/var/lib/nova/instances/2f469c9d-2bf8-44ba-ac9a-e280289802bf/disk,cache=none,format=qcow2,id=hd0,if=none -device scsi-hd,drive=hd0 -drive file=/var/tmp/.guestfs-162/root.13645,snapshot=on,id=appliance,if=none,cache=unsafe -device scsi-hd,drive=appliance -device virtio-serial -serial stdio -device sga -chardev socket,path=/tmp/libguestfsWTO2Jc/guestfsd.sock,id=channel0 -device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 -append panic=1 console=ttyS0 udevtimeout=600 no_timer_check acpi=off printk.time=1 cgroup_disable=memory root=/dev/sdb selinux=0 TERM=xterm 6 S qemu 14018 1 72 80 0 - 217865 poll_s 16:51 ? 00:00:19 /usr/libexec/qemu-kvm -name instance-0035 -S -M rhel6.5.0 -cpu Opteron_G3,+nodeid_msr,+wdt,+skinit,+ibs,+osvw,+3dnowprefetch,+cr8legacy,+extapic,+cmp_legacy,+3dnow,+3dnowext,+pdpe1gb,+fxsr_opt,+mmxext,+ht,+vme -enable-kvm -m 512 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 2f469c9d-2bf8-44ba-ac9a-e280289802bf -smbios type=1,manufacturer=Red Hat Inc.,product=OpenStack Nova,version=2013.2-0.25.rc1.el6ost,serial=44454c4c-4a00-1044-804c-b5c04f39354a,uuid=2f469c9d-2bf8-44ba-ac9a-e280289802bf -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0035.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/nova/instances/2f469c9d-2bf8-44ba-ac9a-e280289802bf/disk,if=none,id=drive-virtio-disk0,format=qcow 2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:37:43:23,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/var/lib/nova/instances/2f469c9d-2bf8-44ba-ac9a-e280289802bf/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 10.35.160.135:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 0 S root 14043 13613 0 80 0 - 25813 pipe_w 16:52 pts/200:00:00 grep qemu [root@cougar07 ~(keystone_admin)]# ps -elf |grep qemu 2 S nova 13775 13645 4 80 0 - 212831 poll_s 16:51 ? 00:00:02 /usr/libexec/qemu-kvm -global virtio-blk-pci.scsi=off -nodefconfig -nodefaults -nographic -machine accel=kvm:tcg -cpu host,+kvmclock -m 500 -no-reboot -kernel /var/tmp/.guestfs-162/kernel.13645 -initrd /var/tmp/.guestfs-162/initrd.13645 -device virtio-scsi-pci,id=scsi -drive file=/var/lib/nova/instances/2f469c9d-2bf8-44ba-ac9a-e280289802bf/disk,cache=none,format=qcow2,id=hd0,if=none -device scsi-hd,drive=hd0 -drive file=/var/tmp/.guestfs-162/root.13645,snapshot=on,id=appliance,if=none,cache=unsafe -device scsi-hd,drive=appliance -device virtio-serial -serial stdio -device sga -chardev socket,path=/tmp/libguestfsWTO2Jc/guestfsd.sock,id=channel0 -device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 -append panic=1 console=ttyS0 udevtimeout=600 no_timer_check acpi=off printk.time=1 cgroup_disable=memory root=/dev/sdb selinux=0 TERM=xterm 0 S root 14135 13613 0 80 0 - 25813 pipe_w 16:52 pts/200:00:00 grep qemu [root@cougar07 ~(keystone_admin)]# kill -9 13645 [root@cougar07 ~(keystone_admin)]# [root@cougar07 ~(keystone_admin)]# [root@cougar07 ~(keystone_admin)]# ps -elf |grep qemu 0 S root 14140 13613 0 80 0 - 25813 pipe_w 16:52 pts/200:00:00 grep qemu [root@cougar07 ~(keystone_admin)]# [root@cougar07
[Yahoo-eng-team] [Bug 1268439] Re: range method is not same in py3.x and py2.x
** Changed in: heat Status: Fix Committed => Fix Released ** Changed in: heat Milestone: None => icehouse-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1268439 Title: range method is not same in py3.x and py2.x Status in OpenStack Telemetry (Ceilometer): In Progress Status in Cinder: In Progress Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Orchestration API (Heat): Fix Released Status in OpenStack Identity (Keystone): In Progress Status in OpenStack Neutron (virtual network service): Fix Committed Status in OpenStack Compute (Nova): In Progress Status in Python client library for Ceilometer: In Progress Status in Python client library for Keystone: In Progress Status in Python client library for Neutron: Invalid Status in Python client library for Swift: Fix Committed Status in OpenStack Object Storage (Swift): In Progress Bug description: in py3.x,range is xrange in py2.x. in py3.x, if you want get a list,you must use: list(range(value)) I review the code, find that many codes use range for loop, if used py3.x environment, it will occure error. so we must modify this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1268439/+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
** Changed in: heat 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/1225191 Title: add qpid-python to requirements.txt Status in Orchestration API (Heat): Fix Released Status in OpenStack Compute (Nova): In Progress 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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Changed in: heat Status: Fix Committed => Fix Released ** Changed in: heat Milestone: None => icehouse-rc1 -- 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/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests Status in Cinder: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Orchestration API (Heat): Fix Released Status in Ironic (Bare Metal Provisioning): Fix Released Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Compute (Nova): In Progress Status in Python client library for Neutron: Fix Committed Status in Trove client binding: Fix Committed Status in OpenStack Data Processing (Sahara, ex. Savanna): Fix Released Status in Trove - Database as a Service: In Progress Status in Tuskar: Fix Released Bug description: Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1280522/+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 1285482] Re: There is not any API sample file for "unshelve a server" API
** Also affects: openstack-api-site 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/1285482 Title: There is not any API sample file for "unshelve a server" API Status in OpenStack Compute (Nova): Fix Released Status in OpenStack API documentation site: New Bug description: Now there is not any API sample file of "unshelve a server" API, and OpenStack API documentation[1] also does not describe the API. [1]: http://api.openstack.org/api-ref-compute-ext.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1285482/+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 1299349] Re: upstream-translation-update Jenkins job failing
Neutron also contains this: https://jenkins.openstack.org/view/All/job/neutron-propose-translation-update/lastBuild/consoleText ** Also 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/1299349 Title: upstream-translation-update Jenkins job failing Status in OpenStack Telemetry (Ceilometer): In Progress Status in Cinder: In Progress Status in OpenStack Image Registry and Delivery Service (Glance): New Status in Orchestration API (Heat): In Progress Status in OpenStack Identity (Keystone): Fix Committed Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): In Progress Bug description: Various upstream-translation-update succeed apparently but looking into the file errors get ignored - and there are errors uploading the files to the translation site like: Error uploading file: There is a syntax error in your file. Line 1936: duplicate message definition... Line 7: ...this is the location of the first definition For keystone, see: http://logs.openstack.org/78/7882359da114079e8411bd3f97c5628f2cd1c098/post/keystone-upstream-translation-update/27cbb22/ This has been fixed on ironic with: https://review.openstack.org/#/c/83935 See also: http://lists.openstack.org/pipermail/openstack-i18n/2014-March/000479.html To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1299349/+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 1299349] Re: upstream-translation-update Jenkins job failing
Glance also affected: https://jenkins.openstack.org/view/All/job/glance- propose-translation-update/lastBuild/consoleText ** Also affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1299349 Title: upstream-translation-update Jenkins job failing Status in OpenStack Telemetry (Ceilometer): In Progress Status in Cinder: In Progress Status in OpenStack Image Registry and Delivery Service (Glance): New Status in Orchestration API (Heat): In Progress Status in OpenStack Identity (Keystone): Fix Committed Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): In Progress Bug description: Various upstream-translation-update succeed apparently but looking into the file errors get ignored - and there are errors uploading the files to the translation site like: Error uploading file: There is a syntax error in your file. Line 1936: duplicate message definition... Line 7: ...this is the location of the first definition For keystone, see: http://logs.openstack.org/78/7882359da114079e8411bd3f97c5628f2cd1c098/post/keystone-upstream-translation-update/27cbb22/ This has been fixed on ironic with: https://review.openstack.org/#/c/83935 See also: http://lists.openstack.org/pipermail/openstack-i18n/2014-March/000479.html To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1299349/+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 1112912] Re: get_firewall_required should use VIF parameter from neutron
** 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/1112912 Title: get_firewall_required should use VIF parameter from neutron Status in OpenStack Neutron (virtual network service): Fix Committed Status in OpenStack Compute (Nova): Fix Released Status in OpenStack Security Advisories: Incomplete Status in Tempest: In Progress Bug description: This bug report is from the discussion of https://review.openstack.org/#/c/19126/17/nova/virt/libvirt/vif.py I'm going to file this as a bug for tracking issue The patch introduces get_firewall_required function. But the patch checks only conf file. This should use quantum VIF parameter. https://github.com/openstack/quantum/blob/master/quantum/plugins/openvswitch/ovs_quantum_plugin.py#L513 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1112912/+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 1279611] Re: urlparse is incompatible for python 3
** Changed in: nova Status: Fix Committed => Fix Released ** Changed in: nova Milestone: None => icehouse-rc1 -- 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/1279611 Title: urlparse is incompatible for python 3 Status in OpenStack Telemetry (Ceilometer): In Progress Status in Cinder: In Progress Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Status in OpenStack Dashboard (Horizon): In Progress Status in Ironic (Bare Metal Provisioning): Fix Released Status in OpenStack Message Queuing Service (Marconi): Fix Committed Status in OpenStack Neutron (virtual network service): Fix Released Status in OpenStack Compute (Nova): Fix Released Status in Python client library for Neutron: Fix Committed Status in OpenStack Data Processing (Sahara, ex. Savanna): Fix Released Status in Storyboard database creator: Fix Committed Status in OpenStack Object Storage (Swift): New Status in Tempest: In Progress Status in Trove - Database as a Service: In Progress Status in Tuskar: In Progress Status in Zuul: A project gating system: Fix Committed Bug description: import urlparse should be changed to : import six.moves.urllib.parse as urlparse for python3 compatible. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1279611/+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 1252967] Re: VMware: delete vm snapshot after nova snapshot
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1252967 Title: VMware: delete vm snapshot after nova snapshot Status in OpenStack Compute (Nova): Fix Released Status in The OpenStack VMwareAPI subTeam: In Progress Bug description: When performing a nova snapshot, the vmware driver takes a VM snapshot and copies out the snapshotted disk. After the operation, the VM snapshot should be deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1252967/+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 1206365] Re: add keypair create/delete notify events
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1206365 Title: add keypair create/delete notify events Status in OpenStack Compute (Nova): Fix Released Bug description: keypair add/delete events can be added to notifications system for audit and other usecases. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1206365/+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 1281936] Re: A v3 API request of "GET /versions/:(id)" occurs "Unexpected API Error."
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1281936
Title:
A v3 API request of "GET /versions/:(id)" occurs "Unexpected API
Error."
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
When I request a v3 API request of "GET /versions/:(id)" occurs "Unexpected
API Error.".
$ curl -i 'http://192.168.1.36:8774/v3/versions/123' -X GET -H
"X-Auth-Project-Id: demo" -H "User-Agent: python-novaclient" -H "Accept:
application/json" -H "X-Auth-Token: "
HTTP/1.1 500 Internal Server Error
Content-Length: 193
Content-Type: application/json; charset=UTF-8
X-Compute-Request-Id: req-baf6f903-b3f1-4c80-9e59-93f1440609a4
Date: Wed, 19 Feb 2014 07:08:13 GMT
{"computeFault": {"message": "Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.\n", "code": 500}}
nova-api logged an error:
2014-02-19 16:14:37.075 ERROR nova.api.openstack.extensions
[req-282a97a5-8f42-4410-a8dd-ff97457d0241 admin demo] Unexpected exception in
API method
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions Traceback (most
recent call last):
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/openstack/extensions.py", line 472, in wrapped
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions return
f(*args, **kwargs)
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions TypeError: show()
got an unexpected keyword argument 'id'
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1281936/+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 1234604] Re: xenapi: migration error - original exception not logged
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1234604 Title: xenapi: migration error - original exception not logged Status in OpenStack Compute (Nova): Fix Released Bug description: If there is a non-properly installed host (maybe the /images directory is not created, or ssh was not setup), the following tempest test fails: nosetests tempest.api.compute.servers.test_server_actions:ServerActionsTestXML.test_resize_server_confirm This is the log entry from n-cpu: [req-ee3f693d-2d80-4f7a-927f-19ae6264fd7b ServerActionsTestXML1666436677-user ServerActionsTestXML1666436677-tenant] Exception during message handling Traceback (most recent call last): File "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 461, in _process_data **args) File "/opt/stack/nova/nova/openstack/common/rpc/dispatcher.py", line 172, in dispatch result = getattr(proxyobj, method)(ctxt, **kwargs) File "/opt/stack/nova/nova/compute/manager.py", line 353, in decorated_function return function(self, context, *args, **kwargs) File "/opt/stack/nova/nova/exception.py", line 90, in wrapped payload) File "/opt/stack/nova/nova/exception.py", line 73, in wrapped return f(self, context, *args, **kw) File "/opt/stack/nova/nova/compute/manager.py", line 243, in decorated_function pass File "/opt/stack/nova/nova/compute/manager.py", line 229, in decorated_function return function(self, context, *args, **kwargs) File "/opt/stack/nova/nova/compute/manager.py", line 294, in decorated_function function(self, context, *args, **kwargs) File "/opt/stack/nova/nova/compute/manager.py", line 271, in decorated_function e, sys.exc_info()) File "/opt/stack/nova/nova/compute/manager.py", line 258, in decorated_function return function(self, context, *args, **kwargs) File "/opt/stack/nova/nova/compute/manager.py", line 3021, in resize_instance block_device_info) File "/opt/stack/nova/nova/virt/xenapi/driver.py", line 284, in migrate_disk_and_power_off dest, instance_type, block_device_info) File "/opt/stack/nova/nova/virt/xenapi/vmops.py", line 939, in migrate_disk_and_power_off context, instance, dest, vm_ref, sr_path) File "/opt/stack/nova/nova/virt/xenapi/vmops.py", line 882, in _migrate_disk_resizing_up self._migrate_vhd(instance, vdi_uuid, dest, sr_path, seq_num) File "/opt/stack/nova/nova/virt/xenapi/vmops.py", line 770, in _migrate_vhd raise exception.MigrationError(reason=msg) MigrationError: Migration error: Failed to transfer vhd to new host It would be good to see what was the actual error message. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1234604/+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 1257135] Re: Make sure "volumeId" in request body while attaching volume to server
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1257135 Title: Make sure "volumeId" in request body while attaching volume to server Status in OpenStack Compute (Nova): Fix Released Bug description: We should check whether the para "volumeId" is in request body. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1257135/+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 1224469] Re: if volume size is None for image bdms nova compute throws an exception
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1224469 Title: if volume size is None for image bdms nova compute throws an exception Status in OpenStack Compute (Nova): Fix Released Bug description: When attempting to boot an instance with a block device with source=image,dest=volume and there is no volume size specified - nova compute will error out: [ndipanov@localhost devstack]$ nova boot --flavor 1 --block-device bootindex=0,source=image,dest=volume,id=42ccba7f-914b- 4e3d-8387-b7b30d96a7a5,type=cdrom,bus=ide testimgvol in nova compute logs: ERROR nova.compute.manager [req-a7200578-8bf4-4791-a5bf-449c473d41b6 demo demo] [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] Error: Invalid input received: Invalid input received: Volume size None must be an integer and greater than 0 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] Traceback (most recent call last): 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] File "/opt/stack/nova/nova/compute/manager.py", line 1038, in _build_instance 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] context, instance, bdms) 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] File "/opt/stack/nova/nova/compute/manager.py", line 1403, in _prep_block_device 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] instance=instance) 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] File "/opt/stack/nova/nova/compute/manager.py", line 1386, in _prep_block_device 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] self._await_block_device_map_created)) 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] File "/opt/stack/nova/nova/virt/block_device.py", line 283, in attach_block_devices 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] block_device_mapping) 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] File "/opt/stack/nova/nova/virt/block_device.py", line 236, in attach 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] '', '', image_id=self.image_id) 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] File "/opt/stack/nova/nova/volume/cinder.py", line 309, in create 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] raise exception.InvalidInput(reason=e.message) 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] InvalidInput: Invalid input received: Invalid input received: Volume size None must be an integer and greater than 0 2013-09-12 09:20:15.362 TRACE nova.compute.manager [instance: 8edd2e9e-4b4d-44ac-92f1-bea38cd5320d] We should disallow empty or default the volume size if not specified. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1224469/+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 1184446] Re: cruft builds up in 'nova service-list' as compute nodes are added and removed
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1184446 Title: cruft builds up in 'nova service-list' as compute nodes are added and removed Status in OpenStack Compute (Nova): Fix Released Status in tripleo - openstack on openstack: Triaged Bug description: This is our current service-list: heat-admin@bootstack-vm-4:~$ nova service-list +--+--+--+-+---++ | Binary | Host | Zone | Status | State | Updated_at | +--+--+--+-+---++ | nova-conductor | bootstack-vm-4.notcompute.novalocal | internal | enabled | up| 2013-05-26T23:42:55.00 | | nova-cert| bootstack-vm-4.notcompute.novalocal | internal | enabled | up| 2013-05-26T23:42:58.00 | | nova-scheduler | bootstack-vm-4.notcompute.novalocal | internal | enabled | up| 2013-05-26T23:42:57.00 | | nova-consoleauth | bootstack-vm-4.notcompute.novalocal | internal | enabled | up| 2013-05-26T23:43:00.00 | | nova-compute | bootstack-vm-4.notcompute.novalocal | nova | enabled | down | 2013-05-23T08:33:59.00 | | nova-compute | compute-test | nova | enabled | down | 2013-05-24T08:54:40.00 | | nova-compute | compute-test2| nova | enabled | up| 2013-05-26T23:42:54.00 | | nova-compute | compute-group| nova | enabled | down | 2013-05-24T08:55:04.00 | | nova-compute | compute-group.novacompute0.novacompute.novalocal | nova | enabled | down | 2013-05-24T09:07:51.00 | | nova-compute | compute-test0| nova | enabled | up| 2013-05-26T23:43:01.00 | | nova-compute | compute-test1| nova | enabled | up| 2013-05-26T23:42:55.00 | | nova-compute | compute-test3| nova | enabled | up| 2013-05-26T23:42:53.00 | | nova-compute | compute-test4| nova | enabled | up| 2013-05-26T23:43:00.00 | | nova-compute | compute-test5| nova | enabled | up| 2013-05-26T23:42:53.00 | note that the hosts in state down will never be coming back - we've rotated them out. There doesn't seem to be a way to gc this except by fiddling by hand. If there is, perhaps this is just a doc bug. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1184446/+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 1252947] Re: libvirtError: Cannot recv data: Connection reset by peer
** Changed in: nova Status: Fix Committed => Fix Released ** Changed in: nova Milestone: None => icehouse-rc1 -- 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/1252947 Title: libvirtError: Cannot recv data: Connection reset by peer Status in OpenStack Compute (Nova): Fix Released Bug description: tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON fails sporadically. See: http://logs.openstack.org/66/54966/2/check/check-tempest- devstack-vm-full/d611ed0/console.html 2013-11-19 22:24:52.379 | == 2013-11-19 22:24:52.380 | FAIL: setUpClass (tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON) 2013-11-19 22:24:52.380 | setUpClass (tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON) 2013-11-19 22:24:52.380 | -- 2013-11-19 22:24:52.380 | _StringException: Traceback (most recent call last): 2013-11-19 22:24:52.380 | File "tempest/api/compute/servers/test_servers_negative.py", line 46, in setUpClass 2013-11-19 22:24:52.380 | resp, server = cls.create_test_server(wait_until='ACTIVE') 2013-11-19 22:24:52.381 | File "tempest/api/compute/base.py", line 118, in create_test_server 2013-11-19 22:24:52.381 | server['id'], kwargs['wait_until']) 2013-11-19 22:24:52.381 | File "tempest/services/compute/json/servers_client.py", line 160, in wait_for_server_status 2013-11-19 22:24:52.381 | extra_timeout=extra_timeout) 2013-11-19 22:24:52.381 | File "tempest/common/waiters.py", line 73, in wait_for_server_status 2013-11-19 22:24:52.381 | raise exceptions.BuildErrorException(server_id=server_id) 2013-11-19 22:24:52.381 | BuildErrorException: Server 62bfeebd-8878-477f-9eac-a8b21ec5ac26 failed to build and is in ERROR status To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1252947/+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 1269395] Re: nova pause causes ERRORs in log
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1269395 Title: nova pause causes ERRORs in log Status in OpenStack Compute (Nova): Fix Released Bug description: Description of problem: The vmwareapi.VMwareVCDriver seems to not suport pausing a VM. Issuing the nova pause results in ERROR in log. It probably should not be rated as ERROR but as WARNING. Version-Release number of selected component (if applicable): openstack-nova-compute-2013.2.1-1.el6ost.noarch How reproducible: always Steps to Reproduce: 1. have a OpenStack with VMwareVCDriver compute nodes 2. nova boot 3. nova pause Actual results: ERROR in log Expected results: WARNING in log. Additional info: 2014-01-15 12:09:27.074 19359 ERROR nova.openstack.common.rpc.amqp [req-f399e515-64ff-4e5a-8dfd-47295f9755c2 c617ab6c5a9c45ac97d59b3d799e431e 89cec4e2039c4344b30e74575444afd1] Exception during message handling 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp Traceback (most recent call last): 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py", line 461, in _process_data 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp **args) 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/openstack/common/rpc/dispatcher.py", line 172, in dispatch 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp result = getattr(proxyobj, method)(ctxt, **kwargs) 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 353, in decorated_function 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/exception.py", line 90, in wrapped 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp payload) 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/exception.py", line 73, in wrapped 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp return f(self, context, *args, **kw) 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 243, in decorated_function 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp pass 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 229, in decorated_function 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 294, in decorated_function 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp function(self, context, *args, **kwargs) 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 271, in decorated_function 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp e, sys.exc_info()) 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 258, in decorated_function 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 3227, in pause_instance 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp self.driver.pause(instance) 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/virt/vmwareapi/driver.py", line 676, in pause 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp _vmops.pause(instance) 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/virt/vmwareapi/vmops.py", line 969, in pause 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp raise NotImplementedError(msg) 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp NotImplementedError: pause not supported for vmwareapi 2014-01-15 12:09:27.074 19359 TRACE nova.openstack.common.rpc.amqp To manage notifications about this bug go to: https://bugs.
[Yahoo-eng-team] [Bug 1267685] Re: boot vm don't support ipv6
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1267685
Title:
boot vm don't support ipv6
Status in OpenStack Compute (Nova):
Fix Released
Status in Python client library for Nova:
In Progress
Bug description:
when boot vm, it can use '--nic ' to set network info, if it want to use ipv6,it hase to use
port-id which hase a ipv6 address, I think it should can use '--nic
net-id=net-uuid, fixed-ip=ip-addr' which include ipv4 and ipv6
address.Currently,nova already prevent that:
if address is not None and not utils.is_valid_ipv4(address):
msg = _("Invalid fixed IP address (%s)") % address
raise exc.HTTPBadRequest(explanation=msg)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1267685/+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 1226370] Re: service record did not updated on time after restart
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1226370 Title: service record did not updated on time after restart Status in OpenStack Compute (Nova): Fix Released Bug description: When using db driver or mc driver for servicegroup, if the service was created before and restart, then the service record will not update on time but need to wait a delay_interval (10s by default) before update. This will cause VM deploy failed when nova compute restart and user deploy VM immediately with ComputeFilter. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1226370/+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 1260249] Re: migration-list: 'unicode' object has no attribute 'iteritems'
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1260249
Title:
migration-list: 'unicode' object has no attribute 'iteritems'
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
There is an AttributeError when we try to use the command "nova
migration-list"
Traceback (most recent call last):
File "/opt/stack/python-novaclient/novaclient/shell.py", line 721, in main
OpenStackComputeShell().main(map(strutils.safe_decode, sys.argv[1:]))
File "/opt/stack/python-novaclient/novaclient/shell.py", line 657, in main
args.func(self.cs, args)
File "/opt/stack/python-novaclient/novaclient/v1_1/contrib/migrations.py",
line 71, in do_migration_list
args.cell_name))
File "/opt/stack/python-novaclient/novaclient/v1_1/contrib/migrations.py",
line 53, in list
return self._list("/os-migrations%s" % query_string, "migrations")
File "/opt/stack/python-novaclient/novaclient/base.py", line 80, in _list
for res in data if res]
File "/opt/stack/python-novaclient/novaclient/base.py", line 426, in
__init__
self._add_details(info)
File "/opt/stack/python-novaclient/novaclient/base.py", line 449, in
_add_details
for (k, v) in six.iteritems(info):
File "/usr/local/lib/python2.7/dist-packages/six.py", line 439, in iteritems
return iter(getattr(d, _iteritems)(**kw))
AttributeError: 'unicode' object has no attribute 'iteritems'
ERROR: 'unicode' object has no attribute 'iteritems'
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1260249/+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 1264223] Re: webob.exc.HTTPBadRequest doesn't accept parameter 'reason'
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1264223
Title:
webob.exc.HTTPBadRequest doesn't accept parameter 'reason'
Status in Cinder:
Fix Released
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
If the specific error message is required, we must set
explanation='message' to initialize subclass of
webob.exc.WSGIHTTPException(). There is some code specify the message
to 'reason' incorrectly.
Ex.
OK: raise webob.exc.HTTPBadRequest(explanation=_('What?'))
WRONG: raise webob.exc.HTTPBadRequest(reason=_("What's up?"))
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1264223/+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 1229190] Re: "nova hypervisor-show" should also show the ip address of the hypervisor
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1229190 Title: "nova hypervisor-show" should also show the ip address of the hypervisor Status in OpenStack Compute (Nova): Fix Released Bug description: After blueprint of https://blueprints.launchpad.net/nova/+spec/no- compute-fanout-to-scheduler, host_ip was also stored in DB. "nova hypervisor-show" will call hypervisor API to get compute node info and the info already include host_ip, it is better that this command can print host_ip out. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1229190/+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 1260891] Re: network_model tests mix IP() and FixedIP
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1260891 Title: network_model tests mix IP() and FixedIP Status in OpenStack Compute (Nova): Fix Released Bug description: network_model tests mix IP() and FixedIP To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1260891/+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 1240922] Re: VM don't resume after detaching volume
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1240922 Title: VM don't resume after detaching volume Status in OpenStack Compute (Nova): Fix Released Bug description: Hi guys, I have a suspend vm with an attached volume, if I detached volume while instance is in suspend state it can't be resumed properly. It happens with both Windows and Linux vm's. LibVirt error: 2494: error : qemuMonitorIORead:502 : Unable to read from monitor: Connection reset by peer Packets versioning in Ubuntu 12.04: ii libvirt-bin 1.0.2-0ubuntu11.13.04.2~cloud0 programs for the libvirt library ii libvirt-dev 1.0.2-0ubuntu11.13.04.2~cloud0 development files for the libvirt library ii libvirt0 1.0.2-0ubuntu11.13.04.2~cloud0 library for interfacing with different virtualization systems ii python-libvirt1.0.2-0ubuntu11.13.04.2~cloud0 libvirt Python bindings ii kvm 1:84+dfsg-0ubuntu16+1.0+noroms+0ubuntu14.10 dummy transitional package from kvm to qemu-kvm ii qemu-common 1.0+noroms-0ubuntu14.10 qemu common functionality (bios, documentation, etc) ii qemu-kvm 1.0+noroms-0ubuntu14.10 Full virtualization on i386 and amd64 hardware ii nova-common 1:2013.1.2-0ubuntu1~cloud0 OpenStack Compute - common files ii nova-compute 1:2013.1.2-0ubuntu1~cloud0 OpenStack Compute - compute node ii nova-compute-kvm 1:2013.1.2-0ubuntu1~cloud0 OpenStack Compute - compute node (KVM) ii python-nova 1:2013.1.2-0ubuntu1~cloud0 OpenStack Compute Python libraries ii python-novaclient 1:2.13.0-0ubuntu1~cloud0 client library for OpenStack Compute API To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1240922/+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 1262461] Re: resize auto-confirmation failed with nova-conductor because of db access in nova-compute
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1262461 Title: resize auto-confirmation failed with nova-conductor because of db access in nova-compute Status in OpenStack Compute (Nova): Fix Released Bug description: I can reproduce this bug in master and stable havana. this bug is similar to https://bugs.launchpad.net/nova/+bug/1158897 but this bug is cause by _reserve_quota_delta() method, which will need to access DB if quota delta is not empty, the trace log is: 2013-12-19 01:39:40.879 ERROR nova.compute [-] No db access allowed in nova-compute: File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 194, in main result = function(*args, **kwargs) File "/opt/stack/nova/nova/openstack/common/loopingcall.py", line 125, in _inner idle = self.f(*self.args, **self.kw) File "/opt/stack/nova/nova/service.py", line 314, in periodic_tasks return self.manager.periodic_tasks(ctxt, raise_on_error=raise_on_error) File "/opt/stack/nova/nova/manager.py", line 101, in periodic_tasks return self.run_periodic_tasks(context, raise_on_error=raise_on_error) File "/opt/stack/nova/nova/openstack/common/periodic_task.py", line 180, in run_periodic_tasks task(self, context) File "/opt/stack/nova/nova/compute/manager.py", line 4535, in _poll_unconfirmed_resizes migration=migration) File "/opt/stack/nova/nova/compute/api.py", line 199, in wrapped return func(self, context, target, *args, **kwargs) File "/opt/stack/nova/nova/compute/api.py", line 189, in inner return function(self, context, instance, *args, **kwargs) File "/opt/stack/nova/nova/compute/api.py", line 216, in _wrapped return fn(self, context, instance, *args, **kwargs) File "/opt/stack/nova/nova/compute/api.py", line 170, in inner return f(self, context, instance, *args, **kw) File "/opt/stack/nova/nova/compute/api.py", line 2158, in confirm_resize reservations = self._reserve_quota_delta(context, deltas) File "/opt/stack/nova/nova/compute/api.py", line 2238, in _reserve_quota_delta return QUOTAS.reserve(context, project_id=project_id, **deltas) File "/opt/stack/nova/nova/quota.py", line 1272, in reserve user_id=user_id) File "/opt/stack/nova/nova/quota.py", line 487, in reserve has_sync=True, project_id=project_id) File "/opt/stack/nova/nova/quota.py", line 354, in _get_quotas usages=False) File "/opt/stack/nova/nova/quota.py", line 264, in get_project_quotas project_quotas = db.quota_get_all_by_project(context, project_id) File "/opt/stack/nova/nova/db/api.py", line 1023, in quota_get_all_by_project return IMPL.quota_get_all_by_project(context, project_id) File "/opt/stack/nova/nova/cmd/compute.py", line 48, in __call__ stacktrace = "".join(traceback.format_stack()) 2013-12-19 01:39:40.879 ERROR nova.compute.manager [-] [instance: 4ffaabaf-a480-421f-a7a7-efd148d7c956] Error auto-confirming resize: nova-compute. Will retry later. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1262461/+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 1288926] Re: incorrect error code when rebooting a rebooting_hard guest
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1288926
Title:
incorrect error code when rebooting a rebooting_hard guest
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
This is using the latest nova from trunk. In our deployment, we had a
hypervisor go down and the tenant issued a hard reboot prior. When
attempting a reboot on a guest with the state HARD_REBOOT, nova
controller throws this error in it's logs and returns 'ERROR: The
server has either erred or is incapable of performing the requested
operation. (HTTP 500)' to the user:
2014-03-06 18:21:00,535 (routes.middleware): DEBUG middleware __call__
Matched POST /tenant1/servers/778032b2-469d-445e-abde-7b9b0b673324/action
2014-03-06 18:21:00,536 (routes.middleware): DEBUG middleware __call__ Route
path: '/{project_id}/servers/:(id)/action', defaults: {'action': u'action',
'controller': }
2014-03-06 18:21:00,536 (routes.middleware): DEBUG middleware __call__ Match
dict: {'action': u'action', 'controller': , 'project_id': u'tenant1', 'id':
u'778032b2-469d-445e-abde-7b9b0b673324'}
2014-03-06 18:21:00,537 (nova.api.openstack.wsgi): DEBUG wsgi _process_stack
Action: 'action', body: {"reboot": {"type": "SOFT"}}
2014-03-06 18:21:00,538 (nova.api.openstack.wsgi): DEBUG wsgi _process_stack
Calling method >
2014-03-06 18:21:00,747 (nova.api.openstack): ERROR __init__ _error Caught
error: Unexpected task state: expecting [None, 'rebooting'] but the actual
state is rebooting_hard
Traceback (most recent call last):
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/nova/api/openstack/__init__.py",
line 125, in __call__
return req.get_response(self.application)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/webob/request.py",
line 1320, in send
application, catch_exc_info=False)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/webob/request.py",
line 1284, in call_application
app_iter = application(self.environ, start_response)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/webob/dec.py",
line 144, in __call__
return resp(environ, start_response)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py",
line 598, in __call__
return self.app(env, start_response)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/webob/dec.py",
line 144, in __call__
return resp(environ, start_response)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/webob/dec.py",
line 144, in __call__
return resp(environ, start_response)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/routes/middleware.py",
line 131, in __call__
response = self.app(environ, start_response)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/webob/dec.py",
line 144, in __call__
return resp(environ, start_response)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/webob/dec.py",
line 130, in __call__
resp = self.call_func(req, *args, **self.kwargs)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/webob/dec.py",
line 195, in call_func
return self.func(req, *args, **kwargs)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/nova/api/openstack/wsgi.py",
line 925, in __call__
content_type, body, accept)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/nova/api/openstack/wsgi.py",
line 987, in _process_stack
action_result = self.dispatch(meth, request, action_args)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/nova/api/openstack/wsgi.py",
line 1074, in dispatch
return method(req=request, **action_args)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/nova/api/openstack/compute/servers.py",
line 1145, in _action_reboot
self.compute_api.reboot(context, instance, reboot_type)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/nova/compute/api.py",
line 199, in wrapped
return func(self, context, target, *args, **kwargs)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/nova/compute/api.py",
line 189, in inner
return function(self, context, instance, *args, **kwargs)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/nova/compute/api.py",
line 170, in inner
return f(self, context, instance, *args, **kw)
File
"/usr/local/gshare/csi-nova.venv/lib/python2.6/site-packages/nova/compute/api.py",
line 2073, in reboot
instance.save(expected_task_state=[None, task_states.REBOOTING])
File
"/usr/local/gshare/csi-nova.venv/lib/python2
[Yahoo-eng-team] [Bug 1258275] Re: Migration record for resize not cleared if exception is thrown during the resize
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1258275 Title: Migration record for resize not cleared if exception is thrown during the resize Status in OpenStack Compute (Nova): Fix Released Bug description: Testing on havana. prep_resize() calls resource tracker's resize_claim() which creates a migration record. This record is cleared during the rt.drop_resize_claim() from confirm_resize() or revert_resize(), however if an exception is thrown before one of these is called or after, but before they clean up the migration record, then the migration record will hang around in the database indefinitely. This results in an WARNING being logged every 60 seconds for every resize operation that ended with the instance in ERROR state as part of the update_available_resource period task, like the following: 2013-12-04 17:49:15.247 25592 WARNING nova.compute.resource_tracker [req-75e94365-1cca-4bca-92a7-19b2c62b9551 e4857f249aec4160bfa19c12eb805a96 a42cfb9766bf41869efab25703f5ce7b] [instance: 12d2551a-6403-4100-ba57-0995594c9c93] Instance not resizing, skipping migration. This message is because the resource tracker's _update_usage_from_migrations() logs this warning if a migration record for an instance is found, but the instance's current state is not in a resize state. These messages will be permanent in the logs even after the instance in question's state is reset, and even after a successful resize has occurred on that instance. There is no way to clean up the old migration record at this point. It seems like there should be some handling when an exception occurs during resize, finish_resize, confirm_resize, revert_resize, etc. that will drop the resize claim, so the claim and migration record do not persist indefinitely. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1258275/+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 1290975] Re: cells AttributeError with compute api methods using new object access style
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1290975 Title: cells AttributeError with compute api methods using new object access style Status in OpenStack Compute (Nova): Fix Released Bug description: The nova-cells service looks up instances locally before passing them to the local compute api, and only converts them to objects if the compute api method is explicitly listed in the run_compute_api method. There is in fact a FIXME around this process, but it appears to not have been addressed yet :) 2014-03-10 17:27:59.881 30193 ERROR nova.cells.messaging [req-3e27c8c0-6b3c-482d-bb9b-d638933ec949 10226892 5915610] Error processing message locally: 'dict' object has no attribute 'metadata' 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging Traceback (most recent call last): 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging File "/opt/rackstack/615.0/nova/lib/python2.6/site-packages/nova/cells/messaging.py", line 211, in _process_locally 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging resp_value = self.msg_runner._process_message_locally(self) 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging File "/opt/rackstack/615.0/nova/lib/python2.6/site-packages/nova/cells/messaging.py", line 1290, in _process_message_locally 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging return fn(message, **message.method_kwargs) 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging File "/opt/rackstack/615.0/nova/lib/python2.6/site-packages/nova/cells/messaging.py", line 706, in run_compute_api_method 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging return fn(message.ctxt, *args, **method_info['method_kwargs']) 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging File "/opt/rackstack/615.0/nova/lib/python2.6/site-packages/nova/compute/api.py", line 199, in wrapped 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging return func(self, context, target, *args, **kwargs) 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging File "/opt/rackstack/615.0/nova/lib/python2.6/site-packages/nova/compute/api.py", line 189, in inner 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging return function(self, context, instance, *args, **kwargs) 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging File "/opt/rackstack/615.0/nova/lib/python2.6/site-packages/nova/compute/api.py", line 170, in inner 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging return f(self, context, instance, *args, **kw) 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging File "/opt/rackstack/615.0/nova/lib/python2.6/site-packages/nova/compute/api.py", line 2988, in update_instance_metadata 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging orig = dict(instance.metadata) 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging AttributeError: 'dict' object has no attribute 'metadata' 2014-03-10 17:27:59.881 30193 TRACE nova.cells.messaging To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1290975/+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 1296502] Re: Needs passing the right project/user id to rollback methods in conductor.manager
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1296502 Title: Needs passing the right project/user id to rollback methods in conductor.manager Status in OpenStack Compute (Nova): Fix Released Bug description: The project/user id of the user is not passed to the quotas.rollback methods in conductor/manager.py if the instance is migrated by admin. See: http://git.openstack.org/cgit/openstack/nova/tree/nova/conductor/manager.py#n711 http://git.openstack.org/cgit/openstack/nova/tree/nova/conductor/manager.py#n741 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1296502/+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 1294102] Re: VMware: get_object_properties may not return any objects
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1294102 Title: VMware: get_object_properties may not return any objects Status in OpenStack Compute (Nova): Fix Released Bug description: 2014-03-18 05:32:28.164 CRITICAL nova.virt.vmwareapi.driver [req-a4d0920a-9ea0-4e3d-b1fe-561133e5b799 None None] In vmwareapi: _call_method (session=52325cb1-82c6-440a-e498-328cf8759e8e) 2014-03-18 05:32:28.164 TRACE nova.virt.vmwareapi.driver Traceback (most recent call last): 2014-03-18 05:32:28.164 TRACE nova.virt.vmwareapi.driver File "/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 835, in _call_method 2014-03-18 05:32:28.164 TRACE nova.virt.vmwareapi.driver return temp_module(*args, **kwargs) 2014-03-18 05:32:28.164 TRACE nova.virt.vmwareapi.driver File "/opt/stack/nova/nova/virt/vmwareapi/vim_util.py", line 170, in get_dynamic_property 2014-03-18 05:32:28.164 TRACE nova.virt.vmwareapi.driver property_dict = get_dynamic_properties(vim, mobj, type, [property_name]) 2014-03-18 05:32:28.164 TRACE nova.virt.vmwareapi.driver File "/opt/stack/nova/nova/virt/vmwareapi/vim_util.py", line 180, in get_dynamic_properties 2014-03-18 05:32:28.164 TRACE nova.virt.vmwareapi.driver if obj_content.objects: 2014-03-18 05:32:28.164 TRACE nova.virt.vmwareapi.driver AttributeError: 'NoneType' object has no attribute 'objects' 2014-03-18 05:32:28.164 TRACE nova.virt.vmwareapi.driver To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1294102/+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 1241665] Re: Mysql losing connection can result in running instance stuck in BUILD
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1241665 Title: Mysql losing connection can result in running instance stuck in BUILD Status in OpenStack Compute (Nova): Fix Released Bug description: I ran into a situation where an instance starting up and getting through the whole spawning process, was actually left in BUILD and never recovered: 2013-10-18 14:28:27.781 2566 DEBUG nova.virt.libvirt.driver [req-50162f97-7093-4373-a26c-8462f7077b61 57975150431487 50706474460443] [instance: f07617b9-9fd0-40ce-9459-71dba09566ee] Instance is running spawn /usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py:2072 2013-10-18 14:28:27.787 2566 INFO nova.virt.libvirt.driver [-] [instance: f07617b9-9fd0-40ce-9459-71dba09566ee] Instance spawned successfully. 2013-10-18 14:28:27.794 2566 DEBUG nova.compute.manager [req-50162f97-7093-4373-a26c-8462f7077b61 57975150431487 50706474460443] [instance: f07617b9-9fd0-40ce-9459-71dba09566ee] Checking state _get_power_state /usr/lib/python2.7/dist-packages/nova/compute/manager.py:801 2013-10-18 14:28:27.826 2566 WARNING nova.openstack.common.db.sqlalchemy.session [req-50162f97-7093-4373-a26c-8462f7077b61 57975150431487 50706474460443] Got mysql server has gone away: (2013, 'Lost connection to MySQL server during query') It looks like this query was never retried and the result is inconsistent. The instance itself is running, getting all the traffic, disk files are periodically checked by nova-compute, but the state is not changing. Restarting nova-compute doesn't correct the status either: 2013-10-18 15:13:51.635 21590 DEBUG nova.compute.manager [req-d438f27e-13a8-4a59-b238-66b2227e4415 None None] [instance: f07617b9-9fd0-40ce-9459-71dba09566ee] Checking state _get_power_state /usr/lib/python2.7/dist-packages/nova/compute/manager.py:801 2013-10-18 15:13:51.642 21590 DEBUG nova.compute.manager [req-d438f27e-13a8-4a59-b238-66b2227e4415 None None] [instance: f07617b9-9fd0-40ce-9459-71dba09566ee] Current state is 1, state in DB is 1. _init_instance /usr/lib/python2.7/dist-packages/nova/compute/manager.py:702 Mysql connection disappeared only for a moment - the next query reconnected / worked without any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1241665/+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 1294069] Re: XenAPI: Boot from volume without image_ref broken
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1294069
Title:
XenAPI: Boot from volume without image_ref broken
Status in devstack - openstack dev environments:
Fix Released
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
https://review.openstack.org/#/c/78194/ changed tempest to clear
image_ref for some BFV tests - in particular the
test_volume_boot_pattern
This now results in a "KeyError: 'disk_format'" exception from Nova
when using the XenAPI driver.
http://paste.openstack.org/show/73733/ is a nicer format of the below
- but might disappear!
2014-03-18 11:20:07.475 ERROR nova.compute.manager
[req-82096fe0-921a-4bc1-9c41-d0aafad4c923 TestVolumeBootPattern-581093620
TestVolumeBootPattern-1800543246] [instance:
2b047f24-675c-4921-8cf3-85584097f106] Error: 'disk_format'
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] Traceback (most recent call last):
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] File
"/opt/stack/nova/nova/compute/manager.py", line 1306, in _build_instance
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] set_access_ip=set_access_ip)
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] File
"/opt/stack/nova/nova/compute/manager.py", line 394, in decorated_function
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] return function(self, context, *args,
**kwargs)
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] File
"/opt/stack/nova/nova/compute/manager.py", line 1708, in _spawn
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] LOG.exception(_('Instance failed to
spawn'), instance=instance)
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] File
"/opt/stack/nova/nova/openstack/common/excutils.py", line 68, in __exit__
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] six.reraise(self.type_, self.value,
self.tb)
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] File
"/opt/stack/nova/nova/compute/manager.py", line 1705, in _spawn
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] block_device_info)
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] File
"/opt/stack/nova/nova/virt/xenapi/driver.py", line 236, in spawn
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] admin_password, network_info,
block_device_info)
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] File
"/opt/stack/nova/nova/virt/xenapi/vmops.py", line 357, in spawn
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] network_info, block_device_info,
name_label, rescue)
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] File
"/opt/stack/nova/nova/virt/xenapi/vmops.py", line 526, in _spawn
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106]
undo_mgr.rollback_and_reraise(msg=msg, instance=instance)
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] File "/opt/stack/nova/nova/utils.py",
line 812, in rollback_and_reraise
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] self._rollback()
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] File
"/opt/stack/nova/nova/openstack/common/excutils.py", line 68, in __exit__
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] six.reraise(self.type_, self.value,
self.tb)
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] File
"/opt/stack/nova/nova/virt/xenapi/vmops.py", line 501, in _spawn
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] disk_image_type =
determine_disk_image_type_step(undo_mgr)
2014-03-18 11:20:07.475 TRACE nova.compute.manager [instance:
2b047f24-675c-4921-8cf3-85584097f106] File
"/opt/stack/nova/nova/virt/xenapi/vmops.py", line 146, in inner
2014-03-18 11:20:07.
[Yahoo-eng-team] [Bug 1227321] Re: DBDuplicateEntry not being translated for DB2
** 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/1227321 Title: DBDuplicateEntry not being translated for DB2 Status in Cinder: New Status in OpenStack Image Registry and Delivery Service (Glance): New Status in Orchestration API (Heat): In Progress Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Neutron (virtual network service): Triaged Status in OpenStack Compute (Nova): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: The tempest.api.compute.keypairs.test_keypairs.test_create_keypair_with_duplicate_name test fails if you're running with a DB2 backend because the nova code is not currently translating the db integrity error if the backing engine is DB2 (ibm_db_sa) in nova.openstack.common.db.sqlalchemy.session._raise_if_duplicate_entry_error. Per full disclosure, nova is not claiming support for DB2 and there is a lot of work that would need to be done for that which my team is planning for icehouse and there is a blueprint here: https://blueprints.launchpad.net/nova/+spec/db2-database My team does have DB2 10.5 working with nova trunk but we have changes to the migration scripts to support that. Also, you have to run with the DB2 patch for sqlalchemy-migrate posted here: https://code.google.com/p/sqlalchemy-migrate/issues/detail?id=151 And you must run with the ibm-db/ibm-db-sa drivers: https://code.google.com/p/ibm-db/source/clones?repo=ibm-db-sa We're trying to get the sqlalchemy-migrate support for DB2 accepted in the icehouse timeframe but need to show the migrate maintainer that he can use the free express-c version of DB2 in ubuntu for the test backend. Anyway, having said all that, fixing the DBDuplicateEntry translation is part of the story so I'm opening a bug to track it and get the patch up to get the ball rolling. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1227321/+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 1254128] Re: VMware: NoneType object has no attribute 'state'
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1254128
Title:
VMware: NoneType object has no attribute 'state'
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
When running the Tempest test suite with VC Driver, one of the tests
failed because an instance failed to build. The error message seen in
the log was:
Traceback (most recent call last):
File "/opt/stack/nova/nova/compute/manager.py", line 1030, in
_build_instance
set_access_ip=set_access_ip)
File "/opt/stack/nova/nova/compute/manager.py", line 1439, in _spawn
LOG.exception(_('Instance failed to spawn'), instance=instance)
File "/opt/stack/nova/nova/compute/manager.py", line 1436, in _spawn
block_device_info)
File "/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 624, in spawn
admin_password, network_info, block_device_info)
File "/opt/stack/nova/nova/virt/vmwareapi/vmops.py", line 431, in spawn
upload_folder, upload_name + ".vmdk")):
File "/opt/stack/nova/nova/virt/vmwareapi/vmops.py", line 1523, in
_check_if_folder_file_exists
file_name)
File "/opt/stack/nova/nova/virt/vmwareapi/vmops.py", line 1486, in
_path_file_exists
if task_info.state in ['queued', 'running']:
AttributeError: 'NoneType' object has no attribute 'state'
This seems to be a rare intermittent failure as we were not able to
reproduce it again (this happened in VMware Minesweeper).
All screen log files are available here:
http://162.209.83.206/logs/52687/3/
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1254128/+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 1260575] Re: security group quota usage is wrong when the security group is deleted by admin
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1260575
Title:
security group quota usage is wrong when the security group is deleted
by admin
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
The quota usage for security group do not decrease when the security
group is deleted by admin.
Use the attachment script to reproduce, here is what i got:
+ new_user
+ ATTEMPT_ID=27449
+ TENANT_NAME=tanant-27449
++ awk '/id/{print $4}'
++ keystone tenant-create --name tanant-27449
+ TENANT_ID=8e37a593f3234b6582f9e436a1b044c4
+ USER_NAME=user-27449
++ awk '/id/{print $4}'
++ keystone user-create --name user-27449 --tenant-id
8e37a593f3234b6582f9e436a1b044c4 --pass secret
+ USER_ID=373d946636324d53ba6161e065f68572
+ as_user nova quota-show
+ OS_USERNAME=user-27449
+ OS_TENANT_NAME=tanant-27449
+ OS_PASSWORD=secret
+ nova quota-show
+-+---+
| Quota | Limit |
+-+---+
| instances | 10|
| cores | 20|
| ram | 51200 |
| floating_ips| 10|
| fixed_ips | -1|
| metadata_items | 128 |
| injected_files | 5 |
| injected_file_content_bytes | 10240 |
| injected_file_path_bytes| 255 |
| key_pairs | 100 |
| security_groups | 10|
| security_group_rules| 20|
+-+---+
+ (( i=0 ))
+ (( i<10 ))
+ echo '** Creating security group sec-27449-0 by user-27449 **'
** Creating security group sec-27449-0 by user-27449 **
+ as_user nova secgroup-create sec-27449-0 sec-27449-0
+ OS_USERNAME=user-27449
+ OS_TENANT_NAME=tanant-27449
+ OS_PASSWORD=secret
+ nova secgroup-create sec-27449-0 sec-27449-0
++-+-+
| Id | Name| Description |
++-+-+
| 39 | sec-27449-0 | sec-27449-0 |
++-+-+
+ (( i++ ))
+ (( i<10 ))
+ echo '** Creating security group sec-27449-1 by user-27449 **'
** Creating security group sec-27449-1 by user-27449 **
+ as_user nova secgroup-create sec-27449-1 sec-27449-1
+ OS_USERNAME=user-27449
+ OS_TENANT_NAME=tanant-27449
+ OS_PASSWORD=secret
+ nova secgroup-create sec-27449-1 sec-27449-1
++-+-+
| Id | Name| Description |
++-+-+
| 40 | sec-27449-1 | sec-27449-1 |
++-+-+
+ (( i++ ))
+ (( i<10 ))
+ echo '** Creating security group sec-27449-2 by user-27449 **'
** Creating security group sec-27449-2 by user-27449 **
+ as_user nova secgroup-create sec-27449-2 sec-27449-2
+ OS_USERNAME=user-27449
+ OS_TENANT_NAME=tanant-27449
+ OS_PASSWORD=secret
+ nova secgroup-create sec-27449-2 sec-27449-2
++-+-+
| Id | Name| Description |
++-+-+
| 41 | sec-27449-2 | sec-27449-2 |
++-+-+
+ (( i++ ))
+ (( i<10 ))
+ echo '** Creating security group sec-27449-3 by user-27449 **'
** Creating security group sec-27449-3 by user-27449 **
+ as_user nova secgroup-create sec-27449-3 sec-27449-3
+ OS_USERNAME=user-27449
+ OS_TENANT_NAME=tanant-27449
+ OS_PASSWORD=secret
+ nova secgroup-create sec-27449-3 sec-27449-3
++-+-+
| Id | Name| Description |
++-+-+
| 42 | sec-27449-3 | sec-27449-3 |
++-+-+
+ (( i++ ))
+ (( i<10 ))
+ echo '** Creating security group sec-27449-4 by user-27449 **'
** Creating security group sec-27449-4 by user-27449 **
+ as_user nova secgroup-create sec-27449-4 sec-27449-4
+ OS_USERNAME=user-27449
+ OS_TENANT_NAME=tanant-27449
+ OS_PASSWORD=secret
+ nova secgroup-create sec-27449-4 sec-27449-4
++-+-+
| Id | Name| Description |
++-+-+
| 43 | sec-27449-4 | sec-27449-4 |
++-+-+
+ (( i++ ))
+ (( i<10 ))
+ echo '** Creating security group sec-27449-5 by user-27449 **'
** Creating security group sec-27449-5 by user-27449 **
+ as_user nova secgroup-create sec-27449-5 sec-27449-5
+ OS_USERNAME=user-27449
+ OS_TENANT_NAME=tanant-27449
+ OS_PASSWORD=secret
+ nova secgroup-create sec-27449-5 sec-27449-5
++-+-+
| Id | Name| Description |
++-+-+
| 44 | sec-27449-5 | sec-27449-5 |
++-+-+
+ (( i++ ))
+ (( i<10 ))
+ echo '** Creating security group sec-27449-6
[Yahoo-eng-team] [Bug 1254320] Re: Network cache should not be refreshed for instances that are still building
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1254320 Title: Network cache should not be refreshed for instances that are still building Status in OpenStack Compute (Nova): Fix Released Bug description: heal_instance_info_cache is a periodic task which refreshes the network cache for instances on a host. Currently it processes instances which are still in the building state, which is both unnecessary (the build itself will update the cache when it completes) and can lead to a race condition; If the periodic task gets Null network information (likely as the instance is still being built) but then gets pre-empted by the build thread and updates the cache after the instance has finished build has finished then the cache is in effect cleared. Simply skipping instances in the building state avoids this situation. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1254320/+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 1285437] Re: HTTPNotFound response does not contain enough explanation
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1285437
Title:
HTTPNotFound response does not contain enough explanation
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
In each RESTful API, there are useful explanation messages for HTTPNotFound
response in the implementation.
However, some messages are not output to the response.
For example, the implementation of the pause action API contains "Server not
found" message for nonexistent server error, but now the message is not output
into the response like the following:
$ curl -i
'http://localhost:8774/v2//servers//action'
-X POST [..]" -d '{"pause": null}'
HTTP/1.1 404 Not Found
Content-Length: 78
Content-Type: application/json; charset=UTF-8
X-Compute-Request-Id: req-a5282f5e-7e59-48cf-a86b-fe2e34347a2f
Date: Thu, 27 Feb 2014 10:21:52 GMT
{"itemNotFound": {"message": "The resource could not be found.", "code": 404}}
$
When receiving the above message, client may consider "what is not found?
project, server, or action?"
so it is better to output right message into a response.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1285437/+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 1244203] Re: Evacuate operation should honor the enable_instance_password conf value
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1244203 Title: Evacuate operation should honor the enable_instance_password conf value Status in OpenStack Compute (Nova): Fix Released Bug description: Currently the Evacuate operation (enabled by the os-evacuate) extension always returns a generated (or user supplied) password, although not all hypervisors support password injection. For server create and rebuild and rescue operations the configuration option "enable_instance_password=False" can be used to suppress returning a meaningless and confusing password, and the evacuate operation should also honor this setting To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1244203/+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 1258380] Re: unimplemented get_floating_ips_by_fixed_address in neutronv2/api.py
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1258380 Title: unimplemented get_floating_ips_by_fixed_address in neutronv2/api.py Status in OpenStack Compute (Nova): Fix Released Bug description: get_floating_ips_by_fixed_address is currently hard coded to return an empty list in the nova neutron API. https://github.com/openstack/nova/blob/master/nova/network/neutronv2/api.py#L770 This is because of a change that was a work around for some issues back in the Folsom / Grizzly releases. https://github.com/openstack/nova/commit/c0709bdd82c83e16cab6ed854d2ef873eb775473 This should be implemented or removed if it isn't needed any longer (dead code) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1258380/+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 1293750] Re: Cells: AttributeError: 'dict' object has no attribute 'disable_terminate'
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1293750 Title: Cells: AttributeError: 'dict' object has no attribute 'disable_terminate' Status in OpenStack Compute (Nova): Fix Released Bug description: When a delete is issued for an instance that doesn't have a cell_name in the db, a delete is broadcast to all cells. As that message passes through the cells rpc layer the instance is converted from an object to a dict. This causes a problem when it gets to the cell since the delete methods expect to receive an object. 2014-03-13 15:21:49.717 31063 ERROR nova.cells.messaging [req-d2d5f4ea-4010-405a-b52a-8f19d3991498 10110789 5877036] Error processing message locally: 'dict' object has no attribute 'disable_terminate' 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging Traceback (most recent call last): 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging File "/opt/rackstack/615.4/nova/lib/python2.6/site-packages/nova/cells/messaging.py", line 211, in _process_locally 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging resp_value = self.msg_runner._process_message_locally(self) 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging File "/opt/rackstack/615.4/nova/lib/python2.6/site-packages/nova/cells/messaging.py", line 1291, in _process_message_locally 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging return fn(message, **message.method_kwargs) 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging File "/opt/rackstack/615.4/nova/lib/python2.6/site-packages/nova/cells/messaging.py", line 1101, in instance_delete_everywhere 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging self.compute_api.delete(message.ctxt, instance) 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging File "/opt/rackstack/615.4/nova/lib/python2.6/site-packages/nova/compute/api.py", line 199, in wrapped 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging return func(self, context, target, *args, **kwargs) 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging File "/opt/rackstack/615.4/nova/lib/python2.6/site-packages/nova/compute/api.py", line 189, in inner 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging return function(self, context, instance, *args, **kwargs) 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging File "/opt/rackstack/615.4/nova/lib/python2.6/site-packages/nova/compute/api.py", line 216, in _wrapped 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging return fn(self, context, instance, *args, **kwargs) 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging File "/opt/rackstack/615.4/nova/lib/python2.6/site-packages/nova/compute/api.py", line 170, in inner 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging return f(self, context, instance, *args, **kw) 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging File "/opt/rackstack/615.4/nova/lib/python2.6/site-packages/nova/compute/api.py", line 1710, in delete 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging self._delete_instance(context, instance) 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging File "/opt/rackstack/615.4/nova/lib/python2.6/site-packages/nova/compute/api.py", line 1700, in _delete_instance 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging task_state=task_states.DELETING) 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging File "/opt/rackstack/615.4/nova/lib/python2.6/site-packages/nova/compute/api.py", line 1395, in _delete 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging if instance.disable_terminate: 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging AttributeError: 'dict' object has no attribute 'disable_terminate' 2014-03-13 15:21:49.717 31063 TRACE nova.cells.messaging To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1293750/+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 1270811] Re: Wrong option is used in test_availability.py
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1270811
Title:
Wrong option is used in test_availability.py
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
I found a testcase bug in
nova/tests/api/openstack/compute/plugins/v3/test_availability_zone.py
def test_create_instance_with_availability_zone(self):
def create(*args, **kwargs):
self.assertIn('availability_zone', kwargs)
return old_create(*args, **kwargs)
old_create = compute_api.API.create
self.stubs.Set(compute_api.API, 'create', create)
image_href = '76fa36fc-c930-4bf3-8c8a-ea2a2420deb6'
flavor_ref = 'http://localhost/v3/flavors/3'
body = {
'server': {
'name': 'config_drive_test',
'image_ref': image_href,
'flavor_ref': flavor_ref,
'metadata': {
'hello': 'world',
'open': 'stack',
},
★ 'availability_zone': "nova",★
},
}
req = fakes.HTTPRequestV3.blank('/v3/servers')
req.method = 'POST'
req.body = jsonutils.dumps(body)
req.headers["content-type"] = "application/json"
admin_context = context.get_admin_context()
service1 = db.service_create(admin_context, {'host': 'host1_zones',
'binary': "nova-compute",
'topic': 'compute',
'report_count': 0})
agg = db.aggregate_create(admin_context,
{'name': 'agg1'}, {'availability_zone': 'nova'})★
db.aggregate_host_add(admin_context, agg['id'], 'host1_zones')
The correct request for availability-zone option is 'os-availability-
zone:availability_zone'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1270811/+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 1274294] Re: vmware section of nova.conf describes host_ip as url but is not
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1274294 Title: vmware section of nova.conf describes host_ip as url but is not Status in OpenStack Compute (Nova): Fix Released Bug description: In nova.conf, the host_ip of the vmware section describes it as being a URL. But the expected input is a hostname or IP address, not a URL. A URL is composed of a scheme, two colons, etc. See http://en.wikipedia.org/wiki/Uniform_resource_locator https://github.com/openstack/nova/blob/master/etc/nova/nova.conf.sample#L3265 [vmware] # # Options defined in nova.virt.vmwareapi.driver # # URL for connection to VMware ESX/VC host. (string value) #host_ip= # Username for connection to VMware ESX/VC host. (string # value) #host_username= # Password for connection to VMware ESX/VC host. (string # value) #host_password= Also here: https://github.com/openstack/nova/blob/master/nova/virt/vmwareapi/driver.py#L49 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1274294/+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 1272195] Re: Previous ip show twice after 'interface-attach'
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1272195 Title: Previous ip show twice after 'interface-attach' Status in OpenStack Compute (Nova): Fix Released Bug description: Hi team, I encounter this problem in the below situation: OS : Ubuntu Version : Icehouse 1. Normally boot a vm xianghui@xianghui:/opt/stack/nova$ nova list +--+--+-++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+--+-++-+--+ | 35cc6c7c-31b1-491a-8e0d-766a098fb8d9 | cirros_3 | ACTIVE | None | Running | private=10.0.0.5 | +--+--+-++-+--+ xianghui@xianghui:/opt/stack/nova$ neutron net-list +--+-++ | id | name| subnets | +--+-++ | 2d6842e2-b82c-4d5c-8601-7928ab85a8fd | private | 44d8d50a-197d-4f52-90c4-487495fdb8b5 10.0.0.0/24 | +--+-++ 2. Attach the instance with an interface xianghui@xianghui:/opt/stack/nova$ nova interface-attach cirros_3 --net-id=2d6842e2-b82c-4d5c-8601-7928ab85a8fd xianghui@xianghui:/opt/stack/nova$ nova list +--+--+-++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+--+-++-+--+ | 35cc6c7c-31b1-491a-8e0d-766a098fb8d9 | cirros_3 | ACTIVE | None | Running | private=10.0.0.5, 10.0.0.5, 10.0.0.6 | | fa79e7a9-a838-484b-b8a2-4447d4f5d6a0 | fedora-1 | SHUTOFF | None | Shutdown| private=10.0.0.3, 172.24.0.2 | | 97a3758f-9777-44cc-9035-ac95e57f8304 | fedora-2 | SHUTOFF | None | Shutdown| private=10.0.0.4 | +--+--+-++-+--+ 3. Above shows the previous ip twice until next update_info_cache() happens. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1272195/+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 1274317] Re: heal_instance_info_cache_interval config is not effective
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1274317 Title: heal_instance_info_cache_interval config is not effective Status in OpenStack Compute (Nova): Fix Released Bug description: There is configuration item in /etc/nova/nova.conf that controls how often the instance info should be updated. By default the value is 60 seconds. However, the current implementation only uses that value to prevent over clocked. Configure it to a different value in nova.conf does not has impact how often the task is executed. If I change the code in /usr/lib/python2.6/site- packages/nova/compute/manager.py with the spacing parameter, the configured value will be in action. Please fix this bug. @periodic_task.periodic_task(spacing=CONF.heal_instance_info_cache_interval) def _heal_instance_info_cache(self, context): To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1274317/+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 1271528] Re: libvirt._create_image is too large and not tested
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1271528 Title: libvirt._create_image is too large and not tested Status in OpenStack Compute (Nova): Fix Released Bug description: We need to split this method is several small and add tests. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1271528/+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 1275352] Re: test_migration_utils runs sqlite tests even if no sqlite configured
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1275352
Title:
test_migration_utils runs sqlite tests even if no sqlite configured
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
There are several jobs that only run if you have sqlite configured in
nova.tests.db.test_migration_utils but there are two which will run
and fail if you don't have sqlite configured:
==
ERROR:
nova.tests.db.test_migration_utils.TestMigrationUtils.test_check_shadow_table_with_unsupported_type
--
_StringException: pythonlogging:'': {{{INFO [nova.tests.db.test_migrations]
Creating DB2 schema nova.novatstu}}}
Traceback (most recent call last):
File "/root/nova-es/nova/tests/db/test_migration_utils.py", line 391, in
test_check_shadow_table_with_unsupported_type
engine = self.engines['sqlite']
KeyError: 'sqlite'
==
ERROR:
nova.tests.db.test_migration_utils.TestMigrationUtils.test_util_drop_unique_constraint_with_not_supported_sqlite_type
--
_StringException: pythonlogging:'': {{{INFO [nova.tests.db.test_migrations]
Creating DB2 schema nova.novatstu}}}
Traceback (most recent call last):
File "/root/nova-es/nova/tests/db/test_migration_utils.py", line 215, in
test_util_drop_unique_constraint_with_not_supported_sqlite_type
for i in xrange(0, len(values)):
UnboundLocalError: local variable 'values' referenced before assignment
Those should be skipped if sqlite isn't configured like the other
sqlite-specific tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1275352/+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 1276575] Re: some filter's info is missing in source/devref/filter_scheduler.rst
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1276575 Title: some filter's info is missing in source/devref/filter_scheduler.rst Status in OpenStack Compute (Nova): Fix Released Bug description: in doc/source/devref/filter_scheduler.rst, it describe the filters as reference DiskFilter NumInstancesFilter PciPassthroughFilter are missing and should be added (BTW, don't know whether it's proper to open a doc defect through bug here, let me know a better way if you have ,thanks) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1276575/+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 1279189] Re: delete or query an not exist snapshot raise exception more readable
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1279189 Title: delete or query an not exist snapshot raise exception more readable Status in OpenStack Compute (Nova): Fix Released Bug description: In V2 API layer code, it would be better if we raise exception instead of return it try: self.volume_api.delete_snapshot(context, id) except exception.NotFound: return exc.HTTPNotFound() > use raise instead of return To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1279189/+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 1280306] Re: check if export is already mounted before mounting it (LibvirtNFSVolumeDriver)
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1280306
Title:
check if export is already mounted before mounting it
(LibvirtNFSVolumeDriver)
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
At the moment there is no check in _mount_nfs if the export is already
mounted. It will be tried to mount the export and if the export is
already mounted an exception is thrown following in a WARNING message
that the export is already mounted. This pollutes the logs with
useless WARNING messages and if there is a real exception (for example
the NFS export is not reachable) we only have a WARNING in the logs.
def _mount_nfs(self, mount_path, nfs_share, options=None, ensure=False):
"""Mount nfs export to mount path."""
utils.execute('mkdir', '-p', mount_path)
# Construct the NFS mount command.
nfs_cmd = ['mount', '-t', 'nfs']
if CONF.libvirt.nfs_mount_options is not None:
nfs_cmd.extend(['-o', CONF.libvirt.nfs_mount_options])
if options is not None:
nfs_cmd.extend(options.split(' '))
nfs_cmd.extend([nfs_share, mount_path])
try:
utils.execute(*nfs_cmd, run_as_root=True)
except processutils.ProcessExecutionError as exc:
if ensure and 'already mounted' in exc.message:
LOG.warn(_("%s is already mounted"), nfs_share)
else:
raise
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1280306/+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 1275772] Re: Missing "raise" statement in the Hyper-V driver when checking the config driver format
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1275772 Title: Missing "raise" statement in the Hyper-V driver when checking the config driver format Status in OpenStack Compute (Nova): Fix Released Bug description: There's a missing raise statement when checking the ConfigDrive format: https://github.com/openstack/nova/blob/master/nova/virt/hyperv/vmops.py#L283 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275772/+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 1279317] Re: xen: agent tests take longer than 15 secs
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1279317
Title:
xen: agent tests take longer than 15 secs
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
gkotton@ubuntu:~/nova$ tox nova.tests.virt.xenapi.test_xenapi
py26 create: /home/gkotton/nova/.tox/py26
ERROR: InterpreterNotFound: python2.6
py27 develop-inst-nodeps: /home/gkotton/nova
py27 runtests: commands[0] | python -m nova.openstack.common.lockutils python
setup.py test --slowest --testr-args=nova.tests.virt.xenapi.test_xenapi
[pbr] Excluding argparse: Python 2.6 only dependency
running test
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \
${PYTHON:-python} -m subunit.run discover -t ./ ./nova/tests --list
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \
${PYTHON:-python} -m subunit.run discover -t ./ ./nova/tests --load-list
/tmp/tmp349WwU
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \
${PYTHON:-python} -m subunit.run discover -t ./ ./nova/tests --load-list
/tmp/tmpccaidD
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \
${PYTHON:-python} -m subunit.run discover -t ./ ./nova/tests --load-list
/tmp/tmpMvMcYb
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \
${PYTHON:-python} -m subunit.run discover -t ./ ./nova/tests --load-list
/tmp/tmpzJ2QHG
Ran 201 (+199) tests in 16.446s (+0.396s)
PASSED (id=350)
Slowest Tests
Test id
Runtime (s)
---
---
nova.tests.virt.xenapi.test_xenapi.XenAPIVMTestCase.test_spawn_agent_upgrade_fails_silently
16.223
nova.tests.virt.xenapi.test_xenapi.XenAPIVMTestCase.test_spawn_fails_agent_not_implemented
16.222
nova.tests.virt.xenapi.test_xenapi.XenAPIVMTestCase.test_spawn_fails_with_agent_bad_return
16.034
nova.tests.virt.xenapi.test_xenapi.XenAPIAggregateTestCase.test_add_aggregate_host_raise_err
1.116
nova.tests.virt.xenapi.test_xenapi.XenAPIVMTestCase.test_maintenance_mode
0.297
nova.tests.virt.xenapi.test_xenapi.XenAPIMigrateInstance.test_migrate_disk_and_power_off
0.277
nova.tests.virt.xenapi.test_xenapi.XenAPIVMTestCase.test_spawn_vlanmanager
0.195
nova.tests.virt.xenapi.test_xenapi.XenAPIAggregateTestCase.test_remote_master_non_empty_pool
0.179
nova.tests.virt.xenapi.test_xenapi.XenAPIMigrateInstance.test_migrate_disk_and_power_off_with_zero_gb_old_and_new_works
0.179
nova.tests.virt.xenapi.test_xenapi.XenAPIDom0IptablesFirewallTestCase.test_static_filters
0.171
py33 create: /home/gkotton/nova/.tox/py33
ERROR: InterpreterNotFound: python3.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1279317/+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 1279739] Re: nova.cmd.rpc_zmq_receiver:main is missing
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1279739 Title: nova.cmd.rpc_zmq_receiver:main is missing Status in devstack - openstack dev environments: Confirmed Status in OpenStack Compute (Nova): Fix Released Status in Messaging API for OpenStack: Invalid Bug description: I am trying to run devstack with zeromq, but the zeromq failed. al/bin/nova-rpc-zmq-receiver & echo $! >/opt/stack/status/stack/zeromq.pid; fg || echo "zeromq failed to start" | tee "/opt/stack/status/stack/zeromq.failure" [1] 25102 cd /opt/stack/nova && /usr/local/bin/nova-rpc-zmq-receiver Traceback (most recent call last): File "/usr/local/bin/nova-rpc-zmq-receiver", line 6, in from nova.cmd.rpc_zmq_receiver import main ImportError: No module named rpc_zmq_receiver zeromq failed to start I found at https://github.com/openstack/nova/blob/master/setup.cfg: nova-rpc-zmq-receiver = nova.cmd.rpc_zmq_receiver:main but at https://github.com/openstack/nova/tree/master/nova/cmd: we have no rpc_zmq_receiver module at all. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1279739/+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 1279300] Re: detach boot device volume without warning
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1279300 Title: detach boot device volume without warning Status in OpenStack Compute (Nova): Fix Released Bug description: If I use block_device_mapping_v2 api to set a backend volume as boot device for instance. The instance will be launched by this remote volume successfully. But, in such case, we can also use detach api to force this boot device being detached. So, when we do it, the guestOS of this instance would be damaged, and the whole system would not work normally if do a I/O operation. It seems can not resume. I think we should give a warning for user at least or even forbiden this operation. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1279300/+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 1280363] Re: Replace exception re-raises with excutils.save_and_reraise_exception() in the Hyper-V driver
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1280363 Title: Replace exception re-raises with excutils.save_and_reraise_exception() in the Hyper-V driver Status in OpenStack Compute (Nova): Fix Released Bug description: A few methods of the Hyper-V driver ops classes use a catch / raise pattern that replaces original exceptions with specific domain exceptions inherited from vmutils.HyperVUtilsException(). The original exception is thus masqueraded and trackable only by analysing the logs. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1280363/+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 1281324] Re: vm_state ERROR vm undeletable if first delete attempt does not succeed.
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1281324 Title: vm_state ERROR vm undeletable if first delete attempt does not succeed. Status in OpenStack Compute (Nova): Fix Released Bug description: We had a neutron failure in our cloud, which lead to a bunch of VM's in state ERROR.. we've repaired neutron but now we can't delete: ERROR: Cannot 'forceDelete' while instance is in vm_state error (HTTP 409) (Request-ID: req-1c4a88c3-4ea1-45a8-b987-629a69b4af06) or stop/start nova stop 01199ed9-b3c3-4ee9-a482-bdfdc7347ce1 ERROR: Instance 01199ed9-b3c3-4ee9-a482-bdfdc7347ce1 in task_state deleting. Cannot stop while the instance is in this state. (HTTP 400) (Request-ID: req-18d58b8d-b360-4b37-b671-34624a6dade4) (ci-overcloud)robertc@lifelesshp:~/work$ nova start 01199ed9-b3c3-4ee9-a482-bdfdc7347ce1 ERROR: Instance 01199ed9-b3c3-4ee9-a482-bdfdc7347ce1 in vm_state error. Cannot start while the instance is in this state. (HTTP 400) (Request-ID: req-b46c0ee6-8ed8-41c3-b400-72f76429209a) normal 'delete' doesn't error.. but doesn't delete the VM either. The problem is that nothing is cancelling the task state, so the VMs are staying stuck indefinitely. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1281324/+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 1281904] Re: Wrong exception type HTTPBadRequest is raised
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1281904
Title:
Wrong exception type HTTPBadRequest is raised
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
When user without admin permission wants to get a list of servers
which are in 'deleted' state, currently it raises HTTPBadRequest.
The code is:
231 if search_opts.get("vm_state") == ['deleted']:
232 if context.is_admin:
233 search_opts['deleted'] = True
234 else:
235 msg = _("Only administrators may list deleted instances")
236 raise exc.HTTPBadRequest(explanation=msg)
This should be changed to HTTPForbidden exception.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1281904/+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 1286006] Re: Static injection pure IPv6 address will throw exception in vmware driver
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1286006 Title: Static injection pure IPv6 address will throw exception in vmware driver Status in OpenStack Compute (Nova): Fix Released Bug description: With use vmware center dirver in nova, and set flat_injected = True to static inject pure IPv6, from code, this function still not be implemented, but it shoud not throw excepption, when the network_info is one pure IPv6 information, it will impact nova compute service work. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1286006/+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 1285209] Re: [libvirt] nfs and glusterfs volume drivers don't unmount their shares when detaching
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1285209 Title: [libvirt] nfs and glusterfs volume drivers don't unmount their shares when detaching Status in OpenStack Compute (Nova): Fix Released Bug description: When attaching volumes from NFS or GlusterFS backends, nova mounts the share in a temporary directory, this is reused when attaching another volume from the same share so there is no need to mount it several times. On the other hand, when disconnecting those volumes nova doesn't even try to unmount the share which may remain mounted and unused there. To clean up after detach, nova could at least try to umount the shares. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1285209/+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 1281973] Re: Compute manager ignores image_meta from api when booting an instance
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1281973 Title: Compute manager ignores image_meta from api when booting an instance Status in OpenStack Compute (Nova): Fix Released Bug description: When booting an instance, in the API layer, we get the image to be used for this instance or, if the instance is booted from a volume, the image metadata attached to the volume (if present). This allows us to know a bit more of the volume through the inherited properties of the image from where it was created. This same image metadata is then passed to the selected compute manager for processing the request. Right now the compute manager completely ignores the image metadata and tries to obtain it only if the instance is booted from an image. This prevents us from obtaining some properties present in the volume that might be needed while starting the instance (think about the hw_disk_bus). Besides, it requires of an extra call to glance that can be avoided. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1281973/+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 1285158] Re: deallocating network not updating database
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1285158
Title:
deallocating network not updating database
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
An instance that fails to spawn (say due to corrupt image download) on
a compute node will call 'deallocate_for_instance' but does not update
the database to remove the networking information.
from compute manager log for instance failing to spawn:
AUDIT nova.compute.manager [req-165b21e5-f727-4d2e-98f3-1a5f0039595e
10546644733724 10540146451709] [instance: 6b28052e-3488-404d-9626-bb42f51ae98f]
Starting instance...
...
AUDIT nova.compute.claims [req-165b21e5-f727-4d2e-98f3-1a5f0039595e
10546644733724 10540146451709] [instance: 6b28052e-3488-404d-9626-bb42f51ae98f]
Claim successful
...
DEBUG nova.network.neutronv2.api [-] [instance:
6b28052e-3488-404d-9626-bb42f51ae98f] Successfully created port:
38b34c17-e228-4d79-9248-c642a42959a8 _create_port
/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py:172
...
2014-02-11 13:20:25.257 24500 DEBUG nova.network.api [-] Updating cache with
info: [VIF({'ovs_interfaceid': None, 'network': Network({'bridge': None,
'subnets': [Subnet({'ips': [FixedIP({'meta': {}, 'version': 4, 'type': 'fixed',
'floating_ips': [], 'address': u'10.100.0.2'})], 'version': 4, 'meta':
{'dhcp_server': u'10.100.0.3'}, 'dns': [], 'routes': [], 'cidr':
u'10.100.0.0/16', 'gateway': IP({'meta': {}, 'version': 4, 'type': 'gateway',
'address': u'10.100.0.1'})})], 'meta': {'injected': False, 'tenant_id':
u'10540146451709'}, 'id': u'09030eb3-bca3-4df4-a5f9-721b6bd5d599', 'label':
u'private'}), 'devname': u'tap38b34c17-e2', 'qbh_params': None, 'meta': {},
'address': u'fa:16:3e:22:7c:aa', 'type': u'other', 'id':
u'38b34c17-e228-4d79-9248-c642a42959a8', 'qbg_params': None})]
update_instance_cache_with_nw_info
/usr/lib/python2.7/dist-packages/nova/network/api.py:72
...
ERROR nova.compute.manager [req-165b21e5-f727-4d2e-98f3-1a5f0039595e
10546644733724 10540146451709] [instance: 6b28052e-3488-404d-9626-bb42f51ae98f]
Instance failed to spawn
TRACE nova.compute.manager [instance: 6b28052e-3488-404d-9626-bb42f51ae98f]
IOError: [Errno 32] Corrupt image download. Checksum was
65327d2b03e53805a3354233b09aee62 expected 82d98abd651173e8c3e74b02d811f8a1
AUDIT nova.compute.manager [req-165b21e5-f727-4d2e-98f3-1a5f0039595e
10546644733724 10540146451709] [instance: 6b28052e-3488-404d-9626-bb42f51ae98f]
Terminating instance
DEBUG nova.compute.manager [req-165b21e5-f727-4d2e-98f3-1a5f0039595e
10546644733724 10540146451709] [instance: 6b28052e-3488-404d-9626-bb42f51ae98f]
Deallocating network for instance _deallocate_network
/usr/lib/python2.7/dist-packages/nova/compute/manager.py:1518
When the instance successfully spawns on another compute node
AUDIT nova.compute.manager [req-165b21e5-f727-4d2e-98f3-1a5f0039595e
10546644733724 10540146451709] [instance: 6b28052e-3488-404d-9626-bb42f51ae98f]
Starting instance...
...
AUDIT nova.compute.claims [req-165b21e5-f727-4d2e-98f3-1a5f0039595e
10546644733724 10540146451709] [instance: 6b28052e-3488-404d-9626-bb42f51ae98f]
Claim successful
...
DEBUG nova.network.neutronv2.api [-] [instance:
6b28052e-3488-404d-9626-bb42f51ae98f] Successfully created port:
59f61b81-3314-4bdd-b455-2611af6653c2 _create_port
/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py:172
...
2014-02-11 13:21:20.491 63160 DEBUG nova.network.api [-] Updating cache with
info: [VIF({'ovs_interfaceid': None, 'network': Network({'bridge': None,
'subnets': [Subnet({'ips': [FixedIP({'meta': {}, 'version': 4, 'type':
u'fixed', 'floating_ips': [], 'address': u'10.100.0.2'})], 'version': 4,
'meta': {u'dhcp_server': u'10.100.0.3'}, 'dns': [], 'routes': [], 'cidr':
u'10.100.0.0/16', 'gateway': IP({'meta': {}, 'version': 4, 'type': u'gateway',
'address': u'10.100.0.1'})})], 'meta': {u'injected': False, u'tenant_id':
u'10540146451709'}, 'id': u'09030eb3-bca3-4df4-a5f9-721b6bd5d599', 'label':
u'private'}), 'devname': u'tap38b34c17-e2', 'qbh_params': None, 'meta': {},
'address': u'fa:16:3e:22:7c:aa', 'type': u'other', 'id':
u'38b34c17-e228-4d79-9248-c642a42959a8', 'qbg_params': None}),
VIF({'ovs_interfaceid': None, 'network': Network({'bridge': None, 'subnets':
[Subnet({'ips': [FixedIP({'meta': {}, 'version': 4, 'type': 'fixed',
'floating_ips': [], 'address': u'10.100.0.4'})], 'version
': 4, 'meta': {'dhcp_server': u'10.100.0.3'}, 'dns': [], 'routes': [], 'cidr':
u'10.100.0.0/16', 'gateway': IP({'meta': {}, 'version': 4, 'type': 'gateway',
'address': u'10.100.0.1'})})], 'meta': {'injected': False, 'tenant_id':
u'10540146451709'}, 'id': u'09030eb3-bca3-4df4-a5f9-721b6bd5d599', 'label':
u'private'}), 'devname': u'tap59f61b81-33', 'qbh_params':
[Yahoo-eng-team] [Bug 1282393] Re: inconsistent documentation of how to run unit tests
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1282393 Title: inconsistent documentation of how to run unit tests Status in OpenStack Compute (Nova): Fix Released Bug description: http://docs.openstack.org/developer/nova/devref/unit_tests.html #running-the-tests says to use run_tests.sh; https://github.com/openstack/nova/blob/master/HACKING.rst says to use tox. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1282393/+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 1285482] Re: There is not any API sample file for "unshelve a server" API
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1285482 Title: There is not any API sample file for "unshelve a server" API Status in OpenStack Compute (Nova): Fix Released Bug description: Now there is not any API sample file of "unshelve a server" API, and OpenStack API documentation[1] also does not describe the API. [1]: http://api.openstack.org/api-ref-compute-ext.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1285482/+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 1288636] Re: Deleted flavor influences new flavor with same id in 'flavor-show' under psql
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1288636 Title: Deleted flavor influences new flavor with same id in 'flavor-show' under psql Status in OpenStack Compute (Nova): Fix Released Bug description: When you create a new flavor with a deleted flavorid, the result in mysql will show the new record. That's OK. But if you operate these commands under psql, you'll find the result will always be the old deleted one. That means, the flavorid will always be occupied by the first record who use this flavorid under psql, even if this flavor has already been deleted. More info can be found at here: http://paste.openstack.org/show/72752/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1288636/+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 1292284] Re: A few tests from test_sqlalchemy_utils fail on SQLAlchemy 0.9.x
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1292284 Title: A few tests from test_sqlalchemy_utils fail on SQLAlchemy 0.9.x Status in OpenStack Compute (Nova): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Committed Bug description: When SQLAlchemy 0.9.x releases are used, some tests from test_sqlalchemy_utils module fail on assertRaises(). This is caused by the fact that we except SQLAlchemy to raise exceptions when reflecting SQLite custom data types from existing DB schema. This was true for SA 0.7.x and 0.8.x branches, but is fixed in 0.9.x releases. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1292284/+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 1290362] Re: HPET timer not supported on non-x86 targets
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1290362 Title: HPET timer not supported on non-x86 targets Status in OpenStack Compute (Nova): Fix Released Bug description: High Precision Event Timer is x86 specific hardware design to replace older PIT and RTC. Also, '-no-hpet' option makes qemu to fail on non x86 targets. he libvirt's xml generated has the following: The error produced... libvirtError: internal error: process exited while connecting to monitor: Option no-hpet not supported for this target For non x86 arch, this bug is affecting test_server_basicops test in Tempest: tempest.scenario.test_server_basic_ops.TestServerBasicOps.test_server_basicops No valid host was found. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1290362/+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 1289993] Re: dhcp_options_enabled used in comment
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1289993
Title:
dhcp_options_enabled used in comment
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
https://review.openstack.org/#/c/58089/ removes check
CONF.dhcp_options_enabled from nova but it is still used in the help
string in nova/virt/baremetal/pxe.py:
cfg.StrOpt('pxe_bootfile_name',
help='This gets passed to Neutron as the bootfile dhcp '
'parameter when the dhcp_options_enabled is set.',
default='pxelinux.0'),
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1289993/+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 1292285] Re: equal_any() DB API helper produces incorrect SQL query
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1292285
Title:
equal_any() DB API helper produces incorrect SQL query
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
Given an attribute name and a list of values equal_any() is meant to
produce a WHERE clause which returns rows for which the column
(denoted by an attribute of an SQLAlchemy model) is equal to ANY of
passed values that involves using of SQL OR operator. In fact, AND
operator is used to combine equality expressions.
E.g. for a model:
class Instance(BaseModel):
__tablename__ = 'instances'
id = sa.Column('id', sa.Integer, primary_key=True)
...
task_state = sa.Column('task_state', sa.String(30))
using of equal_any():
q = model_query(context, Instance).
constraint = Constraint({'task_state': equal_any('error', 'deleting')})
q = constraint.apply(Instance, q)
will produce:
SELECT * from instances
WHERE task_state = 'error' AND task_state = 'deleting'
instead of expected:
SELECT * from instances
WHERE task_state = 'error' OR task_state = 'deleting'
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1292285/+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 1293539] Re: NeutronV2 API is missing associate method.
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1293539 Title: NeutronV2 API is missing associate method. Status in OpenStack Compute (Nova): Fix Released Bug description: Using nova network-associate-host w/neutron an error is returned because associate method is not defined in NeutronV2API. Also, NotImplementedError is not being handled. 2014-03-17 09:12:15.783 TRACE nova.api.openstack action_result = self.dispatch(meth, request, action_args) 2014-03-17 09:12:15.783 TRACE nova.api.openstack File "/opt/stack/nova/nova/api/openstack/wsgi.py", line 1070, in dispatch 2014-03-17 09:12:15.783 TRACE nova.api.openstack return method(req=request, **action_args) 2014-03-17 09:12:15.783 TRACE nova.api.openstack File "/opt/stack/nova/nova/api/openstack/compute/contrib/networks_associate.py", line 60, in _associate_host 2014-03-17 09:12:15.783 TRACE nova.api.openstack self.network_api.associate(context, id, 2014-03-17 09:12:15.783 TRACE nova.api.openstack AttributeError: 'API' object has no attribute 'associate' 2014-03-17 09:12:15.783 TRACE nova.api.openstack - To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1293539/+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 1290903] Re: xenapi: test_rescue incorrectly verifies original swap wasn't attached
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1290903
Title:
xenapi: test_rescue incorrectly verifies original swap wasn't attached
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
The code currently does:
vdi_uuids = []
for vbd_uuid in rescue_vm["VBDs"]:
vdi_uuids.append(xenapi_fake.get_record('VBD', vbd_uuid)["VDI"])
self.assertNotIn("swap", vdi_uuids)
vdi_uuids is a list of uuid references. "swap" will never match a
uuid, so that test will always be true, even if the code is broken.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1290903/+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 1287844] Re: VMware: raise an error for invalid disk_format
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1287844 Title: VMware: raise an error for invalid disk_format Status in OpenStack Compute (Nova): Fix Released Bug description: We need to raise an exception for an disk_format that is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1287844/+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 1292997] Re: nova.volume.cinder.API incorrectly derives from nova.db.base.Base
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1292997 Title: nova.volume.cinder.API incorrectly derives from nova.db.base.Base Status in OpenStack Compute (Nova): Fix Released Bug description: For some reason, nova.volume.cinder.API derives from nova.db.base.Base, which looks like this (in its entirety): class Base(object): """DB driver is injected in the init method.""" def __init__(self, db_driver=None): super(Base, self).__init__() if not db_driver: db_driver = CONF.db_driver self.db = importutils.import_module(db_driver) # pylint: disable=C0103 I checked and nova.volume.cinder.API makes no reference at all to self.db, therefore unless I am mistaken, there's no reason for this inheritance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1292997/+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 1293298] Re: Don't import guestfs directly
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1293298 Title: Don't import guestfs directly Status in OpenStack Compute (Nova): Fix Released Bug description: Library guestfs is not in requirements file, but is imported directly in nova/virt/disk/vfs/guestfs.py. That conflicts with global variable guestfs, leads out one more time import and shadow issue, so remove it from import group. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1293298/+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 1289164] Re: FloatingIpNotFoundForHost isn't handled when showing floating ips by host
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1289164 Title: FloatingIpNotFoundForHost isn't handled when showing floating ips by host Status in OpenStack Compute (Nova): Fix Released Bug description: When showing the floating ips by host, I got this error. $ nova floating-ip-bulk-list --host xxx ERROR: The resource could not be found. (HTTP 404) (Request-ID: req-9a17c8cf-b1cd-4092-b853-7e24126db7e8) and in the nova-api log I got this message: 014-03-05 04:01:40.270 ERROR nova.api.openstack [req-9a17c8cf-b1cd-4092-b853-7e24126db7e8 admin demo] Caught error: Floating ip not found for host xxx. 2014-03-05 04:01:40.270 TRACE nova.api.openstack Traceback (most recent call last): 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/opt/stack/nova/nova/api/openstack/__init__.py", line 125, in __call__ 2014-03-05 04:01:40.270 TRACE nova.api.openstack return req.get_response(self.application) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1296, in send 2014-03-05 04:01:40.270 TRACE nova.api.openstack application, catch_exc_info=False) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1260, in call_application 2014-03-05 04:01:40.270 TRACE nova.api.openstack app_iter = application(self.environ, start_response) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2014-03-05 04:01:40.270 TRACE nova.api.openstack return resp(environ, start_response) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py", line 598, in __call__ 2014-03-05 04:01:40.270 TRACE nova.api.openstack return self.app(env, start_response) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2014-03-05 04:01:40.270 TRACE nova.api.openstack return resp(environ, start_response) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2014-03-05 04:01:40.270 TRACE nova.api.openstack return resp(environ, start_response) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/usr/lib/python2.7/dist-packages/routes/middleware.py", line 131, in __call__ 2014-03-05 04:01:40.270 TRACE nova.api.openstack response = self.app(environ, start_response) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2014-03-05 04:01:40.270 TRACE nova.api.openstack return resp(environ, start_response) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__ 2014-03-05 04:01:40.270 TRACE nova.api.openstack resp = self.call_func(req, *args, **self.kwargs) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func 2014-03-05 04:01:40.270 TRACE nova.api.openstack return self.func(req, *args, **kwargs) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/opt/stack/nova/nova/api/openstack/wsgi.py", line 929, in __call__ 2014-03-05 04:01:40.270 TRACE nova.api.openstack content_type, body, accept) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/opt/stack/nova/nova/api/openstack/wsgi.py", line 991, in _process_stack 2014-03-05 04:01:40.270 TRACE nova.api.openstack action_result = self.dispatch(meth, request, action_args) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/opt/stack/nova/nova/api/openstack/wsgi.py", line 1078, in dispatch 2014-03-05 04:01:40.270 TRACE nova.api.openstack return method(req=request, **action_args) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/opt/stack/nova/nova/api/openstack/compute/contrib/floating_ips_bulk.py", line 48, in show 2014-03-05 04:01:40.270 TRACE nova.api.openstack return self._get_floating_ip_info(context, id) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/opt/stack/nova/nova/api/openstack/compute/contrib/floating_ips_bulk.py", line 57, in _get_floating_ip_info 2014-03-05 04:01:40.270 TRACE nova.api.openstack floating_ips = db.floating_ip_get_all_by_host(context, host) 2014-03-05 04:01:40.270 TRACE nova.api.openstack File "/opt/stack/nova/nova/db/api.py", line 356, in floating_ip_get_all_by_host 2014-03-05 04:01:40.270 TRACE nova.api.openstack return IMPL.floating_ip_get_all_by_host(context, host) 2014-03-05 04:01:40.270 TRA
[Yahoo-eng-team] [Bug 1288661] Re: log messages typos in rebuild_instance function
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1288661
Title:
log messages typos in rebuild_instance function
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
one simple log typos in compute/manager.py rebuild_instance function.
else:
image_ref = orig_image_ref = instance.image_ref
LOG.info(_("disk not on shared storagerebuilding from:"
" '%s'") % str(image_ref))
should change to
LOG.info(_("disk not on shared storage, rebuilding from:"
" '%s'") % str(image_ref))
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1288661/+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 1290487] Re: Libvirt native thread used for "forbidden" purposes
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1290487 Title: Libvirt native thread used for "forbidden" purposes Status in OpenStack Compute (Nova): Fix Released Bug description: In the nova.virt.libvirt.driver.LibvirtDriver. _get_new_connection method two different libvirt event handlers are registered, one for lifecycle events (_event_lifecycle_callback) and one for connection events (_close_callback). These callbacks are called by a native thread that is continually calling libvirt.virEventRunDefaultImpl() in the _native_thread method; the latter method's Docstring contains the following note: This is a native thread which runs the default libvirt event loop implementation. This processes any incoming async events from libvirtd and queues them for later dispatch. This thread is only permitted to use libvirt python APIs, and the driver.queue_event method. In particular any use of logging is forbidden, since it will confuse eventlet's greenthread integration while this rule is adhered to by the _event_lifecycle_callback method, it is violated by _close_callback (the other callback) because it calls the _set_host_enabled method which, among other things, writes to the log. The _close_callback method needs to be altered so that it does not execute any logic that may interfere with eventlet's greenthread integration. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1290487/+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 1294238] Re: default of vnc_port range start seems not to be 5900, but 9100
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1294238 Title: default of vnc_port range start seems not to be 5900, but 9100 Status in OpenStack Compute (Nova): Fix Released Bug description: Description of problem: In the nova conf, there is: # VNC starting port (integer value) #vnc_port=5900 Which means the default value is 5900, but it is not so. with this configuration, vmware VMs seems to have ports >=9100 Version-Release number of selected component (if applicable): openstack-nova-compute-2013.2.2-2.el6ost.noarch How reproducible: Steps to Reproduce: 1. make sure the vnc_port under vmware is unset 2. restart nova-compute 3. boot the VM 4. On the ESXi: ~ # grep vnc /vmfs/volumes/shared/1f9f6326-18bd-4972-8a59-5c268dc28b53/*.vmx RemoteDisplay.vnc.enabled = "true" RemoteDisplay.vnc.port = "9129" 5. openstack-config --set /etc/nova/nova.conf vmware vnc_port 5900 6. restart, boot, check: ~ # grep vnc /vmfs/volumes/shared/-yyy-.../*.vmx RemoteDisplay.vnc.enabled = "true" RemoteDisplay.vnc.port = "59xx" Actual results: default is something else then it was meant to be Expected results: default is what is meant to be Additional info: To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1294238/+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 1288296] Re: Update aggregate allows duplicate names
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1288296 Title: Update aggregate allows duplicate names Status in OpenStack Compute (Nova): Fix Released Bug description: The behaviour to manage naming conflicts is different between aggregate creation and aggregate update. Aggregate create doesn't let you create 2 aggregates with the same name. Aggregate update lets you update an aggregate to a name that already exists. It seems to me it should be consistent, and probably both check for conflict. Here's an example, using a recent devstack: $ nova aggregate-create test ++--+---+---+--+ | Id | Name | Availability Zone | Hosts | Metadata | ++--+---+---+--+ | 14 | test | - | | | ++--+---+---+--+ $ nova aggregate-create test ERROR: There was a conflict when trying to complete your request. (HTTP 409) (Request-ID: req-6711e05e-4efc-4a2d-9117-52d034c74a4f) $ nova aggregate-create test2 ++---+---+---+--+ | Id | Name | Availability Zone | Hosts | Metadata | ++---+---+---+--+ | 15 | test2 | - | | | ++---+---+---+--+ $ nova aggregate-update 15 test Aggregate 15 has been successfully updated. ++--+---+---+--+ | Id | Name | Availability Zone | Hosts | Metadata | ++--+---+---+--+ | 15 | test | - | | | ++--+---+---+--+ $ nova aggregate-list +++---+ | Id | Name | Availability Zone | +++---+ | 14 | test | - | | 15 | test | - | +++---+ Nova api logs from when the aggregate creation fails as expected: 2014-04-05 14:45:34.865 INFO nova.api.openstack.compute.contrib.aggregates [req-aeb307d4-c4c9-4684-8b13-1d81f0b8c692 admin demo] Aggregate test already exists. 2014-04-05 14:45:34.865 INFO nova.api.openstack.wsgi [req-aeb307d4-c4c9-4684-8b13-1d81f0b8c692 admin demo] HTTP exception thrown: There was a conflict when trying to complete your request. 2014-04-05 14:45:34.865 DEBUG nova.api.openstack.wsgi [req-aeb307d4-c4c9-4684-8b13-1d81f0b8c692 admin demo] Returning 409 to user: There was a conflict when trying to complete your request. from (pid=1517) __call__ /opt/stack/nova/nova/api/openstack/wsgi.py:1223 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1288296/+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 1287367] Re: The rescue API should handle NotImplementedError
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1287367 Title: The rescue API should handle NotImplementedError Status in OpenStack Compute (Nova): Fix Released Bug description: There are several nova virt drivers that don't implement the rescue API, but the os compute API doesn't handle NotImplementedError, it returns a 400 instead of a 501. https://wiki.openstack.org/wiki/HypervisorSupportMatrix The API could be tightened up a bit to return a 501 instead like how the pause admin action is handling NotImplementedError. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1287367/+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 1293353] Re: fix wrong comment in live_migration
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1293353 Title: fix wrong comment in live_migration Status in OpenStack Compute (Nova): Fix Released Bug description: https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L4311 comment for block_migration is duplicated, it should be deleted. https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L4343 comment for block_migration should be added. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1293353/+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 1289230] Re: Conversion types is missing in some strings
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1289230
Title:
Conversion types is missing in some strings
Status in Cinder:
Fix Released
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
Ex.:
except nexenta.NexentaException as exc:
-LOG.warning(_('Cannot delete snapshot %(origin): %(exc)s'),
+LOG.warning(_('Cannot delete snapshot %(origin)s: %(exc)s'),
{'origin': origin, 'exc': exc})
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1289230/+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 1288214] Re: Calling GET v3/os-cells/capacities causes an 'Unexpected API Error.'
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1288214
Title:
Calling GET v3/os-cells/capacities causes an 'Unexpected API Error.'
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
When I called Nova V3 API 'GET v3/os-cells/capacities', an 'Unexpected
API Error.' occurred.
http://logs.openstack.org/57/78157/1/check/check-tempest-dsvm-full/bcb3b6b/console.html#_2014-03-05_11_56_34_285
console.html
--
2014-03-05 11:56:34.283 | pythonlogging:'': {{{
2014-03-05 11:56:34.283 | 2014-03-05 11:30:18,083 Request: POST
http://127.0.0.1:5000/v2.0/tokens
2014-03-05 11:56:34.283 | 2014-03-05 11:30:18,083 Request Headers:
{'Content-Type': 'application/json', 'Accept': 'application/json'}
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,083 Request Body: {"auth":
{"tenantName": "CellsV3Test-1270506035", "passwordCredentials": {"username":
"CellsV3Test-365545871", "password": "pass"}}}
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,312 Response Status: 200
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,312 Response Headers:
{'content-length': '10648', 'date': 'Wed, 05 Mar 2014 11:30:18 GMT',
'content-type': 'application/json', 'vary': 'X-Auth-Token', 'connection':
'close'}
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,312 Response Body: {"access":
{"token": {"issued_at": "2014-03-05T11:30:18.255082", "expires":
"2014-03-05T12:30:18Z", "id": "
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,312 Large body (10648) md5
summary: a72282e83c228bfcf861c768bbcbdf79
2014-03-05 11:56:34.285 | 2014-03-05 11:30:18,313 Request: GET
http://127.0.0.1:8774/v3/os-cells/capacities
2014-03-05 11:56:34.285 | 2014-03-05 11:30:18,313 Request Headers:
{'Content-Type': 'application/json', 'Accept': 'application/json',
'X-Auth-Token': ''}
2014-03-05 11:56:34.285 | 2014-03-05 11:31:18,373 Response Status: 500
2014-03-05 11:56:34.285 | 2014-03-05 11:31:18,373 Nova/Cinder request id:
req-ae22c360-c3b8-4ad5-86d1-37e5664fb9ea
2014-03-05 11:56:34.285 | 2014-03-05 11:31:18,373 Response Headers:
{'content-length': '216', 'date': 'Wed, 05 Mar 2014 11:31:18 GMT',
'content-type': 'application/json; charset=UTF-8', 'connection': 'close'}
2014-03-05 11:56:34.285 | 2014-03-05 11:31:18,373 Response Body:
{"computeFault": {"message": "Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if
possible.\n", "code": 500}}
2014-03-05 11:56:34.285 | }}}
--
Full logs are:
http://logs.openstack.org/57/78157/1/check/check-tempest-dsvm-full/bcb3b6b
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1288214/+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 1291238] Re: VMware: VC drivers reports deprectaion message for ESX driver
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1291238 Title: VMware: VC drivers reports deprectaion message for ESX driver Status in OpenStack Compute (Nova): Fix Released Bug description: When using the VC driver the following message is received: 2014-03-12 01:42:32.889 INFO nova.openstack.common.periodic_task [-] Skipping periodic task _periodic_update_dns because its interval is negative 2014-03-12 01:42:32.940 INFO nova.virt.driver [-] Loading compute driver 'vmwareapi.VMwareVCDriver' 2014-03-12 01:42:32.979 WARNING nova.virt.vmwareapi.driver [-] The VMware ESX driver is now deprecated and will be removed in the Juno release. The VC driver will remain and continue to be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1291238/+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 1290036] Re: Test refresh_instance_security_rules in nova.tests.virt.test_virt_drivers
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1290036 Title: Test refresh_instance_security_rules in nova.tests.virt.test_virt_drivers Status in OpenStack Compute (Nova): Fix Released Bug description: Change https://review.openstack.org/#/c/69600/ adds a new method refresh_instance_security_rules to the nova ComputeDriver interface but it missed adding a test to nova.tests.virt.test_virt_driver to make sure all virt drivers are explicitly handling it. There is also a typo in the method's docstring. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1290036/+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 1292984] Re: Log message "fetching image %s from glance" is written in wrong place
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1292984
Title:
Log message "fetching image %s from glance" is written in wrong place
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
In nova.image.glance:
def get_remote_image_service(context, image_href):
"""Create an image_service and parse the id from the given image_href.
The image_href param can be an href of the form
'http://example.com:9292/v1/images/b8b2c6f7-7345-4e2f-afa2-eedaba9cbbe3',
or just an id such as 'b8b2c6f7-7345-4e2f-afa2-eedaba9cbbe3'. If the
image_href is a standalone id, then the default image service is returned.
:param image_href: href that describes the location of an image
:returns: a tuple of the form (image_service, image_id)
"""
# Calling out to another service may take a while, so lets log this
LOG.debug(_("fetching image %s from glance") % image_href)
#NOTE(bcwaldon): If image_href doesn't look like a URI, assume its a
# standalone image ID
if '/' not in str(image_href):
image_service = get_default_image_service()
return image_service, image_href
try:
(image_id, glance_host, glance_port, use_ssl) = \
_parse_image_ref(image_href)
glance_client = GlanceClientWrapper(context=context,
host=glance_host, port=glance_port, use_ssl=use_ssl)
except ValueError:
raise exception.InvalidImageRef(image_href=image_href)
image_service = GlanceImageService(client=glance_client)
return image_service, image_id
Clearly the LOG.debug() message above is incorrect. The method does
not fetch an image at all. It just returns an ImageService object.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1292984/+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 1292298] Re: Log statement for updating info cache needs to be moved
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1292298 Title: Log statement for updating info cache needs to be moved Status in OpenStack Compute (Nova): Fix Released Bug description: From the logs I notice that it says we are updating the info cache with None though that is not always true as if nw_info is not an instance of we NetworkInfo query neutron and then save that. 2014-03-13 02:57:19.647 DEBUG nova.network.api [req-9df20a08-37e1-4b67-94a9-963e6f6110ef TestVolumeBootPattern-554767810 TestVolumeBootPattern-64159061] Updating cache with info: None update_instance_cache_with_nw_info /opt/stack/new/nova/nova/network/api.py:70 2014-03-13 02:57:19.647 DEBUG nova.network.neutronv2.api [req-9df20a08-37e1-4b67-94a9-963e6f6110ef TestVolumeBootPattern-554767810 TestVolumeBootPattern-64159061] get_instance_nw_info() for scenario-server--1401642137 _get_instance_nw_info /opt/stack/new/nova/nova/network/neutronv2/api.py:463 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1292298/+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 1294480] Re: commented out code in test_cinder_cloud
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1294480 Title: commented out code in test_cinder_cloud Status in OpenStack Compute (Nova): Fix Released Bug description: commented out code in test_cinder_cloud To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1294480/+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
