date:20140916

** Also affects: horizon/icehouse
   Importance: Undecided
   Status: New

** Changed in: horizon/icehouse
   Status: New = In Progress

** Changed in: horizon/icehouse
 Assignee: (unassigned) = Julie Pichon (jpichon)

** Changed in: horizon/icehouse
   Importance: Undecided = Low

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

Title:
  Creating a volume from an instance snapshot should validate the volume
  size / min_disk

Status in OpenStack Dashboard (Horizon):
  Fix Committed
Status in OpenStack Dashboard (Horizon) icehouse series:
  In Progress

Bug description:
  This is sort of a follow-up to bug 1241253. When an image is created
  based on an instance snapshot, even though the same min_disk
  restrictions apply, they're not reflected properly in the validation
  and tool tips, resulting in misleading information being shown to the
  user.

  Steps to reproduce:
  -
  1. Create an image with a minimum disk size of e.g. 2GB
  2. Boot an instance from the image
  3. Create a snapshot of the instance (from dashboard or using nova 
create-image)
  4. Back on the images panels, click the Create volume button for the new 
image
  5. The prefilled size and size tooltip do not indicate the correct minimum 
disk size

  
  This seems to be happening because in that case the min_disk attribute is set 
as a property rather than a direct attribute, looking at Glance:

  $ glance image-show id_of_image
  +--+--+
  | Property | Value|
  +--+--+
  ...
  | min_disk | 2|
  ...

  $ glance image-show id_of_instance_snapshot
  +-++
  | Property| Value  |
  +-++
  ...
  | Property 'min_disk' | 2  |
  ...
  | min_disk| 0  |
  ...

  I'm not sure why... Maybe someone from Glance could shed some light on
  this and whether that's the expected behaviour?

  In the meantime it shouldn't be too hard for Horizon to handle the
  case where min_disk is set as a property.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1368600/+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 1319319] Re: The web server allows the HTTP TRACE or TRACK methods.

Hi Mark, could we disable HTTP TRACE support in our web server to avoid
this security issue?

** Changed in: openstack-chef
   Status: Expired = 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/1319319

Title:
  The web server allows the HTTP TRACE or TRACK methods.

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in OpenStack + Chef:
  New
Status in OpenStack Security Advisories:
  Invalid

Bug description:
  
  The Horizon affected by it. This is related to configuration of  
RewriteCond in sites-enabled/openstack-dashboard, covered by 
stackforge/cookbook-openstack-dashboard project.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1319319/+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 1369870] [NEW] Missing Secure Attribute in Encrypted Session (SSL) Cookie

Public bug reported:

Affect URL: https://Ip_address/settings/

Risk: It may be possible to steal user and session information (cookies)
that was sent during an encrypted session

Causes: The web application sends non-secure cookies over SSL

Recommend Fix: Add the 'Secure' attribute to all sensitive cookies

The test Requests and Responses :

GET /admin/ HTTP/1.1
Host: 9.5.29.52
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 
Firefox/24.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Referer: https://9.5.29.52/
Cookie: csrftoken=JPjBiDp6Ex6YDw3sgfZPCTPUwWKZdZTm; 
sessionid=oad3bpy15qm8ntml9wx604yr79cc6zpb
Connection: keep-alive
HTTP/1.1 200 OK
Date: Fri, 12 Sep 2014 07:52:50 GMT
Server: Apache
Vary: Accept-Language,Cookie,Accept-Encoding
X-Frame-Options: SAMEORIGIN
Content-Language: en
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
2014/9/12 504
Transfer-Encoding: chunked
Content-Type: text/html
Set-Cookie: csrftoken=silTP6ARbLvXohF6YYFLlWHce0KZkjPy; expires=Fri, 
11-Sep-2015 07:52:52 GMT; Max-Age=31449600; Path=/; secure
Set-Cookie: sessionid=ygq094phgr6og471j6n0asq7x6q37j6n; httponly; Path=/; secure
!DOCTYPE html
html
head
meta content='text/html; charset=utf-8' http-equiv='Content-Type' /
titleUsage Overview - Cloud Management Dashboard/title
!--
Copyright 2014 IBM Corp.
Copyright 2014 OpenStack Foundation and others
--
link rel=stylesheet href=/static/dashboard/css/5730bed76fd3.css 
type=text/css media=screen /
link rel=shortcut icon href=/static/dashboard/img/favicon.png/
!--
Fix header padding issue in IE  10
--
!--[if lt IE 10 ]
style
.topbar {
padding-bottom: 0px;
}
/style
![endif]--
script type=text/javascript 
src=/static/dashboard/js/841198948869.js/script
script type=text/javascript charset=utf-8
/*
Added so that we can append Horizon scoped JS events to
the DOM load events without running in to the horizon
name-space not currently being defined since we load the
scripts at the bottom of the page.
*/
var addHorizonLoadEvent = function(func) {
var old_onload = window.onload;
if (typeof window.onload != 'function') {
window.onload = func;
} else {
window.onload = function() {
old_onload();
func();
}
}
}
/script
/head
body id= ng-app='hz'
div id=container
div class='topbar'
!--
Copyright 2014 IBM Corp.
Copyright 2014 OpenStack Foundation and others
--
h1 class=branda href=/home/Cloud Management Dashboard/a/h1
div id=user_info class=pull-right
div id=tenant_switcher class=dropdown switcher_bar hide_image  
tabindex=1
divadmin/div
/div
div id=profile_editor_switcher class=dropdown switcher_bar tabindex='1'
a class=dropdown-toggle data-toggle=dropdown 
href=#profile_editor_switcher
divadmin/div
/a
ul id=editor_list class=dropdown-menu
li class='divider'/li
lia href=/settings/Settings/a/li
2014/9/12 505
TOC
lia href=http://docs.openstack.org; target=_newHelp/a/li
lia href=/auth/logout/Sign Out/a/li
/ul
/div
img class=brand_icon src=/static/dashboard/img/logo.png alt=/
/div
/div
div id='main_content'
div class=messages
/div
div class='sidebar'
div
dl class=nav_accordion
dt 
divProject/div
/dt
dd style=display:none;
divh4divCompute/div/h4
ul
lia href=/project/ tabindex=1 Overview/a/li
lia href=/project/instances/ tabindex=2 Instances/a/li
lia href=/project/volumes/ tabindex=3 Volumes/a/li
lia href=/project/images/ tabindex=4 Images/a/li
lia href=/project/access_and_security/ tabindex=5 Access amp; 
Security/a/li
/ul
/div
divh4divNetwork/div/h4
ul
lia href=/project/network_topology/ tabindex=1 Network Topology/a/li
lia href=/project/networks/ tabindex=2 Networks/a/li
lia href=/project/routers/ tabindex=3 Routers/a/li
/ul
/div
divh4divOrchestration/div/h4
ul
lia href=/project/stacks/ tabindex=1 Stacks/a/li
/ul
/div
...
...
...

** 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/1369870

Title:
  Missing Secure Attribute in Encrypted Session (SSL) Cookie

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Affect URL: https://Ip_address/settings/

  Risk: It may be possible to steal user and session information
  (cookies) that was sent during an encrypted session

  Causes: The web application sends non-secure cookies over SSL

  Recommend Fix: Add the 'Secure' attribute to all sensitive cookies

  The test Requests and Responses :

  GET /admin/ HTTP/1.1
  Host: 9.5.29.52
  User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 
Firefox/24.0
  Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
  Accept-Language: en-US,en;q=0.5
  Referer: https://9.5.29.52/
  Cookie: csrftoken=JPjBiDp6Ex6YDw3sgfZPCTPUwWKZdZTm; 
sessionid=oad3bpy15qm8ntml9wx604yr79cc6zpb
  Connection: keep-alive
  HTTP/1.1 200 OK
  Date: Fri, 12 Sep 2014 07:52:50 GMT
  Server: Apache
  Vary:

[Yahoo-eng-team] [Bug 1369871] [NEW] HTTP 500 is returned when using an invalid ip for defined network to attach interface

2014-09-16 Thread Qin Zhao

Public bug reported:

When I post an 'attach interface' request to Nova with an invalid ip for
defined network, Nova returns an HTTP 500 error and a confusing error
message.

REQ: curl -i 
'http://10.90.10.24:8774/v2/19abae5746b242d489d1c2862b228d8b/servers/4e863fad-e868-48a1-8735-2da9a38561e8/os-interface'
 -X POST -H Accept: application/json -H Content-Type: application/json -H 
User-Agent: python-novaclient -H X-Auth-Project-Id: Public -H 
X-Auth-Token: {SHA1}ce7267ae4e84b8f8457ab6a54c353a3e7c7d051c -d 
'{interfaceAttachment: {fixed_ips: [{ip_address: 1.1.1.1}], net_id: 
173854d5-333f-4c78-b5a5-10d2e9c8d827}}'
INFO (connectionpool:187) Starting new HTTP connection (1): 10.90.10.24
DEBUG (connectionpool:357) POST 
/v2/19abae5746b242d489d1c2862b228d8b/servers/4e863fad-e868-48a1-8735-2da9a38561e8/os-interface
 HTTP/1.1 500 128
RESP: [500] {'date': 'Tue, 16 Sep 2014 06:26:54 GMT', 'content-length': '128', 
'content-type': 'application/json; charset=UTF-8', 'x-compute-request-id': 
'req-f69db2a5-a777-471a-b2b5-00aa2ecd2892'}
RESP BODY: {computeFault: {message: The server has either erred or is 
incapable of performing the requested operation., code: 500}}


In fact, Nova works perfect well. The error is caused by my incorrect input. 
Nova should be able to address this incorrect input, and return an HTTP 400 
error in order to to inform the user to correct the request.

** 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/1369871

Title:
  HTTP 500 is returned when using an invalid ip for defined network to
  attach interface

Status in OpenStack Compute (Nova):
  New

Bug description:
  When I post an 'attach interface' request to Nova with an invalid ip
  for defined network, Nova returns an HTTP 500 error and a confusing
  error message.

  REQ: curl -i 
'http://10.90.10.24:8774/v2/19abae5746b242d489d1c2862b228d8b/servers/4e863fad-e868-48a1-8735-2da9a38561e8/os-interface'
 -X POST -H Accept: application/json -H Content-Type: application/json -H 
User-Agent: python-novaclient -H X-Auth-Project-Id: Public -H 
X-Auth-Token: {SHA1}ce7267ae4e84b8f8457ab6a54c353a3e7c7d051c -d 
'{interfaceAttachment: {fixed_ips: [{ip_address: 1.1.1.1}], net_id: 
173854d5-333f-4c78-b5a5-10d2e9c8d827}}'
  INFO (connectionpool:187) Starting new HTTP connection (1): 10.90.10.24
  DEBUG (connectionpool:357) POST 
/v2/19abae5746b242d489d1c2862b228d8b/servers/4e863fad-e868-48a1-8735-2da9a38561e8/os-interface
 HTTP/1.1 500 128
  RESP: [500] {'date': 'Tue, 16 Sep 2014 06:26:54 GMT', 'content-length': 
'128', 'content-type': 'application/json; charset=UTF-8', 
'x-compute-request-id': 'req-f69db2a5-a777-471a-b2b5-00aa2ecd2892'}
  RESP BODY: {computeFault: {message: The server has either erred or is 
incapable of performing the requested operation., code: 500}}

  
  In fact, Nova works perfect well. The error is caused by my incorrect input. 
Nova should be able to address this incorrect input, and return an HTTP 400 
error in order to to inform the user to correct the request.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1369871/+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 1369876] [NEW] Missing HttpOnly Attribute in Session Cookie

Public bug reported:

Affected URL: https://Ip_address/admin/
Entity: csrftoken (Cookie)
Risk: It is possible to steal or manipulate customer session and cookies, which 
might be used to impersonate a legitimate user, allowing the hacker to view or 
alter user records, and to perform transactions as that user.
Causes: The web application sets session cookies without the HttpOnly attribute
Recommend Fix: Add the 'HttpOnly' attribute to all session cookies.

The Test Requests and Responses:
GET /admin/ HTTP/1.1
Host: 9.5.29.52
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 
Firefox/24.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Referer: https://9.5.29.52/
Cookie: csrftoken=JPjBiDp6Ex6YDw3sgfZPCTPUwWKZdZTm; 
sessionid=oad3bpy15qm8ntml9wx604yr79cc6zpb
Connection: keep-alive
HTTP/1.1 200 OK
Date: Fri, 12 Sep 2014 07:52:50 GMT
Server: Apache
Vary: Accept-Language,Cookie,Accept-Encoding
X-Frame-Options: SAMEORIGIN
Content-Language: en
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
2014/9/12 504
Transfer-Encoding: chunked
Content-Type: text/html
Set-Cookie: csrftoken=silTP6ARbLvXohF6YYFLlWHce0KZkjPy; expires=Fri, 
11-Sep-2015 07:52:52 GMT; Max-Age=31449600; Path=/; secure
Set-Cookie: sessionid=ygq094phgr6og471j6n0asq7x6q37j6n; httponly; Path=/; secure
!DOCTYPE html
html
head
meta content='text/html; charset=utf-8' http-equiv='Content-Type' /
titleUsage Overview - Cloud Management Dashboard/title
!--
Copyright 2014 IBM Corp.
Copyright 2014 OpenStack Foundation and others
--
link rel=stylesheet href=/static/dashboard/css/5730bed76fd3.css 
type=text/css media=screen /
link rel=shortcut icon href=/static/dashboard/img/favicon.png/
!--
Fix header padding issue in IE  10
--
!--[if lt IE 10 ]
style
.topbar {
padding-bottom: 0px;
}
/style
![endif]--
script type=text/javascript 
src=/static/dashboard/js/841198948869.js/script
script type=text/javascript charset=utf-8
/*
Added so that we can append Horizon scoped JS events to
the DOM load events without running in to the horizon
name-space not currently being defined since we load the
scripts at the bottom of the page.
*/
var addHorizonLoadEvent = function(func) {
var old_onload = window.onload;
if (typeof window.onload != 'function') {
window.onload = func;
} else {
window.onload = function() {
old_onload();
func();
}
}
}
/script
/head
body id= ng-app='hz'
div id=container
div class='topbar'
!--
Copyright 2014 IBM Corp.
Copyright 2014 OpenStack Foundation and others
--
h1 class=branda href=/home/Cloud Management Dashboard/a/h1
div id=user_info class=pull-right
div id=tenant_switcher class=dropdown switcher_bar hide_image  
tabindex=1
divadmin/div
/div
div id=profile_editor_switcher class=dropdown switcher_bar tabindex='1'
a class=dropdown-toggle data-toggle=dropdown 
href=#profile_editor_switcher
divadmin/div
/a
ul id=editor_list class=dropdown-menu
li class='divider'/li
lia href=/settings/Settings/a/li
2014/9/12 505
TOC
lia href=http://docs.openstack.org; target=_newHelp/a/li
lia href=/auth/logout/Sign Out/a/li
/ul
/div
img class=brand_icon src=/static/dashboard/img/logo.png alt=/
/div
/div
div id='main_content'
div class=messages
/div
div class='sidebar'
div
dl class=nav_accordion
dt 
divProject/div
/dt
dd style=display:none;
divh4divCompute/div/h4
ul
lia href=/project/ tabindex=1 Overview/a/li
lia href=/project/instances/ tabindex=2 Instances/a/li
lia href=/project/volumes/ tabindex=3 Volumes/a/li
lia href=/project/images/ tabindex=4 Images/a/li
lia href=/project/access_and_security/ tabindex=5 Access amp; 
Security/a/li
/ul
/div
divh4divNetwork/div/h4
ul
lia href=/project/network_topology/ tabindex=1 Network Topology/a/li
lia href=/project/networks/ tabindex=2 Networks/a/li
lia href=/project/routers/ tabindex=3 Routers/a/li
/ul
/div
divh4divOrchestration/div/h4
ul
lia href=/project/stacks/ tabindex=1 Stacks/a/li
/ul
/div
...
...
...

** 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/1369876

Title:
  Missing HttpOnly Attribute in Session Cookie

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Affected URL: https://Ip_address/admin/
  Entity: csrftoken (Cookie)
  Risk: It is possible to steal or manipulate customer session and cookies, 
which might be used to impersonate a legitimate user, allowing the hacker to 
view or alter user records, and to perform transactions as that user.
  Causes: The web application sets session cookies without the HttpOnly 
attribute
  Recommend Fix: Add the 'HttpOnly' attribute to all session cookies.

  The Test Requests and Responses:
  GET /admin/ HTTP/1.1
  Host: 9.5.29.52
  User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 
Firefox/24.0
  Accept:

[Yahoo-eng-team] [Bug 1369878] [NEW] Hidden Directory Detected in Horizon

Public bug reported:

Risk:  It is possible to retrieve information about the site's file system 
structure, which may help the attacker to map the web site.
Cause: The web server or application server are configured in an insecure way
Recommend fix:  Issue a 404 - Not Found response status code for a forbidden 
resource, or remove it completely.
Affected URL: https://IP_address/static/

Difference: Path manipulated from: / to: /static/
Reasoning: The test tried to detect hidden directories on the server. The 403 
Forbidden response reveals the existence of the directory, even though access 
is not allowed.

Test Requests and Responses:
GET /static/ HTTP/1.1
Cookie: csrftoken=RYhjGotKeCLLuagINfhLc0uidiy4DTaI; 
sessionid=zqk46d3ypk9c46rzp35cw68sgwgh8klq
Accept-Language: en-US
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Host: 9.5.29.52
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 
Firefox/24.0
HTTP/1.1 403 Forbidden
Date: Fri, 12 Sep 2014 04:05:08 GMT
Server: Apache
Vary: Accept-Encoding
Content-Length: 269
Content-Type: text/html; charset=iso-8859-1

** 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/1369878

Title:
  Hidden Directory Detected in Horizon

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Risk:  It is possible to retrieve information about the site's file system 
structure, which may help the attacker to map the web site.
  Cause: The web server or application server are configured in an insecure way
  Recommend fix:  Issue a 404 - Not Found response status code for a 
forbidden resource, or remove it completely.
  Affected URL: https://IP_address/static/

  Difference: Path manipulated from: / to: /static/
  Reasoning: The test tried to detect hidden directories on the server. The 403 
Forbidden response reveals the existence of the directory, even though access 
is not allowed.

  Test Requests and Responses:
  GET /static/ HTTP/1.1
  Cookie: csrftoken=RYhjGotKeCLLuagINfhLc0uidiy4DTaI; 
sessionid=zqk46d3ypk9c46rzp35cw68sgwgh8klq
  Accept-Language: en-US
  Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
  Host: 9.5.29.52
  User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 
Firefox/24.0
  HTTP/1.1 403 Forbidden
  Date: Fri, 12 Sep 2014 04:05:08 GMT
  Server: Apache
  Vary: Accept-Encoding
  Content-Length: 269
  Content-Type: text/html; charset=iso-8859-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1369878/+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 1369877] [NEW] AttributeError: 'NoopFirewallDriver' object has no attribute 'update_security_group_rules'

2014-09-16 Thread Itzik Brown

Public bug reported:

When using NoopFirewallDriver there seems to be a missing method
'update_security_group_rule'

2014-09-15 16:54:38.167 1069 CRITICAL neutron 
[req-b671b223-1d0c-4545-a9e3-f1d84561762e None] AttributeError: 
'NoopFirewallDriver' object has no attribute 'update_security_group_rules'
2014-09-15 16:54:38.167 1069 TRACE neutron Traceback (most recent call last):
2014-09-15 16:54:38.167 1069 TRACE neutron   File 
/usr/local/bin/neutron-linuxbridge-agent, line 10, in module
2014-09-15 16:54:38.167 1069 TRACE neutron sys.exit(main())
2014-09-15 16:54:38.167 1069 TRACE neutron   File 
/opt/stack/neutron/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py,
 line 1041, in main
2014-09-15 16:54:38.167 1069 TRACE neutron agent.daemon_loop()
2014-09-15 16:54:38.167 1069 TRACE neutron   File 
/opt/stack/neutron/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py,
 line 999, in daemon_loop
2014-09-15 16:54:38.167 1069 TRACE neutron device_info.get('updated', set())
2014-09-15 16:54:38.167 1069 TRACE neutron   File 
/opt/stack/neutron/neutron/agent/securitygroups_rpc.py, line 312, in 
setup_port_filters
2014-09-15 16:54:38.167 1069 TRACE neutron 
self.prepare_devices_filter(new_devices)
2014-09-15 16:54:38.167 1069 TRACE neutron   File 
/opt/stack/neutron/neutron/agent/securitygroups_rpc.py, line 207, in 
prepare_devices_filter
2014-09-15 16:54:38.167 1069 TRACE neutron security_groups, 
security_group_member_ips)
2014-09-15 16:54:38.167 1069 TRACE neutron   File 
/opt/stack/neutron/neutron/agent/securitygroups_rpc.py, line 213, in 
_update_security_group_info
2014-09-15 16:54:38.167 1069 TRACE neutron 
self.firewall.update_security_group_rules(sg_id, sg_rules)
2014-09-15 16:54:38.167 1069 TRACE neutron AttributeError: 'NoopFirewallDriver' 
object has no attribute 'update_security_group_rules'
2014-09-15 16:54:38.167 1069 TRACE neutron

** Affects: neutron
 Importance: Undecided
 Status: Confirmed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1369877

Title:
  AttributeError: 'NoopFirewallDriver' object has no attribute
  'update_security_group_rules'

Status in OpenStack Neutron (virtual network service):
  Confirmed

Bug description:
  When using NoopFirewallDriver there seems to be a missing method
  'update_security_group_rule'

  2014-09-15 16:54:38.167 1069 CRITICAL neutron 
[req-b671b223-1d0c-4545-a9e3-f1d84561762e None] AttributeError: 
'NoopFirewallDriver' object has no attribute 'update_security_group_rules'
  2014-09-15 16:54:38.167 1069 TRACE neutron Traceback (most recent call last):
  2014-09-15 16:54:38.167 1069 TRACE neutron   File 
/usr/local/bin/neutron-linuxbridge-agent, line 10, in module
  2014-09-15 16:54:38.167 1069 TRACE neutron sys.exit(main())
  2014-09-15 16:54:38.167 1069 TRACE neutron   File 
/opt/stack/neutron/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py,
 line 1041, in main
  2014-09-15 16:54:38.167 1069 TRACE neutron agent.daemon_loop()
  2014-09-15 16:54:38.167 1069 TRACE neutron   File 
/opt/stack/neutron/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py,
 line 999, in daemon_loop
  2014-09-15 16:54:38.167 1069 TRACE neutron device_info.get('updated', 
set())
  2014-09-15 16:54:38.167 1069 TRACE neutron   File 
/opt/stack/neutron/neutron/agent/securitygroups_rpc.py, line 312, in 
setup_port_filters
  2014-09-15 16:54:38.167 1069 TRACE neutron 
self.prepare_devices_filter(new_devices)
  2014-09-15 16:54:38.167 1069 TRACE neutron   File 
/opt/stack/neutron/neutron/agent/securitygroups_rpc.py, line 207, in 
prepare_devices_filter
  2014-09-15 16:54:38.167 1069 TRACE neutron security_groups, 
security_group_member_ips)
  2014-09-15 16:54:38.167 1069 TRACE neutron   File 
/opt/stack/neutron/neutron/agent/securitygroups_rpc.py, line 213, in 
_update_security_group_info
  2014-09-15 16:54:38.167 1069 TRACE neutron 
self.firewall.update_security_group_rules(sg_id, sg_rules)
  2014-09-15 16:54:38.167 1069 TRACE neutron AttributeError: 
'NoopFirewallDriver' object has no attribute 'update_security_group_rules'
  2014-09-15 16:54:38.167 1069 TRACE neutron

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1369877/+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 1369871] Re: HTTP 500 is returned when using an invalid ip for defined network to attach interface

2014-09-16 Thread Qin Zhao

** Project changed: nova = neutron

** Also affects: nova
   Importance: Undecided
   Status: New

** Also affects: python-neutronclient
   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/1369871

Title:
  HTTP 500 is returned when using an invalid ip for defined network to
  attach interface

Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack Compute (Nova):
  New
Status in Python client library for Neutron:
  New

Bug description:
  When I post an 'attach interface' request to Nova with an invalid ip
  for defined network, Nova returns an HTTP 500 error and a confusing
  error message.

  REQ: curl -i 
'http://10.90.10.24:8774/v2/19abae5746b242d489d1c2862b228d8b/servers/4e863fad-e868-48a1-8735-2da9a38561e8/os-interface'
 -X POST -H Accept: application/json -H Content-Type: application/json -H 
User-Agent: python-novaclient -H X-Auth-Project-Id: Public -H 
X-Auth-Token: {SHA1}ce7267ae4e84b8f8457ab6a54c353a3e7c7d051c -d 
'{interfaceAttachment: {fixed_ips: [{ip_address: 1.1.1.1}], net_id: 
173854d5-333f-4c78-b5a5-10d2e9c8d827}}'
  INFO (connectionpool:187) Starting new HTTP connection (1): 10.90.10.24
  DEBUG (connectionpool:357) POST 
/v2/19abae5746b242d489d1c2862b228d8b/servers/4e863fad-e868-48a1-8735-2da9a38561e8/os-interface
 HTTP/1.1 500 128
  RESP: [500] {'date': 'Tue, 16 Sep 2014 06:26:54 GMT', 'content-length': 
'128', 'content-type': 'application/json; charset=UTF-8', 
'x-compute-request-id': 'req-f69db2a5-a777-471a-b2b5-00aa2ecd2892'}
  RESP BODY: {computeFault: {message: The server has either erred or is 
incapable of performing the requested operation., code: 500}}

  
  In fact, Nova works perfect well. The error is caused by my incorrect input. 
Nova should be able to address this incorrect input, and return an HTTP 400 
error in order to to inform the user to correct the request.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1369871/+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 1369880] [NEW] Autocomplete HTML Attribute Not Disabled for Password Field in Horizon

Public bug reported:

Risk:  It maybe possible to bypass the web application's authentication
mechanism.

Recommend fix:  Correctly set the autocomplete attribute to off
Affected URL: https://Ip_address/settings/password/
https://Ip_address/auth/login/

Take the second URL's  test result and response for example:
GET /auth/login/?next=/admin/flavors/ HTTP/1.1
Cookie: csrftoken=jlQrGLuo8FZiE9SXhdfTYG7kauyQszJy; 
sessionid=t5b0864y0q00ridvvh5hniczvv40pl4s
Accept-Language: en-US
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: https://9.5.29.52/auth/login/?next=/admin/flavors/
Host: 9.5.29.52
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 
Firefox/24.0
HTTP/1.1 200 OK
Date: Thu, 11 Sep 2014 13:49:17 GMT
Server: Apache
Content-Language: en
Expires: Thu, 11 Sep 2014 13:49:17 GMT
Vary: Cookie,Accept-Language,Accept-Encoding
Cache-Control: max-age=0
X-Frame-Options: SAMEORIGIN
Last-Modified: Thu, 11 Sep 2014 13:49:17 GMT
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8
Set-Cookie: csrftoken=jlQrGLuo8FZiE9SXhdfTYG7kauyQszJy; expires=Thu, 
10-Sep-2015 13:49:19 GMT; Max-Age=31449600; Path=/; secure
Set-Cookie: sessionid=t5b0864y0q00ridvvh5hniczvv40pl4s; httponly; Path=/; secure
!DOCTYPE html
html
head
meta content='text/html; charset=utf-8' http-equiv='Content-Type' /
titleLogin - Cloud Management Dashboard/title
!--
Copyright 2014 IBM Corp.
Copyright 2014 OpenStack Foundation and others
--
link rel=stylesheet href=/static/dashboard/css/5730bed76fd3.css 
type=text/css media=screen /
link rel=shortcut icon href=/static/dashboard/img/favicon.png/
!--
Fix header padding issue in IE  10
--
!--[if lt IE 10 ]
style
.topbar {
padding-bottom: 0px;
}
/style
![endif]--
script type=text/javascript 
src=/static/dashboard/js/841198948869.js/script
script type=text/javascript charset=utf-8
/*
Added so that we can append Horizon scoped JS events to
the DOM load events without running in to the horizon
name-space not currently being defined since we load the
scripts at the bottom of the page.
*/
var addHorizonLoadEvent = function(func) {
var old_onload = window.onload;
if (typeof window.onload != 'function') {
window.onload = func;
} else {
window.onload = function() {
old_onload();
func();
}
}
}
/script
/head
body id=splash ng-app='hz'
!--
Copyright 2014 IBM Corp.
2014/9/12 222
Copyright 2014 OpenStack Foundation and others
--
div id= class=login 
div class=
div class=
div class=modal-header
h3Cloud Management Dashboard/h3
/div
form id=
ng-controller=DummyCtrl
name=
autocomplete=on
class=
action=/auth/login/
method=POST
input type='hidden' name='csrfmiddlewaretoken' 
value='jlQrGLuo8FZiE9SXhdfTYG7kauyQszJy' /
div class=modal-body clearfix
fieldset
div class=form-group clearfix error
span class=help-blockpYou do not have permission to access the 
resource:/p
pb/admin/flavors//b/p
pLogin as different user or go back to a href=/home/ home page/a/p
/span
/div
input type=hidden name=next value=/admin/flavors/ /
input id=id_region name=region type=hidden 
value=http://9.5.29.52:5000/v2.0; /
!-- div class=form-group form-field clearfix 
label for=id_usernameUser Name:/label
span class=help-block /span
input autofocus=autofocus id=id_username name=username type=text /
/div
--
div class=form-group 
label class=control-label  for=id_usernameUser Name/label
div class= 
input autofocus=autofocus class= form-control id=id_username 
name=username type=text /
/div
/div
!-- div class=form-group form-field clearfix 
label for=id_passwordPassword:/label
span class=help-block /span
input id=id_password name=password type=password /
 issue here
/div
--
div class=form-group 
label class=control-label  for=id_passwordPassword/label
div class= 
input class= form-control id=id_password name=password type=password 
/  ---issue here
/div
/div
/fieldset
/div
div class=modal-footer
button type=submit class=btn btn-primary pull-rightSign In/button
div class=openstack-logo/div
div class=copyright
Licensed Materials - Property of IBM Corp. 5765-SKCbr/
copy; Copyright IBM Corp. 2010, 2014 All Rights Reservedbr/
copy; Copyright 2014 OpenStack Foundation and others
/div
/div
/form
/div
/div
/div
2014/9/12 223
TOC
div id=footer
/div
!--
Copyright 2014 IBM Corp.
Copyright 2014 OpenStack Foundation and oth
...
...
...

** 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/1369880

Title:
  Autocomplete HTML Attribute Not Disabled for Password Field in Horizon

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Risk:  It maybe possible to bypass the web application's
  authentication mechanism.

  Recommend fix:  Correctly set the autocomplete attribute to off
  Affected URL: https://Ip_address/settings/password/

[Yahoo-eng-team] [Bug 1369865] [NEW] Permanent Cookie Contains Sensitive Session Information

Public bug reported:

Affected URL: https://Ip_address/admin/
Entity: csrftoken (Cookie)
Risk: It may be possible to steal session information (cookies) that was kept 
on disk as permanent cookies.

Causes: The web application stores sensitive session information in a
permanent cookie (on disk)

Recommend Fix: Avoid storing sensitive session information in permanent
cookies

Test requests and response:
GET /admin/ HTTP/1.1
Host: 9.5.29.52
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 
Firefox/24.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Referer: https://9.5.29.52/
Cookie: csrftoken=JPjBiDp6Ex6YDw3sgfZPCTPUwWKZdZTm; 
sessionid=oad3bpy15qm8ntml9wx604yr79cc6zpb
Connection: keep-alive
HTTP/1.1 200 OK
Date: Fri, 12 Sep 2014 07:52:50 GMT
Server: Apache
Vary: Accept-Language,Cookie,Accept-Encoding
X-Frame-Options: SAMEORIGIN
Content-Language: en
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html
Set-Cookie: csrftoken=silTP6ARbLvXohF6YYFLlWHce0KZkjPy; expires=Fri, 
11-Sep-2015 07:52:52 GMT; Max-Age=31449600; Path=/; secure
Set-Cookie: sessionid=ygq094phgr6og471j6n0asq7x6q37j6n; httponly; Path=/; secure
!DOCTYPE html
html
head
2014/9/12 516
meta content='text/html; charset=utf-8' http-equiv='Content-Type' /
titleUsage Overview - Cloud Management Dashboard/title
!--
Copyright 2014 IBM Corp.
Copyright 2014 OpenStack Foundation and others
--
link rel=stylesheet href=/static/dashboard/css/5730bed76fd3.css 
type=text/css media=screen /
link rel=shortcut icon href=/static/dashboard/img/favicon.png/
!--
Fix header padding issue in IE  10
--
!--[if lt IE 10 ]
style
.topbar {
padding-bottom: 0px;
}
/style
![endif]--
script type=text/javascript 
src=/static/dashboard/js/841198948869.js/script
script type=text/javascript charset=utf-8
/*
Added so that we can append Horizon scoped JS events to
the DOM load events without running in to the horizon
name-space not currently being defined since we load the
scripts at the bottom of the page.
*/
var addHorizonLoadEvent = function(func) {
var old_onload = window.onload;
if (typeof window.onload != 'function') {
window.onload = func;
} else {
window.onload = function() {
old_onload();
func();
}
}
}
/script
/head
body id= ng-app='hz'
div id=container
div class='topbar'
!--
Copyright 2014 IBM Corp.
Copyright 2014 OpenStack Foundation and others
--
h1 class=branda href=/home/Cloud Management Dashboard/a/h1
div id=user_info class=pull-right
div id=tenant_switcher class=dropdown switcher_bar hide_image  
tabindex=1
divadmin/div
/div
div id=profile_editor_switcher class=dropdown switcher_bar tabindex='1'
a class=dropdown-toggle data-toggle=dropdown 
href=#profile_editor_switcher
divadmin/div
/a
ul id=editor_list class=dropdown-menu
li class='divider'/li
lia href=/settings/Settings/a/li
lia href=http://docs.openstack.org; target=_newHelp/a/li
lia href=/auth/logout/Sign Out/a/li
/ul
/div
img class=brand_icon src=/static/dashboard/img/logo.png alt=/
/div
2014/9/12 517
TOC
/div
div id='main_content'
div class=messages
/div
div class='sidebar'
div
dl class=nav_accordion
dt 
divProject/div
/dt
dd style=display:none;
divh4divCompute/div/h4
ul
lia href=/project/ tabindex=1 Overview/a/li
lia href=/project/instances/ tabindex=2 Instances/a/li
lia href=/project/volumes/ tabindex=3 Volumes/a/li
lia href=/project/images/ tabindex=4 Images/a/li
lia href=/project/access_and_security/ tabindex=5 Access amp; 
Security/a/li
/ul
/div
divh4divNetwork/div/h4
ul
lia href=/project/network_topology/ tabindex=1 Network Topology/a/li
lia href=/project/networks/ tabindex=2 Networks/a/li
lia href=/project/routers/ tabindex=3 Routers/a/li
/ul
/div
divh4divOrchestration/div/h4
ul
lia href=/project/stacks/ tabindex=1 Stacks/a/li
/ul
/div
...
...
...

** Affects: horizon
 Importance: Undecided
 Status: New

** Also affects: openstack-chef
   Importance: Undecided
   Status: New

** No longer affects: ossa

** Also affects: horizon
   Importance: Undecided
   Status: New

** No longer affects: openstack-chef

** Description changed:

  Affected URL: https://Ip_address/admin/
  Entity: csrftoken (Cookie)
- Risk: It may be possible to steal session information (cookies) that was kept 
on disk as permanent cookies
- Causes: The web application stores sensitive session information in a 
permanent cookie (on disk)
- Recommend Fix: Avoid storing sensitive session information in permanent 
cookies
+ Risk: It may be possible to steal session information (cookies) that was kept 
on disk as permanent cookies.
+ 
+ Causes: The web application stores sensitive session information in a
+ permanent cookie (on disk)
+ 
+ Recommend Fix: Avoid storing sensitive session information in permanent
+ cookies
  
  Test requests and response:
  GET /admin/ HTTP/1.1
  Host: 9.5.29.52
  User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 
Firefox/24.0
  Accept:

[Yahoo-eng-team] [Bug 1369883] [NEW] detach a volume tips translate error

2014-09-16 Thread Sun Jing

Public bug reported:

when detach a volume,the tips showing to be 断开zhong云硬盘,if dashboard language 
choose chinese.It should be 断开中云硬盘.
 Maybe there is a translating error with file 
openstack\horizon\openstack_dashboard\locale\zh_CN\LC_MESSAGES\django.po.

** 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/1369883

Title:
  detach a volume tips translate error

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  when detach a volume,the tips showing to be 断开zhong云硬盘,if dashboard 
language choose chinese.It should be 断开中云硬盘.
   Maybe there is a translating error with file 
openstack\horizon\openstack_dashboard\locale\zh_CN\LC_MESSAGES\django.po.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1369883/+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 1369945] [NEW] libvirt: libvirt reports even single cell NUMA topologies

2014-09-16 Thread Nikola Đipanov

Public bug reported:

Libvirt reports even single numa nodes in it's hypervisor capabilities
(which we use to figure out if a compute host is a NUMA host). This is
technically correct, but in Nova we assume that to mean - no NUMA
capabilities when scheduling instances.

Right now we just pass what we get from libvirt as is to the resource
tracker, but we need to make sure that single NUMA node hypervisors
are reported back to the resource tracker as non-NUMA.

** Affects: nova
 Importance: High
 Status: Confirmed


** Tags: libvirt

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

Title:
  libvirt: libvirt reports even single cell NUMA topologies

Status in OpenStack Compute (Nova):
  Confirmed

Bug description:
  Libvirt reports even single numa nodes in it's hypervisor capabilities
  (which we use to figure out if a compute host is a NUMA host). This is
  technically correct, but in Nova we assume that to mean - no NUMA
  capabilities when scheduling instances.

  Right now we just pass what we get from libvirt as is to the resource
  tracker, but we need to make sure that single NUMA node hypervisors
  are reported back to the resource tracker as non-NUMA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1369945/+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 1369944] [NEW] Volumes Snapshots table snapshot description truncated

2014-09-16 Thread Matthias Runge

Public bug reported:

Project  Compute  Volumes  Volumes  Snapshots

when using very long names or very long descriptions, texts are not
wrapped, but truncated.

** 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/1369944

Title:
   Volumes  Snapshots table snapshot description truncated

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Project  Compute  Volumes  Volumes  Snapshots

  when using very long names or very long descriptions, texts are not
  wrapped, but truncated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1369944/+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 1369955] [NEW] Double delete a floating ip range using nova-manage command does not return not found error

2014-09-16 Thread Mh Raies

Public bug reported:

I performed following steps -

1. Create a single floating IP (it may in CIDR format also)
root@mc1:/home/ubuntu# nova-manage  floating create --pool test-nova 
--ip_range 68.99.26.170

2. List floating IPs
root@mc1:/home/ubuntu# nova-manage floating list
None68.99.26.170Nonetest-nova   eth0

3. Delete create IP (or IP pool)
root@mc1:/home/ubuntu# nova-manage floating delete 68.99.26.170
2014-09-16 17:43:22.961 15567 WARNING nova.db.sqlalchemy.api 
[req-85523a81-b6ce-4cfd-b474-fdd3a93f70f9 None None] Change will make usage 
less than 0 for the following resources: ['floating_ips']

4. Check deletion in list -
root@mc1:/home/ubuntu# nova-manage floating list
No floating IP addresses have been defined.

5. Again delete deleted floating IP (or Pool)
root@mc1:/home/ubuntu# nova-manage floating delete 68.99.26.170
here command is successful
root@mc1:/home/ubuntu#

In my opinion at step5 there should be some checks (if not implemented)
or it should return an Error saying request IP range does not exist. (As
it is already deleted)


But in this case step 5 is successful without any error message.

** 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/1369955

Title:
  Double delete a floating ip range using nova-manage command does not
  return not found error

Status in OpenStack Compute (Nova):
  New

Bug description:
  I performed following steps -

  1. Create a single floating IP (it may in CIDR format also)
  root@mc1:/home/ubuntu# nova-manage  floating create --pool test-nova 
--ip_range 68.99.26.170

  2. List floating IPs
  root@mc1:/home/ubuntu# nova-manage floating list
  None68.99.26.170Nonetest-nova   eth0

  3. Delete create IP (or IP pool)
  root@mc1:/home/ubuntu# nova-manage floating delete 68.99.26.170
  2014-09-16 17:43:22.961 15567 WARNING nova.db.sqlalchemy.api 
[req-85523a81-b6ce-4cfd-b474-fdd3a93f70f9 None None] Change will make usage 
less than 0 for the following resources: ['floating_ips']

  4. Check deletion in list -
  root@mc1:/home/ubuntu# nova-manage floating list
  No floating IP addresses have been defined.

  5. Again delete deleted floating IP (or Pool)
  root@mc1:/home/ubuntu# nova-manage floating delete 68.99.26.170
  here command is successful
  root@mc1:/home/ubuntu#

  In my opinion at step5 there should be some checks (if not
  implemented) or it should return an Error saying request IP range does
  not exist. (As it is already deleted)

  
  But in this case step 5 is successful without any error message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1369955/+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 1367354] Re: oslo.db's master breaks unittest in OS projects

2014-09-16 Thread Victor Sergeyev

** Changed in: oslo.db
   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/1367354

Title:
  oslo.db's master breaks unittest in OS projects

Status in OpenStack Identity (Keystone):
  Fix Committed
Status in OpenStack Compute (Nova):
  Confirmed
Status in Oslo Database library:
  Fix Released

Bug description:
  When I run the unittests in different OpennStack projects using the
  latest oslo.db there were a lot of failures on Nova, Neutron and
  Keystone. The lot of tests raises OperationalError: (OperationalError)
  cannot start a transaction within a transaction 'BEGIN' () The right
  approach is to fix these projects, but we are in the end of J release,
  so I'm not sure, that we can merge these fixes fast.

  This issue was caused by commit [1], so the faster and simplest
  approach is - to revert this commit an continue our fork on this in K

  [1]
  
https://github.com/openstack/oslo.db/commit/78fd290a89545de31e5c13f3085df23368a8afaa

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1367354/+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 1370022] [NEW] Keystone cannot cope with being behind an SSL terminator for version list

2014-09-16 Thread Andrey Pavlov

Public bug reported:

When keystone set up behind SSL termintator then it returns 'http' as
protocol in URLs returned by version list command -

user@host:~$ curl https://MYHOST:5000/

