Deployment fails if install_kvm=true and user_data blob is passed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Expired
|
Medium
|
Unassigned |
Bug Description
Issue started with 2.5 beta3 (beta 2 was OK).
When deploying from command line and you pass 1) install_kvm=true AND 2) user_data="$(cat ~/user-
Using either install_kvm=true OR user_data="$(cat your.yaml|base64)" by themselves works just fine, just the combination fails.
Note: user-data file can be extremely simple to recreate failure
Steps to recreate:
1) Create simple cloud-init user-data file
cat <<EOF|tee ~/user-data.yaml
#cloud-config
runcmd:
- touch /var/tmp/
EOF
2) Allocate machine:
maas admin machines allocate system_
3) Deploy machine with install_kvm and user_data args:
maas admin machine deploy <systemid> install_kvm=true user_data="$(cat ~/user-
Output of `dpkg -l "*maas*"|cat` and contents of /var/log/maas included in attachement
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Mike Pontillo (mpontillo) |
milestone: | none → 2.5.0rc1 |
Changed in maas: | |
milestone: | 2.5.0rc1 → 2.5.0rc2 |
Changed in maas: | |
milestone: | 2.5.0rc2 → 2.5.1 |
Changed in maas: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in maas: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in maas: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in maas: | |
milestone: | 2.5.4 → none |
Changed in maas: | |
status: | Confirmed → Triaged |
importance: | Undecided → Medium |
Attachment also includes cloud-init.log and cloud-init- output. log from a failed host.