cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-10290) Config drive - only supported for secondary storage
Date Wed, 09 May 2018 11:16:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-10290:

rhtyd commented on issue #2614: WIP perform config drive creation on primary storage (CLOUDSTACK-10290)
   This is still in WIP, we are not in a state to test/merge by end of this week so I'll move
to In case this change we can consider this for before RC1 is cut.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Config drive - only supported for secondary storage
> ---------------------------------------------------
>                 Key: CLOUDSTACK-10290
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions:
>            Reporter: Rohit Yadav
>            Assignee: Daan Hoogland
>            Priority: Major
> Userdata disk looks like this:
>  <disk type='file' device='cdrom'>
>        <driver name='qemu' type='raw' cache='none'/>
>        <source file='/mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266/configdrive.iso'/>
>        <backingStore/>
>        <target dev='hdd' bus='ide'/>
>        <readonly/>
>        <alias name='ide0-1-1'/>
>        <address type='drive' controller='0' bus='1' target='0' unit='1'/>
>      </disk>
> Mount is:
> root# df /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  Filesystem                                                      
1K-blocks    Used Available Use% Mounted on
>  66391040 2973696  63417344  
5% /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
> issue: where to find a primary storage for a VM that is not yet deployed. The configdrive
is created before a storage is assigned. This order of execution must be reversed for this
to work.

This message was sent by Atlassian JIRA

View raw message