{versions: {values: [{status: stable, updated:
2013-03-06T00:00:00Z, media-types: [{base: application/json,
type: application/vnd.openstack.identity-v3+json}, {base:
application/xml, type:
application/vnd.openstack.identity-v3+xml}], id: v3.0, links:
[{href: http://MYHOST:5000/v3/;, rel: self}]}, {status:
stable, updated: 2014-04-17T00:00:00Z, media-types: [{base:
application/json, type:
application/vnd.openstack.identity-v2.0+json}, {base:
application/xml, type:
application/vnd.openstack.identity-v2.0+xml}], id: v2.0, links:
[{href: http://MYHOST:5000/v2.0/;, rel: self}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/content/;,
type: text/html, rel: describedby}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/identity-
dev-guide-2.0.pdf, type: application/pdf, rel:
describedby}]}]}}

my ha_proxyconfig -

frontend keystone_main_frontend
bind 172.31.7.253:5000
bind 172.31.7.252:5000 ssl crt /etc/haproxy/certs/runtime
reqadd X-Forwarded-Proto:\ https if { ssl_fc }
default_backend keystone_main_backend
option httpclose
option http-pretend-keepalive
option forwardfor

backend keystone_main_backend
server HOST1 172.31.0.10:5000 check
server HOST2 172.31.0.12:5000 check
server HOST3 172.31.0.16:5000 check

Similar bug is here https://bugs.launchpad.net/heat/+bug/123

And because of this bug last cinder client doesn't work -

user@host:~$cinder --os-username admin --os-tenant-name admin --os-password 
password --os-auth-url https://MYHOST:5000/v2.0/ --endpoint-type publicURL 
--debug list
ERROR: Unable to establish connection to http://MYHOST:5000/v2.0/tokens


Also - if I set public_endpoint and admin_endpoint in keystone.conf to use 
'https' proto then all works.

** 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/1370022

Title:
  Keystone cannot cope with being behind an SSL terminator for version
  list

Status in OpenStack Identity (Keystone):
  New

Bug description:
  When keystone set up behind SSL termintator then it returns 'http' as
  protocol in URLs returned by version list command -

  user@host:~$ curl https://MYHOST:5000/

  {versions: {values: [{status: stable, updated:
  2013-03-06T00:00:00Z, media-types: [{base: application/json,
  type: application/vnd.openstack.identity-v3+json}, {base:
  application/xml, type:
  application/vnd.openstack.identity-v3+xml}], id: v3.0, links:
  [{href: http://MYHOST:5000/v3/;, rel: self}]}, {status:
  stable, updated: 2014-04-17T00:00:00Z, media-types: [{base:
  application/json, type:
  application/vnd.openstack.identity-v2.0+json}, {base:
  application/xml, type:
  application/vnd.openstack.identity-v2.0+xml}], id: v2.0,
  links: [{href: http://MYHOST:5000/v2.0/;, rel: self},
  {href: http://docs.openstack.org/api/openstack-identity-
  service/2.0/content/, type: text/html, rel: describedby},
  {href: http://docs.openstack.org/api/openstack-identity-service/2.0
  /identity-dev-guide-2.0.pdf, type: application/pdf, rel:
  describedby}]}]}}

  my ha_proxyconfig -

  frontend keystone_main_frontend
  bind 172.31.7.253:5000
  bind 172.31.7.252:5000 ssl crt /etc/haproxy/certs/runtime
  reqadd X-Forwarded-Proto:\ https if { ssl_fc }
  default_backend keystone_main_backend
  option httpclose
  option http-pretend-keepalive
  option forwardfor

  backend keystone_main_backend
  server HOST1 172.31.0.10:5000 check
  server HOST2 172.31.0.12:5000 check
  server HOST3 172.31.0.16:5000 check

  Similar bug is here https://bugs.launchpad.net/heat/+bug/123

  And because of this bug last cinder client doesn't work -

  user@host:~$cinder --os-username admin --os-tenant-name admin --os-password 
password --os-auth-url https://MYHOST:5000/v2.0/ --endpoint-type publicURL 
--debug list
  ERROR: Unable to establish connection to http://MYHOST:5000/v2.0/tokens

  
  Also - if I set public_endpoint and admin_endpoint in keystone.conf to use 
'https' proto then all works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1370022/+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 1370019] [NEW] unshelve and resize instance unnecessarily logs ‘image not found’ error/warning messages

2014-09-16 Thread Pranali Deore

Public bug reported:

unshelve and resize instance (created by bootable volume) unnecessarily
logs ‘image not found’ error/warning messages

In both the cases, it logs following misleading error/warning messages
in the compute.log when image_id_or_uri is passed as None to
nova/compute/utils-get_image_metadata method.

14-09-05 03:41:54.834 ERROR glanceclient.common.http 
[req-80c9db2e-cc3d-481c-a5a3-babd917a3698 admin admin] Request returned failure 
status 404.
14-09-05 03:41:54.834 WARNING nova.compute.utils 
[req-80c9db2e-cc3d-481c-a5a3-babd917a3698 admin admin]  [instance: 
d5b137ab-19a1-484a-a828-6a229ec66950] Can't access image : Image  could not be 
found.

** Affects: nova
 Importance: Undecided
 Assignee: Pranali Deore (pranali-deore)
 Status: New


** Tags: ntt

** Changed in: nova
 Assignee: (unassigned) = Pranali Deore (pranali-deore)

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

Title:
  unshelve and resize instance unnecessarily logs ‘image not found’
  error/warning messages

Status in OpenStack Compute (Nova):
  New

Bug description:
  unshelve and resize instance (created by bootable volume)
  unnecessarily logs ‘image not found’ error/warning messages

  In both the cases, it logs following misleading error/warning messages
  in the compute.log when image_id_or_uri is passed as None to
  nova/compute/utils-get_image_metadata method.

  14-09-05 03:41:54.834 ERROR glanceclient.common.http 
[req-80c9db2e-cc3d-481c-a5a3-babd917a3698 admin admin] Request returned failure 
status 404.
  14-09-05 03:41:54.834 WARNING nova.compute.utils 
[req-80c9db2e-cc3d-481c-a5a3-babd917a3698 admin admin]  [instance: 
d5b137ab-19a1-484a-a828-6a229ec66950] Can't access image : Image  could not be 
found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1370019/+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 1370033] [NEW] Admin should be able to manually select the active instance of a HA router

2014-09-16 Thread Assaf Muller

Public bug reported:

Currently the admin doesn't know where is the master, and where are the
slaves for a given HA router (Until #1365453 is solved). Once that's
possible, the next step should be to enable the admin to manually move
the master state of a router from one agent to another. Manual
rescheduling is possible with legacy routers, and the equivalent should
be possible with HA routers.

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: l3-ha

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1370033

Title:
  Admin should be able to manually select the active instance of a HA
  router

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Currently the admin doesn't know where is the master, and where are
  the slaves for a given HA router (Until #1365453 is solved). Once
  that's possible, the next step should be to enable the admin to
  manually move the master state of a router from one agent to another.
  Manual rescheduling is possible with legacy routers, and the
  equivalent should be possible with HA routers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1370033/+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 1213212] Re: test_resize_server_confirm server failed to build

** Changed in: nova
   Status: Incomplete = Invalid

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

Title:
  test_resize_server_confirm server failed to build

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  When running tempest in parallel occasionally
  test_resize_server_confirm fails to build the server and goes into an
  error state see:

  2013-08-16 14:08:33.607 | 
==
  2013-08-16 14:08:33.607 | FAIL: 
tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_resize_server_confirm[gate,smoke]
  2013-08-16 14:08:33.607 | 
tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_resize_server_confirm[gate,smoke]
  2013-08-16 14:08:33.608 | 
--
  2013-08-16 14:08:33.608 | _StringException: Empty attachments:
  2013-08-16 14:08:33.608 |   stderr
  2013-08-16 14:08:33.609 |   stdout
  2013-08-16 14:08:33.609 | 
  2013-08-16 14:08:33.609 | Traceback (most recent call last):
  2013-08-16 14:08:33.609 |   File 
tempest/api/compute/servers/test_server_actions.py, line 161, in 
test_resize_server_confirm
  2013-08-16 14:08:33.609 | 
self.client.wait_for_server_status(self.server_id, 'VERIFY_RESIZE')
  2013-08-16 14:08:33.609 |   File 
tempest/services/compute/json/servers_client.py, line 165, in 
wait_for_server_status
  2013-08-16 14:08:33.609 | raise 
exceptions.BuildErrorException(server_id=server_id)
  2013-08-16 14:08:33.610 | BuildErrorException: Server 
ed3c7212-f4b6-4365-91b8-bc9e1a60 failed to build and is in ERROR status
  2013-08-16 14:08:33.610 | 
  2013-08-16 14:08:33.610 | 
  2013-08-16 14:08:33.611 | 
==

  A set of logs for this failure can be found here:
  
http://logs.openstack.org/63/42063/1/gate/gate-tempest-devstack-vm-testr-full/fa32f42/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1213212/+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 1240355] Re: Broken pipe error when copying image from glance to vSphere

Closing as invalid, I think the glance direction is more fruitful

** Changed in: nova
   Status: Incomplete = Invalid

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

Title:
  Broken pipe error when copying image from glance to vSphere

Status in OpenStack Image Registry and Delivery Service (Glance):
  New
Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Using the VMwareVCDriver on the latest nova (6affe67067) from master,
  launching an image for the first time is failing when copying image
  from Glance to vSphere. The error that shows in the nova log is:

  Traceback (most recent call last):
File /opt/stack/nova/nova/virt/vmwareapi/io_util.py, line 176, in _inner
  self.output.write(data)
File /opt/stack/nova/nova/virt/vmwareapi/read_write_util.py, line 143, in 
write
  self.file_handle.send(data)
File /usr/lib/python2.7/httplib.py, line 790, in send
  self.sock.sendall(data)
File /usr/local/lib/python2.7/dist-packages/eventlet/green/ssl.py, line 
131, in sendall
  v = self.send(data[count:])
File /usr/local/lib/python2.7/dist-packages/eventlet/green/ssl.py, line 
107, in send
  super(GreenSSLSocket, self).send, data, flags)
File /usr/local/lib/python2.7/dist-packages/eventlet/green/ssl.py, line 
77, in 
  return func(*a, **kw)
File /usr/lib/python2.7/ssl.py, line 198, in send
  v = self._sslobj.write(data)
  error: [Errno 32] Broken pipe

  To reproduce, launch an instance using an image that has not yet been
  uploaded to vSphere. I have attached the full log here:
  http://paste.openstack.org/show/48536/

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1240355/+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 1370037] [NEW] bulk termination of instances

2014-09-16 Thread Matthias Runge

Public bug reported:

while terminating a bulk of instances from the horizon, the first
instance termination failed, the other instances all stayed in available
status.

Steps to Reproduce:
1. Delete a bulk of instances
2. The first deletion process should fail  the instance status should turn to 
Error

Actual results:
The other instances are not been terminated

Expected results:
The termination of the instances should continue to the other instances

** 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/1370037

Title:
  bulk termination of instances

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  while terminating a bulk of instances from the horizon, the first
  instance termination failed, the other instances all stayed in
  available status.

  Steps to Reproduce:
  1. Delete a bulk of instances
  2. The first deletion process should fail  the instance status should turn 
to Error

  Actual results:
  The other instances are not been terminated

  Expected results:
  The termination of the instances should continue to the other instances

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370037/+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 1260301] Re: Expired vnc token doesn't fail fast

outside of project control

** Changed in: nova
   Status: Incomplete = Won't Fix

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

Title:
  Expired vnc token doesn't fail fast

Status in OpenStack Compute (Nova):
  Won't Fix

Bug description:
  If an expired vnc token is used, I'd expect an appropriate HTTP
  response. However, currently novnc just hangs at Starting VNC
  handshake.

  To reproduce

  1. nova get-vnc-console uuid novnc = returns a URI with the token
  2. point browser to the returned URI after the expiry
  3. page hangs at Starting VNC handshake

  Expected response

  An appropriate HTTP response

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1260301/+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 964763] Re: confusing network manager read_deleted usage

While there is definitely debt in here, I'm not convinced that this
artifact helps us move forward on it. I'm going to mark as Opinion. Feel
free to reopen.

** Changed in: nova
   Status: Incomplete = Opinion

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

Title:
  confusing network manager read_deleted usage

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  This is related to the fix for bug #939580

  Reading the code:

  # NOTE(francois.charlier): in some cases the instance might be
 
  # deleted before the IPs are released, so we need to get deleted  
 
  # instances too   
 
  read_deleted_context = context.elevated(read_deleted='yes')
  
  try:
  fixed_ips = self.db.fixed_ip_get_by_instance(read_deleted_context,
   instance_id)
  except exception.FixedIpNotFoundForInstance:

  then:

def fixed_ip_get_by_instance(context, instance_id):
result = model_query(context, models.FixedIp, read_deleted=no).\
 filter_by(instance_id=instance_id).\
 all()

  then:

def model_query(context, *args, **kwargs):
...
read_deleted = kwargs.get('read_deleted') or context.read_deleted

  It's obvious the read_deleted flag is ignored here. And, in any case,
  we only want to read deleted instances, not deleted fixed IPs.

  Now, I understand what's going on - later, in
  _disassociate_floating_ip(), we do:

  instance = self.db.instance_get(context, fixed_ip['instance_id'])

  and it's *this* call we want to pass the read_deleted flag.

  I started moving the setting of read_deleted on the context closer to
  where we actually needed, but it's hard to do this with confidence
  because there are many DB calls which the author of the fix may have
  intended to pass read_deleted='yes' to.  This is a sign that we've
  seriously confused the code by setting read_deleted='yes' in a fairly
  arbitrary place.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/964763/+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 1184482] Re: Unable to connect the SQL server with openstack server most of time while installing openstack essex

very old bug

** Changed in: nova
   Status: Incomplete = Invalid

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

Title:
  Unable to connect the SQL server with openstack server most of time
  while installing openstack essex

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  When i try to create Openstack essex most of the time the SQL Server is not 
communicating with openstack server  and it fails,Not able to get the login 
page. 
  command :
  sudo ./osinstall.sh -f 172.16.1.0/24 -f 11.1.0.0/16 -s 512 -p eth2 -t demo -v 
qemu

  When i type the above command it says SQL Server error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1184482/+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 1174401] Re: Unittests test_libvirt fails if libvirt actually installed on system

old incomplete bug

** Changed in: nova
   Status: Incomplete = Invalid

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

Title:
  Unittests test_libvirt fails if libvirt actually installed on system

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  I'm trying to run unittests and got lot of fails.
  I have libvirt installed and it seems that fake libvirt drivver don't work in 
such env.

  
  ==
  FAIL: nova.tests.test_libvirt.LibvirtConnTestCase.test_xml_and_uri
  --
  _StringException: pythonlogging:'nova': {{{
  Loading network driver 'nova.network.linux_net'
  Loading network driver 'nova.network.linux_net'
  Loading network driver 'nova.network.linux_net'
  URI qemu:///system does not support events
  }}}

  Traceback (most recent call last):
File /root/openstack/nova/app/nova/tests/test_libvirt.py, line 946, in 
test_xml_and_uri
  expect_kernel=True, expect_ramdisk=True)
File /root/openstack/nova/app/nova/tests/test_libvirt.py, line 2011, in 
_check_xml_and_uri
  (check(tree), expected_result, i))
  MismatchError: !=:
  reference = '00020003-0004-0005-0006-000700080009'
  actual= 'cef19ce0-0ca2-11df-855d-b19fbce37686'
  : 00020003-0004-0005-0006-000700080009 != 
cef19ce0-0ca2-11df-855d-b19fbce37686 failed check 12

    begin captured logging  
  nova.network.driver: INFO: Loading network driver 'nova.network.linux_net'
  nova.network.driver: INFO: Loading network driver 'nova.network.linux_net'
  nova.network.driver: INFO: Loading network driver 'nova.network.linux_net'
  nova.virt.libvirt.driver: WARNING: URI qemu:///system does not support events
  -  end captured logging  -

  ==
  FAIL: nova.tests.test_libvirt.LibvirtConnTestCase.test_xml_and_uri_no_kernel
  --
  _StringException: pythonlogging:'nova': {{{
  Loading network driver 'nova.network.linux_net'
  Loading network driver 'nova.network.linux_net'
  Loading network driver 'nova.network.linux_net'
  URI qemu:///system does not support events
  }}}

  Traceback (most recent call last):
File /root/openstack/nova/app/nova/tests/test_libvirt.py, line 939, in 
test_xml_and_uri_no_kernel
  expect_kernel=False, expect_ramdisk=False)
File /root/openstack/nova/app/nova/tests/test_libvirt.py, line 2011, in 
_check_xml_and_uri
  (check(tree), expected_result, i))
  MismatchError: !=:
  reference = '00020003-0004-0005-0006-000700080009'
  actual= 'cef19ce0-0ca2-11df-855d-b19fbce37686'
  : 00020003-0004-0005-0006-000700080009 != 
cef19ce0-0ca2-11df-855d-b19fbce37686 failed check 14

    begin captured logging  
  nova.network.driver: INFO: Loading network driver 'nova.network.linux_net'
  nova.network.driver: INFO: Loading network driver 'nova.network.linux_net'
  nova.network.driver: INFO: Loading network driver 'nova.network.linux_net'
  nova.virt.libvirt.driver: WARNING: URI qemu:///system does not support events
  -  end captured logging  -

  ==
  FAIL: nova.tests.test_libvirt.LibvirtConnTestCase.test_xml_and_uri_no_ramdisk
  --
  _StringException: pythonlogging:'nova': {{{
  Loading network driver 'nova.network.linux_net'
  Loading network driver 'nova.network.linux_net'
  Loading network driver 'nova.network.linux_net'
  URI qemu:///system does not support events
  }}}

  Traceback (most recent call last):
File /root/openstack/nova/app/nova/tests/test_libvirt.py, line 933, in 
test_xml_and_uri_no_ramdisk
  expect_kernel=True, expect_ramdisk=False)
File /root/openstack/nova/app/nova/tests/test_libvirt.py, line 2011, in 
_check_xml_and_uri
  (check(tree), expected_result, i))
  MismatchError: !=:
  reference = '00020003-0004-0005-0006-000700080009'
  actual= 'cef19ce0-0ca2-11df-855d-b19fbce37686'
  : 00020003-0004-0005-0006-000700080009 != 
cef19ce0-0ca2-11df-855d-b19fbce37686 failed check 12

    begin captured logging  
  nova.network.driver: INFO: Loading network driver 'nova.network.linux_net'
  nova.network.driver: INFO: Loading network driver 'nova.network.linux_net'
  nova.network.driver: INFO: Loading network driver 'nova.network.linux_net'
  nova.virt.libvirt.driver: WARNING: URI qemu:///system does not support events
  -  end captured logging  -

[Yahoo-eng-team] [Bug 1147841] Re: deleted columns should be NOT NULL

Yeh, I think this was fixed, please reopen if not

** Changed in: nova
   Status: Incomplete = 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/1147841

Title:
  deleted columns should be NOT NULL

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  NULL is not valid for 'deleted' columns now.  Default values should be
  0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1147841/+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 1175290] Re: Block migrating an instance from an O_DIRECT supported fs to non O_DIRECT supported fs fails

honestly, if you are going to do live migration it is assumed that you
have similar back ends. I'm not convinced a valid use case is live
migration to different filesystems.

** Changed in: nova
   Status: Incomplete = Won't Fix

** Changed in: nova
   Status: Won't Fix = Opinion

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

Title:
  Block migrating an instance from an O_DIRECT supported fs to non
  O_DIRECT supported fs fails

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  I tried block migrating an instance from a server that can use
  O_DIRECT to a server that has ZFS as a filesystem. This fails with
  libvirt complaining about:

  2013-05-01 19:12:05.286+: 12030: error : qemuProcessWaitForMonitor:1796 : 
internal error process exited while connecting to monitor: char device 
redirected to /dev/pts/38
  kvm: -drive 
file=/var/lib/nova/instances/instance-00ae/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none:
 could not open disk image /var/lib/nova/instances/instance-00ae/disk: 
Invalid argument

  
  This either needs to be checked and fail or (preferably) the libvirt.xml 
needs to be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1175290/+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 1370058] [NEW] Refactor metadef ORM as_dict method to to_dict for consistency

2014-09-16 Thread Wayne

Public bug reported:

The Metadef ORM classes should refactor as_dict to to_dict to be
consistent with other glance ORM classes.

** Affects: glance
 Importance: Undecided
 Assignee: Wayne (wayne-okuma)
 Status: New

** Changed in: glance
 Assignee: (unassigned) = Wayne (wayne-okuma)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1370058

Title:
  Refactor metadef ORM as_dict method to to_dict for consistency

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  The Metadef ORM classes should refactor as_dict to to_dict to be
  consistent with other glance ORM classes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1370058/+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 1328872] Re: Launch an instance with OpenStack Networking (neutron) in OpenStack Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora - icehouse Failed to close

2014-09-16 Thread Jaroslav Henner

Adding log with TRACE

augeas-libs.x86_641.1.0-12.el7   @rhel7-released
openstack-nova-api.noarch 2014.1.2-1.el7ost  @puddle
openstack-nova-common.noarch  2014.1.2-1.el7ost  @puddle
openstack-nova-compute.noarch 2014.1.2-1.el7ost  @puddle
python-nova.noarch2014.1.2-1.el7ost  @puddle


** Also affects: nova
   Importance: Undecided
   Status: New

** Attachment added: log
   https://bugs.launchpad.net/nova/+bug/1328872/+attachment/4205244/+files/log

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

Title:
  Launch an instance with OpenStack Networking (neutron) in OpenStack
  Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora  -
  icehouse  Failed to close augeas aug_close: do_aug_close: you must
  call 'aug-init' first to initialize Augeas

Status in OpenStack Compute (Nova):
  New
Status in OpenStack Manuals:
  Expired

Bug description:
  centos6.5+icehouse
  when ：
   Launch an instance with OpenStack Networking (neutron) error

  2014-06-10 13:14:58.354 2786 INFO oslo.messaging._drivers.impl_qpid [-] 
Connected to AMQP server on controller:5672
  2014-06-10 13:23:39.074 2786 WARNING nova.virt.disk.vfs.guestfs 
[req-29f113b4-6f3a-4c59-a2dc-70c4bd0514af f9ebab09cbe1446fb07229f9ba53edad 
7fa0b1e3152c4082a876f6dcd28d5e15] Failed to close augeas aug_close: 
do_aug_close: you must call 'aug-init' first to initialize Augeas
  2014-06-10 13:23:40.555 2786 ERROR nova.virt.libvirt.driver 
[req-29f113b4-6f3a-4c59-a2dc-70c4bd0514af f9ebab09cbe1446fb07229f9ba53edad 
7fa0b1e3152c4082a876f6dcd28d5e15] An error occurred while trying to launch a 
defined domain with xml: domain type='kvm'



  
  [root@controller ~]# ssh-keygen
  Generating public/private rsa key pair.
  Enter file in which to save the key (/root/.ssh/id_rsa): 
  Enter passphrase (empty for no passphrase): 
  Enter same passphrase again: 
  Your identification has been saved in /root/.ssh/id_rsa.
  Your public key has been saved in /root/.ssh/id_rsa.pub.
  The key fingerprint is:
  8b:73:1d:01:76:5d:85:77:0b:c4:fb:0c:97:d0:4b:d7 root@controller
  The key's randomart image is:
  +--[ RSA 2048]+
  |o ..o|
  |   . o  .+.oE|
  |  .   =.*|
  |   . o = |
  |S .   =  |
  |   . o .   o |
  |  o o .  |
  |   o |
  | |
  +-+

  
  nova keypair-add --pub-key ~/.ssh/id_rsa.pub demo-key


  [root@controller ~]# nova keypair-list
  +--+-+
  | Name | Fingerprint |
  +--+-+
  | demo-key | 8b:73:1d:01:76:5d:85:77:0b:c4:fb:0c:97:d0:4b:d7 |
  +--+-+


  [root@controller ~]# nova flavor-list
  
++---+---+--+---+--+---+-+---+
  | ID | Name  | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor 
| Is_Public |
  
++---+---+--+---+--+---+-+---+
  | 1  | m1.tiny   | 512   | 1| 0 |  | 1 | 1.0 
| True  |
  | 2  | m1.small  | 2048  | 20   | 0 |  | 1 | 1.0 
