Bug #1604393 “MAAS is not listing the storage disks” : Bugs : MAAS

Revision history for this message

Praveen (panniger) wrote on 2016-07-19:

#1

Maas Commission Output file Edit (130.4 KiB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)

Revision history for this message

Praveen (panniger) wrote on 2016-07-19:

#2

Block Output file after Commission Edit (14.0 KiB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)

Revision history for this message

Praveen (panniger) wrote on 2016-07-19:

#3

Maas server version Edit (13.2 KiB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)

Revision history for this message

Andres Rodriguez (andreserl) wrote on 2016-07-19:

#4

Can you please provide the version of MAAS you are using, as well as what you are using for commissioning?

Changed in maas:
status:	New → Incomplete

Revision history for this message

Praveen (panniger) wrote on 2016-07-19:

#5

I am using the MAAS of the version 1.9.3+bzr4577-0ubuntu1 (trusty1)
And I am trying to commission a CISCO UCS Server.

Revision history for this message

Andres Rodriguez (andreserl) wrote on 2016-07-19:

#6

Can you please upgrade to MAAS 1.9.4 and retry ? What store are you using ?

Revision history for this message

Praveen (panniger) wrote on 2016-07-20:

#7

MAAS_Version.JPG Edit (29.8 KiB, image/jpeg)

Hi Andre,

I tried to update the maas-cert-server but it is saying that i am already running the latest version.

Thanks,
Praveen

Revision history for this message

Praveen (panniger) wrote on 2016-07-26:

#8

Hi Andre,

We have tried with the latest version. Please let us know if you have any work around to processed further.
Our cert run is blocked.

I really appreciate any help you provide.

Thanks,
Praveen

Revision history for this message

Virginie Dotta (vdotta) wrote on 2016-07-28:

#9

Similar bug on the same release. Any ideas ?

Revision history for this message

Praveen (panniger) wrote on 2016-08-01:

#10

We have not seen similar issue. Please let us know if you have any work around.

Thanks,
Praveen

Changed in maas:
status:	Incomplete → New

Revision history for this message

Andres Rodriguez (andreserl) wrote on 2016-08-01:

#11

Logs needed:

