Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-23211

Manually created VMs that use volumes with any type different from file can't be seen on the compute resource

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • NEW
    • Release Notes
    • 900
    • Hide
      .Libvirt VM details with any volume type can be accessed in the web UI

      Previously, when you manually created a virtual machine with a volume type other than `file` in Libvirt and then attempted to access the details of the virtual machine in the web UI, Satellite produced an ambiguous error.
      The loading of volumes in the Libvirt compute resource has been fixed.
      As a result, you can access details of your virtual machines with volumes of any type in the web UI.
      Show
      .Libvirt VM details with any volume type can be accessed in the web UI Previously, when you manually created a virtual machine with a volume type other than `file` in Libvirt and then attempted to access the details of the virtual machine in the web UI, Satellite produced an ambiguous error. The loading of volumes in the Libvirt compute resource has been fixed. As a result, you can access details of your virtual machines with volumes of any type in the web UI.
    • Bug Fix
    • Done
    • Rocket
    • Moderate
    • No

      Description of problem:

      When a libvirt server has VMs with other types of storage domains (block/raw, iSCSI, LVM but NOT file), when the user goes to Infrastructure -> Compute Resource -> <libvirt compute resource> -> <click over a VM>

      ~~~
      getting " something went wrong undefined method `allocation' for nil:NilClass "
      ~~~

      This issue is described here: https://github.com/fog/fog-libvirt/pull/105

      However, that PR was never merged and ended being closed.

      The patch proposed by such PR works and resolves the issue (no extended tests executed)

      Version-Release number of selected component (if applicable):
      Happens since 6.10 until now

      How reproducible:

      Always, when
      Steps to Reproduce:
      1. Create a VM with a volume of type different from file
      2. Try going into the compute resource and see the properties of such VM

      Actual results:

      Error getting " something went wrong undefined method `allocation' for nil:NilClass "

      Expected results:

      Open the VM properties

      Additional info:

        1.
        		 [QE] Manually created VMs that use volumes with any type different from file can't be seen on the compute resource Sub-task Closed Undefined Gaurav Talreja

            gtalreja@redhat.com Gaurav Talreja
            rhn-support-jpasqual Joniel Pasqualetto
            Gaurav Talreja Gaurav Talreja
            Lena Ansorgová Lena Ansorgová
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: