Hello guys, Has anyone ever had issues while doing a nova resize, confirm ? I noticed I'm being able to do the resize, the hypervisor (hyper-v) is indeed upgrading the cpu, ram and disk setting according to the flavor I'm setting in "nova resize".
but then, it gets stuck in the VERIFY_RESIZE status, it won't let me do a "nova resize-confirm <instance>" aborting on error 400. Has anyone got this sort of issue and managed to solve ? PS.: I noticed that even though my metadata service is up&running, my instances are not being able to curl for --user-data (when that is passed as parameter) nor for metadata. Could it be related to that ? Thank you a lot $ nova boot \ --image 39284e7f-ddf4-43fc-99c7-71f826d54309 \ --flavor 2 \ centos-on-hyperv +-------------------------------------+--------------------------------------+ | Property | Value | +-------------------------------------+--------------------------------------+ | status | BUILD | updated | 2013-05-16T16:25:59Z | OS-EXT-STS:task_state | scheduling | OS-EXT-SRV-ATTR:host | None | key_name | None | image | VHD-CentOS-64-x64 | hostId | | OS-EXT-STS:vm_state | building | OS-EXT-SRV-ATTR:instance_name | instance-0000004d | OS-EXT-SRV-ATTR:hypervisor_hostname | None | flavor | m1.small | id | 7363a018-4372-40ac-906b-ab804b20d08e | security_groups | [{u'name': u'default'}] | user_id | d920fc85ecd9426ebd9e3f8c7300f5d4 | name | centos-on-hyperv | adminPass | DufDUJtv887e | tenant_id | 670f5dd4070d44b6a8308277a236d1af | created | 2013-05-16T16:25:58Z | OS-DCF:diskConfig | MANUAL | metadata | {} | accessIPv4 | | accessIPv6 | | progress | 0 | OS-EXT-STS:power_state | 0 | OS-EXT-AZ:availability_zone | nova | config_drive | +-------------------------------------+--------------------------------------+ $ nova list +--------------------------------------+-----------------------+---------+---------------------+ | ID | Name | Status | Networks +--------------------------------------+-----------------------+---------+---------------------+ | 7363a018-4372-40ac-906b-ab804b20d08e | centos-on-hyperv | ACTIVE | public=172.x.y.z | +--------------------------------------+-----------------------+---------+---------------------+ $ nova resize centos-on-hyperv 4 $ nova list +--------------------------------------+-----------------------+---------+---------------------+ | ID | Name | Status | Networks +--------------------------------------+-----------------------+---------+---------------------+ | 7363a018-4372-40ac-906b-ab804b20d08e | centos-on-hyperv | RESIZE | public=172.24.4.228 | $ nova list +--------------------------------------+-----------------------+---------+---------------------+ | ID | Name | Status | Networks +--------------------------------------+-----------------------+---------+---------------------+ | 7363a018-4372-40ac-906b-ab804b20d08e | centos-on-hyperv | VERIFY_RESIZE | public=172.24.4.228 | $ nova resize-confirm centos-on-hyperv (...) RESP: [400] {'date': 'Thu, 16 May 2013 16:34:04 GMT', 'content-length': '74', 'content-type': 'application/json; charset=UTF-8', 'x-compute-request-id': 'req-2fbd4427-1b5f-4841-b512-7c90e5abfd10'} RESP BODY: {"badRequest": {"message": "Instance has not been resized.", "code": 400}} (...) BadRequest: Instance has not been resized. (HTTP 400) (Request-ID: req-2fbd4427-1b5f-4841-b512-7c90e5abfd10) ERROR: Instance has not been resized. (HTTP 400) (Request-ID: req-2fbd4427-1b5f-4841-b512-7c90e5abfd10) $ nova list +--------------------------------------+-----------------------+---------+---------------------+ | ID | Name | Status | Networks +--------------------------------------+-----------------------+---------+---------------------+ | 7363a018-4372-40ac-906b-ab804b20d08e | centos-on-hyperv | VERIFY_RESIZE | public=172.24.4.228 | >> It won't let me neither confirm nor revert it to the previous state, I'm >> forced to do a >> "nova reset-state" to force it into an error state, to, only then, be able >> to shut-it-down >> and let it go up again. >> But again: if I check it on the hypervisor, I can see that the instance has >> been resized in >> cpu, ram and disk. it's just that the "nova resize-confirm" just won't work >> and let the VM go back >> to ACTIVE status Any ideas? Thank you! _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp