Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-18077

Libvirt Agents plugin says hypervisor exceeds threshold

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Linux Fedora Core 18
      Jenkins 1.515
      Libvirt Slaves 1.8.1
      libvirt library 0.10.2.4
    • Similar Issues:

      Description

      Despite having my concurrent threshold set to "0" to disable this check, occasionally VMs refuse to launch even though the threshold should be disabled. The following error message appears.

      ERROR: Capacity threshold (0) reached at hypervisor "QEMU - 192.168.100.1", slave commissioning delayed.

        Attachments

          Activity

          Hide
          travispaul Travis Paul added a comment -

          This also occurs if the threshold is set to a number higher than the number of VMs not just 0. For example, I set the threshold to 32 with only 8 VMs and still saw the capacity error message.

          Show
          travispaul Travis Paul added a comment - This also occurs if the threshold is set to a number higher than the number of VMs not just 0. For example, I set the threshold to 32 with only 8 VMs and still saw the capacity error message.
          Hide
          mike_kingsbury Mike Kingsbury added a comment -

          Still present in 2019.  v1.8.5.  Even with an arbitrarily high number in the thousands. 

          Show
          mike_kingsbury Mike Kingsbury added a comment - Still present in 2019.  v1.8.5.  Even with an arbitrarily high number in the thousands. 

            People

            Assignee:
            bgermann Bastian Germann
            Reporter:
            jekeller Jacob Keller
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated: