MAAS

Non-Ubuntu images can't be deployed with cloud-init 24.1

Bug #2058619 reported by Björn Tillenius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
High
Alexsander de Souza

Bug Description

If you build a custom, non-Ubuntu, image using the packer-maas templates, including the latest version of cloud-init, the deployment of the image fails.

It seems that the networking is never being configured, so it can't reach the MAAS metadata service.

Björn Tillenius (bjornt)
Changed in maas:
importance: Undecided → High
tags: added: bug-council
Revision history for this message
Thorsten Merten (thorsten-merten) wrote :

Can you reproduce this and file a bug to cloud init including boot logs cloud init logs etc

Changed in maas:
assignee: nobody → Alexsander de Souza (alexsander-souza)
Revision history for this message
Björn Tillenius (bjornt) wrote :

It turned out that this was a bug in cloud-init, and only applied to their el-testing COPR repo. Red Hat applied a patch to cloud-init when packaging it for rhel, so for official rhel images this wasn't an issue.

Cloud-init now has applied the relevant patch, so the next cloud-init release should work.

https://github.com/canonical/cloud-init/issues/3781

Changed in maas:
status: New → Invalid
tags: removed: bug-council
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.