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

Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • None
    • vsphere-cloud plugin version 2.3
      build-flow plugin version 0.17
      Jenkins build 1.599

      [Java version / OS does not matter]

      Steps
      1) Deploy a Jenkins instance from the appropriate war, and get those 2 plugins installed.
      2) Configure a test vcenter, a vsphere cloud slave instance (in my case the configuration was: boot on demand, connect via ssh launcher, shut down when idle after 10 min of idle time).
      3) Tie a job to the slave and kick it off.

      I observe that the build simply sits in queue and never kicks off.

            Unassigned Unassigned
            paragdoke Parag Doke
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: