Public bug reported:
1. Create a volume "nova volume-create --display-name test_volume 1"
[root@controller51 nova(keystone_admin)]# nova volume-list
+--------------------------------------+-----------+-------------------------+------+-------------+---------------------------------------------------------------------------+
| ID | Status | Display Name |
Size | Volume Type | Attached to
|
+--------------------------------------+-----------+-------------------------+------+-------------+---------------------------------------------------------------------------+
| a740ca7b-6881-4e28-9fdb-eb0d80336757 | available | test_volume |
1 | None |
|
| 1f1c19c7-a5f9-4683-a1f6-e339f02e1410 | in-use | NFVO_system_disk2 |
30 | None | 6fa391f8-bd8b-483d-9286-3cebc9a93d55
|
| d868710e-30d4-4095-bd8f-fea9f16fe8ea | in-use | NFVO_data_software_disk |
30 | None |
a07abdd5-07a6-4b41-a285-9b825f7b5623;6fa391f8-bd8b-483d-9286-3cebc9a93d55 |
| b03a39ca-ebc1-4472-9a04-58014e67b37c | in-use | NFVO_system_disk1 |
30 | None | a07abdd5-07a6-4b41-a285-9b825f7b5623
|
+--------------------------------------+-----------+-------------------------+------+-------------+---------------------------------------------------------------------------+
2. use The following command will boot a new instance and attach a volume at
the same time：
[root@controller51 nova(keystone_admin)]# nova boot --flavor 1 --image
1736471c-3530-49f2-ad34-6ef7da285050 --block-device-mapping
vdb=a740ca7b-6881-4e28-9fdb-eb0d80336757:blank:1:1 --nic
net-id=31fce69e-16b9-4114-9fa9-589763e58fb0 test
+--------------------------------------+-----------------------------------------------------------------------------------+
| Property | Value
|
+--------------------------------------+-----------------------------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | -
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | -
|
| OS-EXT-SRV-ATTR:instance_name | instance-00000082
|
| OS-EXT-STS:power_state | 0
|
| OS-EXT-STS:task_state | scheduling
|
| OS-EXT-STS:vm_state | building
|
| OS-SRV-USG:launched_at | -
|
| OS-SRV-USG:terminated_at | -
|
| accessIPv4 |
|
| accessIPv6 |
|
| adminPass | sWTuKqzrpS32
|
| config_drive |
|
| created | 2015-03-02T11:34:29Z
|
| flavor | m1.tiny (1)
|
| hostId |
|
| id | 868cfd12-eb36-4140-b7b3-98cfcec627cd
|
| image |
VMB_X86_64_LX_2.6.32_64_REL_2014_12_26.img
(1736471c-3530-49f2-ad34-6ef7da285050) |
| key_name | -
|
| metadata | {}
|
| name | test
|
| os-extended-volumes:volumes_attached | [{"id":
"547aae0e-455e-4d18-9c3c-e86bdc6c62e7"}] |
| progress | 0
|
| security_groups | default
|
| serial_type | file
|
| status | BUILD
|
| tenant_id | df86efb4c5264f3c9bbe3df6717f8654
|
| updated | 2015-03-02T11:34:30Z
|
| user_id | 7d376e69fc5d4697a1edb2600815de3f
|
+--------------------------------------+-----------------------------------------------------------------------------------+
3、if the instance are scheduled the host1, but, if the host1 network service is
inactive, then will reschedule the other host,
before reschedule ,as for create instance command the parameter
delete-on-terminate is 1, so will run delete volume.
but, the issue is after reschedule another host, the volume is deleted ,the
instance cannot build success.
** 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/1427179
Title:
boot from volume instance failed,because when reschedule delete the
volume
Status in OpenStack Compute (Nova):
New
Bug description:
1. Create a volume "nova volume-create --display-name test_volume 1"
[root@controller51 nova(keystone_admin)]# nova volume-list
+--------------------------------------+-----------+-------------------------+------+-------------+---------------------------------------------------------------------------+
| ID | Status | Display Name
| Size | Volume Type | Attached to
|
+--------------------------------------+-----------+-------------------------+------+-------------+---------------------------------------------------------------------------+
| a740ca7b-6881-4e28-9fdb-eb0d80336757 | available | test_volume
| 1 | None |
|
| 1f1c19c7-a5f9-4683-a1f6-e339f02e1410 | in-use | NFVO_system_disk2
| 30 | None | 6fa391f8-bd8b-483d-9286-3cebc9a93d55
|
| d868710e-30d4-4095-bd8f-fea9f16fe8ea | in-use | NFVO_data_software_disk
| 30 | None |
a07abdd5-07a6-4b41-a285-9b825f7b5623;6fa391f8-bd8b-483d-9286-3cebc9a93d55 |
| b03a39ca-ebc1-4472-9a04-58014e67b37c | in-use | NFVO_system_disk1
| 30 | None | a07abdd5-07a6-4b41-a285-9b825f7b5623
|
+--------------------------------------+-----------+-------------------------+------+-------------+---------------------------------------------------------------------------+
2. use The following command will boot a new instance and attach a volume at
the same time：
[root@controller51 nova(keystone_admin)]# nova boot --flavor 1 --image
1736471c-3530-49f2-ad34-6ef7da285050 --block-device-mapping
vdb=a740ca7b-6881-4e28-9fdb-eb0d80336757:blank:1:1 --nic
net-id=31fce69e-16b9-4114-9fa9-589763e58fb0 test
+--------------------------------------+-----------------------------------------------------------------------------------+
| Property | Value
|
+--------------------------------------+-----------------------------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | -
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | -
|
| OS-EXT-SRV-ATTR:instance_name | instance-00000082
|
| OS-EXT-STS:power_state | 0
|
| OS-EXT-STS:task_state | scheduling
|
| OS-EXT-STS:vm_state | building
|
| OS-SRV-USG:launched_at | -
|
| OS-SRV-USG:terminated_at | -
|
| accessIPv4 |
|
| accessIPv6 |
|
| adminPass | sWTuKqzrpS32
|
| config_drive |
|
| created | 2015-03-02T11:34:29Z
|
| flavor | m1.tiny (1)
|
| hostId |
|
| id | 868cfd12-eb36-4140-b7b3-98cfcec627cd
|
| image |
VMB_X86_64_LX_2.6.32_64_REL_2014_12_26.img
(1736471c-3530-49f2-ad34-6ef7da285050) |
| key_name | -
|
| metadata | {}
|
| name | test
|
| os-extended-volumes:volumes_attached | [{"id":
"547aae0e-455e-4d18-9c3c-e86bdc6c62e7"}] |
| progress | 0
|
| security_groups | default
|
| serial_type | file
|
| status | BUILD
|
| tenant_id | df86efb4c5264f3c9bbe3df6717f8654
|
| updated | 2015-03-02T11:34:30Z
|
| user_id | 7d376e69fc5d4697a1edb2600815de3f
|
+--------------------------------------+-----------------------------------------------------------------------------------+
3、if the instance are scheduled the host1, but, if the host1 network service
is inactive, then will reschedule the other host,
before reschedule ,as for create instance command the parameter
delete-on-terminate is 1, so will run delete volume.
but, the issue is after reschedule another host, the volume is deleted
,the instance cannot build success.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1427179/+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