1. cloud-init.log and cloud-init-output.log from the commissioning environment (There's an option to enable SSH. You can use that to connect to the environment, wait till everything is done, and grab the logs).

2. On the same commissioning environment, grab the output of:

lsblk --exclude 1,2,7 -d -P -o NAME,RO,RM,MODEL,ROTA
udevadm info -q all -n <block-device-name>

3. On the same commissioning environment, cloud-init version (dpkg -l | grep cloud-init)

4. MAAS logs at the *exact* moment this particular machine is commissioning.

5. The commissioning output (see in the UI, the device block section. NOT lshw).

Changed in maas:
status:	New → Incomplete

Revision history for this message

Virginie Dotta (vdotta) wrote on 2016-08-01:

#12

Find logs below,

1. cloud-init.log and cloud-init-output.log - attached in the rar file

2.lsblk --exclude 1,2,7 -d -P -o NAME,RO,RM,MODEL,ROTA
udevadm info -q all -n <block-device-name>

ubuntu@Server-MAAS:/var/log$ lsblk --exclude 1,2,7 -d -P -o NAME,RO,RM,MODEL,ROTA
NAME="vda" RO="0" RM="0" MODEL="" ROTA="1"
NAME="vdb" RO="0" RM="0" MODEL="" ROTA="1"
ubuntu@Server-MAAS:/var/log$ udevadm info -q all -n vda
P: /devices/pci0000:00/0000:00:06.0/virtio3/block/vda
N: vda
E: DEVNAME=/dev/vda
E: DEVPATH=/devices/pci0000:00/0000:00:06.0/virtio3/block/vda
E: DEVTYPE=disk
E: ID_PART_TABLE_TYPE=dos
E: MAJOR=253
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=4807

ubuntu@Server-MAAS:/var/log$ udevadm info -q all -n vdb
P: /devices/pci0000:00/0000:00:07.0/virtio4/block/vdb
N: vdb
S: disk/by-label/cidata
E: DEVLINKS=/dev/disk/by-label/cidata
E: DEVNAME=/dev/vdb
E: DEVPATH=/devices/pci0000:00/0000:00:07.0/virtio4/block/vdb
E: DEVTYPE=disk
E: ID_FS_LABEL=cidata
E: ID_FS_LABEL_ENC=cidata
E: ID_FS_TYPE=iso9660
E: ID_FS_USAGE=filesystem
E: ID_FS_VERSION=Joliet Extension
E: MAJOR=253
E: MINOR=16
E: SUBSYSTEM=block
E: USEC_INITIALIZED=4930

3. dpkg -l | grep cloud-init

ubuntu@Server-MAAS:/var/log$ dpkg -l | grep cloud-init
ii cloud-init 0.7.5-0ubuntu1.19 all Init scripts for cloud instances

4. MaaS Logs

The one taken from the maas.log from the MaaS Server.

Aug 1 14:38:46 Server-MAAS maas.api: [INFO] Request from user ubuntu to acquire a node with constraints <QueryDict: {u'agent_name': [u'158f0820-6427-418d-85b8-334f05cd3901'], u'name': [u'bootstrap.maas']}>
Aug 1 14:38:46 Server-MAAS maas.node: [INFO] bootstrap: Status transition from READY to ALLOCATED
Aug 1 14:38:46 Server-MAAS maas.node: [INFO] bootstrap: allocated to user ubuntu
Aug 1 14:38:52 Server-MAAS maas.node: [INFO] bootstrap: Releasing node
Aug 1 14:38:52 Server-MAAS maas.node: [INFO] bootstrap: Status transition from ALLOCATED to RELEASING
Aug 1 14:38:52 Server-MAAS maas.node: [INFO] bootstrap: Status transition from RELEASING to READY
Aug 1 14:38:52 Server-MAAS maas.dns: [INFO] Generating new DNS zone file for maas
Aug 1 14:38:52 Server-MAAS maas.dns: [INFO] Generating new DNS zone file for 4.18.172.in-addr.arpa

The output of the command sudo ./deploy.sh -o juno -s opencontrail -t nonha IBM-TME -f none
is the Logs.rar attached

5. The commissioning output (see in the UI, the device block section. NOT lshw)

[
{
  "BLOCK_SIZE": "4096",
  "NAME": "sda",
  "ID_PATH": "/dev/disk/by-id/wwn-0x3000000600000001",
  "PATH": "/dev/sda",
  "ROTA": "1",
  "RM": "0",
  "MODEL": "VIRTUAL-DISK",
  "RO": "1",
  "SERIAL": "3000000600000001",
  "SIZE": "1468006400"
},
{
  "BLOCK_SIZE": "4096",
  "NAME": "vda",
  "PATH": "/dev/vda",
  "ROTA": "1",
  "RM": "0",
  "MODEL": "",
  "RO": "0",
  "SIZE": "128849018880"
}
]

Find logs below,

1. cloud-init.log and cloud-init-output.log - attached in the rar file

2.lsblk --exclude 1,2,7 -d -P -o NAME,RO,RM,MODEL,ROTA
udevadm info -q all -n <block-device-name>

ubuntu@Server-MAAS:/var/log$ lsblk --exclude 1,2,7 -d -P -o NAME,RO,RM,MODEL,ROTA 
NAME="vda" RO="0" RM="0" MODEL="" ROTA="1"
NAME="vdb" RO="0" RM="0" MODEL="" ROTA="1"
ubuntu@Server-MAAS:/var/log$ udevadm info -q all -n vda
P: /devices/pci0000:00/0000:00:06.0/virtio3/block/vda
N: vda
E: DEVNAME=/dev/vda
E: DEVPATH=/devices/pci0000:00/0000:00:06.0/virtio3/block/vda
E: DEVTYPE=disk
E: ID_PART_TABLE_TYPE=dos
E: MAJOR=253
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=4807

ubuntu@Server-MAAS:/var/log$ udevadm info -q all -n vdb
P: /devices/pci0000:00/0000:00:07.0/virtio4/block/vdb
N: vdb
S: disk/by-label/cidata
E: DEVLINKS=/dev/disk/by-label/cidata
E: DEVNAME=/dev/vdb
E: DEVPATH=/devices/pci0000:00/0000:00:07.0/virtio4/block/vdb
E: DEVTYPE=disk
E: ID_FS_LABEL=cidata
E: ID_FS_LABEL_ENC=cidata
E: ID_FS_TYPE=iso9660
E: ID_FS_USAGE=filesystem
E: ID_FS_VERSION=Joliet Extension
E: MAJOR=253
E: MINOR=16
E: SUBSYSTEM=block
E: USEC_INITIALIZED=4930

3. dpkg -l | grep cloud-init

ubuntu@Server-MAAS:/var/log$ dpkg -l | grep cloud-init
ii  cloud-init                            0.7.5-0ubuntu1.19                all          Init scripts for cloud instances

4. MaaS Logs

The one taken from the maas.log from the MaaS Server.

Aug  1 14:38:46 Server-MAAS maas.api: [INFO] Request from user ubuntu to acquire a node with constraints <QueryDict: {u'agent_name': [u'158f0820-6427-418d-85b8-334f05cd3901'], u'name': [u'bootstrap.maas']}>
Aug  1 14:38:46 Server-MAAS maas.node: [INFO] bootstrap: Status transition from READY to ALLOCATED
Aug  1 14:38:46 Server-MAAS maas.node: [INFO] bootstrap: allocated to user ubuntu
Aug  1 14:38:52 Server-MAAS maas.node: [INFO] bootstrap: Releasing node
Aug  1 14:38:52 Server-MAAS maas.node: [INFO] bootstrap: Status transition from ALLOCATED to RELEASING
Aug  1 14:38:52 Server-MAAS maas.node: [INFO] bootstrap: Status transition from RELEASING to READY
Aug  1 14:38:52 Server-MAAS maas.dns: [INFO] Generating new DNS zone file for maas
Aug  1 14:38:52 Server-MAAS maas.dns: [INFO] Generating new DNS zone file for 4.18.172.in-addr.arpa

The output of the command sudo ./deploy.sh -o juno -s opencontrail -t nonha IBM-TME -f none
is the Logs.rar attached

5. The commissioning output (see in the UI, the device block section. NOT lshw)

[
 {
  "BLOCK_SIZE": "4096", 
  "NAME": "sda", 
  "ID_PATH": "/dev/disk/by-id/wwn-0x3000000600000001", 
  "PATH": "/dev/sda", 
  "ROTA": "1", 
  "RM": "0", 
  "MODEL": "VIRTUAL-DISK", 
  "RO": "1", 
  "SERIAL": "3000000600000001", 
  "SIZE": "1468006400"
 }, 
 {
  "BLOCK_SIZE": "4096", 
  "NAME": "vda", 
  "PATH": "/dev/vda", 
  "ROTA": "1", 
  "RM": "0", 
  "MODEL": "", 
  "RO": "0", 
  "SIZE": "128849018880"
 }
]

Revision history for this message

Virginie Dotta (vdotta) wrote on 2016-08-01:

#13

Logs.rar Edit (32.1 KiB, application/rar)

Revision history for this message

sivarama prasad Ravipati (sivar-y-deactivatedaccount) wrote on 2016-08-01:

#14

Download full text (27.5 KiB)

Hi. I am Using MAAS 1.9.3 on Ubuntu 14.04[trusty]. I am using DELL servers. Power type is IPMI. Power driver as LAN_2_0[IPMI 2.0].

I followed http://www.ubuntu.com/download/cloud/install-openstack-with-autopilot. I want to deploy OpenStack using Autopilot on top of Ubuntu 14.04.

Ubuntu MAAS not recognizing Nodes storage devices. Without recognizing nodes it was moving to "Ready" state and the power state is "on".

And When I tried to deploy Nodes it was showing "The deploy action for 1 node failed with error: {"network": ["Node must be configured to use a network"]}"

cloud-init.log
==============

Aug 1 12:24:51 rich-oil [CLOUDINIT] helpers.py[DEBUG]: Running config-scripts-per-instance using lock (<FileLock using file '/var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_scripts_per_instance'>)
Aug 1 12:24:51 rich-oil [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_scripts_user - wb: [420] 20 bytes
Aug 1 12:24:51 rich-oil [CLOUDINIT] helpers.py[DEBUG]: Running config-scripts-user using lock (<FileLock using file '/var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_scripts_user'>)
Aug 1 12:24:51 rich-oil [CLOUDINIT] util.py[DEBUG]: Running command ['/var/lib/cloud/instance/scripts/user_data.sh'] with allowed return codes [0] (shell=False, capture=False)
Aug 1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_ssh_authkey_fingerprints - wb: [420] 20 bytes
Aug 1 12:26:31 rich-oil [CLOUDINIT] helpers.py[DEBUG]: Running config-ssh-authkey-fingerprints using lock (<FileLock using file '/var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_ssh_authkey_fingerprints'>)
Aug 1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cloudinit.mergers.m_list'] that have attributes ['Merger']
Aug 1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Found m_list with attributes ['Merger'] in ['cloudinit.mergers.m_list']
Aug 1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cloudinit.mergers.m_dict'] that have attributes ['Merger']
Aug 1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Found m_dict with attributes ['Merger'] in ['cloudinit.mergers.m_dict']
Aug 1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cloudinit.mergers.m_str'] that have attributes ['Merger']
Aug 1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Found m_str with attributes ['Merger'] in ['cloudinit.mergers.m_str']
Aug 1 12:26:31 rich-oil [CLOUDINIT] __init__.py[DEBUG]: Merging 'dict' into 'dict' using method '_handle_unknown' of 'LookupMerger: (3)'
Aug 1 12:26:31 rich-oil [CLOUDINIT] __init__.py[DEBUG]: Merging using located merger 'DictMerger: (method=no_replace,recurse_str=False,recurse_dict=True,recurse_array=False,allow_delete=False)' since it had method '_on_dict'
Aug 1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cloudinit.mergers.m_list'] that have attributes ['Merger']
Aug 1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Found m_lis...

Hi. I am Using MAAS 1.9.3 on Ubuntu 14.04[trusty].  I am using DELL servers. Power type is IPMI. Power driver as LAN_2_0[IPMI 2.0].

I followed http://www.ubuntu.com/download/cloud/install-openstack-with-autopilot. I want to deploy OpenStack using Autopilot on top of Ubuntu 14.04.

Ubuntu MAAS not recognizing Nodes storage devices. Without recognizing nodes it was moving to "Ready" state and the power state is "on".

And When I tried to deploy Nodes it was showing    "The deploy action for 1 node failed with error: {"network": ["Node must be configured to use a network"]}"

cloud-init.log
==============

Aug  1 12:24:51 rich-oil [CLOUDINIT] helpers.py[DEBUG]: Running config-scripts-per-instance using lock (<FileLock using file '/var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_scripts_per_instance'>)
Aug  1 12:24:51 rich-oil [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_scripts_user - wb: [420] 20 bytes
Aug  1 12:24:51 rich-oil [CLOUDINIT] helpers.py[DEBUG]: Running config-scripts-user using lock (<FileLock using file '/var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_scripts_user'>)
Aug  1 12:24:51 rich-oil [CLOUDINIT] util.py[DEBUG]: Running command ['/var/lib/cloud/instance/scripts/user_data.sh'] with allowed return codes [0] (shell=False, capture=False)
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_ssh_authkey_fingerprints - wb: [420] 20 bytes
Aug  1 12:26:31 rich-oil [CLOUDINIT] helpers.py[DEBUG]: Running config-ssh-authkey-fingerprints using lock (<FileLock using file '/var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_ssh_authkey_fingerprints'>)
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cloudinit.mergers.m_list'] that have attributes ['Merger']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Found m_list with attributes ['Merger'] in ['cloudinit.mergers.m_list']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cloudinit.mergers.m_dict'] that have attributes ['Merger']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Found m_dict with attributes ['Merger'] in ['cloudinit.mergers.m_dict']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cloudinit.mergers.m_str'] that have attributes ['Merger']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Found m_str with attributes ['Merger'] in ['cloudinit.mergers.m_str']
Aug  1 12:26:31 rich-oil [CLOUDINIT] __init__.py[DEBUG]: Merging 'dict' into 'dict' using method '_handle_unknown' of 'LookupMerger: (3)'
Aug  1 12:26:31 rich-oil [CLOUDINIT] __init__.py[DEBUG]: Merging using located merger 'DictMerger: (method=no_replace,recurse_str=False,recurse_dict=True,recurse_array=False,allow_delete=False)' since it had method '_on_dict'
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cloudinit.mergers.m_list'] that have attributes ['Merger']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Found m_list with attributes ['Merger'] in ['cloudinit.mergers.m_list']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cloudinit.mergers.m_dict'] that have attributes ['Merger']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Found m_dict with attributes ['Merger'] in ['cloudinit.mergers.m_dict']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cloudinit.mergers.m_str'] that have attributes ['Merger']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Found m_str with attributes ['Merger'] in ['cloudinit.mergers.m_str']
Aug  1 12:26:31 rich-oil [CLOUDINIT] __init__.py[DEBUG]: Merging 'dict' into 'dict' using method '_handle_unknown' of 'LookupMerger: (3)'
Aug  1 12:26:31 rich-oil [CLOUDINIT] __init__.py[DEBUG]: Merging using located merger 'DictMerger: (method=no_replace,recurse_str=False,recurse_dict=True,recurse_array=False,allow_delete=False)' since it had method '_on_dict'
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cloudinit.mergers.m_list'] that have attributes ['Merger']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Found m_list with attributes ['Merger'] in ['cloudinit.mergers.m_list']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cloudinit.mergers.m_dict'] that have attributes ['Merger']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Found m_dict with attributes ['Merger'] in ['cloudinit.mergers.m_dict']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cloudinit.mergers.m_str'] that have attributes ['Merger']
Aug  1 12:26:31 rich-oil [CLOUDINIT] importer.py[DEBUG]: Found m_str with attributes ['Merger'] in ['cloudinit.mergers.m_str']
Aug  1 12:26:31 rich-oil [CLOUDINIT] __init__.py[DEBUG]: Merging 'dict' into 'dict' using method '_handle_unknown' of 'LookupMerger: (3)'
Aug  1 12:26:31 rich-oil [CLOUDINIT] __init__.py[DEBUG]: Merging using located merger 'DictMerger: (method=no_replace,recurse_str=False,recurse_dict=True,recurse_array=False,allow_delete=False)' since it had method '_on_dict'
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Reading from /etc/ssh/sshd_config (quiet=False)
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Read 2539 bytes from /etc/ssh/sshd_config
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Reading from /home/ubuntu/.ssh/authorized_keys (quiet=False)
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Read 399 bytes from /home/ubuntu/.ssh/authorized_keys
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_keys_to_console - wb: [420] 20 bytes

