Uploaded image for project: 'CloudStack'
  1. CloudStack
  2. CLOUDSTACK-10290

Config drive - only supported for secondary storage

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 4.11.0.0
    • None
    • None
    • Security Level: Public (Anyone can view this level - this is the default.)
    • None

    Description

      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
      some-nfs-server.com:/nfs/secondary/ConfigDrive/i-2-24-VM  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.

      Attachments

        Activity

          People

            dahn Daan
            bhaisaab Rohit Yadav
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: