cannot use new stemcell after new cloudinit step / cdrom removal

[thelangley]

Describe the bug
Using latest CPI, upgrading from ubuntu jammy v1.999 to v1.1015
VM clones but the bosh agent never responds. The NICs end up with no IP address configured
Can revert to older stemcell and it works fine

To Reproduce
Steps to reproduce the behavior:

1. Deploy bosh using jammy v1.999, CPI 98.0.1, works nicely
2. Attempt to deploy bosh using jammy 1.1015 and CPI 98.0.1. bosh agent fails to reply. VM fails to configure required IP address

CPI Error Log
Unfortunately, it's the Bosh deploy itself that is erroring so I'm not sure how to share this

Expected behavior

1. Deploy bosh using jammy v1.999, CPI 98.0.1, works nicely
2. Deploy bosh using jammy v1.1015, CPI 98.0.1, works nicely

Release Version & Related Info (please complete the following information):

• CPI Version: 98.0.1
• BOSH Director Version: 282.1.2
• Stemcell Name & Version: v1.1015
• vCenter Version: 8.0.3
• NSX(T) Version (If using): 4.2.3.1

Additional context
cloudfoundry/bosh-linux-stemcell-builder#463 references both the CPI change and the Stemcell change. I think the stemcell has been released but the matching CPI has not

I think the code change to support the new non-CDROM cloudinit has been merged recently into CPI on master but a new release is required.

[thelangley]

or it's just the agent itself cloudfoundry/bosh-agent#392

[selzoc]

We've reverted the change to the stemcell builder in cloudfoundry/bosh-linux-stemcell-builder#466 and will cut a new stemcell to consume that change.

[selzoc]

https://github.com/cloudfoundry/bosh-linux-stemcell-builder/releases/tag/ubuntu-jammy%2Fv1.1016 has been released with a fix. Thanks for the report!