Aug  1 12:26:31 rich-oil [CLOUDINIT] helpers.py[DEBUG]: Running config-keys-to-console using lock (<FileLock using file '/var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_keys_to_console'>)
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Running command ['/usr/lib/cloud-init/write-ssh-key-fingerprints', '', 'ssh-dss'] with allowed return codes [0] (shell=False, capture=True)
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_phone_home - wb: [420] 20 bytes
Aug  1 12:26:31 rich-oil [CLOUDINIT] helpers.py[DEBUG]: Running config-phone-home using lock (<FileLock using file '/var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_phone_home'>)
Aug  1 12:26:31 rich-oil [CLOUDINIT] cc_phone_home.py[DEBUG]: Skipping module named phone-home, no 'phone_home' configuration found
Aug  1 12:26:31 rich-oil [CLOUDINIT] helpers.py[DEBUG]: Running config-final-message using lock (<cloudinit.helpers.DummyLock object at 0x7f498e295790>)
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Reading from /proc/uptime (quiet=False)
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Read 14 bytes from /proc/uptime
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Cloud-init v. 0.7.5 finished at Mon, 01 Aug 2016 12:26:31 +0000. Datasource DataSourceMAAS [http://192.168.10.15/MAAS/metadata/].  Up 159.67 seconds
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instance/boot-finished - wb: [420] 52 bytes
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_power_state_change - wb: [420] 20 bytes
Aug  1 12:26:31 rich-oil [CLOUDINIT] helpers.py[DEBUG]: Running config-power-state-change using lock (<FileLock using file '/var/lib/cloud/instances/node-8d1bc364-57e0-11e6-bcc1-080027893615/sem/config_power_state_change'>)
Aug  1 12:26:31 rich-oil [CLOUDINIT] cc_power_state_change.py[DEBUG]: no power_state provided. doing nothing
Aug  1 12:26:31 rich-oil [CLOUDINIT] cloud-init[DEBUG]: Ran 11 modules with 0 failures
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Creating symbolic link from '/run/cloud-init/result.json' => '../../var/lib/cloud/data/result.json'
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Reading from /proc/uptime (quiet=False)
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: Read 14 bytes from /proc/uptime
Aug  1 12:26:31 rich-oil [CLOUDINIT] util.py[DEBUG]: cloud-init mode 'modules' took 100.126 seconds (100.13)

cloud-init-output.log
=====================
ubuntu@rich-oil:/var/log$ sudo tail -f cloud-init-output.log

Success
Success
Success
Success
Success
Success
Success
Success
Success
Cloud-init v. 0.7.5 finished at Mon, 01 Aug 2016 12:26:31 +0000. Datasource DataSourceMAAS [http://192.168.10.15/MAAS/metadata/].  Up 159.67 seconds

ubuntu@rich-oil:/var/log$ udevadm info -q all -n sdc
P: /devices/pci0000:00/0000:00:1c.0/0000:03:00.0/host4/port-4:0/end_device-4:0/target4:0:0/4:0:0:0/block/sdc
N: sdc
S: disk/by-id/ata-FUJITSU_MHZ2080BK_G2_K85CT9A25MJA
S: disk/by-id/wwn-0x500000e0441c3b38
S: disk/by-path/pci-0000:03:00.0-sas-0x1221000000000000-lun-0
E: DEVLINKS=/dev/disk/by-id/ata-FUJITSU_MHZ2080BK_G2_K85CT9A25MJA /dev/disk/by-id/wwn-0x500000e0441c3b38 /dev/disk/by-path/pci-0000:03:00.0-sas-0x1221000000000000-lun-0
E: DEVNAME=/dev/sdc
E: DEVPATH=/devices/pci0000:00/0000:00:1c.0/0000:03:00.0/host4/port-4:0/end_device-4:0/target4:0:0/4:0:0:0/block/sdc
E: DEVTYPE=disk
E: ID_ATA=1
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_FEATURE_SET_AAM=1
E: ID_ATA_FEATURE_SET_AAM_CURRENT_VALUE=254
E: ID_ATA_FEATURE_SET_AAM_ENABLED=1
E: ID_ATA_FEATURE_SET_AAM_VENDOR_RECOMMENDED_VALUE=254
E: ID_ATA_FEATURE_SET_APM=1
E: ID_ATA_FEATURE_SET_APM_CURRENT_VALUE=128
E: ID_ATA_FEATURE_SET_APM_ENABLED=1
E: ID_ATA_FEATURE_SET_HPA=1
E: ID_ATA_FEATURE_SET_HPA_ENABLED=0
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=80
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_BUS=ata
E: ID_MODEL=FUJITSU_MHZ2080BK_G2
E: ID_MODEL_ENC=FUJITSU\x20MHZ2080BK\x20G2\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_PART_TABLE_TYPE=dos
E: ID_PATH=pci-0000:03:00.0-sas-0x1221000000000000-lun-0
E: ID_PATH_TAG=pci-0000_03_00_0-sas-0x1221000000000000-lun-0
E: ID_REVISION=8A22
E: ID_SERIAL=FUJITSU_MHZ2080BK_G2_K85CT9A25MJA
E: ID_SERIAL_SHORT=K85CT9A25MJA
E: ID_TYPE=disk
E: ID_WWN=0x500000e0441c3b38
E: ID_WWN_WITH_EXTENSION=0x500000e0441c3b38
E: MAJOR=8
E: MINOR=32
E: SUBSYSTEM=block
E: USEC_INITIALIZED=781599

ubuntu@rich-oil:/var/log$ udevadm info -q all -n sdd
P: /devices/pci0000:00/0000:00:1c.0/0000:03:00.0/host4/port-4:1/end_device-4:1/target4:0:1/4:0:1:0/block/sdd
N: sdd
S: disk/by-id/ata-ST9500620NS_9XF04700
S: disk/by-id/wwn-0x5000c5002e19551b
S: disk/by-path/pci-0000:03:00.0-sas-0x1221000001000000-lun-0
E: DEVLINKS=/dev/disk/by-id/ata-ST9500620NS_9XF04700 /dev/disk/by-id/wwn-0x5000c5002e19551b /dev/disk/by-path/pci-0000:03:00.0-sas-0x1221000001000000-lun-0
E: DEVNAME=/dev/sdd
E: DEVPATH=/devices/pci0000:00/0000:00:1c.0/0000:03:00.0/host4/port-4:1/end_device-4:1/target4:0:1/4:0:1:0/block/sdd
E: DEVTYPE=disk
E: ID_ATA=1
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_FEATURE_SET_HPA=1
E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=98
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=98
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_ROTATION_RATE_RPM=7200
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_BUS=ata
E: ID_MODEL=ST9500620NS
E: ID_MODEL_ENC=ST9500620NS\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_PART_TABLE_TYPE=dos
E: ID_PATH=pci-0000:03:00.0-sas-0x1221000001000000-lun-0
E: ID_PATH_TAG=pci-0000_03_00_0-sas-0x1221000001000000-lun-0
E: ID_REVISION=AA02
E: ID_SERIAL=ST9500620NS_9XF04700
E: ID_SERIAL_SHORT=9XF04700
E: ID_TYPE=disk
E: ID_WWN=0x5000c5002e19551b
E: ID_WWN_WITH_EXTENSION=0x5000c5002e19551b
E: MAJOR=8
E: MINOR=48
E: SUBSYSTEM=block
E: USEC_INITIALIZED=339328

ubuntu@rich-oil:/var/log$ udevadm info -q all -n sda
P: /devices/pci0000:00/0000:00:1d.7/usb2/2-3/2-3:1.0/host2/target2:0:0/2:0:0:0/block/sda
N: sda
S: disk/by-id/usb-iDRAC_LCDRIVE_20080519-0:0
S: disk/by-path/pci-0000:00:1d.7-usb-0:3:1.0-scsi-0:0:0:0
E: DEVLINKS=/dev/disk/by-id/usb-iDRAC_LCDRIVE_20080519-0:0 /dev/disk/by-path/pci-0000:00:1d.7-usb-0:3:1.0-scsi-0:0:0:0
E: DEVNAME=/dev/sda
E: DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb2/2-3/2-3:1.0/host2/target2:0:0/2:0:0:0/block/sda
E: DEVTYPE=disk
E: ID_BUS=usb
E: ID_INSTANCE=0:0
E: ID_MODEL=LCDRIVE
E: ID_MODEL_ENC=LCDRIVE\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_MODEL_ID=0249
E: ID_PATH=pci-0000:00:1d.7-usb-0:3:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=pci-0000_00_1d_7-usb-0_3_1_0-scsi-0_0_0_0
E: ID_REVISION=0323
E: ID_SERIAL=iDRAC_LCDRIVE_20080519-0:0
E: ID_SERIAL_SHORT=20080519
E: ID_TYPE=disk
E: ID_USB_DRIVER=usb-storage
E: ID_USB_INTERFACES=:080650:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=iDRAC
E: ID_VENDOR_ENC=iDRAC\x20\x20\x20
E: ID_VENDOR_ID=0624
E: MAJOR=8
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=146414

ubuntu@rich-oil:/var/log$ udevadm info -q all -n sde
P: /devices/platform/host5/session1/target5:0:0/5:0:0:1/block/sde
N: sde
S: disk/by-id/scsi-33000000600000001
S: disk/by-id/wwn-0x3000000600000001
S: disk/by-label/cloudimg-rootfs
S: disk/by-path/ip-192.168.10.15:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-t-trusty-release-lun-1
S: disk/by-uuid/ec1f78e3-8766-40f6-a360-70f870ab8b02
E: DEVLINKS=/dev/disk/by-id/scsi-33000000600000001 /dev/disk/by-id/wwn-0x3000000600000001 /dev/disk/by-label/cloudimg-rootfs /dev/disk/by-path/ip-192.168.10.15:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-t-trusty-release-lun-1 /dev/disk/by-uuid/ec1f78e3-8766-40f6-a360-70f870ab8b02
E: DEVNAME=/dev/sde
E: DEVPATH=/devices/platform/host5/session1/target5:0:0/5:0:0:1/block/sde
E: DEVTYPE=disk
E: ID_BUS=scsi
E: ID_FS_LABEL=cloudimg-rootfs
E: ID_FS_LABEL_ENC=cloudimg-rootfs
E: ID_FS_TYPE=ext4
E: ID_FS_USAGE=filesystem
E: ID_FS_UUID=ec1f78e3-8766-40f6-a360-70f870ab8b02
E: ID_FS_UUID_ENC=ec1f78e3-8766-40f6-a360-70f870ab8b02
E: ID_FS_VERSION=1.0
E: ID_MODEL=VIRTUAL-DISK
E: ID_MODEL_ENC=VIRTUAL-DISK
E: ID_PATH=ip-192.168.10.15:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-t-trusty-release-lun-1
E: ID_PATH_TAG=ip-192_168_10_15_3260-iscsi-iqn_2004-05_com_ubuntu_maas_ephemeral-ubuntu-amd64-hwe-t-trusty-release-lun-1
E: ID_REVISION=0001
E: ID_SCSI=1
E: ID_SCSI_SERIAL=beaf61
E: ID_SERIAL=33000000600000001
E: ID_SERIAL_SHORT=3000000600000001
E: ID_TYPE=disk
E: ID_VENDOR=IET
E: ID_VENDOR_ENC=IET\x20\x20\x20\x20\x20
E: ID_WWN=0x3000000600000001
E: ID_WWN_WITH_EXTENSION=0x3000000600000001
E: MAJOR=8
E: MINOR=64
E: SUBSYSTEM=block
E: USEC_INITIALIZED=325668

ubuntu@rich-oil:/var/log$ ls /dev/sd*
/dev/sda  /dev/sdb  /dev/sdc  /dev/sdc1  /dev/sdc2  /dev/sdc5  /dev/sdd  /dev/sde
ubuntu@rich-oil:/var/log$ sudo fdisk -l

Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000bed9e

Device Boot      Start         End      Blocks   Id  System

Disk /dev/sdc: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000a8f82

Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048   122773503    61385728   83  Linux
/dev/sdc2       122775550   156301311    16762881    5  Extended
/dev/sdc5       122775552   156301311    16762880   82  Linux swap / Solaris

Disk /dev/sde: 1468 MB, 1468006400 bytes
46 heads, 61 sectors/track, 1021 cylinders, total 2867200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

ubuntu@rich-oil:/var/log$ dpkg -l | grep cloud-init
ii  cloud-init                          0.7.5-0ubuntu1.18                all          Init scripts for cloud instances
ii  cloud-initramfs-dyn-netconf         0.25ubuntu1.14.04.1              all          write a network interface file in /run for BOOTIF

maas.log
========

Aug  1 17:37:43 maas-admin maas.api: [INFO] rich-oil: Enlisted new node
Aug  1 17:37:43 maas-admin maas.dns: [INFO] Generating new DNS zone file for maas
Aug  1 17:37:43 maas-admin maas.dns: [INFO] Generating new DNS zone file for 10.168.192.in-addr.arpa
Aug  1 17:37:44 maas-admin maas.power: [INFO] rich-oil: Power state has changed from unknown to on.
Aug  1 17:38:28 maas-admin maas.lease_upload_service: [INFO] Uploading 2 DHCP leases to region controller.
Aug  1 17:42:58 maas-admin maas.power: [INFO] rich-oil: Power state has changed from on to off.
Aug  1 17:49:05 maas-admin maas.node: [INFO] rich-oil: Status transition from NEW to COMMISSIONING
Aug  1 17:49:05 maas-admin maas.power: [INFO] Changing power state (on) of node: rich-oil (node-8d1bc364-57e0-11e6-bcc1-080027893615)
Aug  1 17:49:05 maas-admin maas.node: [INFO] rich-oil: Commissioning started
Aug  1 17:49:07 maas-admin maas.power: [INFO] Changed power state (on) of node: rich-oil (node-8d1bc364-57e0-11e6-bcc1-080027893615)
Aug  1 17:53:29 maas-admin maas.lease_upload_service: [INFO] Uploading 3 DHCP leases to region controller.
Aug  1 17:54:46 maas-admin maas.node: [INFO] rich-oil: Status transition from COMMISSIONING to READY
Aug  1 17:55:06 maas-admin maas.node_query: [INFO] rich-oil: Power is on.
Aug  1 17:55:28 maas-admin maas.lease_upload_service: [INFO] Uploading 4 DHCP leases to region controller.
Aug  1 17:57:28 maas-admin maas.import-images: [INFO] Started importing boot images.
Aug  1 17:57:29 maas-admin maas.import-images: [INFO] Finished importing boot images, the region does not have any new images.
Aug  1 17:58:00 maas-admin maas.bootsources: [INFO] Updated boot sources cache.
Aug  1 17:58:00 maas-admin maas.bootresources: [INFO] Started importing of boot images from 1 source(s).
Aug  1 17:58:34 maas-admin maas.bootresources: [INFO] Importing images from source: http://maas.ubuntu.com/images/ephemeral-v2/releases/
Aug  1 17:59:11 maas-admin maas.bootresources: [INFO] Finished importing of boot images from 1 source(s).
Aug  1 17:59:11 maas-admin maas.import-images: [INFO] Started importing boot images.
Aug  1 17:59:11 maas-admin maas.import-images: [INFO] Finished importing boot images, the region does not have any new images.
Aug  1 18:17:28 maas-admin maas.import-images: [INFO] Started importing boot images.
Aug  1 18:17:29 maas-admin maas.import-images: [INFO] Finished importing boot images, the region does not have any new images.
Aug  1 18:18:20 maas-admin maas.node: [INFO] rich-oil: Status transition from READY to ALLOCATED
Aug  1 18:18:20 maas-admin maas.node: [INFO] rich-oil: allocated to user admin

regiond.log
===========
2016-08-01 18:21:30 [-] Error on request (132) node.action: {"network": ["Node must be configured to use a network"]}
        Traceback (most recent call last):
          File "/usr/lib/python2.7/threading.py", line 783, in __bootstrap
            self.__bootstrap_inner()
          File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
            self.run()
          File "/usr/lib/python2.7/threading.py", line 763, in run
            self.__target(*self.__args, **self.__kwargs)
          File "/usr/lib/python2.7/dist-packages/provisioningserver/utils/twisted.py", line 793, in worker
            return target()
        --- <exception caught here> ---
          File "/usr/lib/python2.7/dist-packages/twisted/python/threadpool.py", line 191, in _worker
            result = context.call(ctx, function, *args, **kwargs)
          File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 118, in callWithContext
            return self.currentContext().callWithContext(ctx, func, *args, **kw)
          File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 81, in callWithContext
            return func(*args,**kw)
          File "/usr/lib/python2.7/dist-packages/provisioningserver/utils/twisted.py", line 826, in callInContext
            return func(*args, **kwargs)
          File "/usr/lib/python2.7/dist-packages/maasserver/utils/orm.py", line 501, in call_within_transaction
            return func_outside_txn(*args, **kwargs)
          File "/usr/lib/python2.7/dist-packages/maasserver/utils/orm.py", line 328, in retrier
            return func(*args, **kwargs)
          File "/usr/lib/python2.7/dist-packages/django/db/transaction.py", line 339, in inner
            return func(*args, **kwargs)
          File "/usr/lib/python2.7/dist-packages/maasserver/websockets/handlers/node.py", line 1070, in action
            return action.execute(**extra_params)
          File "/usr/lib/python2.7/dist-packages/maasserver/node_action.py", line 327, in execute
            self.node.start(self.user)
          File "/usr/lib/python2.7/dist-packages/maasserver/utils/orm.py", line 485, in call_within_transaction
            return func_within_txn(*args, **kwargs)
          File "/usr/lib/python2.7/dist-packages/django/db/transaction.py", line 339, in inner
            return func(*args, **kwargs)
          File "/usr/lib/python2.7/dist-packages/maasserver/models/node.py", line 2538, in start
            return self._start(user, user_data)
          File "/usr/lib/python2.7/dist-packages/maasserver/utils/orm.py", line 485, in call_within_transaction
            return func_within_txn(*args, **kwargs)
          File "/usr/lib/python2.7/dist-packages/django/db/transaction.py", line 339, in inner
            return func(*args, **kwargs)
          File "/usr/lib/python2.7/dist-packages/maasserver/models/node.py", line 2585, in _start
            self._start_deployment()
          File "/usr/lib/python2.7/dist-packages/maasserver/models/node.py", line 848, in _start_deployment
            ["Node must be configured to use a network"]})
        django.core.exceptions.ValidationError: {u'network': [u'Node must be configured to use a network']}

2016-08-01 18:57:43+0530 [-] TFTP starting on 69
2016-08-01 18:57:43+0530 [-] Starting protocol <tftp.protocol.TFTP instance at 0x7fb9e20d0098>
2016-08-01 18:57:43+0530 [-] TFTP Listener started at 192.168.10.15:69
2016-08-01 18:57:43+0530 [-] TFTP starting on 69
2016-08-01 18:57:43+0530 [-] Starting protocol <tftp.protocol.TFTP instance at 0x7fb9e20d0488>
2016-08-01 18:57:43+0530 [-] TFTP Listener started at 127.0.0.1:69
2016-08-01 18:57:43+0530 [-] TFTP starting on 69
2016-08-01 18:57:43+0530 [-] Starting protocol <tftp.protocol.TFTP instance at 0x7fb9e20d06c8>
2016-08-01 18:57:43+0530 [-] TFTP Listener started at ::1:69
2016-08-01 18:57:43+0530 [Uninitialized] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at http://192.168.10.15/MAAS/rpc/).
2016-08-01 18:57:45+0530 [HTTPPageGetter,client] Region is not advertising RPC endpoints.
2016-08-01 18:57:47+0530 [HTTPPageGetter,client] Region is not advertising RPC endpoints.
2016-08-01 18:57:49+0530 [HTTPPageGetter,client] Region is not advertising RPC endpoints.
2016-08-01 18:57:51+0530 [Uninitialized] ClusterClient connection established (HOST:IPv4Address(TCP, '127.0.0.1', 46083) PEER:IPv4Address(TCP, u'127.0.0.1', 5253))
2016-08-01 18:57:51+0530 [Uninitialized] ClusterClient connection established (HOST:IPv4Address(TCP, '192.168.10.15', 55986) PEER:IPv4Address(TCP, u'192.168.10.15', 5250))
2016-08-01 18:57:51+0530 [Uninitialized] ClusterClient connection established (HOST:IPv4Address(TCP, '127.0.0.1', 56778) PEER:IPv4Address(TCP, u'127.0.0.1', 5251))
2016-08-01 18:57:53+0530 [ClusterClient,client] Event-loop 'maas-admin:pid=550' authenticated.
2016-08-01 18:57:53+0530 [ClusterClient,client] Event-loop 'maas-admin:pid=555' authenticated.
2016-08-01 18:57:53+0530 [Uninitialized] ClusterClient connection established (HOST:IPv4Address(TCP, '127.0.0.1', 48334) PEER:IPv4Address(TCP, u'127.0.0.1', 5252))
2016-08-01 18:57:53+0530 [ClusterClient,client] Event-loop 'maas-admin:pid=558' authenticated.
2016-08-01 18:57:53+0530 [ClusterClient,client] Event-loop 'maas-admin:pid=575' authenticated.
2016-08-01 18:57:53+0530 [ClusterClient,client] Cluster '26974af8-0ee9-4b0a-ae37-fd93009078ab' registered (via maas-admin:pid=555).
2016-08-01 18:57:53+0530 [ClusterClient,client] Cluster '26974af8-0ee9-4b0a-ae37-fd93009078ab' registered (via maas-admin:pid=575).
2016-08-01 18:57:53+0530 [ClusterClient,client] Cluster '26974af8-0ee9-4b0a-ae37-fd93009078ab' registered (via maas-admin:pid=550).
2016-08-01 18:57:54+0530 [ClusterClient,client] Cluster '26974af8-0ee9-4b0a-ae37-fd93009078ab' registered (via maas-admin:pid=558).
2016-08-01 18:58:01+0530 [HTTPPageGetter,client] Region is not advertising RPC endpoints.
2016-08-01 18:58:03+0530 [HTTPPageGetter,client] Region is not advertising RPC endpoints.
2016-08-01 18:58:05+0530 [HTTPPageGetter,client] Region is not advertising RPC endpoints.
2016-08-01 18:58:11+0530 [HTTPPageGetter,client] Region is not advertising RPC endpoints.
2016-08-01 18:58:13+0530 [HTTPPageGetter,client] Region is not advertising RPC endpoints.
2016-08-01 18:58:15+0530 [HTTPPageGetter,client] Region is not advertising RPC endpoints.
2016-08-01 18:58:17+0530 [HTTPPageGetter,client] Region is not advertising RPC endpoints.

Commissioning output from MAAS UI
==================================

ommissioning output from UI
===============================
/dev/sda
            - lshw:dev:
              8:0

/dev/cdrom
            - lshw:logicalname:
              /dev/sr0
            - lshw:dev:
              11:0
            - lshw:version:
              D150

/dev/sdb
            - lshw:dev:
              8:16
            - lshw:configuration:
              - lshw:setting:
                id: sectorsize
                value: 512

/dev/sde
            - lshw:logicalname:
              /media/root-ro
            - lshw:dev:
              8:64
            - lshw:version:
              1.0
            - lshw:serial:
              ec1f78e3-8766-40f6-a360-70f870ab8b02

/dev/sdc
                - lshw:dev:
                  8:32
                - lshw:version:
                  8A22
                - lshw:serial:
                  K85CT9A25MJA
                - lshw:size:
                  units: bytes
                  80026361856

/dev/sdc1
                  - lshw:dev:
                    8:33
                  - lshw:version:
                    1.0
                  - lshw:serial:
                    c9dc27f6-8ad3-47f0-8327-b2f11b75f169
                  - lshw:size:
                    units: bytes
                    62858985472
 /dev/sdc2
                  - lshw:dev:
                    8:34
                  - lshw:size:
                    units: bytes
                    17165190144
/dev/sdc5
                    - lshw:dev:
                      8:37
                    - lshw:capacity:
                      17165189120

/dev/sdd
                - lshw:dev:
                  8:48
                - lshw:version:
                  AA02
                - lshw:serial:
                  9XF04700
                - lshw:size:
                  units: bytes
                  500107862016

Revision history for this message

Virginie Dotta (vdotta) wrote on 2016-08-01:

#15

I forgot to say that I upgraded to MaaS 1.9.4 and same issue !!

Revision history for this message

sivarama prasad Ravipati (sivar-y-deactivatedaccount) wrote on 2016-08-02:

#16

Download full text (12.2 KiB)

1. cloud-init.log and cloud-init-output.log from the commissioning environment
ubuntu@inconsequential-dock:/var/log$ sudo tail -f cloud-init.log
sudo: unable to resolve host inconsequential-dock
Aug 1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: Cloud-init v. 0.7.5 finished at Mon, 01 Aug 2016 15:39:17 +0000. Datasource DataSourceMAAS [http://192.168.10.15/MAAS/metadata/]. Up 138.65 seconds
Aug 1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instance/boot-finished - wb: [420] 52 bytes
Aug 1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/node-5202c09a-57fc-11e6-9daf-080027893615/sem/config_power_state_change - wb: [420] 20 bytes
Aug 1 15:39:17 inconsequential-dock [CLOUDINIT] helpers.py[DEBUG]: Running config-power-state-change using lock (<FileLock using file '/var/lib/cloud/instances/node-5202c09a-57fc-11e6-9daf-080027893615/sem/config_power_state_change'>)
Aug 1 15:39:17 inconsequential-dock [CLOUDINIT] cc_power_state_change.py[DEBUG]: no power_state provided. doing nothing
Aug 1 15:39:17 inconsequential-dock [CLOUDINIT] cloud-init[DEBUG]: Ran 11 modules with 0 failures
Aug 1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: Creating symbolic link from '/run/cloud-init/result.json' => '../../var/lib/cloud/data/result.json'
Aug 1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: Reading from /proc/uptime (quiet=False)
Aug 1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: Read 15 bytes from /proc/uptime
Aug 1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: cloud-init mode 'modules' took 95.530 seconds (95.53)
^Cubuntu@inconsequential-dock:/var/log$ sudo tail -f cloud-init-output.log
sudo: unable to resolve host inconsequential-dock
Success
Success
Success
Success
Success
Success
Success
Success
Success
Cloud-init v. 0.7.5 finished at Mon, 01 Aug 2016 15:39:17 +0000. Datasource DataSourceMAAS [http://192.168.10.15/MAAS/metadata/]. Up 138.65 seconds

2. On the same commissioning environment, grab the output of:
lsblk --exclude 1,2,7 -d -P -o NAME,RO,RM,MODEL,ROTA
udevadm info -q all -n <block-device-name>

ubuntu@inconsequential-dock:/var/log$ lsblk --exclude 1,2,7 -d -P -o NAME,RO,RM,MODEL,ROTA
NAME="sda" RO="0" RM="0" MODEL="ST1000NM0033-9ZM" ROTA="1"
NAME="sdb" RO="1" RM="0" MODEL="VIRTUAL-DISK " ROTA="1"

ubuntu@inconsequential-dock:/var/log$ udevadm info -q all -n sda
P: /devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sda
N: sda
S: disk/by-id/ata-ST1000NM0033-9ZM173_Z1W2TF35
S: disk/by-id/wwn-0x5000c500794c8b10
E: DEVLINKS=/dev/disk/by-id/ata-ST1000NM0033-9ZM173_Z1W2TF35 /dev/disk/by-id/wwn-0x5000c500794c8b10
E: DEVNAME=/dev/sda
E: DEVPATH=/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sda
E: DEVTYPE=disk
E: ID_ATA=1
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_FEATURE_SET_HPA=1
E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=116
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=1...

1. cloud-init.log and cloud-init-output.log from the commissioning environment
ubuntu@inconsequential-dock:/var/log$ sudo tail -f cloud-init.log
sudo: unable to resolve host inconsequential-dock
Aug  1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: Cloud-init v. 0.7.5 finished at Mon, 01 Aug 2016 15:39:17 +0000. Datasource DataSourceMAAS [http://192.168.10.15/MAAS/metadata/].  Up 138.65 seconds
Aug  1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instance/boot-finished - wb: [420] 52 bytes
Aug  1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/node-5202c09a-57fc-11e6-9daf-080027893615/sem/config_power_state_change - wb: [420] 20 bytes
Aug  1 15:39:17 inconsequential-dock [CLOUDINIT] helpers.py[DEBUG]: Running config-power-state-change using lock (<FileLock using file '/var/lib/cloud/instances/node-5202c09a-57fc-11e6-9daf-080027893615/sem/config_power_state_change'>)
Aug  1 15:39:17 inconsequential-dock [CLOUDINIT] cc_power_state_change.py[DEBUG]: no power_state provided. doing nothing
Aug  1 15:39:17 inconsequential-dock [CLOUDINIT] cloud-init[DEBUG]: Ran 11 modules with 0 failures
Aug  1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: Creating symbolic link from '/run/cloud-init/result.json' => '../../var/lib/cloud/data/result.json'
Aug  1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: Reading from /proc/uptime (quiet=False)
Aug  1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: Read 15 bytes from /proc/uptime
Aug  1 15:39:17 inconsequential-dock [CLOUDINIT] util.py[DEBUG]: cloud-init mode 'modules' took 95.530 seconds (95.53)
^Cubuntu@inconsequential-dock:/var/log$ sudo tail -f cloud-init-output.log
sudo: unable to resolve host inconsequential-dock
Success
Success
Success
Success
Success
Success
Success
Success
Success
Cloud-init v. 0.7.5 finished at Mon, 01 Aug 2016 15:39:17 +0000. Datasource DataSourceMAAS [http://192.168.10.15/MAAS/metadata/].  Up 138.65 seconds

2. On the same commissioning environment, grab the output of:
lsblk --exclude 1,2,7 -d -P -o NAME,RO,RM,MODEL,ROTA
udevadm info -q all -n <block-device-name>

ubuntu@inconsequential-dock:/var/log$ lsblk --exclude 1,2,7 -d -P -o NAME,RO,RM,MODEL,ROTA
NAME="sda" RO="0" RM="0" MODEL="ST1000NM0033-9ZM" ROTA="1"
NAME="sdb" RO="1" RM="0" MODEL="VIRTUAL-DISK    " ROTA="1"

ubuntu@inconsequential-dock:/var/log$ udevadm info -q all -n sda
P: /devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sda
N: sda
S: disk/by-id/ata-ST1000NM0033-9ZM173_Z1W2TF35
S: disk/by-id/wwn-0x5000c500794c8b10
E: DEVLINKS=/dev/disk/by-id/ata-ST1000NM0033-9ZM173_Z1W2TF35 /dev/disk/by-id/wwn-0x5000c500794c8b10
E: DEVNAME=/dev/sda
E: DEVPATH=/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sda
E: DEVTYPE=disk
E: ID_ATA=1
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_FEATURE_SET_HPA=1
E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=116
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=116
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_ROTATION_RATE_RPM=7200
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_BUS=ata
E: ID_MODEL=ST1000NM0033-9ZM173
E: ID_MODEL_ENC=ST1000NM0033-9ZM173\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_PART_TABLE_TYPE=dos
E: ID_REVISION=SN04
E: ID_SERIAL=ST1000NM0033-9ZM173_Z1W2TF35
E: ID_SERIAL_SHORT=Z1W2TF35
E: ID_TYPE=disk
E: ID_WWN=0x5000c500794c8b10
E: ID_WWN_WITH_EXTENSION=0x5000c500794c8b10
E: MAJOR=8
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=924302

ubuntu@inconsequential-dock:/var/log$ udevadm info -q all -n sdb
P: /devices/platform/host6/session1/target6:0:0/6:0:0:1/block/sdb
N: sdb
S: disk/by-id/scsi-33000000600000001
S: disk/by-id/wwn-0x3000000600000001
S: disk/by-label/cloudimg-rootfs
S: disk/by-path/ip-192.168.10.15:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-t-trusty-release-lun-1
S: disk/by-uuid/ec1f78e3-8766-40f6-a360-70f870ab8b02
E: DEVLINKS=/dev/disk/by-id/scsi-33000000600000001 /dev/disk/by-id/wwn-0x3000000600000001 /dev/disk/by-label/cloudimg-rootfs /dev/disk/by-path/ip-192.168.10.15:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-t-trusty-release-lun-1 /dev/disk/by-uuid/ec1f78e3-8766-40f6-a360-70f870ab8b02
E: DEVNAME=/dev/sdb
E: DEVPATH=/devices/platform/host6/session1/target6:0:0/6:0:0:1/block/sdb
E: DEVTYPE=disk
E: ID_BUS=scsi
E: ID_FS_LABEL=cloudimg-rootfs
E: ID_FS_LABEL_ENC=cloudimg-rootfs
E: ID_FS_TYPE=ext4
E: ID_FS_USAGE=filesystem
E: ID_FS_UUID=ec1f78e3-8766-40f6-a360-70f870ab8b02
E: ID_FS_UUID_ENC=ec1f78e3-8766-40f6-a360-70f870ab8b02
E: ID_FS_VERSION=1.0
E: ID_MODEL=VIRTUAL-DISK
E: ID_MODEL_ENC=VIRTUAL-DISK
E: ID_PATH=ip-192.168.10.15:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-t-trusty-release-lun-1
E: ID_PATH_TAG=ip-192_168_10_15_3260-iscsi-iqn_2004-05_com_ubuntu_maas_ephemeral-ubuntu-amd64-hwe-t-trusty-release-lun-1
E: ID_REVISION=0001
E: ID_SCSI=1
E: ID_SCSI_SERIAL=beaf61
E: ID_SERIAL=33000000600000001
E: ID_SERIAL_SHORT=3000000600000001
E: ID_TYPE=disk
E: ID_VENDOR=IET
E: ID_VENDOR_ENC=IET\x20\x20\x20\x20\x20
E: ID_WWN=0x3000000600000001
E: ID_WWN_WITH_EXTENSION=0x3000000600000001
E: MAJOR=8
E: MINOR=16
E: SUBSYSTEM=block
E: USEC_INITIALIZED=649468

3. On the same commissioning environment, cloud-init version (dpkg -l | grep cloud-init)

ubuntu@inconsequential-dock:/var/log$ dpkg -l | grep cloud-init
ii  cloud-init                          0.7.5-0ubuntu1.18                all          Init scripts for cloud instances
ii  cloud-initramfs-dyn-netconf         0.25ubuntu1.14.04.1              all          write a network interface file in /run for BOOTIF

4. MAAS logs at the *exact* moment this particular machine is commissioning.

Maas.log
=========

Aug  1 20:56:30 maas-admin maas.api: [INFO] inconsequential-dock: Enlisted new node
Aug  1 20:56:30 maas-admin maas.dns: [INFO] Generating new DNS zone file for maas
Aug  1 20:56:30 maas-admin maas.dns: [INFO] Generating new DNS zone file for 10.168.192.in-addr.arpa
Aug  1 20:56:43 maas-admin maas.lease_upload_service: [INFO] Uploading 3 DHCP leases to region controller.
Aug  1 20:56:43 maas-admin maas.power: [INFO] inconsequential-dock: Power state has changed from unknown to on.
Aug  1 20:57:43 maas-admin maas.import-images: [INFO] Started importing boot images.
Aug  1 20:57:43 maas-admin maas.import-images: [INFO] Finished importing boot images, the region does not have any new images.
Aug  1 20:57:51 maas-admin maas.bootsources: [INFO] Updated boot sources cache.
Aug  1 20:57:51 maas-admin maas.bootresources: [INFO] Started importing of boot images from 1 source(s).
Aug  1 20:57:55 maas-admin maas.bootresources: [INFO] Importing images from source: http://maas.ubuntu.com/images/ephemeral-v2/releases/
Aug  1 20:58:00 maas-admin maas.bootresources: [INFO] Finished importing of boot images from 1 source(s).
Aug  1 20:58:00 maas-admin maas.import-images: [INFO] Started importing boot images.
Aug  1 20:58:00 maas-admin maas.import-images: [INFO] Finished importing boot images, the region does not have any new images.
Aug  1 21:01:58 maas-admin maas.power: [INFO] inconsequential-dock: Power state has changed from on to off.
Aug  1 21:03:04 maas-admin maas.node: [INFO] inconsequential-dock: Status transition from NEW to COMMISSIONING
Aug  1 21:03:04 maas-admin maas.power: [INFO] Changing power state (on) of node: inconsequential-dock (node-5202c09a-57fc-11e6-9daf-080027893615)
Aug  1 21:03:04 maas-admin maas.node: [INFO] inconsequential-dock: Commissioning started
Aug  1 21:03:06 maas-admin maas.power: [INFO] Changed power state (on) of node: inconsequential-dock (node-5202c09a-57fc-11e6-9daf-080027893615)
Aug  1 21:05:43 maas-admin maas.lease_upload_service: [INFO] Uploading 4 DHCP leases to region controller.
Aug  1 21:07:33 maas-admin maas.node: [INFO] inconsequential-dock: Status transition from COMMISSIONING to READY

Clusterd.log
=============

2016-08-02 11:22:35+0530 [-] Log opened.
2016-08-02 11:22:35+0530 [-] twistd 13.2.0 (/usr/bin/python 2.7.6) starting up.
2016-08-02 11:22:35+0530 [-] reactor class: twisted.internet.epollreactor.EPollReactor.
2016-08-02 11:22:35+0530 [-] Site starting on 5248
2016-08-02 11:22:35+0530 [-] set uid/gid 107/114
2016-08-02 11:22:35+0530 [-] TFTP starting on 69
2016-08-02 11:22:35+0530 [-] Starting protocol <tftp.protocol.TFTP instance at 0x7f334eed0320>
2016-08-02 11:22:35+0530 [-] TFTP Listener started at 192.168.10.15:69
2016-08-02 11:22:35+0530 [-] TFTP starting on 69
2016-08-02 11:22:35+0530 [-] Starting protocol <tftp.protocol.TFTP instance at 0x7f334eed06c8>
2016-08-02 11:22:35+0530 [-] TFTP Listener started at 127.0.0.1:69
2016-08-02 11:22:35+0530 [-] TFTP starting on 69
2016-08-02 11:22:35+0530 [-] Starting protocol <tftp.protocol.TFTP instance at 0x7f334eed0908>
2016-08-02 11:22:35+0530 [-] TFTP Listener started at ::1:69
2016-08-02 11:22:35+0530 [Uninitialized] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at http://192.168.10.15/MAAS/rpc/).
2016-08-02 11:22:37+0530 [HTTPPageGetter,client] Region is not advertising RPC endpoints.
2016-08-02 11:22:39+0530 [HTTPPageGetter,client] Region is not advertising RPC endpoints.
2016-08-02 11:22:41+0530 [Uninitialized] ClusterClient connection established (HOST:IPv4Address(TCP, '127.0.0.1', 52281) PEER:IPv4Address(TCP, u'127.0.0.1', 5251))
2016-08-02 11:22:41+0530 [ClusterClient,client] Event-loop 'maas-admin:pid=534' authenticated.
2016-08-02 11:22:41+0530 [Uninitialized] ClusterClient connection established (HOST:IPv4Address(TCP, '127.0.0.1', 42374) PEER:IPv4Address(TCP, u'127.0.0.1', 5253))
2016-08-02 11:22:41+0530 [ClusterClient,client] Event-loop 'maas-admin:pid=774' authenticated.
2016-08-02 11:22:41+0530 [Uninitialized] ClusterClient connection established (HOST:IPv4Address(TCP, '127.0.0.1', 54320) PEER:IPv4Address(TCP, u'127.0.0.1', 5252))
2016-08-02 11:22:41+0530 [ClusterClient,client] Event-loop 'maas-admin:pid=718' authenticated.
2016-08-02 11:22:41+0530 [Uninitialized] ClusterClient connection established (HOST:IPv4Address(TCP, '192.168.10.15', 40727) PEER:IPv4Address(TCP, u'192.168.10.15', 5250))
2016-08-02 11:22:41+0530 [ClusterClient,client] Event-loop 'maas-admin:pid=604' authenticated.
2016-08-02 11:22:42+0530 [ClusterClient,client] Cluster '26974af8-0ee9-4b0a-ae37-fd93009078ab' registered (via maas-admin:pid=534).
2016-08-02 11:22:42+0530 [ClusterClient,client] Cluster '26974af8-0ee9-4b0a-ae37-fd93009078ab' registered (via maas-admin:pid=774).
2016-08-02 11:22:42+0530 [ClusterClient,client] Cluster '26974af8-0ee9-4b0a-ae37-fd93009078ab' registered (via maas-admin:pid=718).
2016-08-02 11:22:42+0530 [ClusterClient,client] Cluster '26974af8-0ee9-4b0a-ae37-fd93009078ab' registered (via maas-admin:pid=604).

5. The commissioning output (see in the UI, the device block section. NOT lshw).

Commissioning information from UI
==================================

/dev/sda
            - lshw:dev:
              8:0
            - lshw:version:
              SN04
            - lshw:serial:
              Z1W2TF35
            - lshw:size:
              units: bytes
              1000204886016

/dev/sda1
              - lshw:dev:
                8:1
              - lshw:version:
                1.0
              - lshw:serial:
                9229b94c-04cf-4b9d-86e2-da390fb87eff
              - lshw:size:
                units: bytes
                974442725376
/dev/sda2
              - lshw:dev:
                8:2
              - lshw:size:
                units: bytes
                25759319040
              - lshw:capacity:
                25759319040

/dev/sda5
                - lshw:dev:
                  8:5
                - lshw:capacity:
                  25759318016

/dev/sdb
            - lshw:logicalname:
              /media/root-ro
            - lshw:dev:
              8:16
            - lshw:version:
              1.0
            - lshw:serial:
              ec1f78e3-8766-40f6-a360-70f870ab8b02
            - lshw:size:
              units: bytes
              1468006400

Revision history for this message

Virginie Dotta (vdotta) wrote on 2016-08-05:

#17

Hi there,

I managed to list nodes and see all disks.

To make this possible,
1/ first, install the MaaS Server
2/ Boot a node you want to enlist, using an ubuntu ISO
3/ Choose to connect it to an existing MaaS Server. The node will shutdown
4/ Go to the MaaS Server into the Nodes tab and click on the Add Hardware button on the top right corner. Choose Machine
5/ Fill in all information regarding your node. When you will click on the Save button, the node will automatically boot and commission itself
6/ Just wait some minutes, the node will turns off and will be set to Ready in your MaaS GUI. You will see also disk information

:)

Revision history for this message

Andres Rodriguez (andreserl) wrote on 2016-09-26:

#18

We investigated a similar issue in a different bug report and we found out that this was a problem when using the trusty kernel rather than the xenial kernel. In order to verify this, please do the following:

1. Change from images from 'releases' to 'daily' (Under the Settings Page, Boot Images section).
2. Use hwe-x Kernel for commissioning instead. (Under the Settings page 'Commissioning' section).
3. Re-attempt commissioning.

In the meantime, I'll mark this bug as 'Incomplete'. If you believe this bug is still present, please mark it again as 'New'.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-11-26:

#19

[Expired for MAAS trunk because there has been no activity for 60 days.]

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-11-26:

#20

[Expired for MAAS 1.9 because there has been no activity for 60 days.]

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-11-26:

#21

[Expired for MAAS 2.0 because there has been no activity for 60 days.]

	Status	Importance	Assigned to
MAAS	Expired	Undecided	Unassigned
1.9	Fix Released	Undecided	Unassigned
2.0	Expired	Undecided	Unassigned

MAAS

MAAS is not listing the storage disks

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches