[Yahoo-eng-team] [Bug 1258767] [NEW] Enable VMWare ESXDriver support set_host_enabled

2013-12-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The API of set_host_enabled was not supportted in VMWare ESXDriver, we
should support this feature.

** Affects: nova
 Importance: Undecided
 Assignee: Jay Lau (jay-lau-513)
 Status: New


** Tags: vmware
-- 
Enable VMWare ESXDriver support set_host_enabled
https://bugs.launchpad.net/bugs/1258767
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to OpenStack Compute (nova).

-- 
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 1258767] [NEW] Enable VMWare ESXDriver support set_host_enabled

2013-12-07 Thread Jay Lau
Public bug reported:

The API of set_host_enabled was not supportted in VMWare ESXDriver, we
should support this feature.

** Affects: nova
 Importance: Undecided
 Assignee: Jay Lau (jay-lau-513)
 Status: New


** Tags: vmware

** Changed in: python-heatclient
 Assignee: (unassigned) => Jay Lau (jay-lau-513)

** Tags added: vmware

** Project changed: python-heatclient => nova

-- 
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/1258767

Title:
  Enable VMWare ESXDriver support set_host_enabled

Status in OpenStack Compute (Nova):
  New

Bug description:
  The API of set_host_enabled was not supportted in VMWare ESXDriver, we
  should support this feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1258767/+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 1182908] Re: Wrong initialization of instance attributes in horizon/tables/actions.py

2013-12-07 Thread David Lyle
** Changed in: horizon
   Importance: Undecided => Low

** Changed in: horizon
   Status: In Progress => Fix Committed

** Changed in: horizon
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1182908

Title:
  Wrong initialization of instance attributes in
  horizon/tables/actions.py

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  1.
  In 
https://github.com/openstack/horizon/blob/master/horizon/tables/actions.py#L193

  the value of self.requires_input gets always filled by class attribute of the 
same name defined in 
https://github.com/openstack/horizon/blob/master/horizon/tables/actions.py#L177
  so it never takes the value from parameter given in initializer

  It can be easily fixed, it is already in the right format e.g here
  
https://github.com/openstack/horizon/blob/master/horizon/tables/actions.py#L185

  This could be in more places. So maybe checking the code for this kind
  of bug would be good.

  2.
  Also, I have noticed some unused class attributes e.g. 
https://github.com/openstack/horizon/blob/master/horizon/tables/actions.py#L349 

  Would be good to delete those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1182908/+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 1258635] Re: Race with changing image status when snapshotting

2013-12-07 Thread Zhi Kun Liu
** Also affects: tempest
   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/1258635

Title:
  Race with changing image status when snapshotting

Status in OpenStack Compute (Nova):
  New
Status in Tempest:
  New

Bug description:
  {code}
  19:18:16 
==
  19:18:16 FAIL: setUpClass 
(tempest.api.compute.images.test_list_image_filters.ListImageFiltersTestJSON)
  19:18:16 setUpClass 
(tempest.api.compute.images.test_list_image_filters.ListImageFiltersTestJSON)
  19:18:16 
--
  19:18:16 _StringException: Traceback (most recent call last):
  19:18:16   File "tempest/api/compute/images/test_list_image_filters.py", line 
61, in setUpClass
  19:18:16 resp, body = cls.create_image_from_server(cls.server1['id'])
  19:18:16   File "tempest/api/compute/base.py", line 172, in 
create_image_from_server
  19:18:16 server_id, name)
  19:18:16   File "tempest/services/compute/json/images_client.py", line 49, in 
