Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
Sender Email:
-
HD-Node:Zurich
Description
Dear Fiware Lab support center,
I'm tech lead for team tybo in Accelerator SpeedUp Europe.
We're using Node Zurich, tenant id 00000000000000000000000000012003.
I created a volume some time ago and attached it to one instance (id
8e151775-c92f-4929-b059-d9885c8b67c6). I just found out, that a volume
may only be attached to one instance (I first thought, I can attach it
to all instances). So I wanted to detach this volume from the instance,
delete it, create two volumes and attach those to our two instances.
I unmounted the volume on the instance and went into the web interface
(https://cloud.lab.fiware.org/#nova/volumes/). There I clicked the
checkbox before the volume's name -> actions -> edit attachments -> red
button "detach volume" -> detach volume and I get the follwing error:
{"itemNotFound": {"message": "The resource could not be found.", "code":
404}}
When I click the volume's name, column "Attachments" says "Not
attached". But:
root@c-3po:/media# fdisk -l
Disk /dev/vda: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders, total 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e9d5e
Device Boot Start End Blocks Id System
/dev/vda1 * 2048 41929649 20963801 83 Linux
Disk /dev/vdb: 107.4 GB, 107374182400 bytes
13 heads, 44 sectors/track, 366634 cylinders, total 209715200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xbee9e70e
Device Boot Start End Blocks Id System
/dev/vdb1 2048 209715199 104856576 83 Linux
root@c-3po:/media#
How can I detach this volume and create new ones?
Yours
Raul Pinto
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Raul Pinto <pinto@tybo.rocks>]
Activity
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
11h 21m | 1 | Zurich Node Helpdesk | 25/Jun/15 11:07 AM | |||||
|
5s | 1 | Zurich Node Helpdesk | 25/Jun/15 11:07 AM | |||||
|
69d 3h 33m | 1 | Zurich Node Helpdesk | 02/Sep/15 2:41 PM |
Fix Version/s | 2021 [ 12600 ] |
Summary | FIWARE.Request.Lab.FI-Lab Assistance: Can't detach volume. | FIWARE.Request.Lab.Zurich.FI-Lab Assistance: Can't detach volume. |
HD-Node | Zurich [ 10926 ] |
Summary | [Fiware-lab-help] FI-Lab Assistance: Can't detach volume | FIWARE.Request.Lab.FI-Lab Assistance: Can't detach volume. |
Sender Email | pinto@tybo.rocks |
Resolution | Done [ 10000 ] | |
Status | Answered [ 10104 ] | Closed [ 6 ] |
Status | In Progress [ 3 ] | Answered [ 10104 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Component/s | FIWARE-LAB-HELP [ 10279 ] |
Field | Original Value | New Value |
---|---|---|
Assignee | Zurich Node Helpdesk [ zhaw node helpdesk ] |
Hi Raul,
We will follow up via email - we have not seen this issue before. We see
that the volume you have created is stuck in a 'detaching' status.
root@node-1:~# date
Thu Jun 25 11:06:34 CEST 2015
root@node-1:~# cinder show 436412a6-ca56-4703-ad29-bd28608cf6d7
-------------------------------
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+root@node-1:~#