| True  |
  | 3  | m1.medium | 4096  | 40   | 0 |  | 2 | 1.0 
| True  |
  | 4  | m1.large  | 8192  | 80   | 0 |  | 4 | 1.0 
| True  |
  | 5  | m1.xlarge | 16384 | 160  | 0 |  | 8 | 1.0 
| True  |
  
++---+---+--+---+--+---+-+---+

  
  [root@controller ~]# nova image-list
  
+--+-+++
  | ID   | Name| Status | 
Server |
  
+--+-+++
  | 8c030990-f828-4109-9b08-76f1057e145a | cirros-0.3.2-x86_64 | ACTIVE |   
 |
  
+--+-+++

  
  [root@controller ~]# neutron net-list
  
+--+--+-+
  | id   | name | subnets   
  |
  
+--+--+-+
  | 37e7c14d-1c8f-483d-be86-ed9081ba4131 | demo-net | 
8519df59-54fa-4441-99da-a5fa7bba5b36 192.168.1.0/24 |
  | 742c3506-8c38-4349-bb0b-740f8d593a5b | ext-net  | 
3f222bbf-617a-406d-86b1-30ec897a065d 10.16.114.0/24 |

[Yahoo-eng-team] [Bug 1370061] [NEW] Image metadata cleanup

2014-09-16 Thread Bartosz Fic

Public bug reported:

In this task there are few things which should be fixed for images in
views.py. Comments about appropriate issues in flavors are here
https://review.openstack.org/#/c/112874/  .  Main goal of this bug is to
fix review comments  in admin/images/views.py regarding exception
handling.

** Affects: horizon
 Importance: Undecided
 Assignee: Bartosz Fic (bartosz-fic)
 Status: New


** Tags: metadef

** Changed in: horizon
 Assignee: (unassigned) = Bartosz Fic (bartosz-fic)

** Description changed:

  In this task there are few things which should be fixed for images in
  views.py. Comments about appropriate issues in flavors are here
  https://review.openstack.org/#/c/112874/  .  Main goal of this bug is to
- fix review comments  in admin/flavors/views.py regarding exception
+ fix review comments  in admin/images/views.py regarding exception
  handling.

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

Title:
  Image metadata cleanup

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In this task there are few things which should be fixed for images in
  views.py. Comments about appropriate issues in flavors are here
  https://review.openstack.org/#/c/112874/  .  Main goal of this bug is
  to fix review comments  in admin/images/views.py regarding exception
  handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370061/+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 1370068] [NEW] Numa filter fails to get instance_properties

2014-09-16 Thread Przemyslaw Czesnowicz

Public bug reported:

NUMATopologyFilter tries to get  instance_properties from
filter_properties. But in fact instance_properties are in another
dictionary (request_spec)  that is embedded in  filter_properties.

** 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/1370068

Title:
  Numa filter fails to get instance_properties

Status in OpenStack Compute (Nova):
  New

Bug description:
  NUMATopologyFilter tries to get  instance_properties from
  filter_properties. But in fact instance_properties are in another
  dictionary (request_spec)  that is embedded in  filter_properties.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1370068/+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 1193284] Re: [nova-compute] list index out of range

Critical used to hide stack traces, we've fixed that fact. No idea what
the original bug was, but at least we could address these in the future.

** Changed in: nova
   Status: Incomplete = Invalid

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

Title:
  [nova-compute] list index out of range

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  OS: CentOS 6.4
  Version: openstack Grizzly

  I installed the openstack with yum. And I created a network use this command:
  nova-manage network create ippool --bridge_interface=br100 192.168.0.0/24 
1 250

  When restart nova-compute service, I got an CRITICAL error:
  2013-06-21 17:30:18 14836 INFO nova.compute.manager [-] Loading compute 
driver 'libvirt.LibvirtDriver'
  2013-06-21 17:30:18 14836 AUDIT nova.service [-] Starting compute node 
(version 2012.2.3-1.el6)
  2013-06-21 17:30:20 14836 CRITICAL nova [-] list index out of range

  My nova.conf is:
  ...
  # network
  network_manager=nova.network.manager.FlatDHCPManager
  my_ip=10.66.21.59
  fixed_range=192.168.0.0/24
  flat_network_bridge=br100
  cc_host=192.168.0.1
  network_size=8
  routing_source_ip=192.168.0.1
  ...

  nova-api/nova-network service started OK. Only nova-compute crashed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1193284/+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 1187872] Re: `message` attribute of NovaException not updated

** Changed in: nova
   Status: Incomplete = Opinion

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

Title:
  `message` attribute of NovaException not updated

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  NovaException's objects have a `message` attribute which can be used
  to override the error message for an exception.

  The class can be given a default such as:

  class MyException(NovaException):
  message = _('myexception')

  For additional flexibility, we also have the ability to override this
  on a per-object basis by passing in a custom `message`, like:

  exc = MyException('foo')

  
  Now when we render the error message like `repr(exc)` we see 'foo' as 
expected.

  However if we try to inspect the exception's `message` attribute,
  counterintuitively, we still see 'myexception'.

  The solution here is, for clarity, to set the instance attribute
  `message` with the overridden value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1187872/+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 1157275] Re: NoFloatingIpInterface: Interface eth0 not found

** Changed in: nova
   Status: Incomplete = Invalid

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

Title:
  NoFloatingIpInterface: Interface eth0 not found

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Similar problem than bug #992008 but in different piece of code.

  There have been a lot of patched since that bug, and now it happens
  again.

  In the line 555 of nova /nova/network/manager.py

  https://github.com/openstack/nova/blob/stable/folsom/nova/network/manager.py

  the function _associate_floating_ip is mising the interface
  declaration. If I add it:

   interface = FLAGS.public_interface or floating_ip['interface']

  then the configuration flag overrides the database flag, which is
  crucial for the multihost environments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1157275/+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 1258315] Re: Nova resize returns error code 255

very old incomplete bug

** Changed in: nova
   Status: Incomplete = Invalid

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

Title:
  Nova resize returns error code 255

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  When running nova resize command on an active VM, it completed
  without any error. However the VM went into error state. The scheduler
  somehow dispatched the job to an incorrect hypervisor (i.e.
  10.52.224.45 instead of actual hosting hypervisor wpc0043 which is
  10.52.225.43) and returned error code 255.

  # nova list
  | ID   | Name| Status | Task State | 
Power State | Networks  |
  
+--+-+++-+---+
  | 5eb01835-e41e-4bf3-9256-e8caa88686ff | cont011 | ACTIVE | None   | 
Running | contpoc=10.52.225.114 |
  
+--+-+++-+---+

  #nova show cont011
  
+--+--+
  | Property | Value
|
  
+--+--+
  | status   | ACTIVE   
|
  | updated  | 2013-12-05T19:45:12Z 
|
  | OS-EXT-STS:task_state| None 
|
  | OS-EXT-SRV-ATTR:host | wpc0043.svc.eng.pdx.wd   
|
  | key_name | None 
|
  | image| centos64 
(7cfa1455-0cd5-4e82-a7ec-418e25813415)  |
  | contpoc network  | 10.52.225.114
|
  | hostId   | 
9051224512ffaf16c9be843034687da080ab1e40f5e2fd57a5613d67 |
  | OS-EXT-STS:vm_state  | active   
|
  | OS-EXT-SRV-ATTR:instance_name| instance-001c
|
  | OS-SRV-USG:launched_at   | 2013-12-05T19:47:07.00   
|
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | wpc0043.svc.eng.pdx.wd   
|
  | flavor   | m1.medium (3)
|
  | id   | 5eb01835-e41e-4bf3-9256-e8caa88686ff 
|
  | security_groups  | [{u'name': u'default'}]  
|
  | OS-SRV-USG:terminated_at | None 
|
  | user_id  | 35073614013e42d8908f23597c4e2c8c 
|
  | name | cont011  
|
  | created  | 2013-12-05T19:45:04Z 
|
  | tenant_id| 544912394e764a099633ee4218ff822e 
|
  | OS-DCF:diskConfig| MANUAL   
|
  | metadata | {}   
|
  | os-extended-volumes:volumes_attached | []   
|
  | accessIPv4   |  
|
  | accessIPv6   |  
|
  | progress | 0
|
  | OS-EXT-STS:power_state   | 1
|
  | OS-EXT-AZ:availability_zone  | nova 
|
  | config_drive |  
|
  
+--+--+

  
  [root@wpc0016 ~]# nova flavor-list
  
++---+---+--+---+--+---+-+---+
  | ID | Name  | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor 
| Is_Public |
  
++---+---+--+---+--+---+-+---+
  | 1  | m1.tiny   | 512   | 1| 0 |  | 1 | 1.0 
| True  |

[Yahoo-eng-team] [Bug 1221147] Re: tempest.api.compute.servers.test_virtual_interfaces.VirtualInterfacesTestJSON fails on a swift check job

really old stack trace, no further debug, not actionable

** Changed in: nova
   Status: Incomplete = Invalid

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

Title:
  tempest.api.compute.servers.test_virtual_interfaces.VirtualInterfacesTestJSON
  fails on a swift check job

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  From: http://logs.openstack.org/26/44626/5/check/gate-tempest-
  devstack-vm-full/2ff3cca/console.html

  2013-09-05 05:03:35.761 | 
==
  2013-09-05 05:03:35.763 | FAIL: setUpClass 
(tempest.api.compute.servers.test_virtual_interfaces.VirtualInterfacesTestJSON)
  2013-09-05 05:03:35.773 | setUpClass 
(tempest.api.compute.servers.test_virtual_interfaces.VirtualInterfacesTestJSON)
  2013-09-05 05:03:35.791 | 
--
  2013-09-05 05:03:35.798 | _StringException: Traceback (most recent call last):
  2013-09-05 05:03:35.799 |   File 
tempest/api/compute/servers/test_virtual_interfaces.py, line 37, in setUpClass
  2013-09-05 05:03:35.799 | resp, server = 
cls.create_server(wait_until='ACTIVE')
  2013-09-05 05:03:35.799 |   File tempest/api/compute/base.py, line 140, in 
create_server
  2013-09-05 05:03:35.800 | server['id'], kwargs['wait_until'])
  2013-09-05 05:03:35.800 |   File 
tempest/services/compute/json/servers_client.py, line 174, in 
wait_for_server_status
  2013-09-05 05:03:35.800 | raise exceptions.TimeoutException(message)
  2013-09-05 05:03:35.801 | TimeoutException: Request timed out
  2013-09-05 05:03:35.801 | Details: Server 
949a5c32-a0fc-4bee-b3f1-26184d25aa75 failed to reach ACTIVE status within the 
required time (400 s). Current status: BUILD.

  This is the first test in the sequence that fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1221147/+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 1195361] Re: QEMU hypervisor type returned when libvirt_type = kvm

Honestly, it's really a docs bug.

** Also affects: openstack-manuals
   Importance: Undecided
   Status: New

** Changed in: nova
   Status: Incomplete = Won't Fix

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

Title:
  QEMU hypervisor type returned when libvirt_type = kvm

Status in OpenStack Compute (Nova):
  Won't Fix
Status in OpenStack Manuals:
  New

Bug description:
  As the following output indicates, the QEMU hypervisor type is used
  even when libvirt_type = kvm in nova.conf.

  # grep libvirt_type /etc/nova/nova.conf
  libvirt_type = kvm
  # nova hypervisor-show 1 | grep hypervisor_type
  | hypervisor_type  | QEMU 

  It appears that the OpenStack libvirt driver uses the libvirt
  connection type to determine the hypervisor type instead of the
  libvirt_type configuration option.  Should libvirt_type be used to
  determine KVM vs QEMU hypervisor type or is there another
  configuration for this?  From a user perspective, getting the QEMU
  versus KVM hypervisor type correct is important when setting the
  hypervisor_type property on an image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1195361/+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 1370077] [NEW] Set default vnic_type in neutron.

2014-09-16 Thread Baodong (Robert) Li

Public bug reported:

https://review.openstack.org/#/c/72334/ introduced binding:vnic_type
into the neutron port binding extension. Ml2 plugin has been updated to
support the vnic_type, but others may not. Nova expects every port has a
correct vnic_type. Therefore, neutron should make sure each port to have
this attribute set correctly. By default, the vnic_type should be
VNIC_TYPE_NORMAL

** Affects: neutron
 Importance: Undecided
 Assignee: Sam Betts (sambetts)
 Status: Confirmed

** Changed in: neutron
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1370077

Title:
  Set default vnic_type in neutron.

Status in OpenStack Neutron (virtual network service):
  Confirmed

Bug description:
  https://review.openstack.org/#/c/72334/ introduced binding:vnic_type
  into the neutron port binding extension. Ml2 plugin has been updated
  to support the vnic_type, but others may not. Nova expects every port
  has a correct vnic_type. Therefore, neutron should make sure each port
  to have this attribute set correctly. By default, the vnic_type should
  be VNIC_TYPE_NORMAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1370077/+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 1370080] [NEW] when we are redirected back to the launch instance box with error: You must select an image. and select an image, the volume size changes to 1GB.

Public bug reported:


1. launch an instance and select boot from image (create new volume)
2. in 'Device size (GB):' write 10GB
3. save without selecting an image

results:

when we are redirected back to the launch instance box with error: You
must select an image.  and select an image, the volume size changes to
1GB.

expected results: 
1. size should not change
2. if we have to change size, than size should be deleted completely once we 
select a new image.

** 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/1370080

Title:
  when we are redirected back to the launch instance box with error:
  You must select an image.  and select an image, the volume size
  changes to 1GB.

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  
  1. launch an instance and select boot from image (create new volume)
  2. in 'Device size (GB):' write 10GB
  3. save without selecting an image

  results:

  when we are redirected back to the launch instance box with error:
  You must select an image.  and select an image, the volume size
  changes to 1GB.

  expected results: 
  1. size should not change
  2. if we have to change size, than size should be deleted completely once we 
select a new image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370080/+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 1370088] [NEW] admin is getting: You are not allowed to terminate instances

Public bug reported:

I am getting a permission error on deleting of instances as user admin:

Error: You are not allowed to terminate instances: Dafna-763bb301-33da-
47d2-bb90-e83edb1199f1, Dafna-c8c9e379-8c1c-40fd-a7a9-f57cfeed072d,
Dafna-ab9aae09-d551-453c-b2ed-d40ba97a78dc,
Dafna-04267001-c7f2-4b74-ba81-f26f7846294d, Dafna-a44b71a0-b4f2-4223
-a0ac-e84c094ce23f, Dafna-a6fdb7aa-14ed-4b60-90c0-f144fc4eaf87, Dafna-
37795fc3-1d1a-40bb-9290-92f5938d017e, Dafna-2defb0fa-5057-4cb7-b60d-
bdf69629af85, Dafna-6b05e4f8-4b5f-4125-93ab-4cc4082116bb, Dafna-
49f6e328-9384-465b-b7b9-af51ae555c17


the instances in nova list did change to deleting and after a while were 
actually deleted. 
It took two UI refreshes to show the correct list


root@tigris01 ~(keystone_admin)]# nova list 
+--++++-+--+
| ID   | Name   
| Status | Task State | Power State | Networks |
+--++++-+--+
| 04267001-c7f2-4b74-ba81-f26f7846294d | 
Dafna-04267001-c7f2-4b74-ba81-f26f7846294d | BUILD  | deleting   | NOSTATE 
|  |
| 2defb0fa-5057-4cb7-b60d-bdf69629af85 | 
Dafna-2defb0fa-5057-4cb7-b60d-bdf69629af85 | BUILD  | deleting   | NOSTATE 
|  |
| 37795fc3-1d1a-40bb-9290-92f5938d017e | 
Dafna-37795fc3-1d1a-40bb-9290-92f5938d017e | BUILD  | deleting   | NOSTATE 
|  |
| 49f6e328-9384-465b-b7b9-af51ae555c17 | 
Dafna-49f6e328-9384-465b-b7b9-af51ae555c17 | BUILD  | deleting   | NOSTATE 
|  |
| 6b05e4f8-4b5f-4125-93ab-4cc4082116bb | 
Dafna-6b05e4f8-4b5f-4125-93ab-4cc4082116bb | BUILD  | deleting   | NOSTATE 
|  |
| 763bb301-33da-47d2-bb90-e83edb1199f1 | 
Dafna-763bb301-33da-47d2-bb90-e83edb1199f1 | BUILD  | deleting   | NOSTATE 
|  |
| a44b71a0-b4f2-4223-a0ac-e84c094ce23f | 
Dafna-a44b71a0-b4f2-4223-a0ac-e84c094ce23f | BUILD  | deleting   | NOSTATE 
|  |
| a6fdb7aa-14ed-4b60-90c0-f144fc4eaf87 | 
Dafna-a6fdb7aa-14ed-4b60-90c0-f144fc4eaf87 | BUILD  | deleting   | NOSTATE 
|  |
| ab9aae09-d551-453c-b2ed-d40ba97a78dc | 
Dafna-ab9aae09-d551-453c-b2ed-d40ba97a78dc | BUILD  | deleting   | NOSTATE 
|  |
| c8c9e379-8c1c-40fd-a7a9-f57cfeed072d | 
Dafna-c8c9e379-8c1c-40fd-a7a9-f57cfeed072d | BUILD  | deleting   | NOSTATE 
|  |
+--++++-+--+


[root@tigris01 ~(keystone_admin)]# nova list 
++--+++-+--+
| ID | Name | Status | Task State | Power State | Networks |
++--+++-+--+
++--+++-+--+
[root@tigris01 ~(keystone_admin)]# 

here is grep on one of the instances from the logs:

http://fpaste.org/133921/

** 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/1370088

Title:
  admin is getting: You are not allowed to terminate instances

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  I am getting a permission error on deleting of instances as user
  admin:

  Error: You are not allowed to terminate instances: Dafna-763bb301
  -33da-47d2-bb90-e83edb1199f1, Dafna-c8c9e379-8c1c-40fd-
  a7a9-f57cfeed072d, Dafna-ab9aae09-d551-453c-b2ed-d40ba97a78dc,
  Dafna-04267001-c7f2-4b74-ba81-f26f7846294d, Dafna-a44b71a0-b4f2-4223
  -a0ac-e84c094ce23f, Dafna-a6fdb7aa-14ed-4b60-90c0-f144fc4eaf87, Dafna-
  37795fc3-1d1a-40bb-9290-92f5938d017e, Dafna-2defb0fa-5057-4cb7-b60d-
  bdf69629af85, Dafna-6b05e4f8-4b5f-4125-93ab-4cc4082116bb, Dafna-
  49f6e328-9384-465b-b7b9-af51ae555c17


  the instances in nova list did change to deleting and after a while were 
actually deleted. 
  It took two UI refreshes to show the correct list

  
  root@tigris01 ~(keystone_admin)]# nova list 
  
+--++++-+--+
  | ID   | Name 
  | Status | Task State | Power State | Networks |
  
+--++++-+--+
  | 04267001-c7f2-4b74-ba81-f26f7846294d | 
Dafna-04267001-c7f2-4b74-ba81-f26f7846294d | BUILD  | deleting   | NOSTATE 
|  |
  | 2defb0fa-5057-4cb7-b60d-bdf69629af85 | 
Dafna-2defb0fa-5057-4cb7-b60d-bdf69629af85 | BUILD  | deleting   | NOSTATE 
|  |
  | 37795fc3-1d1a-40bb-9290-92f5938d017e |

[Yahoo-eng-team] [Bug 1370099] [NEW] Refactor metadef namespace _select_namespaces_query to include filtering

2014-09-16 Thread Wayne

Public bug reported:

Move the filtering logic out of _get_all into the
_select_namespaces_query def so that all query building logic is in the
same method.

** Affects: glance
 Importance: Undecided
 Assignee: Wayne (wayne-okuma)
 Status: New

** Changed in: glance
 Assignee: (unassigned) = Wayne (wayne-okuma)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1370099

Title:
  Refactor metadef namespace _select_namespaces_query to include
  filtering

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  Move the filtering logic out of _get_all into the
  _select_namespaces_query def so that all query building logic is in
  the same method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1370099/+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 1370114] [NEW] add advanced view on instance history

Public bug reported:

it would be helpful to add to horizon an advanced view on instance to show 
history such as : 
snapshots
rebuild
attach/detach of ip

** 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/1370114

Title:
  add advanced view on instance history

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  it would be helpful to add to horizon an advanced view on instance to show 
history such as : 
  snapshots
  rebuild
  attach/detach of ip

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370114/+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 1370112] [NEW] NSX plugin should set VNIC_TYPE

2014-09-16 Thread Salvatore Orlando

Public bug reported:

This nova commit:
http://git.openstack.org/cgit/openstack/nova/commit/?id=a8a5d44c8aca218f00649232c2b8a46aee59b77e
made VNIC_TYPE a compulsory port bindings attribute.

This broke the NSX plugin which is now not able to boot VMs anymore. Probably
other plugins are affected.
Whether VNIC_TYPE is really a required attribute questionable; the fact that
port bindings is such a messy interface that can cause this kind of breakages
is at least annoying.

Regardless, all plugins must now adapt.
This will also be fixed once a general fix for bug 1370077 is introduced -
nevertheless, the NSX plugin can't risk staying broken for more time, and also
its 3rd party integration tests are disabled because of this. For this reason
we're opening a bug specific for this plugin to fast-track a fix for it.

** Affects: neutron
Importance: High
Assignee: Salvatore Orlando (salvatore-orlando)
Status: In Progress

** Tags: vmware

--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1370112

Title:
NSX plugin should set VNIC_TYPE

Status in OpenStack Neutron (virtual network service):
In Progress

Bug description:
This nova commit:
http://git.openstack.org/cgit/openstack/nova/commit/?id=a8a5d44c8aca218f00649232c2b8a46aee59b77e
made VNIC_TYPE a compulsory port bindings attribute.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1370112/+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 1368032] Re: Add missing metadata definitions for Aggregate filters added in Juno

2014-09-16 Thread Travis Tripp

Fix proposed to branch: master
Review: https://review.openstack.org/#/c/120688/

** Also affects: glance
   Importance: Undecided
   Status: New

** Changed in: glance
 Assignee: (unassigned) = Travis Tripp (travis-tripp)

** Changed in: glance
   Status: New = In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1368032

Title:
  Add missing metadata definitions for Aggregate filters added in Juno

