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)
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 Server- MAAS:/var/ log$ udevadm info -q all -n vda pci0000: 00/0000: 00:06.0/ virtio3/ block/vda /devices/ pci0000: 00/0000: 00:06.0/ virtio3/ block/vda TABLE_TYPE= dos D=4807
NAME="vda" RO="0" RM="0" MODEL="" ROTA="1"
NAME="vdb" RO="0" RM="0" MODEL="" ROTA="1"
ubuntu@
P: /devices/
N: vda
E: DEVNAME=/dev/vda
E: DEVPATH=
E: DEVTYPE=disk
E: ID_PART_
E: MAJOR=253
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZE
ubuntu@ Server- MAAS:/var/ log$ udevadm info -q all -n vdb pci0000: 00/0000: 00:07.0/ virtio4/ block/vdb label/cidata /dev/disk/ by-label/ cidata /devices/ pci0000: 00/0000: 00:07.0/ virtio4/ block/vdb ENC=cidata filesystem Joliet Extension D=4930
P: /devices/
N: vdb
S: disk/by-
E: DEVLINKS=
E: DEVNAME=/dev/vdb
E: DEVPATH=
E: DEVTYPE=disk
E: ID_FS_LABEL=cidata
E: ID_FS_LABEL_
E: ID_FS_TYPE=iso9660
E: ID_FS_USAGE=
E: ID_FS_VERSION=
E: MAJOR=253
E: MINOR=16
E: SUBSYSTEM=block
E: USEC_INITIALIZE
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-334f05cd39 01'], u'name': [u'bootstrap. maas']} > in-addr. arpa
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.
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)
[ by-id/wwn- 0x3000000600000 001",
{
"BLOCK_SIZE": "4096",
"NAME": "sda",
"ID_PATH": "/dev/disk/
"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"
}
]