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

Debian 10.7 image always ends with "Failure to in post-provisioning for XXX"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • _unsorted
    • Jenkins 2.249.3
      Azure VM Agents 1.5.1

      We have successfully been using an debian 9 image for some time, but want to upgrade to 10.7
      we are basing our image onĀ 
      publisher: "Debian"
      offer: "debian-10"
      sku: "10"
      version: "latest"

      This image is using cloud-init for some tasks in favour of waagent (I think this might be the cause of our issues)
      So when the vm provissions, it al goes fine, it shows up in azure, but the part where jenkins connects to the vm and updates credentials for the user to use for ssh newer completes.

      and after some time jenkins gives up and deletes the vm.

      So by using delete lock on the vm in aure, I have been abel to capture a VM, and i have been able to verify that the jenkins user on the vm have not yet gotten his login/ssh password set. If i swithc back to the old debian 9.x image it all works fine again.
      So I could set the jenkins password in the packer image that we are creating, but it both would be a bad idea, and I think it would only solve the issue that jenkins cannot ssh, but all the init scripts will not be able to run anyway..
      is there some way one can increase debug output from the plugin?

            azure_devops Azure DevOps
            fvissing Frank Vissing
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: