Hi Ryan,
I'm more than happy to let maas supply the data, I'm only trying to override the default behaviour by adding to /etc/maas/preseeds/curtin_userdata to get around the nvme bug.
Here's the output:
root@maas1:~# maas admin node get-curtin-config node-4c4aecf2-e332-11e5-a740-00163e1ca9db Success. Machine-readable output follows: apt_mirrors: ubuntu_archive: http://archive.ubuntu.com//ubuntu ubuntu_security: http://archive.ubuntu.com//ubuntu apt_proxy: http://10.10.4.221:8000/ debconf_selections: maas: 'cloud-init cloud-init/datasources multiselect MAAS
cloud-init cloud-init/maas-metadata-url string http://10.10.4.221/MAAS/metadata/
cloud-init cloud-init/maas-metadata-credentials string oauth_token_key=<redacted>
install: log_file: /tmp/install.log post_files: - /tmp/install.log kernel: mapping: {} package: linux-generic late_commands: maas: - wget - --no-proxy - http://10.10.4.221/MAAS/metadata/latest/by-id/node-4c4aecf2-e332-11e5-a740-00163e1ca9db/ - --post-data - op=netboot_off - -O - /dev/null network: config: - id: eth0 mac_address <redacted> mtu: 1500 name: eth0 subnets: - address: 10.10.4.11/22 dns_nameservers: [] gateway: 10.10.4.1 type: static type: physical - id: eth1 mac_address: <redacted> mtu: 1500 name: eth1 subnets: - type: manual type: physical - bond_interfaces: - eth0 - eth1 id: bond0 mac_address: <redacted> mtu: 1500 name: bond0 params: bond-downdelay: 0 bond-lacp_rate: fast bond-miimon: 100 bond-mode: 802.3ad bond-updelay: 0 bond-xmit_hash_policy: layer2 subnets: - type: manual type: bond - address: 10.10.4.221 search: - <redacted> type: nameserver version: 1 network_commands: builtin: - curtin - net-meta - custom partitioning_commands: builtin: - curtin - block-meta - custom power_state: mode: reboot reporting: maas: consumer_key: <redacted> endpoint: http://10.10.4.221/MAAS/metadata/status/node-4c4aecf2-e332-11e5-a740-00163e1ca9db token_key: <redacted> token_secret: <redacted> type: webhook storage: config: - id: sdc model: Samsung SSD 840 name: sdc serial: <redacted> type: disk wipe: superblock - id: sda model: ST2000DM001-1CH1 name: sda serial: <redacted> type: disk wipe: superblock - id: sdb model: ST2000DM001-1CH1 name: sdb serial: <redacted> type: disk wipe: superblock - grub_device: true id: nvme0n1 name: nvme0n1 path: /dev/nvme0n1 ptable: msdos type: disk wipe: superblock - device: nvme0n1 id: nvme0n1-part1 name: nvme0n1-part1 number: 1 offset: 4194304B size: 128026935296B type: partition uuid: edf17540-d929-41cc-85de-c4df78802b8d wipe: superblock - fstype: ext4 id: nvme0n1-part1_format label: '' type: format uuid: ce3b35c2-48ee-4d6f-9b20-0ff9642b2961 volume: nvme0n1-part1 - device: nvme0n1-part1_format id: nvme0n1-part1_mount path: / type: mount version: 1
Hi Ryan,
I'm more than happy to let maas supply the data, I'm only trying to override the default behaviour by adding to /etc/maas/ preseeds/ curtin_ userdata to get around the nvme bug.
Here's the output:
root@maas1:~# maas admin node get-curtin-config node-4c4aecf2- e332-11e5- a740-00163e1ca9 db archive. ubuntu. com//ubuntu archive. ubuntu. com//ubuntu 10.10.4. 221:8000/ datasources multiselect MAAS
Success.
Machine-readable output follows:
apt_mirrors:
ubuntu_archive: http://
ubuntu_security: http://
apt_proxy: http://
debconf_selections:
maas: 'cloud-init cloud-init/
cloud-init cloud-init/ maas-metadata- url string http:// 10.10.4. 221/MAAS/ metadata/
cloud-init cloud-init/ maas-metadata- credentials string oauth_token_ key=<redacted>
install: 10.10.4. 221/MAAS/ metadata/ latest/ by-id/node- 4c4aecf2- e332-11e5- a740-00163e1ca9 db/ nameservers: [] downdelay: 0 lacp_rate: fast xmit_hash_ policy: layer2 commands: 10.10.4. 221/MAAS/ metadata/ status/ node-4c4aecf2- e332-11e5- a740-00163e1ca9 db d929-41cc- 85de-c4df78802b 8d part1_format 48ee-4d6f- 9b20-0ff9642b29 61 part1_format
log_file: /tmp/install.log
post_files:
- /tmp/install.log
kernel:
mapping: {}
package: linux-generic
late_commands:
maas:
- wget
- --no-proxy
- http://
- --post-data
- op=netboot_off
- -O
- /dev/null
network:
config:
- id: eth0
mac_address <redacted>
mtu: 1500
name: eth0
subnets:
- address: 10.10.4.11/22
dns_
gateway: 10.10.4.1
type: static
type: physical
- id: eth1
mac_address: <redacted>
mtu: 1500
name: eth1
subnets:
- type: manual
type: physical
- bond_interfaces:
- eth0
- eth1
id: bond0
mac_address: <redacted>
mtu: 1500
name: bond0
params:
bond-
bond-
bond-miimon: 100
bond-mode: 802.3ad
bond-updelay: 0
bond-
subnets:
- type: manual
type: bond
- address: 10.10.4.221
search:
- <redacted>
type: nameserver
version: 1
network_commands:
builtin:
- curtin
- net-meta
- custom
partitioning_
builtin:
- curtin
- block-meta
- custom
power_state:
mode: reboot
reporting:
maas:
consumer_key: <redacted>
endpoint: http://
token_key: <redacted>
token_secret: <redacted>
type: webhook
storage:
config:
- id: sdc
model: Samsung SSD 840
name: sdc
serial: <redacted>
type: disk
wipe: superblock
- id: sda
model: ST2000DM001-1CH1
name: sda
serial: <redacted>
type: disk
wipe: superblock
- id: sdb
model: ST2000DM001-1CH1
name: sdb
serial: <redacted>
type: disk
wipe: superblock
- grub_device: true
id: nvme0n1
name: nvme0n1
path: /dev/nvme0n1
ptable: msdos
type: disk
wipe: superblock
- device: nvme0n1
id: nvme0n1-part1
name: nvme0n1-part1
number: 1
offset: 4194304B
size: 128026935296B
type: partition
uuid: edf17540-
wipe: superblock
- fstype: ext4
id: nvme0n1-
label: ''
type: format
uuid: ce3b35c2-
volume: nvme0n1-part1
- device: nvme0n1-
id: nvme0n1-part1_mount
path: /
type: mount
version: 1