Sorry for the late reply, The quest actually is not related to the problem, it was something caught in the logs so I was interested if it can somehow cause problems.
Cloudstack is 4.22 + KVM + Advanced Networks + Security Groups. The issue we face is that creating new instances (Debian 13 + cloud-init) causes them to have no network connectivity at launch. Rebooting them fixes the problem. After some tests we figured out that it only happens when multiple instances are created. In the DHCP server we see the error "Wrong IP address" for those instances. The ips are provided statically at launch so they are definitely not the same. The same issue is also seen when launching multiple vms without providing IPs. Those are the findings so far. Best regards, Jordan On Thu, Apr 16, 2026 at 10:27 AM Wei ZHOU <[email protected]> wrote: > If users do not want to get a password from VR, they can remove > "set_passwords" from cloud-init config. > > > ps: password server uses 8080, while SSH public key and metadata use port > 80 (apache2 service in VR). > > Kind regards, > Wei > > On Thu, Apr 16, 2026 at 9:03 AM Wido den Hollander via users < > [email protected]> wrote: > >> >> >> Op 15-04-2026 om 09:09 schreef jordan j: >> > Hello everyone, >> > >> > Is there a way to disable the password setup for cloudstack >> > instances? >> > This is because I dont want to use a password but just a >> > certificate, also port 8080 is disabled in the ACL and the cloud-init >> > timing out makes the instance boot slower. >> > If it cannot be stopped can you at least reduce the timeout duration? >> > >> >> Just uncheck "password enabled" at the VM template. Then this won't >> happen. >> >> But even for a SSH pubkey the VM needs to connect to the VR on 8080, why >> would you block this? >> >> Wido >> >> > Regards, >> > Jordan >> > >> >>