Status in OpenStack Image Registry and Delivery Service (Glance):
  In Progress
Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  The below spec implemented in Juno added numerous properties that can
  be set on host aggregates.  The Metadata Definitions catalog should
  include these properties.

  https://github.com/openstack/nova-specs/blob/master/specs/juno/per-
  aggregate-filters.rst

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1368032/+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 1370116] [NEW] Allow sending nova service-disable/enable to Hypervisor

Public bug reported:

under admin - Hypervisors - allow disable and enable the compute from
horizon.

to prevent further scheduling of instance launch on a compute we need to run: 
 nova service-disable --reason REASON NODENAME nova-compute

It would be helpful if we can send this through the hypervisors menu.

** 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/1370116

Title:
  Allow sending nova service-disable/enable to Hypervisor

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  under admin - Hypervisors - allow disable and enable the compute
  from horizon.

  to prevent further scheduling of instance launch on a compute we need to run: 
   nova service-disable --reason REASON NODENAME nova-compute

  It would be helpful if we can send this through the hypervisors menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370116/+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 1370121] [NEW] Allow destroy of instances from the Hypervisor view under the admin menu

Public bug reported:

it would be helpful if we can perform actions on instances from the hypervisor 
view such as: destroy, resize, migrate, snapshot
this would be helpful in case we have maintenance on a specific hypervisor and 
would like to perform actions on the instances before we begin. 
primarily with instances booted from volumes which have consistent data

** 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/1370121

Title:
  Allow destroy of instances from the Hypervisor view under the admin
  menu

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  it would be helpful if we can perform actions on instances from the 
hypervisor view such as: destroy, resize, migrate, snapshot
  this would be helpful in case we have maintenance on a specific hypervisor 
and would like to perform actions on the instances before we begin. 
  primarily with instances booted from volumes which have consistent data

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370121/+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 1370126] [NEW] add error history log in horizon

Public bug reported:

currently, when there is an error on actions in horizon we are getting a pop-up 
error which disappears. 
I think it would be helpful to keep a history of these errors in horizon and 
allow to filter them by an object or time so that admin would be able to view 
past errors with searching all the logs in the servers themselves.

** 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/1370126

Title:
  add error history log in horizon

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  currently, when there is an error on actions in horizon we are getting a 
pop-up error which disappears. 
  I think it would be helpful to keep a history of these errors in horizon and 
allow to filter them by an object or time so that admin would be able to view 
past errors with searching all the logs in the servers themselves.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370126/+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 1370110] [NEW] Neutron L3 HA router support

2014-09-16 Thread Akihiro Motoki

Public bug reported:

Neutron L3 HA router (High Availability mode) support is one of the important 
community topics in Juno, and the blueprint of Neutron side has been merged as 
FFE. This bug is to add L3 HA support to admin/project router panels.
It just adds one attribute in Neutron API and would be a small patch.

** Affects: horizon
 Importance: High
 Assignee: Akihiro Motoki (amotoki)
 Status: New


** Tags: neutron

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

Title:
  Neutron L3 HA router support

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Neutron L3 HA router (High Availability mode) support is one of the important 
community topics in Juno, and the blueprint of Neutron side has been merged as 
FFE. This bug is to add L3 HA support to admin/project router panels.
  It just adds one attribute in Neutron API and would be a small patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370110/+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 1370137] [NEW] pyscss can't compile bootstrap 3.2.0

2014-09-16 Thread Radomir Dopieralski

Public bug reported:

As reported in https://github.com/Kronuz/pyScss/issues/287
We need to upgrade pyscss as soon as this fix is released to allow unbundling 
of bootstrap.

** Affects: horizon
 Importance: High
 Assignee: Radomir Dopieralski (thesheep)
 Status: In Progress

** Changed in: horizon
 Assignee: (unassigned) = Radomir Dopieralski (thesheep)

** Changed in: horizon
   Status: New = In Progress

** Changed in: horizon
   Importance: Undecided = High

** Changed in: horizon
Milestone: None = juno-rc1

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

Title:
  pyscss can't compile bootstrap 3.2.0

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  As reported in https://github.com/Kronuz/pyScss/issues/287
  We need to upgrade pyscss as soon as this fix is released to allow unbundling 
of bootstrap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370137/+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 1370133] [NEW] Unable to dismiss flavor details pop-over unless we click on the flavor detail link itself

2014-09-16 Thread mariam john

Public bug reported:

When we go to Projects-Instances and assuming we have an instance
already created, click the link under the Size column. For example, if
it is m1.nano, clicking it will bring up a pop-over with the flavor
details. Currently, to dismiss it, we have to click the m1.nano link
again. Without clicking the link itself, if we click the 'Launch
Instance' button for example, you can see the flavor detail pop-over
spill into that form also.

** Affects: horizon
 Importance: Undecided
 Assignee: mariam john (mariamj)
 Status: New

** Attachment added: pop-over.png
   
https://bugs.launchpad.net/bugs/1370133/+attachment/4205419/+files/pop-over.png

** Changed in: horizon
 Assignee: (unassigned) = mariam john (mariamj)

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

Title:
  Unable to dismiss flavor details pop-over unless we click on the
  flavor detail link itself

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When we go to Projects-Instances and assuming we have an instance
  already created, click the link under the Size column. For example, if
  it is m1.nano, clicking it will bring up a pop-over with the flavor
  details. Currently, to dismiss it, we have to click the m1.nano link
  again. Without clicking the link itself, if we click the 'Launch
  Instance' button for example, you can see the flavor detail pop-over
  spill into that form also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370133/+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 1155800] Re: Cannot delete / confirm / revert resize an instance if nova-compute crashes after VERIFY_RESIZE

2014-09-16 Thread Dan Smith

This is super old, lots has changed since then, and several folks have
not been able to reproduce. Please re-open if this is still valid.

** Changed in: nova
   Importance: High = Undecided

** Changed in: nova
   Status: Triaged = Invalid

** Changed in: nova
 Assignee: Dan Smith (danms) = (unassigned)

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

Title:
  Cannot delete / confirm / revert resize an instance if nova-compute
  crashes after VERIFY_RESIZE

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  How to reproduce the bug:

  nova boot ... vm1
  nova migrate vm1 (or resize)

  wait for the vm status to reach VERIFY_RESIZE

  stop nova-compute on the host where vm1 is running

  nova delete vm1

  Error: The server has either erred or is incapable of performing the
  requested operation. (HTTP 500) (Request-ID: req-be1379bc-6a5b-
  41f5-a554-60e02acfdb79)

  restart quickly the nova-compute service, before the status becomes XXX in:
  nova-manage service list

  Note: the vm is still running on the hypervisor.

  nova show vm1
  VM status is still: VERIFY_RESIZE

  nova resize-confirm vm1

  ERROR: Cannot 'confirmResize' while instance is in task_state deleting
  (HTTP 409) (Request-ID: req-9660c776-ebc3-4397-a8e2-7ad83e8b6a0f)

  nova resize-revert vm1

  ERROR: Cannot 'revertResize' while instance is in task_state deleting
  (HTTP 409) (Request-ID: req-3cf0141b-ee3d-478f-8aa0-89091028a227)

  nova delete vm1

  The server has either erred or is incapable of performing the
  requested operation. (HTTP 500) (Request-ID: req-2cb17333-6cc9-42ca-
  baaa-da88ec90153f)

  nova-api log when running nova delete:
  http://paste.openstack.org/show/33783/

  Notes:

  Tests have been performed using the Hyper-V driver, but the issue
  seems to be unrelated to the driver.

  After stopping nova-compute, by waiting long enough for the service to
  be marked as XXX in nova-manage service list, issuing nova delete
  vm1 succeeds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1155800/+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 1370077] Re: Set default vnic_type in neutron.

2014-09-16 Thread Sam Betts

** Also affects: nova
   Importance: Undecided
   Status: New

** Changed in: nova
 Assignee: (unassigned) = Sam Betts (sambetts)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1370077

Title:
  Set default vnic_type in neutron.

Status in OpenStack Neutron (virtual network service):
  Confirmed
Status in OpenStack Compute (Nova):
  New

Bug description:
  https://review.openstack.org/#/c/72334/ introduced binding:vnic_type
  into the neutron port binding extension. Ml2 plugin has been updated
  to support the vnic_type, but others may not. Nova expects every port
  has a correct vnic_type. Therefore, neutron should make sure each port
  to have this attribute set correctly. By default, the vnic_type should
  be VNIC_TYPE_NORMAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1370077/+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 1370174] [NEW] Downloaded openstack RC should contain either of tenant name or tenant ID

2014-09-16 Thread Akihiro Motoki

Public bug reported:

At now OpenStack RC file downloaded from access_and_security panel contains 
both tenant ID and tenant name.
It sometimes leads to confusions when a tenant with the same name is recreated.
It usually happens especially in development/test deployments.

I believe either of tenant ID or tenant name is enough.
My preference is tenant name because it is easier to understand.

It works with keystone v2.

If I understand correctly, Keystone v3 API introduced domain and
tenant is unique inside domain, so just removing tenant ID does not work.
domain_name and tenant name?
I hope input from someone familiar with Keystone v3.

** 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/1370174

Title:
  Downloaded openstack RC should contain either of tenant name or tenant
  ID

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  At now OpenStack RC file downloaded from access_and_security panel contains 
both tenant ID and tenant name.
  It sometimes leads to confusions when a tenant with the same name is 
recreated.
  It usually happens especially in development/test deployments.

  I believe either of tenant ID or tenant name is enough.
  My preference is tenant name because it is easier to understand.

  It works with keystone v2.

  If I understand correctly, Keystone v3 API introduced domain and
  tenant is unique inside domain, so just removing tenant ID does not work.
  domain_name and tenant name?
  I hope input from someone familiar with Keystone v3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370174/+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 1370177] [NEW] Lack of EC2 image attributes for volume backed snapshot.

Public bug reported:

For EBS images AWS returns device names, volume sizes, delete on
termination flags in block device mapping structure.

$ euca-describe-images ami-d13845e1
IMAGE   ami-d13845e1amazon/amzn-ami-hvm-2014.03.2.x86_64-ebsamazon  
available   public  x86_64  machine ebs hvm 
xen
BLOCKDEVICEMAPPING  /dev/xvda   snap-d15cde24   8   true

The same in xml form:
blockDeviceMapping
item
deviceName/dev/xvda/deviceName
ebs
snapshotIdsnap-d15cde24/snapshotId
volumeSize8/volumeSize
deleteOnTerminationtrue/deleteOnTermination
volumeTypestandard/volumeType
/ebs
/item
/blockDeviceMapping

But Nova didn't do it now:

$ euca-describe-images ami-000a
IMAGE   ami-000aNone (sn-in)ef3ddd7aa4b24cda974200baef02730b
available   private machine aki-0002ari-0003
instance-store  
BLOCKDEVICEMAPPING  snap-0005

The same in xml form:
  blockDeviceMapping
item
  ebs
snapshotIdsnap-0005/snapshotId
  /ebs
/item
  /blockDeviceMapping

NB. In Grizzly device names and delete on termination flags was returned. It 
was changed by 
https://github.com/openstack/nova/commit/33e3d4c6b9e0b11500fe47d861110be1c1981572
Now these attributes are not stored in instance snapshots, so there is no way 
to output them.

Device name is most critical attribute. Because there is another one 
compatibility issue: Nova isn't able to adjust attributes of volume being 
created at instance launch stage. For example in AWS we can change volume size 
and delete on termination flag of a device by set new values in parameters of 
run instance command. To identify the device in image block device mapping we 
use device name. For example:
euca-run-instances ... -b /dev/vda=:100
runs an instance with vda device increased to 100 GB.
Thus if we haven't device names in images, we haven't a chance to fix this 
compatibility problem.

** 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/1370177

Title:
  Lack of EC2 image attributes for volume backed snapshot.

Status in OpenStack Compute (Nova):
  New

Bug description:
  For EBS images AWS returns device names, volume sizes, delete on
  termination flags in block device mapping structure.

  $ euca-describe-images ami-d13845e1
  IMAGE ami-d13845e1amazon/amzn-ami-hvm-2014.03.2.x86_64-ebsamazon  
available   public  x86_64  machine ebs hvm 
xen
  BLOCKDEVICEMAPPING/dev/xvda   snap-d15cde24   8   true

  The same in xml form:
  blockDeviceMapping
  item
  deviceName/dev/xvda/deviceName
  ebs
  snapshotIdsnap-d15cde24/snapshotId
  volumeSize8/volumeSize
  deleteOnTerminationtrue/deleteOnTermination
  volumeTypestandard/volumeType
  /ebs
  /item
  /blockDeviceMapping

  But Nova didn't do it now:

  $ euca-describe-images ami-000a
  IMAGE ami-000aNone (sn-in)ef3ddd7aa4b24cda974200baef02730b
available   private machine aki-0002ari-0003
instance-store  
  BLOCKDEVICEMAPPINGsnap-0005

  The same in xml form:
blockDeviceMapping
  item
ebs
  snapshotIdsnap-0005/snapshotId
/ebs
  /item
/blockDeviceMapping

  NB. In Grizzly device names and delete on termination flags was returned. It 
was changed by 
https://github.com/openstack/nova/commit/33e3d4c6b9e0b11500fe47d861110be1c1981572
  Now these attributes are not stored in instance snapshots, so there is no way 
to output them.

  Device name is most critical attribute. Because there is another one 
compatibility issue: Nova isn't able to adjust attributes of volume being 
created at instance launch stage. For example in AWS we can change volume size 
and delete on termination flag of a device by set new values in parameters of 
run instance command. To identify the device in image block device mapping we 
use device name. For example:
  euca-run-instances ... -b /dev/vda=:100
  runs an instance with vda device increased to 100 GB.
  Thus if we haven't device names in images, we haven't a chance to fix this 
compatibility problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1370177/+subscriptions

-- 
Mailing list:

[Yahoo-eng-team] [Bug 1358772] Re: get_available_datastores - possible issue with datastore accessibility

2014-09-16 Thread Radoslav Gerganov

We don't have host_mor after the removal of the ESX driver. I think this
bug is invalid.

** Changed in: nova
   Status: Triaged = Invalid

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

Title:
  get_available_datastores - possible issue with datastore accessibility

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Vipin found this issue during a code 'port' from nova to oslo.vmware in 
review 114551:
  https://review.openstack.org/#/c/114551/14/oslo/vmware/selector.py,unified

  
https://github.com/openstack/nova/blob/master/nova/virt/vmwareapi/ds_util.py#L303

  Quote from vipin:

  I think there is a problem here.

  Assume that cluster_mor is None and host_mor is h1. If a datastore d1
  is attached to hosts h1 and h2 where it is accessible only to h2 and
  not h1, summary.accessible will be True even though it is not
  accessible to h1.

  We should use HostMountInfo.accessible in this case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1358772/+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 1370186] [NEW] very long Volume Description causes generic error

2014-09-16 Thread Cindy Lu

Public bug reported:

I copied the following line many, many times in the Create/Edit Volume 
description field:
asdfasdf asdfasdfa asdfasdf asdfasdf asdfasdf asdf, until the field's scrollbar 
appears (I believe we plan to change the description field back to a single 
line rather than the textbox).

When I clicked save, I got the error Unable to update volume.  This
seems to be preventable error related to the description length. When I
update the description with abcd, it works just fine.

** 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/1370186

Title:
  very long Volume Description causes generic error

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  I copied the following line many, many times in the Create/Edit Volume 
description field:
  asdfasdf asdfasdfa asdfasdf asdfasdf asdfasdf asdf, until the field's 
scrollbar appears (I believe we plan to change the description field back to a 
single line rather than the textbox).

  When I clicked save, I got the error Unable to update volume.  This
  seems to be preventable error related to the description length. When
  I update the description with abcd, it works just fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370186/+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 1370184] [NEW] Ironic driver states file out-of-date

2014-09-16 Thread David Shrewsbury

Public bug reported:

The current ironic states file, nova/virt/ironic/ironic_states.py, is
out-of-date, and was recently updated in ironic with this change:

https://review.openstack.org/118467

Ideally, we should keep these in sync to prevent confusion.

** Affects: nova
 Importance: Undecided
 Assignee: David Shrewsbury (dshrews)
 Status: In Progress


** Tags: ironic

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

Title:
  Ironic driver states file out-of-date

Status in OpenStack Compute (Nova):
  In Progress

Bug description:
  The current ironic states file, nova/virt/ironic/ironic_states.py, is
  out-of-date, and was recently updated in ironic with this change:

  https://review.openstack.org/118467

  Ideally, we should keep these in sync to prevent confusion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1370184/+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 1353008] Re: MAAS Provider: LXC did not get DHCP address, stuck in pending

2014-09-16 Thread Scott Moser

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided = Medium

** Changed in: cloud-init (Ubuntu)
   Status: New = Fix Released

** Changed in: cloud-init (Ubuntu)
 Assignee: (unassigned) = Scott Moser (smoser)

** Also affects: cloud-init (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: cloud-init (Ubuntu Trusty)
   Importance: Undecided = Medium

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1353008

Title:
  MAAS Provider: LXC did not get DHCP address, stuck in pending

Status in Init scripts for use on cloud images:
  Fix Committed
Status in juju-core:
  Triaged
Status in “cloud-init” package in Ubuntu:
  Fix Released
Status in “cloud-init” source package in Trusty:
  In Progress

Bug description:
  Note, that after I went onto the system, it *did* have an IP address.

    0/lxc/3:
  agent-state: pending
  instance-id: juju-machine-0-lxc-3
  series: trusty
  hardware: arch=amd64

  cloud-init-output.log snip:

  Cloud-init v. 0.7.5 running 'init' at Mon, 04 Aug 2014 23:57:12 +. Up 
572.29 seconds.
  ci-info: +++Net device info+++
  ci-info: ++--+---+---+---+
  ci-info: | Device |  Up  |  Address  |Mask   | Hw-Address|
  ci-info: ++--+---+---+---+
  ci-info: |   lo   | True | 127.0.0.1 | 255.0.0.0 | . |
  ci-info: |  eth0  | True | . | . | 00:16:3e:34:aa:57 |
  ci-info: ++--+---+---+---+
  ci-info: !!!Route info 
failed
  Cloud-init v. 0.7.5 running 'modules:config' at Mon, 04 Aug 2014 23:57:12 
+. Up 572.99 seconds.
  Cloud-init v. 0.7.5 running 'modules:final' at Mon, 04 Aug 2014 23:57:14 
+. Up 574.42 seconds.
  Cloud-init v. 0.7.5 finished at Mon, 04 Aug 2014 23:57:14 +. Datasource 
DataSourceNoCloudNet [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net].  Up 
574.54 seconds

  syslog on system, showing DHCPACK 1 second later:

  root@juju-machine-0-lxc-3:/home/ubuntu# grep DHCP /var/log/syslog
  Aug  4 23:57:13 juju-machine-0-lxc-3 dhclient: DHCPREQUEST of 10.96.3.173 on 
eth0 to 255.255.255.255 port 67 (xid=0x1687c544)
  Aug  4 23:57:13 juju-machine-0-lxc-3 dhclient: DHCPOFFER of 10.96.3.173 from 
10.96.0.10
  Aug  4 23:57:13 juju-machine-0-lxc-3 dhclient: DHCPACK of 10.96.3.173 from 
10.96.0.10
  Aug  5 05:28:15 juju-machine-0-lxc-3 dhclient: DHCPREQUEST of 10.96.3.173 on 
eth0 to 10.96.0.10 port 67 (xid=0x1687c544)
  Aug  5 05:28:15 juju-machine-0-lxc-3 dhclient: DHCPACK of 10.96.3.173 from 
10.96.0.10
  Aug  5 11:15:00 juju-machine-0-lxc-3 dhclient: DHCPREQUEST of 10.96.3.173 on 
eth0 to 10.96.0.10 port 67 (xid=0x1687c544)
  Aug  5 11:15:00 juju-machine-0-lxc-3 dhclient: DHCPACK of 10.96.3.173 from 
10.96.0.10

  It appears in every case, cloud-init init-local has failed very early
  visible in juju logs /var/lib/juju/containers/container/console.log:

  Traceback (most recent call last):
File /usr/bin/cloud-init, line 618, in module
  sys.exit(main())
File /usr/bin/cloud-init, line 614, in main
  get_uptime=True, func=functor, args=(name, args))
File /usr/lib/python2.7/dist-packages/cloudinit/util.py, line 1875, in 
log_time
  ret = func(*args, **kwargs)
File /usr/bin/cloud-init, line 491, in status_wrapper
  force=True)
File /usr/lib/python2.7/dist-packages/cloudinit/util.py, line 1402, in 
sym_link
  os.symlink(source, link)
  OSError: [Errno 2] No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1353008/+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 1370191] [NEW] db deadlock on service_update()

2014-09-16 Thread Russell Bryant

Public bug reported:

Several methods in nova.db.sqlalchemy.api are decorated with
@_retry_on_deadlock.  service_update() is not currently one of them, but
it should be based on the following backtrace:

4-09-15 15:40:22.574 34384 ERROR nova.servicegroup.drivers.db [-] model
server went away
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db Traceback
(most recent call last):
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib/python2.7/site-packages/nova/servicegroup/drivers/db.py, line
95, in _report_state
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
service.service_ref, state_catalog)
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib/python2.7/site-packages/nova/conductor/api.py, line 218, in
service_update
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
return self._manager.service_update(context, service, values)
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib/python2.7/site-packages/nova/utils.py, line 967, in wrapper
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
return func(*args, **kwargs)
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib/python2.7/site-packages/oslo/messaging/rpc/server.py, line 139,
in inner
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
return func(*args, **kwargs)
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib/python2.7/site-packages/nova/conductor/manager.py, line 491, in
service_update
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db svc =
self.db.service_update(context, service['id'], values)
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib/python2.7/site-packages/nova/db/api.py, line 148, in
service_update
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
return IMPL.service_update(context, service_id, values)
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py, line 146, in
wrapper
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
return f(*args, **kwargs)
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py, line 533, in
service_update
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
service_ref.update(values)
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py, line 447,
in __exit__
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
self.rollback()
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib64/python2.7/site-packages/sqlalchemy/util/langhelpers.py, line
58, in __exit__
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
compat.reraise(exc_type, exc_value, exc_tb)
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py, line 444,
in __exit__
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
self.commit()
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py, line 358,
in commit
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
t[1].commit()
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py, line 1195,
in commit
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
self._do_commit()
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py, line 1226,
in _do_commit
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
self.connection._commit_impl()
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py, line 491,
in _commit_impl
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
self._handle_dbapi_exception(e, None, None, None, None)
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py, line 1024,
in _handle_dbapi_exception
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
exc_info
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib64/python2.7/site-packages/sqlalchemy/util/compat.py, line 196,
in raise_from_cause
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db
reraise(type(exception), exception, tb=exc_tb)
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db   File
/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py, line 488,
in _commit_impl
2014-09-15 15:40:22.574 34384 TRACE nova.servicegroup.drivers.db