create_image
  19:18:16 post_body, self.headers)
  19:18:16   File "tempest/common/rest_client.py", line 302, in post
  19:18:16 return self.request('POST', url, headers, body)
  19:18:16   File "tempest/common/rest_client.py", line 436, in request
  19:18:16 resp, resp_body)
  19:18:16   File "tempest/common/rest_client.py", line 491, in _error_checker
  19:18:16 raise exceptions.Conflict(resp_body)
  19:18:16 Conflict: An object with that identifier already exists
  19:18:16 Details: {u'conflictingRequest': {u'message': u"Cannot 'createImage' 
while instance is in task_state image_uploading", u'code': 409}}
  {code}

  This is a tempest bug - but the test creates a server, starts a
  snapshot and then waits for the server to have the "ACTIVE" state.
  There is waiting for the image to have finished uploading - but the
  instance may not have been returned to the "ACTIVE" state immediately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1258635/+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 1252827] Re: VMWARE: Intermittent problem with stats reporting

2013-12-07 Thread Alan Pevec
** Also affects: nova/havana
   Importance: Undecided
   Status: New

** Changed in: nova/havana
   Importance: Undecided => High

** Changed in: nova/havana
   Status: New => In Progress

** Changed in: nova/havana
 Assignee: (unassigned) => Gary Kotton (garyk)

** Changed in: nova/havana
Milestone: None => 2013.2.1

** Tags removed: havana-backport-potential

-- 
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/1252827

Title:
  VMWARE: Intermittent problem with stats reporting

Status in OpenStack Compute (Nova):
  Fix Committed
Status in OpenStack Compute (nova) havana series:
  In Progress
Status in The OpenStack VMwareAPI subTeam:
  In Progress

Bug description:
  I see that sometimes vmware driver reports 0 stats. Please take a look
  at the following log file for more information:
  http://162.209.83.206/logs/51404/6/screen-n-cpu.txt.gz

  excerpts from log file:
  2013-11-18 15:41:03.994 20162 WARNING nova.virt.vmwareapi.vim_util [-] Unable 
to retrieve value for datastore Reason: None
  2013-11-18 15:41:04.029 20162 WARNING nova.virt.vmwareapi.vim_util [-] Unable 
to retrieve value for host Reason: None
  2013-11-18 15:41:04.029 20162 WARNING nova.virt.vmwareapi.vim_util [-] Unable 
to retrieve value for resourcePool Reason: None
  2013-11-18 15:41:04.029 20162 DEBUG nova.compute.resource_tracker [-] 
Hypervisor: free ram (MB): 0 _report_hypervisor_resource_view 
/opt/stack/nova/nova/compute/resource_tracker.py:389
  2013-11-18 15:41:04.029 20162 DEBUG nova.compute.resource_tracker [-] 
Hypervisor: free disk (GB): 0 _report_hypervisor_resource_view 
/opt/stack/nova/nova/compute/resource_tracker.py:390
  2013-11-18 15:41:04.030 20162 DEBUG nova.compute.resource_tracker [-] 
Hypervisor: VCPU information unavailable _report_hypervisor_resource_view 
/opt/stack/nova/nova/compute/resource_tracker.py:397

  During this time we cannot spawn any server. Look at the
  http://162.209.83.206/logs/51404/6/screen-n-sch.txt.gz

  excerpts from log file:
  2013-11-18 15:41:52.475 DEBUG nova.filters 
[req-dc82a954-3cc5-4627-ae01-b3d1ec2155af 
InstanceActionsTestXML-tempest-716947327-user 
InstanceActionsTestXML-tempest-716947327-tenant] Filter AvailabilityZoneFilter 
returned 1 host(s) get_filtered_objects /opt/stack/nova/nova/filters.py:88
  2013-11-18 15:41:52.476 DEBUG nova.scheduler.filters.ram_filter 
[req-dc82a954-3cc5-4627-ae01-b3d1ec2155af 
InstanceActionsTestXML-tempest-716947327-user 
InstanceActionsTestXML-tempest-716947327-tenant] (Ubuntu1204Server, 
domain-c26(c1)) ram:-576 disk:0 io_ops:0 instances:1 does not have 64 MB usable 
ram, it only has -576.0 MB usable ram. host_passes 
/opt/stack/nova/nova/scheduler/filters/ram_filter.py:60
  2013-11-18 15:41:52.476 INFO nova.filters 
[req-dc82a954-3cc5-4627-ae01-b3d1ec2155af 
InstanceActionsTestXML-tempest-716947327-user 
InstanceActionsTestXML-tempest-716947327-tenant] Filter RamFilter returned 0 
hosts
  2013-11-18 15:41:52.477 WARNING nova.scheduler.driver 
[req-dc82a954-3cc5-4627-ae01-b3d1ec2155af 
InstanceActionsTestXML-tempest-716947327-user 
InstanceActionsTestXML-tempest-716947327-tenant] [instance: 
1a648022-1783-4874-8b41-c3f4c89d8500] Setting instance to ERROR state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1252827/+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 1258848] [NEW] vif doesn't exist Error message in tempest runs

2013-12-07 Thread Matthew Treinish
Public bug reported:

On a successful tempest run the following error message was in the nova
logs:

ERROR nova.network.manager [req-1ef0c266-bec4-4414-ae27-f6937e6baa2a
ListServersNegativeTestXML-tempest-117344783-user
ListServersNegativeTestXML-tempest-117344783-tenant] Unable to release
10.1.0.2 because vif doesn't exist.

This causes the test job to fail.

Logs are located here:
http://logs.openstack.org/78/60578/2/check/check-tempest-dsvm-full/0cc61b2/

** Affects: nova
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1258848

Title:
  vif doesn't exist Error message in tempest runs

Status in OpenStack Compute (Nova):
  New

Bug description:
  On a successful tempest run the following error message was in the
  nova logs:

  ERROR nova.network.manager [req-1ef0c266-bec4-4414-ae27-f6937e6baa2a
  ListServersNegativeTestXML-tempest-117344783-user
  ListServersNegativeTestXML-tempest-117344783-tenant] Unable to release
  10.1.0.2 because vif doesn't exist.

  This causes the test job to fail.

  Logs are located here:
  http://logs.openstack.org/78/60578/2/check/check-tempest-dsvm-full/0cc61b2/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1258848/+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 1258856] [NEW] tempest.api.compute.servers.test_server_actions.ServerActionsTestXML.test_stop_start_server fails with quota error

2013-12-07 Thread Peter Portante
Public bug reported:

See: http://logs.openstack.org/10/56710/10/check/check-tempest-dsvm-
full/187705b/console.html.gz

2013-12-07 01:35:54.908 | 
==
2013-12-07 01:35:54.909 | FAIL: 
tempest.api.compute.servers.test_server_actions.ServerActionsTestXML.test_stop_start_server[gate]
2013-12-07 01:35:54.909 | 
tempest.api.compute.servers.test_server_actions.ServerActionsTestXML.test_stop_start_server[gate]
2013-12-07 01:35:54.909 | 
--
2013-12-07 01:35:54.909 | _StringException: Empty attachments:
2013-12-07 01:35:54.909 |   stderr
2013-12-07 01:35:54.909 |   stdout
2013-12-07 01:35:54.910 | 
2013-12-07 01:35:54.910 | pythonlogging:'': {{{
2013-12-07 01:35:54.910 | 2013-12-07 01:15:59,684 Request: GET 
http://127.0.0.1:8774/v2/04d6f70250e94a5e94e506386812bba3/servers/562fe7bb-f952-4cc3-af24-5d612dc3f022
2013-12-07 01:35:54.910 | 2013-12-07 01:15:59,685 Request Headers: 
{'Content-Type': 'application/xml', 'Accept': 'application/xml', 
'X-Auth-Token': ''}
2013-12-07 01:35:54.910 | 2013-12-07 01:15:59,745 Response Status: 404
2013-12-07 01:35:54.910 | 2013-12-07 01:15:59,745 Nova request id: 
req-ee502842-f694-4b3f-b696-0b0d1a2ce925
2013-12-07 01:35:54.911 | 2013-12-07 01:15:59,745 Response Headers: 
{'content-length': '137', 'date': 'Sat, 07 Dec 2013 01:15:59 GMT', 
'content-type': 'application/xml; charset=UTF-8', 'connection': 'close'}
2013-12-07 01:35:54.911 | 2013-12-07 01:15:59,746 Response Body: http://docs.openstack.org/compute/api/v1.1";>Instance 
could not be found
2013-12-07 01:35:54.911 | 2013-12-07 01:15:59,746 Request: DELETE 
http://127.0.0.1:8774/v2/04d6f70250e94a5e94e506386812bba3/servers/562fe7bb-f952-4cc3-af24-5d612dc3f022
2013-12-07 01:35:54.911 | 2013-12-07 01:15:59,746 Request Headers: 
{'X-Auth-Token': ''}
2013-12-07 01:35:54.911 | 2013-12-07 01:15:59,801 Response Status: 404
2013-12-07 01:35:54.911 | 2013-12-07 01:15:59,802 Nova request id: 
req-703c4944-902f-4a14-a27c-0ae724ce66b1
2013-12-07 01:35:54.911 | 2013-12-07 01:15:59,802 Response Headers: 
{'content-length': '73', 'date': 'Sat, 07 Dec 2013 01:15:59 GMT', 
'content-type': 'application/json; charset=UTF-8', 'connection': 'close'}
2013-12-07 01:35:54.912 | 2013-12-07 01:15:59,802 Response Body: 
{"itemNotFound": {"message": "Instance could not be found", "code": 404}}
2013-12-07 01:35:54.912 | 2013-12-07 01:15:59,803 Object not found
2013-12-07 01:35:54.912 | Details: {"itemNotFound": {"message": "Instance could 
not be found", "code": 404}}
2013-12-07 01:35:54.912 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base Traceback (most recent call last):
2013-12-07 01:35:54.912 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base   File "tempest/api/compute/base.py", line 188, in 
rebuild_server
2013-12-07 01:35:54.912 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base cls.servers_client.delete_server(server_id)
2013-12-07 01:35:54.912 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base   File 
"tempest/services/compute/xml/servers_client.py", line 238, in delete_server
2013-12-07 01:35:54.913 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base return self.delete("servers/%s" % str(server_id))
2013-12-07 01:35:54.913 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base   File "tempest/common/rest_client.py", line 308, in 
delete
2013-12-07 01:35:54.913 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base return self.request('DELETE', url, headers)
2013-12-07 01:35:54.913 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base   File "tempest/common/rest_client.py", line 436, in 
request
2013-12-07 01:35:54.913 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base resp, resp_body)
2013-12-07 01:35:54.913 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base   File "tempest/common/rest_client.py", line 481, in 
_error_checker
2013-12-07 01:35:54.914 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base raise exceptions.NotFound(resp_body)
2013-12-07 01:35:54.914 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base NotFound: Object not found
2013-12-07 01:35:54.914 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base Details: {"itemNotFound": {"message": "Instance could 
not be found", "code": 404}}
2013-12-07 01:35:54.914 | 2013-12-07 01:15:59.803 5212 TRACE 
tempest.api.compute.base 
2013-12-07 01:35:54.914 | 2013-12-07 01:15:59,803 Request: POST 
http://127.0.0.1:8774/v2/04d6f70250e94a5e94e506386812bba3/servers
2013-12-07 01:35:54.914 | 2013-12-07 01:15:59,804 Request Headers: 
{'Content-Type': 'application/xml', 'Accept': 'application/xml', 
'X-Auth-Token': ''}
2013-12-07 01:35:54.914 | 2013-12-07 01:15:59,804 Request Body: 
2013-12-07 01:35:54.915 | http://docs.openstack.org/compute/api/v1.1"; 
name="ServerActionsTestXML-instance-tempest-1497396172" 
im