[Yahoo-eng-team] [Bug 1472956] [NEW] Wrong line python-ldap=2.4; python_version=='2.7' in test_requirements
Public bug reported: Line 16 python-ldap=2.4;python_version=='2.7' will block the keystone from installing via devstack. Should it be python-ldap=2.4 # python_version=='2.7'? ** 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/1472956 Title: Wrong line python-ldap=2.4;python_version=='2.7' in test_requirements Status in OpenStack Identity (Keystone): New Bug description: Line 16 python-ldap=2.4;python_version=='2.7' will block the keystone from installing via devstack. Should it be python-ldap=2.4 # python_version=='2.7'? To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1472956/+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 1444909] [NEW] Attached volumes migration fails due to swap volume
Public bug reported: In cinder, when try to migrate an attached volume. The n-cpu reports the error: =n-cpu= 2015-04-16 17:35:30.581 ERROR root [req-cf02b6cd-4bd7-4e59-986b-278596cec0a6 admin admin] Original exception being dropped: ['Tracebac k (most recent call last):\n', ' File /opt/stack/nova/nova/compute/manager.py, line 340, in decorated_function\n return function (self, context, *args, **kwargs)\n', ' File /opt/stack/nova/nova/compute/manager.py, line 4939, in swap_volume\n context, old_vo lume_id, instance_uuid=instance.uuid)\n', AttributeError: 'unicode' object has no attribute 'uuid'\n] 2015-04-16 17:35:31.043 ERROR root [req-cf02b6cd-4bd7-4e59-986b-278596cec0a6 admin admin] Original exception being dropped: ['Tracebac k (most recent call last):\n', ' File /opt/stack/nova/nova/compute/manager.py, line 295, in decorated_function\n return function (self, context, *args, **kwargs)\n', ' File /opt/stack/nova/nova/compute/manager.py, line 352, in decorated_function\n kwargs[\' instance\'], e, sys.exc_info())\n', ' File /opt/stack/nova/nova/compute/utils.py, line 87, in add_instance_fault_from_exc\nfaul t_obj.instance_uuid = instance.uuid\n', AttributeError: 'unicode' object has no attribute 'uuid'\n] 2015-04-16 17:35:31.046 ERROR oslo_messaging.rpc.dispatcher [req-cf02b6cd-4bd7-4e59-986b-278596cec0a6 admin admin] Exception during me ssage handling: string indices must be integers 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher Traceback (most recent call last): 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatch er.py, line 142, in _dispatch_and_reply 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher executor_callback)) 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatch er.py, line 186, in _dispatch 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher executor_callback) 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatch er.py, line 130, in _do_dispatch 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher result = func(ctxt, **new_args) 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 6756, in swap_volum e 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher new_volume_id) 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/exception.py, line 88, in wrapped 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher payload) 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py, li ne 85, in __exit__ 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/exception.py, line 71, in wrapped 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher return f(self, context, *args, **kw) 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 311, in decorated_f unction 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher instance_uuid = keyed_args['instance']['uuid'] 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher TypeError: string indices must be integers 2015-04-16 17:35:31.046 TRACE oslo_messaging.rpc.dispatcher ** Affects: cinder Importance: Undecided Status: New ** Affects: nova Importance: Undecided Status: New ** Also affects: cinder 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/1444909 Title: Attached volumes migration fails due to swap volume Status in Cinder: New Status in OpenStack Compute (Nova): New Bug description: In cinder, when try to migrate an attached volume. The n-cpu reports the error: =n-cpu= 2015-04-16 17:35:30.581 ERROR root [req-cf02b6cd-4bd7-4e59-986b-278596cec0a6 admin admin] Original exception being dropped: ['Tracebac k (most recent call last):\n', ' File /opt/stack/nova/nova/compute/manager.py, line 340, in decorated_function\n return function (self, context, *args, **kwargs)\n', ' File /opt/stack/nova/nova/compute/manager.py, line 4939, in swap_volume\n context, old_vo lume_id, instance_uuid=instance.uuid)\n', AttributeError: 'unicode' object has no attribute 'uuid'\n] 2015-04-16 17:35:31.043 ERROR
[Yahoo-eng-team] [Bug 1414802] Re: volume-attach already attached and already detached are not mutually exclusive
** Changed in: cinder Assignee: (unassigned) = Vincent Hou (houshengbo) ** 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/1414802 Title: volume-attach already attached and already detached are not mutually exclusive Status in Cinder: New Status in OpenStack Compute (Nova): New Bug description: nova volume-attach 81eef059-1490-4ec3-b0fc-b1b4e6380ee8 639e0a87-1190-42d4-b3a1-a385090aec06 ERROR: Invalid volume: already attached (HTTP 400) (Request-ID: req-1c51a40b-1015-4cee-b313-5dda524a3555) nova volume-detach 81eef059-1490-4ec3-b0fc-b1b4e6380ee8 639e0a87-1190-42d4-b3a1-a385090aec06 ERROR: Invalid volume: already detached (HTTP 400) (Request-ID: req-bb99c24e-1ca8-4f02-bb0a-9bb125857637) I'm trying to resolve a much larger problem with my openstack environment, involving volume exporting, and I ran across this situation. Whatever the tests are for these two messages, they should be mutually exclusive. Maybe a third message is needed, for some intermediate state? To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1414802/+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 1328773] Re: Incorrectly set kernal_id and ramdisk_id for the instance
This bug was resolved by a later patch. ** 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/1328773 Title: Incorrectly set kernal_id and ramdisk_id for the instance Status in OpenStack Compute (Nova): Invalid Bug description: Env: Launch the nova and glance services with devstack and choose libvirt as the hypervisor driver. If we launch the VM, the kernal_id and ramdisk_id are set to null, but actually they should be referring to two other images according to the image properties. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1328773/+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 1328773] [NEW] Incorrectly set kernal_id and ramdisk_id for the instance
Public bug reported: Env: Launch the nova and glance services with devstack and choose libvirt as the hypervisor driver. If we launch the VM, the kernal_id and ramdisk_id are set to null, but actually they should be referring to two other images according to the image properties. ** Affects: nova Importance: Undecided Assignee: Vincent Hou (houshengbo) Status: New ** Changed in: nova Assignee: (unassigned) = Vincent Hou (houshengbo) -- 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/1328773 Title: Incorrectly set kernal_id and ramdisk_id for the instance Status in OpenStack Compute (Nova): New Bug description: Env: Launch the nova and glance services with devstack and choose libvirt as the hypervisor driver. If we launch the VM, the kernal_id and ramdisk_id are set to null, but actually they should be referring to two other images according to the image properties. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1328773/+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 1316927] [NEW] Make the version of the glance api configurable for the image upload and download
Public bug reported: Nova uses glance client to upload or download the image. However, the version 1 is hard coded. The user cannot switch to another version. We need to add a flag for the configuration like glance_api_version to decide which glance api we are going to use. This part of work has already been done for cinder. ** Affects: nova Importance: Undecided Assignee: Vincent Hou (houshengbo) Status: New ** Changed in: nova Assignee: (unassigned) = Vincent Hou (houshengbo) -- 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/1316927 Title: Make the version of the glance api configurable for the image upload and download Status in OpenStack Compute (Nova): New Bug description: Nova uses glance client to upload or download the image. However, the version 1 is hard coded. The user cannot switch to another version. We need to add a flag for the configuration like glance_api_version to decide which glance api we are going to use. This part of work has already been done for cinder. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1316927/+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 1155512] Re: Issues with booting from the volume
This issue has been fixed by https://review.openstack.org/#/c/33296/. ** Changed in: nova Status: In Progress = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1155512 Title: Issues with booting from the volume Status in OpenStack Compute (Nova): Fix Released Bug description: Folks, correct me when I make a mistake. Issue 1: First, I create a bootable volume with cinder create --image-id $image_id--display_name=boot_volume --display_description test bootable volume 2. What I expect: the image has been copied into the volume. Then, I boot a VM from this volume with nova boot --flavor 2 --block-device-mapping vda=$vol_id --security_groups=default VM_test. What I expect: the VM should be successfully booted and in healthy state. Result: The VM is unable to ping. Issue 2: First, I create a volume with with cinder create 2. Then, I boot a VM from this non-bootable volume with nova boot --flavor 2 --block-device-mapping vda=$vol_id --security_groups=default VM_test_1. What I expect: see some warning or error message telling me that this volume is not bootable. Result: the VM is successfully booted with no error, but it cannot be pinged. Please advise with your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1155512/+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 1157042] Re: VMs and volumes can be accessed in a different tenant by a different user
Hi Sandeep. Thank you for asking. This is a bug no longer valid. I was using service as the tenant/projecet, service is actually a tenant, in which any user can access the resource. If we create different users and tenants, it should behave normally. ** Changed in: cinder Status: Incomplete = 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/1157042 Title: VMs and volumes can be accessed in a different tenant by a different user Status in Cinder: Invalid Status in OpenStack Compute (Nova): Invalid Bug description: 1. Set username=admin and tenant=admin, create a volume and a VM. Run cinder list and nova list. Remember the volume-id and vm-id. 2. Switch to another user and tenant, run cinder list and nova list. There is no volume or VM listed. 3. Since we have already known the volume-id and vm-id. It is possible to try all the commands which applies to volumes and VMs, like delete, attach, start, stop, reboot... Theoretically under a different user and tenant, we are not supposed to access the volume or the VM. However, we can do any operation we want, as long as we know the volume-id and VM-id. Related blueprint: https://blueprints.launchpad.net/cinder/+spec /volume-acl To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1157042/+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 1257617] [NEW] Nova is unable to authenticate via keystone
Public bug reported:
I updated the code yesterday with devstack. The latest nova code gave me
the following error, when I tried any nova command.
==n-api==
2013-12-04 13:49:40.151 INFO requests.packages.urllib3.connectionpool [-]
Starting new HTTPS connection (1): 9.119.148.201
2013-12-04 13:49:40.472 WARNING keystoneclient.middleware.auth_token [-]
Retrying on HTTP connection exception: [Errno 1] _ssl.c:504:
error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
2013-12-04 13:49:40.975 INFO requests.packages.urllib3.connectionpool [-]
Starting new HTTPS connection (1): 9.119.148.201
2013-12-04 13:49:41.008 WARNING keystoneclient.middleware.auth_token [-]
Retrying on HTTP connection exception: [Errno 1] _ssl.c:504:
error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
2013-12-04 13:49:42.012 INFO requests.packages.urllib3.connectionpool [-]
Starting new HTTPS connection (1): 9.119.148.201
2013-12-04 13:49:42.053 WARNING keystoneclient.middleware.auth_token [-]
Retrying on HTTP connection exception: [Errno 1] _ssl.c:504:
error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
2013-12-04 13:49:44.058 INFO requests.packages.urllib3.connectionpool [-]
Starting new HTTPS connection (1): 9.119.148.201
2013-12-04 13:49:44.100 ERROR keystoneclient.middleware.auth_token [-] HTTP
connection exception: [Errno 1] _ssl.c:504: error:140770FC:SSL
routines:SSL23_GET_SERVER_HELLO:unknown protocol
2013-12-04 13:49:44.103 DEBUG keystoneclient.middleware.auth_token [-] Token
validation failure. from (pid=7023) _validate_user_token
/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py:826
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token Traceback
(most recent call last):
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token File
/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py,
line 821, in _validate_user_token
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token data =
self.verify_uuid_token(user_token, retry)
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token File
/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py,
line 1096, in verify_uuid_token
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token
self.auth_version = self._choose_api_version()
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token File
/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py,
line 519, in _choose_api_version
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token
versions_supported_by_server = self._get_supported_versions()
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token File
/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py,
line 539, in _get_supported_versions
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token
response, data = self._json_request('GET', '/')
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token File
/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py,
line 749, in _json_request
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token response
= self._http_request(method, path, **kwargs)
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token File
/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py,
line 714, in _http_request
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token raise
NetworkError('Unable to communicate with keystone')
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token
NetworkError: Unable to communicate with keystone
2013-12-04 13:49:44.103 TRACE keystoneclient.middleware.auth_token
2013-12-04 13:49:44.110 WARNING keystoneclient.middleware.auth_token [-]
Authorization failed for token 4517bf0837d30dcf7b9cd438075c9d92
2013-12-04 13:49:44.111 INFO keystoneclient.middleware.auth_token [-] Invalid
user token - rejecting request
2013-12-04 13:49:44.114 INFO nova.osapi_compute.wsgi.server [-] 9.119.148.201
GET /v2/26b6d3afa22340a4aa5896068ab58f97/extensions HTTP/1.1 status: 401 len:
197 time: 3.9667039
2013-12-04 13:49:44.117 DEBUG keystoneclient.middleware.auth_token [-]
Authenticating user token from (pid=7023) __call__
/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py:568
2013-12-04 13:49:44.121 DEBUG keystoneclient.middleware.auth_token [-] Removing
headers from request environment:
X-Identity-Status,X-Domain-Id,X-Domain-Name,X-Project-Id,X-Project-Name,X-Project-Domain-Id,X-Project-Domain-Name,X-User-Id,X-User-Name,X-User-Domain-Id,X-User-Domain-Name,X-Roles,X-Service-Catalog,X-User,X-Tenant-Id,X-Tenant-Name,X-Tenant,X-Role
from (pid=7023) _remove_auth_headers
/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py:627
[Yahoo-eng-team] [Bug 1001118] Re: DELETE request for 'Security group rule' of another user is throwing error code 500
If users belong to the same tenant, the security groups and the rules
within them are shared between all the users in this tenant, which means
anyone in this tenant can get, update or delete the rules created by
anyone in this tenant.
If users belong to different tenants, the security groups and the rules
within them are not shared across different tenants.
The user needs to specify the security group's name to delete the rule
within it. Security group not found will be returned, if User B in
Tenant B tries to delete a security group created by User A in Tenant A.
The same result will be returned, if User B in Tenant B tries to delete
a rule created by User A in Tenant A for the security group.
** Changed in: nova
Status: Confirmed = 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/1001118
Title:
DELETE request for 'Security group rule' of another user is throwing
error code 500
Status in OpenStack Compute (Nova):
Opinion
Bug description:
When security group rule of user is tried to be deleted with another
user who is not the ower of Rule, error code of 500 is thrown.
Steps to reproduce:
1. Create two users A and B
2. Create a security group and assign rule 'R' using credentials of A
3. Try to DELETE rule 'R' using credentials of B
Expected Result:
The error message should indicate that Rule is not found i.e error code of
404 should be returned indicating NotFound exception
Actual Result:
novaclient.exceptions.ClientException: The server has either erred or is
incapable of performing the requested operation. (HTTP 500)
LOG:
rajalakshmi_ganesan@pshys0183~tests:-)./apitool.py GET os-security-groups
REQ: curl -i http://10.233.52.27:5000/v2.0/tokens -X POST -H Content-Type:
application/json -H User-Agent: python-novaclient
REQ BODY: {auth: {tenantName: demo, passwordCredentials:
{username: demo, password: muralik}}}
RESP:{'date': 'Fri, 18 May 2012 12:37:23 GMT', 'content-type':
'application/json', 'content-length': '2149', 'status': '200', 'vary':
'X-Auth-Token'} {access: {token: {expires:
2012-05-19T12:37:23Z, id: a7d2c1801e0547419f7aa928d4c54629,
tenant: {enabled: true, id: 732001bbd21942f1bec893c67c850066,
name: demo, description: null}}, serviceCatalog:
[{endpoints: [{adminURL:
http://10.233.52.27:8774/v2/732001bbd21942f1bec893c67c850066;,
region: RegionOne, publicURL:
http://10.233.52.27:8774/v2/732001bbd21942f1bec893c67c850066;,
internalURL:
http://10.233.52.27:8774/v2/732001bbd21942f1bec893c67c850066}],
endpoints_links: [], type: compute, name: Compute Service},
{endpoints: [{adminURL: http://10.233.52.27:;, region:
RegionOne, publicURL: http://10.233.52.27:;, internalURL:
http://10.233.52.27:}], endpoints_links: [], type: s3,
name: S3 Service}, {endpoints: [{adminURL:
http://10.233.52.27:9292/v1;, region: RegionOne, publicURL:
http://10.233.52.27:9292/v1;, internalURL:
http://10.233.52.27:9292/v1}], endpoints_links: [], type:
image, name: Image Service}, {endpoints: [{adminURL:
http://10.233.52.27:8776/v1/732001bbd21942f1bec893c67c850066;,
region: RegionOne, publicURL:
http://10.233.52.27:8776/v1/732001bbd21942f1bec893c67c850066;,
internalURL:
http://10.233.52.27:8776/v1/732001bbd21942f1bec893c67c850066}],
endpoints_links: [], type: volume, name: Volume Service},
{endpoints: [{adminURL: http://10.233.52.27:8773/services/Admin;,
region: RegionOne, publicURL:
http://10.233.52.27:8773/services/Cloud;, internalURL:
http://10.233.52.27:8773/services/Cloud}], endpoints_links: [],
type: ec2, name: EC2 Service}, {endpoints: [{adminURL:
http://10.233.52.27:35357/v2.0;, region: RegionOne, publicURL:
http://10.233.52.27:5000/v2.0;, internalURL:
http://10.233.52.27:5000/v2.0}], endpoints_links: [], type:
identity, name: Identity Service}], user: {username: demo,
roles_links: [], id: ea25a32fa3b941fdb18e09d696b842eb, roles:
[{id: 0b2f9dbc2e484ca1a425cae0188ec5c7, name: Member}, {id:
84494358fd4c47d69127dd7befb3367b, name: anotherrole}], name:
demo}}}
REQ: curl -i
http://10.233.52.27:8774/v2/732001bbd21942f1bec893c67c850066/os-
security-groups?fresh=1337324897.0 -X GET -H X-Auth-Project-Id: demo
-H User-Agent: python-novaclient -H X-Auth-Token:
a7d2c1801e0547419f7aa928d4c54629
REQ: curl -i
http://10.233.52.27:8774/v2/732001bbd21942f1bec893c67c850066/os-
security-groups?fresh=1337324897.0 -X GET -H X-Auth-Project-Id: demo
-H User-Agent: python-novaclient -H X-Auth-Token:
a7d2c1801e0547419f7aa928d4c54629
RESP:{'status': '200', 'content-length': '859', 'content-location':
u'http://10.233.52.27:8774/v2/732001bbd21942f1bec893c67c850066/os-
security-groups?fresh=1337324897.0', 'x-compute-request-id': 'req-
a6be085b-44f4-4a63-9586-d9bb2c94', 'date': 'Fri, 18 May 2012
12:37:23 GMT', 'content-type':
[Yahoo-eng-team] [Bug 1155512] Re: Issues with booting from the volume
** Changed in: cinder Status: Incomplete = Opinion ** Changed in: cinder Status: Opinion = Invalid ** No longer affects: cinder -- 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/1155512 Title: Issues with booting from the volume Status in OpenStack Compute (Nova): In Progress Bug description: Folks, correct me when I make a mistake. Issue 1: First, I create a bootable volume with cinder create --image-id $image_id--display_name=boot_volume --display_description test bootable volume 2. What I expect: the image has been copied into the volume. Then, I boot a VM from this volume with nova boot --flavor 2 --block-device-mapping vda=$vol_id --security_groups=default VM_test. What I expect: the VM should be successfully booted and in healthy state. Result: The VM is unable to ping. Issue 2: First, I create a volume with with cinder create 2. Then, I boot a VM from this non-bootable volume with nova boot --flavor 2 --block-device-mapping vda=$vol_id --security_groups=default VM_test_1. What I expect: see some warning or error message telling me that this volume is not bootable. Result: the VM is successfully booted with no error, but it cannot be pinged. Please advise with your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1155512/+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
