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

ExportXMLWordPrintable

      I am trying to set up a Jenkins with Windows on-demand slaves.

      The Windows EC2-Instances are started by the plugin, but the WinRM connection cannot be established. The logs are stuck in a "Waiting for WinRM to come up"-loop.

      But I can create a WinRM-connection to the instances manually using a python library. When I compare both (the connection attempt by the EC2-Plugin and the connection by the lython tool) I observe the following:

      • the POST-request to /wsman is answered with a 401 by the Windows instance
      • this seems to be the case because the Authorization header is completely missing in the request

      Is this a bug in the plugin or am I doing something wrong?

            Assignee:
            FABRIZIO MANFREDI
            Reporter:
            Christoph Niehoff
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: