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

Jclouds CloudStack plugin always uses static NAT

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • jclouds-plugin
    • None
    • Jenkins - 2.462.3
      Jclouds plugin - 2.35
      CloudStack - 4.19.1.3
      KVM - libvirt 8, qemu 1:6.2
      Basic Shared CloudStack guest network (DefaultSharedNetworkOfferingWithSGService network offering)

      I'm trying to connect Jenkins to CloudStack fleet, but CloudStack stops VMs shortly after starting them.

      After checking logs and the plugin code I found that plugin checks if it needs public IP and then tries to configure static NAT.

      The problem is that in all my tests the plugin always requests static NAT, not depending on my configuration, even when "Public IP" check box is not marked.

      This does not work for shared network. Originally it does not have public IPs at all, and then VM start fails because it can't get public IP. If I create public IP pool, then VM start fails on static NAT configuration as shared CloudStack network does not support static NAT.

      2024-11-26 16:19:20,653 INFO  [c.c.a.ApiServer] (qtp341748265-451:ctx-edd74b0f ctx-63c8f43f ctx-98da2aed) (logid:f8487eba) Unable to create static nat rule; StaticNat service is not supported in network with specified id

      I'd expect the plugin to check CloudStack API if it may use public IP and static NAT.
      Alternatively, it can just respect "Public IP" setting also for basic network type of CloudStack

            felfert Fritz Elfert
            askr Alex
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: