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

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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.

            Assignee:
            Unassigned
            Reporter:
            Parag Doke
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: