[UBUNTU 20.04] Subiquity installer does not accept user-data generated after manual installation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
High
|
Skipper Bug Screeners | ||
subiquity (Ubuntu) |
Confirmed
|
Undecided
|
Canonical Foundations Team | ||
Focal |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I'm installing Ubuntu 20.04 with a nocloud-net installation source on a z/VM guest. I'm currently limited to seeing installation output only through webhook reporter, because I cannot access shell on the target system during installation.
After manual installation a user-data to repeat the process automatically is stored in /var/log/
- there is no "version" entry, so Subiquity does not accept it at all:
curtin start subiquity/
curtin finish subiquity/
- when I add version: 1, I get the following error:
curtin start subiquity/
curtin finish subiquity/
Failed validating 'type' in schema[
{'type': 'string'}
On instance['toggle']:
None
And when I change this too I get the related issues with netplan and storage configuration.
Kernel command line:
cio_ignore=
User-data:
#cloud-config
autoinstall:
apt:
geoip: true
preserve_
primary:
- arches: [amd64, i386]
uri: http://
- arches: [default]
uri: http://
identity: {hostname: m8330038, password: /wjUJRFEEW5PA.
realname: user, username: user}
keyboard: {layout: us, toggle: null, variant: ''}
locale: en_US
network:
ethernets:
encbdf0:
addresses: [172.18.76.38/15]
gateway4: 172.18.0.1
version: 2
proxy: http://
ssh:
allow-pw: true
authorized-
install-server: true
storage:
config:
- {device_id: 0.0.3695, blocksize: 4096, disk_layout: cdl, mode: quick, preserve: false,
type: dasd, id: dasd-dasda}
- {ptable: vtoc, serial: 0X3695, path: /dev/dasda, wipe: superblock-
preserve: false, name: '', grub_device: false, device_id: 0.0.3695, type: disk,
id: disk-dasda}
- {device: disk-dasda, size: 22153265152, wipe: superblock, flag: '', number: 1,
preserve: false, type: partition, id: partition-0}
- {fstype: ext4, volume: partition-0, preserve: false, type: format, id: format-0}
- {device: format-0, path: /, type: mount, id: mount-0}
tags: | added: architecture-s39064 bugnameltc-185920 severity-high targetmilestone-inin--- |
Changed in ubuntu: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
affects: | linux (Ubuntu) → subiquity (Ubuntu) |
Changed in subiquity (Ubuntu): | |
assignee: | Skipper Bug Screeners (skipper-screen-team) → Canonical Foundations Team (canonical-foundations) |
Changed in ubuntu-z-systems: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
importance: | Undecided → High |
tags: | added: rls-ff-incoming |
tags: |
added: targetmilestone-inin2004 removed: targetmilestone-inin--- |
Changed in ubuntu-z-systems: | |
status: | New → Confirmed |
tags: | added: id-5ed912b79ef6c42dd6647bba |
tags: | removed: rls-ff-incoming |
Changed in subiquity (Ubuntu Focal): | |
status: | New → Confirmed |
I think this is fixed in the latest released version of the snap, or maybe just in git. Will check status and report back (probably tomorrow).