MAAS enlisted Nodes are not commissioning, bubble a virsh login failed error

Asked by murtazasolangi

Getting same issue in two testing scenario with a latest series, I believe, I am missing something or doing something wrong, stuck since two weeks on this point, so need some help to make me correct & put me on a right direction

Following Guide Series: https://ideasnet.wordpress.com/2014/04/24/ubuntu-server-how-to-install-metal-as-a-server-maas-cloud-infrastructure-in-ubuntu-14-04lts-server-edition-part-2%E2%80%B3/

Architecture:

RC and CC on same machine

Testing Scenario 1:

Release: ubuntu 14.04 trusty tahr maas version : 1.8.2+bzr4041-0ubuntu1~trusty1

Testing Scenario 2:

Release: ubuntu 14.10 (Utopic Unicorn) with maas version : 1.7.0~beta8+bzr3272-0ubuntu1.2

sudo apt-get update sudo apt-get upgrade
sudo apt-get install maas-regional-controller
sudo apt-get install maas-cluster-controller
sudo apt-get install maas-dhcp maas-dns
sudo apt-get install qemu-kvm
sudo apt-get install libvirt-bin

sudo maas-region-admin createsuperuser

Cluster Interface managed with DHCP & DNS
0-maas-controller0: IP : 10.17.17.200 DHCP: 10.17.17.10 – 10.17.17.50
0-maas-controller00: IP : 10.17.17.220 DHCP: 10.17.17.225 – 10.17.17.250

Note: Testing was isolated so no option for DHCP conflict issue here.

$: sudo mkdir /home/maas
$: sudo chown maas:maas /home/maas
$: sudo chsh -s /bin/bash maas
$: sudo su - maas

SSH-Keygen created & added on GUI
Three keys generated and added]
maas@0-maas-controller0
cloud9@0-maas-controller0
abdullah@abdullah-pc [host]

maas@0-maas-controller0:$ ssh-copy-id -i ~/.ssh/id_rsa abdullah@192.168.1.100
maas@0-maas-controller0:$ ssh abdullah@192.168.1.100
successfully loged without password
maas@0-maas-controller0:$ virsh -c qemu+ssh://abdullah@192.168.1.100/system list --all

Output
4 0-maas-controller0 running
3 0-maas-controller00 shut off
    node001 shut off
    node002 shut off
    node01 shut off
    node02 shut off

Enlistment successful for nodes

Nodes got IP's from DHCP at a PXE boot, then shut off automatically, and successfully enlisted in GUI
node01
node02
All nodes with their MAC addresses are shown in
GUI → Network → Connected Network interface cards

Node Editing:
Architecture : amd64/generic
OS: Ubuntu
Release: Ubuntu 14.04 LTS “Trusty Tahr”
Power Type: Virsh (virtual systems)
Power address: [Tested both options]
qemu+ssh://abdullah@192.168.1.100/system
&
qemu:///system

Problem: Node Commissioning Failed

Error: Failed to power on node — Node could not be powered on: virsh failed with return code 1: Failed to login to virsh console.

cloud9@0-maas-controller00:~$ sudo tail -f /var/log/maas/maas-django.log
INFO 2015-09-27 12:11:19,919 twisted /usr/lib/python2.7/dist-packages/piston/handler.py:27: exceptions.UserWarning: Handler already registered for model BootResource, you may experience inconsistent results.

Warning:
Failed to query node's BMC — Node could not be queried node-88f059ba-6233-11e5-a7f7-5254002b966e (thick-light.local) virsh failed with return code 1: Failed to login to virsh console.

Copy of bug
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1171988

INFO 2015-09-27 12:11:19,935 twisted /usr/lib/python2.7/dist-packages/piston/handler.py:27: exceptions.UserWarning: Handler already registered for model BootSource, you may experience inconsistent results.

Copy of bug
https://bugs.launchpad.net/maas/+bug/1277658

Took actions against Issue

add member maas to libvirt
# grep ^libvirtd /etc/group
libvirtd:x:112:cloud9, maas
so no issue to user's permissions

Clock checking on nodes and MAAS controller
by verifying both UTC and Local time
Confused about this bug https://bugs.launchpad.net/maas/+bug/978127
do we need to change time parameters manually in /cloud.init file? Or any where else? or fixed in latest releases?

dpkg-reconfigure maas-regional-controller
dpkg-reconfigure maas-cluster-controller

tested with different VM hardware i,e SCSI, SATA, Virtio

verified all ssh-keysgen with all users and re-added on GUI

But the Issue is still same

Networking:

           Host machine: ifconfig
                     l0: 127.0.0.1
                     virb0: 192.168.122.1
                     virb1: 10.17.17.1
                     wlan0: 192.168.1.100
           0-maas-controller0: ifconfig
                    eth0: 10.17.17.2XX
                    l0: 127.0.0.1
                   virb0: 192.168.122.1

any help or clue will be highly appreciable.

Thanks in advance

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu maas Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.