[Yahoo-eng-team] [Bug 1339923] Re: failures in tempest.thirdparty.boto.test_ec2_keys

2014-09-16 Thread David Kranz

This is still showing up in logstash

http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiQm90b1NlcnZlckVycm9yOiBCb3RvU2VydmVyRXJyb3I6IDUwMCBJbnRlcm5hbCBTZXJ2ZXIgRXJyb3JcIiBBTkQgTk9UIGJ1aWxkX2JyYW5jaDpcInN0YWJsZS9oYXZhbmFcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQxMDg5MDk1MTI4M30=

Opening to nova for now as tempest should not be getting a 500.

** Also affects: nova
   Importance: Undecided
   Status: New

** Changed in: tempest
   Status: New = Invalid

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

Title:
  failures in tempest.thirdparty.boto.test_ec2_keys

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

Bug description:
  per http://logs.openstack.org/07/105307/9/check/check-tempest-dsvm-
  postgres-full/190d3ce/console.html, seeing failures unrelated to my
  patch:

  
tempest.thirdparty.boto.test_ec2_security_groups.EC2SecurityGroupTest.test_create_authorize_security_group
  
--
   
   BotoServerError: BotoServerError: 500 Internal Server Error
   ?xml version=1.0?
   ResponseErrorsErrorCodeOperationalError/CodeMessageUnknown 
error 
occurred./Message/Error/ErrorsRequestIDreq-ab53ffd6-fd2f-4747-b0ed-8240381adc12/RequestID/Response
   
   
   tempest.thirdparty.boto.test_ec2_keys.EC2KeysTest.test_create_ec2_keypair
   -
   
   BotoServerError: BotoServerError: 500 Internal Server Error
   ?xml version=1.0?
   ResponseErrorsErrorCodeOperationalError/CodeMessageUnknown 
error 
occurred./Message/Error/ErrorsRequestIDreq-930ffb3f-ece3-47ee-89e7-9d3afe273c9e/RequestID/Response
   
   
   tempest.thirdparty.boto.test_ec2_keys.EC2KeysTest.test_duplicate_ec2_keypair
   
   
   BotoServerError: BotoServerError: 500 Internal Server Error
   ?xml version=1.0?
   ResponseErrorsErrorCodeOperationalError/CodeMessageUnknown 
error 
occurred./Message/Error/ErrorsRequestIDreq-dda2e5f0-58c9-43ab-81a7-103f12d7915f/RequestID/Response
   
   
   tempest.thirdparty.boto.test_ec2_keys.EC2KeysTest.test_get_ec2_keypair
   --
   
   BotoServerError: BotoServerError: 500 Internal Server Error
   ?xml version=1.0?
   ResponseErrorsErrorCodeOperationalError/CodeMessageUnknown 
error 
occurred./Message/Error/ErrorsRequestIDreq-08ac28ea-5d4e-4f83-a256-53717e6bce9e/RequestID/Response
   

  the final cleanup exception is similar to 
  https://bugs.launchpad.net/tempest/+bug/1339910 but the cause is not a 
duplicate 
  keypair:

   tearDownClass (tempest.thirdparty.boto.test_ec2_keys.EC2KeysTest)
   -
   
   Captured traceback:
   ~~~
   Traceback (most recent call last):
 File tempest/thirdparty/boto/test.py, line 272, in tearDownClass
   raise exceptions.TearDownException(num=fail_count)
   TearDownException: 1 cleanUp operation failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1339923/+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 1370126] Re: add error history log in horizon

This is a good idea, but it is not a bug. It is new, significant
functionality to Horizon, and should be handled via the blueprint
process. Note a related blueprint to improve error messaging in horizon
(although it does not mentiona a history):
https://blueprints.launchpad.net/horizon/+spec/improve-error-message-
details-for-usability


** Changed in: horizon
   Status: New = Invalid

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

Title:
  add error history log in horizon

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  currently, when there is an error on actions in horizon we are getting a 
pop-up error which disappears. 
  I think it would be helpful to keep a history of these errors in horizon and 
allow to filter them by an object or time so that admin would be able to view 
past errors with searching all the logs in the servers themselves.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370126/+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 1335889] Re: Race condition in the stress volume_attach_delete test

2014-09-16 Thread David Kranz

I am not seeing how this is a bug in tempest. Tempest is deleting the vm
only after nova reports that the volume is 'in-use' which seems fine.
It would be nice if there was a backtrace, log, or something associated
with this ticket. This might be a cinder issue but more likely nova and
the test is making a nova call.

** Changed in: tempest
   Status: New = Invalid

** Also affects: nova
   Importance: Undecided
   Status: New

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

Title:
  Race condition in quickly attaching / deleting volumes

Status in Cinder:
  New
Status in OpenStack Compute (Nova):
  Confirmed
Status in Tempest:
  Invalid

Bug description:
  It seems that there is a race condition in the stress
  volume_attach_delete test. It creates VMs and volumes, attaches
  volumes and deletes everything.

  The test is waiting for volumes to be in 'in-use' state before
  deleting VMs. It seems that Nova/Cinder don't have time to register
  volumes as attached in their databases before VMs get deleted. Volumes
  are then left attached to deleted VMs and unable to be deleted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1335889/+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 1370121] Re: Allow destroy of instances from the Hypervisor view under the admin menu

These instance functions are already available via Admin  System 
Instances

** Changed in: horizon
   Status: New = Invalid

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

Title:
  Allow destroy of instances from the Hypervisor view under the admin
  menu

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  it would be helpful if we can perform actions on instances from the 
hypervisor view such as: destroy, resize, migrate, snapshot
  this would be helpful in case we have maintenance on a specific hypervisor 
and would like to perform actions on the instances before we begin. 
  primarily with instances booted from volumes which have consistent data

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370121/+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 1370116] Re: Allow sending nova service-disable/enable to Hypervisor

This is a good idea for a new feature in horizon. Please file a
blueprint for this.

** Tags added: nova

** Changed in: horizon
   Status: New = Invalid

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

Title:
  Allow sending nova service-disable/enable to Hypervisor

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  under admin - Hypervisors - allow disable and enable the compute
  from horizon.

  to prevent further scheduling of instance launch on a compute we need to run: 
   nova service-disable --reason REASON NODENAME nova-compute

  It would be helpful if we can send this through the hypervisors menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370116/+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 1328872] Re: Launch an instance with OpenStack Networking (neutron) in OpenStack Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora - icehouse Failed to close

Looks like an upstream issue with auges

** Changed in: nova
   Status: New = Invalid

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

Title:
  Launch an instance with OpenStack Networking (neutron) in OpenStack
  Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora  -
  icehouse  Failed to close augeas aug_close: do_aug_close: you must
  call 'aug-init' first to initialize Augeas

Status in OpenStack Compute (Nova):
  Invalid
Status in OpenStack Manuals:
  Expired

Bug description:
  centos6.5+icehouse
  when ：
   Launch an instance with OpenStack Networking (neutron) error

  2014-06-10 13:14:58.354 2786 INFO oslo.messaging._drivers.impl_qpid [-] 
Connected to AMQP server on controller:5672
  2014-06-10 13:23:39.074 2786 WARNING nova.virt.disk.vfs.guestfs 
[req-29f113b4-6f3a-4c59-a2dc-70c4bd0514af f9ebab09cbe1446fb07229f9ba53edad 
7fa0b1e3152c4082a876f6dcd28d5e15] Failed to close augeas aug_close: 
do_aug_close: you must call 'aug-init' first to initialize Augeas
  2014-06-10 13:23:40.555 2786 ERROR nova.virt.libvirt.driver 
[req-29f113b4-6f3a-4c59-a2dc-70c4bd0514af f9ebab09cbe1446fb07229f9ba53edad 
7fa0b1e3152c4082a876f6dcd28d5e15] An error occurred while trying to launch a 
defined domain with xml: domain type='kvm'



  
  [root@controller ~]# ssh-keygen
  Generating public/private rsa key pair.
  Enter file in which to save the key (/root/.ssh/id_rsa): 
  Enter passphrase (empty for no passphrase): 
  Enter same passphrase again: 
  Your identification has been saved in /root/.ssh/id_rsa.
  Your public key has been saved in /root/.ssh/id_rsa.pub.
  The key fingerprint is:
  8b:73:1d:01:76:5d:85:77:0b:c4:fb:0c:97:d0:4b:d7 root@controller
  The key's randomart image is:
  +--[ RSA 2048]+
  |o ..o|
  |   . o  .+.oE|
  |  .   =.*|
  |   . o = |
  |S .   =  |
  |   . o .   o |
  |  o o .  |
  |   o |
  | |
  +-+

  
  nova keypair-add --pub-key ~/.ssh/id_rsa.pub demo-key


  [root@controller ~]# nova keypair-list
  +--+-+
  | Name | Fingerprint |
  +--+-+
  | demo-key | 8b:73:1d:01:76:5d:85:77:0b:c4:fb:0c:97:d0:4b:d7 |
  +--+-+


  [root@controller ~]# nova flavor-list
  
++---+---+--+---+--+---+-+---+
  | ID | Name  | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor 
| Is_Public |
  
++---+---+--+---+--+---+-+---+
  | 1  | m1.tiny   | 512   | 1| 0 |  | 1 | 1.0 
| True  |
  | 2  | m1.small  | 2048  | 20   | 0 |  | 1 | 1.0 
| True  |
  | 3  | m1.medium | 4096  | 40   | 0 |  | 2 | 1.0 
| True  |
  | 4  | m1.large  | 8192  | 80   | 0 |  | 4 | 1.0 
| True  |
  | 5  | m1.xlarge | 16384 | 160  | 0 |  | 8 | 1.0 
| True  |
  
++---+---+--+---+--+---+-+---+

  
  [root@controller ~]# nova image-list
  
+--+-+++
  | ID   | Name| Status | 
Server |
  
+--+-+++
  | 8c030990-f828-4109-9b08-76f1057e145a | cirros-0.3.2-x86_64 | ACTIVE |   
 |
  
+--+-+++

  
  [root@controller ~]# neutron net-list
  
+--+--+-+
  | id   | name | subnets   
  |
  
+--+--+-+
  | 37e7c14d-1c8f-483d-be86-ed9081ba4131 | demo-net | 
8519df59-54fa-4441-99da-a5fa7bba5b36 192.168.1.0/24 |
  | 742c3506-8c38-4349-bb0b-740f8d593a5b | ext-net  | 
3f222bbf-617a-406d-86b1-30ec897a065d 10.16.114.0/24 |
  
+--+--+-+

  
  [root@controller ~]# nova secgroup-list
  +--+-+-+
  | Id   | Name| Description |
  +--+-+-+
  | dbfc7446-c08a-4497-b1a6-64cefc2646f0 | default | default |
  +--+-+-+


  [root@controller ~]# nova boot

[Yahoo-eng-team] [Bug 1339923] Re: failures in tempest.thirdparty.boto.test_ec2_keys

So... this error in tempest runs was actually postgresql running out of
db handles

** Changed in: nova
   Status: New = Invalid

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

Title:
  failures in tempest.thirdparty.boto.test_ec2_keys

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

Bug description:
  per http://logs.openstack.org/07/105307/9/check/check-tempest-dsvm-
  postgres-full/190d3ce/console.html, seeing failures unrelated to my
  patch:

  
tempest.thirdparty.boto.test_ec2_security_groups.EC2SecurityGroupTest.test_create_authorize_security_group
  
--
   
   BotoServerError: BotoServerError: 500 Internal Server Error
   ?xml version=1.0?
   ResponseErrorsErrorCodeOperationalError/CodeMessageUnknown 
error 
occurred./Message/Error/ErrorsRequestIDreq-ab53ffd6-fd2f-4747-b0ed-8240381adc12/RequestID/Response
   
   
   tempest.thirdparty.boto.test_ec2_keys.EC2KeysTest.test_create_ec2_keypair
   -
   
   BotoServerError: BotoServerError: 500 Internal Server Error
   ?xml version=1.0?
   ResponseErrorsErrorCodeOperationalError/CodeMessageUnknown 
error 
occurred./Message/Error/ErrorsRequestIDreq-930ffb3f-ece3-47ee-89e7-9d3afe273c9e/RequestID/Response
   
   
   tempest.thirdparty.boto.test_ec2_keys.EC2KeysTest.test_duplicate_ec2_keypair
   
   
   BotoServerError: BotoServerError: 500 Internal Server Error
   ?xml version=1.0?
   ResponseErrorsErrorCodeOperationalError/CodeMessageUnknown 
error 
occurred./Message/Error/ErrorsRequestIDreq-dda2e5f0-58c9-43ab-81a7-103f12d7915f/RequestID/Response
   
   
   tempest.thirdparty.boto.test_ec2_keys.EC2KeysTest.test_get_ec2_keypair
   --
   
   BotoServerError: BotoServerError: 500 Internal Server Error
   ?xml version=1.0?
   ResponseErrorsErrorCodeOperationalError/CodeMessageUnknown 
error 
occurred./Message/Error/ErrorsRequestIDreq-08ac28ea-5d4e-4f83-a256-53717e6bce9e/RequestID/Response
   

  the final cleanup exception is similar to 
  https://bugs.launchpad.net/tempest/+bug/1339910 but the cause is not a 
duplicate 
  keypair:

   tearDownClass (tempest.thirdparty.boto.test_ec2_keys.EC2KeysTest)
   -
   
   Captured traceback:
   ~~~
   Traceback (most recent call last):
 File tempest/thirdparty/boto/test.py, line 272, in tearDownClass
   raise exceptions.TearDownException(num=fail_count)
   TearDownException: 1 cleanUp operation failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1339923/+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 1335889] Re: Race condition in the stress volume_attach_delete test

So I believe this is the same basic issue that exists between cinder and
nova in the fact that it is assumed the event will happen within a
reasonable amount of time, and if it doesn't... sadness.

** Also affects: cinder
   Importance: Undecided
   Status: New

** Changed in: nova
   Status: New = Confirmed

** Changed in: nova
   Importance: Undecided = High

** Summary changed:

- Race condition in the stress volume_attach_delete test
+ Race condition in quickly attaching / deleting volumes

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

Title:
  Race condition in quickly attaching / deleting volumes

Status in Cinder:
  New
Status in OpenStack Compute (Nova):
  Confirmed
Status in Tempest:
  Invalid

Bug description:
  It seems that there is a race condition in the stress
  volume_attach_delete test. It creates VMs and volumes, attaches
  volumes and deletes everything.

  The test is waiting for volumes to be in 'in-use' state before
  deleting VMs. It seems that Nova/Cinder don't have time to register
  volumes as attached in their databases before VMs get deleted. Volumes
  are then left attached to deleted VMs and unable to be deleted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1335889/+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 1370022] Re: Keystone cannot cope with being behind an SSL terminator for version list

2014-09-16 Thread Lance Bragstad

Andrey, you'll need to set 'https' in your keystone configuration in
order to use SSL with Keystone.

Maybe we can look for an opportunity to improve the documentation.

** Changed in: keystone
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1370022

Title:
  Keystone cannot cope with being behind an SSL terminator for version
  list

Status in OpenStack Identity (Keystone):
  Invalid

Bug description:
  When keystone set up behind SSL termintator then it returns 'http' as
  protocol in URLs returned by version list command -

  user@host:~$ curl https://MYHOST:5000/

  {versions: {values: [{status: stable, updated:
  2013-03-06T00:00:00Z, media-types: [{base: application/json,
  type: application/vnd.openstack.identity-v3+json}, {base:
  application/xml, type:
  application/vnd.openstack.identity-v3+xml}], id: v3.0, links:
  [{href: http://MYHOST:5000/v3/;, rel: self}]}, {status:
  stable, updated: 2014-04-17T00:00:00Z, media-types: [{base:
  application/json, type:
  application/vnd.openstack.identity-v2.0+json}, {base:
  application/xml, type:
  application/vnd.openstack.identity-v2.0+xml}], id: v2.0,
  links: [{href: http://MYHOST:5000/v2.0/;, rel: self},
  {href: http://docs.openstack.org/api/openstack-identity-
  service/2.0/content/, type: text/html, rel: describedby},
  {href: http://docs.openstack.org/api/openstack-identity-service/2.0
  /identity-dev-guide-2.0.pdf, type: application/pdf, rel:
  describedby}]}]}}

  my ha_proxyconfig -

  frontend keystone_main_frontend
  bind 172.31.7.253:5000
  bind 172.31.7.252:5000 ssl crt /etc/haproxy/certs/runtime
  reqadd X-Forwarded-Proto:\ https if { ssl_fc }
  default_backend keystone_main_backend
  option httpclose
  option http-pretend-keepalive
  option forwardfor

  backend keystone_main_backend
  server HOST1 172.31.0.10:5000 check
  server HOST2 172.31.0.12:5000 check
  server HOST3 172.31.0.16:5000 check

  Similar bug is here https://bugs.launchpad.net/heat/+bug/123

  And because of this bug last cinder client doesn't work -

  user@host:~$cinder --os-username admin --os-tenant-name admin --os-password 
password --os-auth-url https://MYHOST:5000/v2.0/ --endpoint-type publicURL 
--debug list
  ERROR: Unable to establish connection to http://MYHOST:5000/v2.0/tokens

  
  Also - if I set public_endpoint and admin_endpoint in keystone.conf to use 
'https' proto then all works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1370022/+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 1370206] [NEW] Description text area should be fixed width

2014-09-16 Thread Cindy Lu

Public bug reported:

Create/Edit Volume dialog have a resizeable Description field.

We should prevent user from resizing the width because it will overflow
into the help description.  See attached image.

** Affects: horizon
 Importance: Undecided
 Status: New

** Attachment added: Untitled.png
   
https://bugs.launchpad.net/bugs/1370206/+attachment/4205745/+files/Untitled.png

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

Title:
  Description text area should be fixed width

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Create/Edit Volume dialog have a resizeable Description field.

  We should prevent user from resizing the width because it will
  overflow into the help description.  See attached image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370206/+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 1370209] [NEW] failed to load user-data

2014-09-16 Thread Jaroslav Henner

Public bug reported:

Quite often, the tempest ssh tests fails, probably because of some
problem with loading user-data served on the network. My theory is that
the ssh is started after cloud-init in cirros, and this causes
connection reset.

I have found that many logs in the gat exhibits similar message as ours,
but many of them are in PASSED. I think not many tests are relying on
ssh, but many are starting VMs, so we have high SUCCESS ratio. The
querry:

http://logstash.openstack.org/index.html#eyJzZWFyY2giOiJtZXNzYWdlOlwiZmFpbGVkIHRvIGdldCBodHRwOi8vMTY5LjI1NC4xNjkuMjU0LzIwMDktMDQtMDQvdXNlci1kYXRhXCIiLCJmaWVsZHMiOlsiYnVpbGRfc3RhdHVzIl0sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNDMyMDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIiwic3RhbXAiOjE0MTA4OTQzOTQxMDB9

Log from the test attached.

** Affects: neutron
 Importance: Undecided
 Status: New

** Attachment added: log
   https://bugs.launchpad.net/bugs/1370209/+attachment/4205774/+files/log

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1370209

Title:
  failed to load user-data

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Quite often, the tempest ssh tests fails, probably because of some
  problem with loading user-data served on the network. My theory is
  that the ssh is started after cloud-init in cirros, and this causes
  connection reset.

  I have found that many logs in the gat exhibits similar message as
  ours, but many of them are in PASSED. I think not many tests are
  relying on ssh, but many are starting VMs, so we have high SUCCESS
  ratio. The querry:

  
http://logstash.openstack.org/index.html#eyJzZWFyY2giOiJtZXNzYWdlOlwiZmFpbGVkIHRvIGdldCBodHRwOi8vMTY5LjI1NC4xNjkuMjU0LzIwMDktMDQtMDQvdXNlci1kYXRhXCIiLCJmaWVsZHMiOlsiYnVpbGRfc3RhdHVzIl0sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNDMyMDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIiwic3RhbXAiOjE0MTA4OTQzOTQxMDB9

  Log from the test attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1370209/+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 1370207] [NEW] race condition between nova scheduler and nova compute

2014-09-16 Thread wei du

Public bug reported:

This is for nova 2014.1.2.

Here, nova DB is the shared resources between nova-scheduler and nova-
compute. Nova-scheduler checks DB to see if hv node can meet the
provision requirement, nova-compute is the actual process to modify DB
to reduce the free_ram_mb.

For example, current available RAM on hv is 56G, with 
ram_allocation_ration=1.0. Within a minute, 3 vm provision requests are coming 
to scheduler, each asking for 24G RAM.
 
 t1: scheduler gets a request for vm1, assign vm1 to hv
 t2: scheduler gets a request for vm2, assign vm2 to hv
 t3: vm1 is created, nova-compute updates nova DB with RAM=32G
 t4: scheduler gets a request for vm3, assign vm3 to hv
 t5: vm2 is created, nova-compute updates nova DB with RAM=8G
 t6: vm3 is created, nova-compute updates nova DB with RAM=-16G

In the end, we have a negative RAM with ram_allocation_ratio=1.0.

** 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/1370207

Title:
  race condition between nova scheduler and nova compute

Status in OpenStack Compute (Nova):
  New

Bug description:
  This is for nova 2014.1.2.

  Here, nova DB is the shared resources between nova-scheduler and nova-
  compute. Nova-scheduler checks DB to see if hv node can meet the
  provision requirement, nova-compute is the actual process to modify DB
  to reduce the free_ram_mb.

  For example, current available RAM on hv is 56G, with 
ram_allocation_ration=1.0. Within a minute, 3 vm provision requests are coming 
to scheduler, each asking for 24G RAM.
   
   t1: scheduler gets a request for vm1, assign vm1 to hv
   t2: scheduler gets a request for vm2, assign vm2 to hv
   t3: vm1 is created, nova-compute updates nova DB with RAM=32G
   t4: scheduler gets a request for vm3, assign vm3 to hv
   t5: vm2 is created, nova-compute updates nova DB with RAM=8G
   t6: vm3 is created, nova-compute updates nova DB with RAM=-16G

  In the end, we have a negative RAM with ram_allocation_ratio=1.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1370207/+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 1370114] Re: add advanced view on instance history

horizon is displaying the full output of 'nova instance-action-list'. To
add these events to the history would require a change in nova, not
horizon.

** Tags added: nova

** Changed in: horizon
   Status: New = Invalid

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

Title:
  add advanced view on instance history

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  it would be helpful to add to horizon an advanced view on instance to show 
history such as : 
  snapshots
  rebuild
  attach/detach of ip

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370114/+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 1370226] [NEW] LibvirtISCSIVolumeDriver cannot find volumes that include pci-* in the /dev/disk/by-path device

2014-09-16 Thread Jay Bryant

Public bug reported:

I am currently unable to attach iSCSI volumes to our system because the
path that is expected by the LibvirtISCSIVolumeDriver doesn't match what
is being created in /dev/disk/by-path:

2014-09-16 01:33:22.533 24304 DEBUG nova.openstack.common.lockutils 
[req-f466db73-0a7c-4e1f-85ad-473c688d0a68 None] Semaphore / lock released 
connect_volume inner 
/usr/lib/python2.6/site-packages/nova/openstack/common/lockutils.py:328
2014-09-16 01:33:22.534 24304 ERROR nova.virt.block_device 
[req-f466db73-0a7c-4e1f-85ad-473c688d0a68 None] [instance: 
097e5a6a-ed49-4914-a0ed-5d58959594c9] Driver failed to attach volume 
97e38815-c934-48a7-b343-880c5a9bf4b8 at /dev/vdd
2014-09-16 01:33:22.534 24304 TRACE nova.virt.block_device [instance: 
097e5a6a-ed49-4914-a0ed-5d58959594c9] Traceback (most recent call last):
2014-09-16 01:33:22.534 24304 TRACE nova.virt.block_device [instance: 
097e5a6a-ed49-4914-a0ed-5d58959594c9]   File 
/usr/lib/python2.6/site-packages/nova/virt/block_device.py, line 252, in 
attach
2014-09-16 01:33:22.534 24304 TRACE nova.virt.block_device [instance: 
097e5a6a-ed49-4914-a0ed-5d58959594c9] device_type=self['device_type'], 
encryption=encryption)
2014-09-16 01:33:22.534 24304 TRACE nova.virt.block_device [instance: 
097e5a6a-ed49-4914-a0ed-5d58959594c9]   File 
/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py, line 1283, in 
attach_volume
2014-09-16 01:33:22.534 24304 TRACE nova.virt.block_device [instance: 
097e5a6a-ed49-4914-a0ed-5d58959594c9] conf = 
self._connect_volume(connection_info, disk_info)
2014-09-16 01:33:22.534 24304 TRACE nova.virt.block_device [instance: 
097e5a6a-ed49-4914-a0ed-5d58959594c9]   File 
/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py, line 1237, in 
_connect_volume
2014-09-16 01:33:22.534 24304 TRACE nova.virt.block_device [instance: 
097e5a6a-ed49-4914-a0ed-5d58959594c9] return 
driver.connect_volume(connection_info, disk_info)
2014-09-16 01:33:22.534 24304 TRACE nova.virt.block_device [instance: 
097e5a6a-ed49-4914-a0ed-5d58959594c9]   File 
/usr/lib/python2.6/site-packages/nova/openstack/common/lockutils.py, line 
325, in inner
2014-09-16 01:33:22.534 24304 TRACE nova.virt.block_device [instance: 
097e5a6a-ed49-4914-a0ed-5d58959594c9] return f(*args, **kwargs)
2014-09-16 01:33:22.534 24304 TRACE nova.virt.block_device [instance: 
097e5a6a-ed49-4914-a0ed-5d58959594c9]   File 
/usr/lib/python2.6/site-packages/nova/virt/libvirt/volume.py, line 295, in 
connect_volume
2014-09-16 01:33:22.534 24304 TRACE nova.virt.block_device [instance: 
097e5a6a-ed49-4914-a0ed-5d58959594c9] % (host_device))
2014-09-16 01:33:22.534 24304 TRACE nova.virt.block_device [instance: 
097e5a6a-ed49-4914-a0ed-5d58959594c9] NovaException: iSCSI device not found at 
/dev/disk/by-path/ip-10.90.50.10:3260-iscsi-iqn.1986-03.com.ibm:2145.abbav3700.node2-lun-4

The paths that are being created, however, are  of the following format:

[root@abba-n09 rules.d]# ll /dev/disk/by-path/
total 0
lrwxrwxrwx. 1 root root  9 Sep 16 10:56 
pci-:0c:00.2-ip-10.90.50.11:3260-iscsi-iqn.1986-03.com.ibm:2145.abbav3700.node1-lun-0
 - ../../sdc
lrwxrwxrwx. 1 root root  9 Sep 16 10:56 
pci-:0c:00.2-ip-10.90.50.11:3260-iscsi-iqn.1986-03.com.ibm:2145.abbav3700.node1-lun-1
 - ../../sdd
lrwxrwxrwx. 1 root root  9 Sep 16 10:56 
pci-:0c:00.2-ip-10.90.50.11:3260-iscsi-iqn.1986-03.com.ibm:2145.abbav3700.node1-lun-2
 - ../../sde
lrwxrwxrwx. 1 root root  9 Sep 16 10:56 
pci-:0c:00.2-ip-10.90.50.11:3260-iscsi-iqn.1986-03.com.ibm:2145.abbav3700.node1-lun-3
 - ../../sdf
lrwxrwxrwx. 1 root root  9 Sep 10 18:46 pci-:16:00.0-scsi-0:2:0:0 - 
../../sda
lrwxrwxrwx. 1 root root 10 Sep 10 18:46 pci-:16:00.0-scsi-0:2:0:0-part1 - 
../../sda1
lrwxrwxrwx. 1 root root 10 Sep 10 18:46 pci-:16:00.0-scsi-0:2:0:0-part2 - 
../../sda2
lrwxrwxrwx. 1 root root 10 Sep 10 18:46 pci-:16:00.0-scsi-0:2:0:0-part3 - 
../../sda3
lrwxrwxrwx. 1 root root 10 Sep 10 18:46 pci-:16:00.0-scsi-0:2:0:0-part4 - 
../../sda4
lrwxrwxrwx. 1 root root  9 Sep 10 18:46 pci-:16:00.0-scsi-0:2:1:0 - 
../../sdb
[root@abba-n09 rules.d]#

When the devices are created the physical location of the HBA is being included:
0c:00.2 Mass storage controller: Emulex Corporation OneConnect 10Gb iSCSI 
Initiator (be3) (rev 02)

Looking at the code, I see that theLibvirtISERVolumeDriver actually does
the check that accounts for this  /dev/disk/by-path formatting in the
_get_host_device function:

def _get_host_device(self, iser_properties):
time.sleep(1)
host_device = None
device = (ip-%s-iscsi-%s-lun-%s %
  (iser_properties['target_portal'],
   iser_properties['target_iqn'],
   iser_properties.get('target_lun', 0)))
look_for_device = glob.glob('/dev/disk/by-path/*%s' % device)
if look_for_device:
host_device = look_for_device[0]
return host_device

So, I was able to get the volume to

[Yahoo-eng-team] [Bug 1370229] [NEW] Total VCPUs could change on PowerKVM host, but change not reflected in host stats

2014-09-16 Thread Jennifer Mulsow

Public bug reported:

PowerKVM hosts support the feature of split cores. If a user enables 4
subcores per core on a system with 16 CPUS, then total VCPUs reported by
virsh and libvirt's getInfo() API changes from 16 to 64.

However, the hypervisor details API still shows 16 for VCPUs.

This is because the total VCPUs of a host are only collected once; the
first time libvirt driver obtains all the host stats, and that value is
saved off and used from that point on every time the host stats are
calculated.


In nova.virt.libvirt.driver.LibvirtDriver:

def _get_vcpu_total(self):
Get available vcpu number of physical computer.

:returns: the number of cpu core instances can be used.


if self._vcpu_total != 0:
return self._vcpu_total

try:
total_pcpus = self._conn.getInfo()[2]


This should be changed to always fetch the total VCPUs, instead of
relying on it never changing.

** 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/1370229

Title:
  Total VCPUs could change on PowerKVM host, but change not reflected in
  host stats

Status in OpenStack Compute (Nova):
  New

Bug description:
  PowerKVM hosts support the feature of split cores. If a user enables 4
  subcores per core on a system with 16 CPUS, then total VCPUs reported
  by virsh and libvirt's getInfo() API changes from 16 to 64.

  However, the hypervisor details API still shows 16 for VCPUs.

  This is because the total VCPUs of a host are only collected once; the
  first time libvirt driver obtains all the host stats, and that value
  is saved off and used from that point on every time the host stats are
  calculated.

  
  In nova.virt.libvirt.driver.LibvirtDriver:

  def _get_vcpu_total(self):
  Get available vcpu number of physical computer.

  :returns: the number of cpu core instances can be used.

  
  if self._vcpu_total != 0:
  return self._vcpu_total

  try:
  total_pcpus = self._conn.getInfo()[2]
  

  This should be changed to always fetch the total VCPUs, instead of
  relying on it never changing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1370229/+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 1370229] Re: Total VCPUs could change on PowerKVM host, but change not reflected in host stats

I'm not really convinced this is a useful thing to do. Dynamically
changing the underlying host hardware has other implications for
reporting. If this is desired it needs to come in as a spec for
discussion.

** Changed in: nova
   Importance: Undecided = Wishlist

** Changed in: nova
   Status: New = Opinion

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

Title:
  Total VCPUs could change on PowerKVM host, but change not reflected in
  host stats

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  PowerKVM hosts support the feature of split cores. If a user enables 4
  subcores per core on a system with 16 CPUS, then total VCPUs reported
  by virsh and libvirt's getInfo() API changes from 16 to 64.

  However, the hypervisor details API still shows 16 for VCPUs.

  This is because the total VCPUs of a host are only collected once; the
  first time libvirt driver obtains all the host stats, and that value
  is saved off and used from that point on every time the host stats are
  calculated.

  
  In nova.virt.libvirt.driver.LibvirtDriver:

  def _get_vcpu_total(self):
  Get available vcpu number of physical computer.

  :returns: the number of cpu core instances can be used.

  
  if self._vcpu_total != 0:
  return self._vcpu_total

  try:
  total_pcpus = self._conn.getInfo()[2]
  

  This should be changed to always fetch the total VCPUs, instead of
  relying on it never changing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1370229/+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 1337695] Re: get console output v3 API allows to fetch selecting range of output

v3 closed

** Changed in: nova
   Status: Incomplete = Invalid

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

Title:
  get console output v3 API allows to fetch selecting range of output

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  In our application ,we need to call this method several times .For each time 
,it will retrieve all the output. 
  It would be nice to return selecting range of output instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1337695/+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 1195817] Re: Races in info cache updates cause traceback w/ cells

closing as it's been in incomplete status waiting for feedback for a
long time

** Changed in: nova
   Status: Incomplete = Invalid

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

Title:
  Races in info cache updates cause traceback w/ cells

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  info_cache updates can occur at the same time an instance is being
  deleted... causing None to be returned from the info_cache_update DB
  API call vs the new info_cache data...  This causes a traceback to be
  logged when trying to update nova-cells.

  The fix should be similar to this:

  http://paste.openstack.org/show/38221/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1195817/+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 1276639] Re: block live migration does not work when a volume is attached

Long incomplete bug waiting for confirmation.

** Changed in: nova
   Status: Incomplete = Invalid

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

Title:
  block live migration does not work when a volume is attached

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Environment:
   - Two compute nodes, running Ubuntu 12.04 LTS
   - KVM Hypervisor
   - Ceph (dumpling) back-end for Cinder
   - Grizzly-level Openstack

  Steps to reproduce:
   1) Create instance and volume
   2) Attach volume to instance
   3) Attempt a block migration between compute nodes - eg: nova live-migration 
--block-migrate 9b85b983-dced-4574-b14c-c72e4d92982a

  Packages:
  ii  ceph 0.67.5-1precise
  ii  ceph-common  0.67.5-1precise
  ii  ceph-fs-common   0.67.5-1precise
  ii  ceph-fuse0.67.5-1precise
  ii  ceph-mds 0.67.5-1precise
  ii  curl 7.29.0-1precise.ceph
  ii  kvm  
1:84+dfsg-0ubuntu16+1.0+noroms+0ubuntu14.13
  ii  kvm-ipxe 1.0.0+git-3.55f6c88-0ubuntu1
  ii  libcephfs1   0.67.5-1precise
  ii  libcurl3 7.29.0-1precise.ceph
  ii  libcurl3-gnutls  7.29.0-1precise.ceph
  ii  libleveldb1  1.12.0-1precise.ceph
  ii  nova-common  1:2013.1.4-0ubuntu1~cloud0
  ii  nova-compute 1:2013.1.4-0ubuntu1~cloud0
  ii  nova-compute-kvm 1:2013.1.4-0ubuntu1~cloud0
  ii  python-ceph  0.67.5-1precise
  ii  python-cinderclient  1:1.0.3-0ubuntu1~cloud0
  ii  python-nova  1:2013.1.4-0ubuntu1~cloud0
  ii  python-novaclient1:2.13.0-0ubuntu1~cloud0
  ii  qemu-common  1.0+noroms-0ubuntu14.13
  ii  qemu-kvm 1.0+noroms-0ubuntu14.13
  ii  qemu-utils   1.0+noroms-0ubuntu14.13
  ii  libvirt-bin  1.0.2-0ubuntu11.13.04.5~cloud1
  ii  libvirt0 1.0.2-0ubuntu11.13.04.5~cloud1
  ii  python-libvirt   1.0.2-0ubuntu11.13.04.5~cloud1

  /var/log/nova/nova-compute on source:

  2014-02-05 16:36:46.014 998 INFO nova.compute.manager [-] Lifecycle event 2 
on VM 9b85b983-dced-4574-b14c-c72e4d92982a
  2014-02-05 16:36:46.233 998 INFO nova.compute.manager [-] [instance: 
9b85b983-dced-4574-b14c-c72e4d92982a] During sync_power_state the instance has 
a pending task. Skip.
  2014-02-05 16:36:46.234 998 INFO nova.compute.manager [-] Lifecycle event 2 
on VM 9b85b983-dced-4574-b14c-c72e4d92982a
  2014-02-05 16:36:46.468 998 INFO nova.compute.manager [-] [instance: 
9b85b983-dced-4574-b14c-c72e4d92982a] During sync_power_state the instance has 
a pending task. Skip.
  2014-02-05 16:41:09.029 998 INFO nova.compute.manager [-] Lifecycle event 1 
on VM 9b85b983-dced-4574-b14c-c72e4d92982a
  2014-02-05 16:41:09.265 998 INFO nova.compute.manager [-] [instance: 
9b85b983-dced-4574-b14c-c72e4d92982a] During sync_power_state the instance has 
a pending task. Skip.
  2014-02-05 16:41:09.640 998 ERROR nova.virt.libvirt.driver [-] [instance: 
9b85b983-dced-4574-b14c-c72e4d92982a] Live Migration failure: Unable to read 
from monitor: Connection reset by peer
  2014-02-05 16:41:12.165 998 WARNING nova.compute.manager [-] [instance: 
9b85b983-dced-4574-b14c-c72e4d92982a] Instance shutdown by itself. Calling the 
stop API.
  2014-02-05 16:41:12.398 998 INFO nova.virt.libvirt.driver [-] [instance: 
9b85b983-dced-4574-b14c-c72e4d92982a] Instance destroyed successfully.

  /var/log/libvirt/libvirtd.log on source:

  2014-02-05 14:41:07.607+: 3437: error : qemuMonitorIORead:502 : Unable to 
read from monitor: Connection reset by peer
  2014-02-05 14:41:09.633+: 3441: error : 
virNetClientProgramDispatchError:175 : An error occurred, but the cause is 
unknown
  2014-02-05 14:41:09.634+: 3441: error : 
qemuDomainObjEnterMonitorInternal:997 : operation failed: domain is no longer 
running
  2014-02-05 14:41:09.634+: 3441: warning : doPeer2PeerMigrate3:2872 : 
Guest instance-0315 probably left in 'paused' state on source

  /var/log/nova/nova-compute.log on target:

  2014-02-05 16:36:38.841 INFO nova.virt.libvirt.driver 
[req-0f0eaabf-9e29-4d45-88c9-20194be51d49 aaf3e92b69e04958b43348677ab7b38b 
1859d80f51ff4180b591f7fe2668fd68] Instance launched has CPU info:
  {vendor: Intel, model: SandyBridge, arch: x86_64, features: 
[pdpe1gb, osxsave, dca, pcid, pdcm, xtpr, tm2, est, smx, 
vmx, ds_cpl, monitor, dtes64, pbe, tm, ht, ss, acpi, ds, 
vme], topology: {cores: 6, threads: 2, sockets: 1}}
  2014-02-05 16:36:46.008 28458 INFO nova.compute.manager [-] Lifecycle event 0 
on VM 9b85b983-dced-4574-b14c-c72e4d92982a

[Yahoo-eng-team] [Bug 1187379] Re: nova-api and nova-compute not running

** Changed in: nova
   Status: Incomplete = Invalid

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

Title:
  nova-api and nova-compute not running

Status in OpenStack Compute (Nova):
  Invalid

Bug description:

  hi

  I am installing Openstack Grizzly nova components,  when I run nova-api and 
nova-compute , I get an error as  :
  nova ArgsAlreadyParsedError: arguments already parsed: cannot register CLI 
option

  All other nova services are running properly.. 
  I already have following settings in api-paste.ini :

  [filter:authtoken]
  paste.filter_factory = keystoneclient.middleware.auth_token:filter_factory

  Still the issue persists.. what can I do to resolve this ??

  I have my nova.conf ..

  Following is the error trace ;

  
  2013-06-03 14:53:10.797 18356 CRITICAL nova [-] arguments already parsed: 
cannot register CLI option
  2013-06-03 14:53:10.797 18356 TRACE nova Traceback (most recent call last):
  2013-06-03 14:53:10.797 18356 TRACE nova File ./nova-api, line 5, in 
module
  2013-06-03 14:53:10.797 18356 TRACE nova 
pkg_resources.run_script('nova==2013.1.1', 'nova-api')
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in run_script
  2013-06-03 14:53:10.797 18356 TRACE nova 
self.require(requires)[0].run_script(script_name, ns)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235, in run_script
  2013-06-03 14:53:10.797 18356 TRACE nova execfile(script_filename, namespace, 
namespace)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/local/lib/python2.7/dist-packages/nova-2013.1.1-py2.7.egg/EGG-INFO/scripts/nova-api,
 line 59, in module
  2013-06-03 14:53:10.797 18356 TRACE nova max_url_len=16384)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/local/lib/python2.7/dist-packages/nova-2013.1.1-py2.7.egg/nova/service.py,
 line 598, in __init__
  2013-06-03 14:53:10.797 18356 TRACE nova self.app = self.loader.load_app(name)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/local/lib/python2.7/dist-packages/nova-2013.1.1-py2.7.egg/nova/wsgi.py, 
line 482, in load_app
  2013-06-03 14:53:10.797 18356 TRACE nova return deploy.loadapp(config:%s % 
self.config_path, name=name)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 247, in 
loadapp
  2013-06-03 14:53:10.797 18356 TRACE nova return loadobj(APP, uri, name=name, 
**kw)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 272, in 
loadobj
  2013-06-03 14:53:10.797 18356 TRACE nova return context.create()
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 710, in create
  2013-06-03 14:53:10.797 18356 TRACE nova return self.object_type.invoke(self)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 144, in invoke
  2013-06-03 14:53:10.797 18356 TRACE nova **context.local_conf)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/lib/python2.7/dist-packages/paste/deploy/util.py, line 56, in fix_call
  2013-06-03 14:53:10.797 18356 TRACE nova val = callable(*args, **kw)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/lib/python2.7/dist-packages/paste/urlmap.py, line 25, in urlmap_factory
  2013-06-03 14:53:10.797 18356 TRACE nova app = loader.get_app(app_name, 
global_conf=global_conf)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 350, in 
get_app
  2013-06-03 14:53:10.797 18356 TRACE nova name=name, 
global_conf=global_conf).create()
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 710, in create
  2013-06-03 14:53:10.797 18356 TRACE nova return self.object_type.invoke(self)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 144, in invoke
  2013-06-03 14:53:10.797 18356 TRACE nova **context.local_conf)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/lib/python2.7/dist-packages/paste/deploy/util.py, line 56, in fix_call
  2013-06-03 14:53:10.797 18356 TRACE nova val = callable(*args, **kw)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/local/lib/python2.7/dist-packages/nova-2013.1.1-py2.7.egg/nova/api/auth.py,
 line 61, in pipeline_factory
  2013-06-03 14:53:10.797 18356 TRACE nova app = filter(app)
  2013-06-03 14:53:10.797 18356 TRACE nova File 
/usr/local/lib/python2.7/dist-packages/nova-2013.1.1-py2.7.egg/nova/wsgi.py, 
line 331, in _factory
  2013-06-03 14:53:10.797 18356 TRACE nova return cls(app, **local_config)
  2013-06-03 14:53:10.797 18356 TRACE nova File

[Yahoo-eng-team] [Bug 1190086] Re: empty console log output with grizzly on centOS distribution

** Changed in: nova
   Status: Incomplete = Invalid

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

Title:
  empty console log output with grizzly on centOS distribution

Status in OpenStack Compute (Nova):
  Invalid
Status in “nova” package in Ubuntu:
  Invalid

Bug description:
  we tried to boot  fedora image f17-x86_64-openstack-sda.qcow2 from
  openstack grizzley installation, but no console output is generated.

  
  when i look into  /var/log/libvirt/qemu/instance-0067.log after i see a 
empty console log, 

  following is the content :

  2013-06-11 22:06:38.609+: starting up
  LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none 
/usr/libexec/qemu-kvm -name instance-0067 -S -M rhel6.4.0 -cpu 
SandyBridge,+pdpe1gb,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme
 -enable-kvm -m 2048 -smp 1,sockets=1,cores=1,threads=1 -uuid 
6e0857f4-ed3e-4e1a-81db-d69456b17651 -smbios type=1,manufacturer=Red Hat 
Inc.,product=OpenStack 
Nova,version=2013.1.1-3.el6,serial=36353030-3437-5553-4532-34364d434e43,uuid=6e0857f4-ed3e-4e1a-81db-d69456b17651
 -nodefconfig -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0067.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/6e0857f4-ed3e-4e1a-81db-d69456b17651/disk,if=none,id=drive-virtio-disk0,format=qcow2,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=23,id=hostnet0,vhost=on,vhostfd=24 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:51:44:cf,bus=pci.0,addr=0x3 
-chardev 
file,id=charserial0,path=/var/lib/nova/instances/6e0857f4-ed3e-4e1a-81db-d69456b17651/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.1.255.253:0 -k en-us -vga cirrus -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
  char device redirected to /dev/pts/0

  
  explicit  probe into virsh console reveals this :

  virsh # list
   IdName   State
  
   4 instance-0068  running

  virsh # console instance-0068
  Connected to domain instance-0068
  Escape character is ^]
  error: internal error character device (null) is not using a PTY

  
  and given below is respective  libvirt.xml file. any pointers on approaching 
this issues is appreciated. 

  
  domain type=kvm
uuid6e0857f4-ed3e-4e1a-81db-d69456b17651/uuid
nameinstance-0067/name
memory2097152/memory
vcpu1/vcpu
sysinfo type=smbios
  system
entry name=manufacturerRed Hat Inc./entry
entry name=productOpenStack Nova/entry
entry name=version2013.1.1-3.el6/entry
entry name=serial36353030-3437-5553-4532-34364d434e43/entry
entry name=uuid6e0857f4-ed3e-4e1a-81db-d69456b17651/entry
  /system
/sysinfo
os
  typehvm/type
  boot dev=hd/
  smbios mode=sysinfo/
/os
features
  acpi/
  apic/
/features
clock offset=utc
  timer name=pit tickpolicy=delay/
  timer name=rtc tickpolicy=catchup/
/clock
cpu mode=host-model match=exact/
devices
  disk type=file device=disk
driver name=qemu type=qcow2 cache=none/
source 
file=/var/lib/nova/instances/6e0857f4-ed3e-4e1a-81db-d69456b17651/disk/
target bus=virtio dev=vda/
  /disk
  interface type=bridge
mac address=fa:16:3e:51:44:cf/
model type=virtio/
source bridge=br-int/
target dev=tap4ce130e7-1a/
virtualport type=openvswitch
  parameters interfaceid=4ce130e7-1acc-4a06-8f84-78a320f0f108/
/virtualport
  /interface
  serial type='pty'
   target port='0'/
  /serial
  console type='pty'
   target type='serial' port='0'/
  /console
  serial type=file
source 
path=/var/lib/nova/instances/6e0857f4-ed3e-4e1a-81db-d69456b17651/console.log/
  /serial
  serial type=pty/
  input type=tablet bus=usb/
  graphics type=vnc autoport=yes keymap=en-us listen=10.1.255.253/
/devices
  /domain

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1190086/+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 1161411] Re: Neutron SecGroup API should validate group name

Talking with Phil today on IRC. Because you can now reference by UUID he
said this wasn't really an issue they were into digging into any more.
I'm changing to Opinion / Wishlist in case someone wants to make this
part better in the future.

** Changed in: nova
   Status: Incomplete = Opinion

** Changed in: nova
   Importance: Medium = Wishlist

** Changed in: nova
   Status: Opinion = Confirmed

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

Title:
  Neutron SecGroup API should validate group name

Status in OpenStack Compute (Nova):
  Confirmed

Bug description:
  The validation of names and groups comes from the security group API
  driver validate_property() method, and the NativeNovaSecurityGroupAPI
  and NativeQuantumSecurityGroupAPI in Nova have different rules (Nova
  blocks empty names and descriptions and quantum does no validation).

  Normally an empty name is not an issue, since all SG APIs are based on
  the ID of the group.   However the action to add an instance to a
  security group takes a name not an ID - and will not accept an empty
  name.Hence for consistency with Nova behavior the
  QuantumSecurityGroupAPI should perform the same validation as Nova.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1161411/+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 1331913] Re: tempest.api.volume.test_volumes_actions.VolumesActionsTestXML.test_volume_upload fails

2014-09-16 Thread David Kranz

I really don't know if this is a problem with glance or devstack or
something else.

** Changed in: tempest
   Status: New = Invalid

** 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 Glance.
https://bugs.launchpad.net/bugs/1331913

Title:
  
tempest.api.volume.test_volumes_actions.VolumesActionsTestXML.test_volume_upload
  fails

Status in OpenStack Image Registry and Delivery Service (Glance):
  New
Status in Tempest:
  Invalid

Bug description:
  See: http://logs.openstack.org/07/81707/7/check/check-tempest-dsvm-
  full/8b1ee80/console.html

  2014-06-19 03:37:29.394 | 
tempest.api.volume.test_volumes_actions.VolumesActionsTestXML.test_volume_upload[gate,image]
  2014-06-19 03:37:29.394 | 

  2014-06-19 03:37:29.395 | 
  2014-06-19 03:37:29.395 | Captured traceback:
  2014-06-19 03:37:29.395 | ~~~
  2014-06-19 03:37:29.395 | Traceback (most recent call last):
  2014-06-19 03:37:29.395 |   File tempest/test.py, line 126, in wrapper
  2014-06-19 03:37:29.395 | return f(self, *func_args, **func_kwargs)
  2014-06-19 03:37:29.395 |   File 
tempest/api/volume/test_volumes_actions.py, line 107, in test_volume_upload
  2014-06-19 03:37:29.395 | 
self.image_client.wait_for_image_status(image_id, 'active')
  2014-06-19 03:37:29.395 |   File 
tempest/services/image/v1/json/image_client.py, line 289, in 
wait_for_image_status
  2014-06-19 03:37:29.395 | status=status)
  2014-06-19 03:37:29.395 | ImageKilledException: Image 
ecd98deb-ca3d-4207-b6c9-49ae6434e765 'killed' while waiting for 'active'

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1331913/+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 1370247] [NEW] glance_store rbd driver accidentally changed chunk size units

2014-09-16 Thread Josh Durgin

Public bug reported:

In migrating to glance_store, there was a typo of operators, so 1024**2
became 1024^6, which is 1026 in python, which makes the default chunk
size off by a couple orders of magnitude (~8k rather than 8mb).

** Affects: glance
 Importance: Undecided
 Assignee: Josh Durgin (jdurgin)
 Status: New

** Changed in: glance
 Assignee: (unassigned) = Josh Durgin (jdurgin)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1370247

Title:
  glance_store rbd driver accidentally changed chunk size units

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  In migrating to glance_store, there was a typo of operators, so
  1024**2 became 1024^6, which is 1026 in python, which makes the
  default chunk size off by a couple orders of magnitude (~8k rather
  than 8mb).

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1370247/+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 1370250] [NEW] Can not set volume attributes at instance launch by EC2 API

Public bug reported:

AWS allows to change block device attributes (such as volume size,
delete on termination behavior, existence) at instance launch.

For example, image xxx has devices:
vda, size 10, delete on termination
vdb, size 100, delete on termination
vdc, size 100, delete on termination
We can run an instance by
euca-run-instances ... xxx -b /dev/vda=:20 -b /dev/vdb=::false -b /dev/vdc=none
to get the instance with devices:
vda, size 20, delete on termination
vdb, size 100, not delete on termination

For Nova we get now:
$ euca-run-instances --instance-type m1.nano -b /dev/vda=::true ami-000a
euca-run-instances: error (InvalidBDMFormat): Block Device Mapping is Invalid: 
Unrecognized legacy format.

** 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/1370250

Title:
  Can not set volume attributes at instance launch by EC2 API

Status in OpenStack Compute (Nova):
  New

Bug description:
  AWS allows to change block device attributes (such as volume size,
  delete on termination behavior, existence) at instance launch.

  For example, image xxx has devices:
  vda, size 10, delete on termination
  vdb, size 100, delete on termination
  vdc, size 100, delete on termination
  We can run an instance by
  euca-run-instances ... xxx -b /dev/vda=:20 -b /dev/vdb=::false -b 
/dev/vdc=none
  to get the instance with devices:
  vda, size 20, delete on termination
  vdb, size 100, not delete on termination

  For Nova we get now:
  $ euca-run-instances --instance-type m1.nano -b /dev/vda=::true ami-000a
  euca-run-instances: error (InvalidBDMFormat): Block Device Mapping is 
Invalid: Unrecognized legacy format.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1370250/+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 1370265] [NEW] Crash on describing EC2 volume backed image with multiple devices

Public bug reported:

EC2 describe images crashes on volume backed instance snapshot which has
several volumes:

$ euca-describe-images
euca-describe-images: error (KeyError): Unknown error occurred.

Steps to reproduce
1 Create bootable volume
$ cinder create --image image-id size

2 Boot instance from volume
$ nova boot --flavor m1.nano --block-device-mapping /dev/vda=volume_id:::1 
inst

3 Create empty volume
$ cinder create 1

4 Attach the volume to the instance
$ nova volume-attach inst empty-volume-id /dev/vdd

5 Create volume backed snapshot
$ nova image-create inst sn-in

6 Describe EC2 images
$ euca-describe-images

** 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/1370265

Title:
  Crash on describing EC2 volume backed image with multiple devices

Status in OpenStack Compute (Nova):
  New

Bug description:
  EC2 describe images crashes on volume backed instance snapshot which
  has several volumes:

  $ euca-describe-images
  euca-describe-images: error (KeyError): Unknown error occurred.

  Steps to reproduce
  1 Create bootable volume
  $ cinder create --image image-id size

  2 Boot instance from volume
  $ nova boot --flavor m1.nano --block-device-mapping /dev/vda=volume_id:::1 
inst

  3 Create empty volume
  $ cinder create 1

  4 Attach the volume to the instance
  $ nova volume-attach inst empty-volume-id /dev/vdd

  5 Create volume backed snapshot
  $ nova image-create inst sn-in

  6 Describe EC2 images
  $ euca-describe-images

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1370265/+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 1369386] Re: ipset_enabled = True default is not upgrade friendly

2014-09-16 Thread Armando Migliaccio

I agree with all these points, but similar decisions were made in the
past, so I am not sure why this one should be treated any differently.

For instance, at the end of the Icehouse cycle, Neutron got a new
dependency on novaclient and yet we enabled notification by default.
This led to a similar unfriendly upgrade path the reason where Neutron
needed novaclient installed when previously it didn't.

As far this is concerned, I think this issue raised enough awareness
that we can fix the actual problem where it belongs, like TripleO,
package specs, puppet/chef cookbooks, rather than churning more changes
than are strictly required. Even deploying from source does not prevent
you from incurring from issues like these from time to time. Another
example is DVR: that requires L3 and Firewall agents to run on the
compute boxes now. This may lead to new dependencies that need to be
solved. We chose to keep DVR disabled by default, and that clearly gives
more time to people to catch up, but that's not why we did it.


** Changed in: neutron
   Status: In Progress = Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1369386

Title:
  ipset_enabled = True default is not upgrade friendly

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  Adds ipset support for Security Groups

  In commit 2562a9271c828e982a74593e8fd07be13b0cfc4a we recently added
  ipset support for Security Groups.

  The default is currently set to True which is not upgrade friendly in
  that anyone upgrading to the most recent Neutron code immediately has
  to have the ipset binary installed or their commands fail.

  It seems like we should set this to false by default (as a safe
  default) and allow users to opt in since it is really an
  optimization...

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1369386/+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 1370286] [NEW] rephrase action_past in Access Security

2014-09-16 Thread Cindy Lu

Public bug reported:

https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/access_and_security/keypairs/tables.py#L37

 def action_past(count):
return ungettext_lazy(
uKey pair deleted,
uKey pairs deleted,
count
)
Seems like convention in Horizon to say Deleted Key Pair instead.

Reference:
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/tables.py#L132

** 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/1370286

Title:
  rephrase action_past in Access  Security

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/access_and_security/keypairs/tables.py#L37

   def action_past(count):
  return ungettext_lazy(
  uKey pair deleted,
  uKey pairs deleted,
  count
  )
  Seems like convention in Horizon to say Deleted Key Pair instead.

  Reference:
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/tables.py#L132

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370286/+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 1370273] Re: volume type-create allows only spaces as type name

2014-09-16 Thread Gloria Gu

horizon bug https://bugs.launchpad.net/horizon/+bug/1357586

** Also affects: horizon
   Importance: Undecided
   Status: New

** No longer affects: horizon

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

Title:
  volume type-create  allows only spaces as type name

Status in Cinder:
  Triaged

Bug description:
  When use cinder command to create volume type

  cinder type-create

  It gets created with an empty name.

  Name is a required field. Cinder should not allow name with just
  spaces.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1370273/+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 1370297] [NEW] volume/snapshot allows name with only white spaces

2014-09-16 Thread Gloria Gu

Public bug reported:

When create or edit volume or snapshot, it allows name field with only
white spaces.

How to reproduce:

Just go to project - volume to create a volume with only white spaces a
name, the volume shows up in the volume table with an empty name.


same for snapshot

Expect:

form should not allow empty name when create/edit volume or snapshot


This is split from https://bugs.launchpad.net/horizon/+bug/1357586 since volume 
and snapshot name is different from volume type name.

** 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/1370297

Title:
  volume/snapshot allows name with only white spaces

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When create or edit volume or snapshot, it allows name field with only
  white spaces.

  How to reproduce:

  Just go to project - volume to create a volume with only white spaces
  a name, the volume shows up in the volume table with an empty name.

  
  same for snapshot

  Expect:

  form should not allow empty name when create/edit volume or snapshot

  
  This is split from https://bugs.launchpad.net/horizon/+bug/1357586 since 
volume and snapshot name is different from volume type name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370297/+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 1348629] Re: Baremetal driver reports bogus vm_mode of 'baremetal'

2014-09-16 Thread Michael Still

** Also affects: nova/juno
   Importance: Medium
 Assignee: Daniel Berrange (berrange)
   Status: In Progress

** Changed in: nova/juno
Milestone: None = juno-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/1348629

Title:
  Baremetal driver reports bogus vm_mode of 'baremetal'

Status in OpenStack Compute (Nova):
  In Progress
Status in OpenStack Compute (nova) juno series:
  In Progress

Bug description:
  The Baremetal driver reports a 'vm_mode' of 'baremetal' for supported
  instance types. This is bogus because the baremetal driver is running
  OS using the native machine ABI, which is represented by vm_mode.HVM

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1348629/+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 1361183] Re: Shouldn't pass instance.uuid when call _set_instance_error_state

2014-09-16 Thread Alex Xu

** Changed in: nova
   Status: In Progress = Invalid

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

Title:
  Shouldn't pass instance.uuid when call _set_instance_error_state

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  This found by review code.

  We already turn the _set_instance_error_state to use instance object. but 
there 
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1942
  still pass the uuid.

  When there is exception raised, will get error as below:
  2014-08-25 19:57:31.784 ERROR oslo.messaging.rpc.dispatcher 
[req-164071ff-f94e-4cb4-999b-2d595c6e77c6 admin admin] Exception during message 
handling: string in
  dices must be integers, not str
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher Traceback (most 
recent call last):
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 
134, in _dis
  patch_and_reply
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher 
incoming.message))
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 
177, in _dis
  patch
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher return 
self._do_dispatch(endpoint, method, ctxt, args)
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 
123, in _do_
  dispatch
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher result = 
getattr(endpoint, method)(ctxt, **new_args)
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/exception.py, line 88, in wrapped
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher payload)
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/openstack/common/excutils.py, line 82, in __exit__
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/exception.py, line 71, in wrapped
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher return 
f(self, context, *args, **kw)
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/compute/manager.py, line 296, in decorated_function
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher pass
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/openstack/common/excutils.py, line 82, in __exit__
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/compute/manager.py, line 282, in decorated_function
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/compute/manager.py, line 346, in decorated_function
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/compute/manager.py, line 324, in decorated_function
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher 
kwargs['instance'], e, sys.exc_info())
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/openstack/common/excutils.py, line 82, in __exit__
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/compute/manager.py, line 312, in decorated_function
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/compute/manager.py, line 1984, in build_and_run_instance
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher node, limits)
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/openstack/common/lockutils.py, line 325, in inner
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher return 
f(*args, **kwargs)
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/compute/manager.py, line 1942, in 
do_build_and_run_instance
  2014-08-25 19:57:31.784 TRACE oslo.messaging.rpc.dispatcher 
self._set_instance_error_state(context, instance.uuid)
  2014-08-25 19:57:31.784 TRACE

[Yahoo-eng-team] [Bug 1370297] Re: volume/snapshot allows name with only white spaces

2014-09-16 Thread Liyingjun

** Also affects: cinder
   Importance: Undecided
   Status: New

** Changed in: cinder
 Assignee: (unassigned) = Liyingjun (liyingjun)

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

Title:
  volume/snapshot allows name with only white spaces

Status in Cinder:
  New
Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When create or edit volume or snapshot, it allows name field with only
  white spaces.

  How to reproduce:

  Just go to project - volume to create a volume with only white spaces
  a name, the volume shows up in the volume table with an empty name.

  
  same for snapshot

  Expect:

  form should not allow empty name when create/edit volume or snapshot

  
  This is split from https://bugs.launchpad.net/horizon/+bug/1357586 since 
volume and snapshot name is different from volume type name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1370297/+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 1370317] [NEW] l2population_rpc_base.py depends on ovs_neutron_agent

2014-09-16 Thread YAMAMOTO Takashi

Public bug reported:

l2pop UT (neutron/tests/unit/agent/l2population_rpc_base.py) depends on 
ovs_neutron_agent.
it's better to make it independent from OVS agent because the l2pop module is 
used by other agents like ofagent.

** 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/1370317

Title:
  l2population_rpc_base.py depends on ovs_neutron_agent

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  l2pop UT (neutron/tests/unit/agent/l2population_rpc_base.py) depends on 
ovs_neutron_agent.
  it's better to make it independent from OVS agent because the l2pop module is 
used by other agents like ofagent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1370317/+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 1156563] Re: Uptime/VCPU hours of stopped Instances Keep on increasing even if instance satus is in shutdown mode

Since it causes enough confusion that people open bug reports, we should
rename the column. Any suggestion on what would be appropriate? Time
since creation sounds like it should be good enough.

** Changed in: horizon
 Assignee: Santiago Baldassin (santiago-b-baldassin) = (unassigned)

** Changed in: horizon
   Status: Invalid = Confirmed

** Tags removed: horizon uptime
** Tags added: ux

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

Title:
  Uptime/VCPU  hours of stopped Instances Keep on increasing even if
  instance satus is in shutdown mode

Status in OpenStack Dashboard (Horizon):
  Confirmed

Bug description:
  I am using Folsom on Ubunru 12.04 with Horizon.

  Created 5 instances on KVM on 12.04 (running nova-compute only )and with out 
stopping VM, restarted Host machine.
  Under Instance Tab status of all instance is Shutdown but under Overview 
Uptime of VM keeps on increasing.
  Same in case of VCPU hours.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1156563/+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 1370322] [NEW] Add a tooltip for Admin State in the Network forms

Public bug reported:

It's not always clear to users what admin state means. A tooltip that
reads something like Whether the network is up and forwarding packets
would help with this.

Actually, if my understanding is correct, we might want to consider
renaming Admin state to simply say Active in the dashboard?

** Affects: horizon
 Importance: Medium
 Status: New


** Tags: neutron ux

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

Title:
  Add a tooltip for Admin State in the Network forms

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  It's not always clear to users what admin state means. A tooltip
  that reads something like Whether the network is up and forwarding
  packets would help with this.

  Actually, if my understanding is correct, we might want to consider
  renaming Admin state to simply say Active in the dashboard?

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370322/+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 1370323] [NEW] Capitalisation of Create Router

Public bug reported:

Most forms seem to capitalise the title and button (e.g. Create
Volume, Create Security Group, Launch Instance). The router
template however uses Create router for its title and button. This
should be changed to Create Router for consistency.

https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/routers/templates/routers/_create.html

Because both Create Router and Create router strings are already in
the po files, this can go through during String Freeze as it won't add
any additional translation work.

** Affects: horizon
Importance: Low
Status: New

** Tags: low-hanging-fruit

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

Title:
Capitalisation of Create Router

Status in OpenStack Dashboard (Horizon):
New

Bug description:
Most forms seem to capitalise the title and button (e.g. Create
Volume, Create Security Group, Launch Instance). The router
template however uses Create router for its title and button. This
should be changed to Create Router for consistency.

https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/routers/templates/routers/_create.html

Because both Create Router and Create router strings are already
in the po files, this can go through during String Freeze as it won't
add any additional translation work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370323/+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 1369986] Re: Federaton extension fails due to missing pysaml2 library

2014-09-16 Thread Morgan Fainberg

Based on comments on the review this is not an open bug.

** Changed in: keystone
   Status: Incomplete = Invalid

** Changed in: keystone
Milestone: juno-rc1 = None

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1369986

Title:
  Federaton extension fails due to missing pysaml2 library

Status in OpenStack Identity (Keystone):
  Invalid

Bug description:
  When enabling federation extension on my fresh devstack setup I noticed 
Keystone failed due to missing pysaml2 library.
  It is probably due to the fact that pysaml2 is present in 
test-requirements.txt file and absent in requirements.txt.

  I think the solution is to ad pysaml2 to the requirements.txt file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1369986/+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 1370326] [NEW] Last Updated in Admin System Info panel is not displayed with translated string

2014-09-16 Thread Akihiro Motoki

Public bug reported:

Last Updated column in Admin System Info panel is not displayed with
translated string even if PO file contains perper Last Updated entry.

Replacing pgettext with pgettext_lazy in
openstack_dashboard/dashboards/admin/info/tables.py addresses the
problem.

** Affects: horizon
 Importance: Low
 Assignee: Akihiro Motoki (amotoki)
 Status: New


** Tags: i18n

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

Title:
  Last Updated in Admin System Info panel is not displayed with
  translated string

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Last Updated column in Admin System Info panel is not displayed with
  translated string even if PO file contains perper Last Updated
  entry.

  Replacing pgettext with pgettext_lazy in
  openstack_dashboard/dashboards/admin/info/tables.py addresses the
  problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370326/+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 1370330] [NEW] Cannot attach a volume without '/dev/' prefix by EC2 API