MAAS enlisted Nodes are not commissioning, bubble a virsh login failed error
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:/
Architecture:
RC and CC on same machine
Testing Scenario 1:
Release: ubuntu 14.04 trusty tahr maas version : 1.8.2+bzr4041-
Testing Scenario 2:
Release: ubuntu 14.10 (Utopic Unicorn) with maas version : 1.7.0~beta8+
sudo apt-get update sudo apt-get upgrade
sudo apt-get install maas-regional-
sudo apt-get install maas-cluster-
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-
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-
cloud9@
abdullah@
maas@0-
maas@0-
successfully loged without password
maas@0-
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:
&
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@
INFO 2015-09-27 12:11:19,919 twisted /usr/lib/
Warning:
Failed to query node's BMC — Node could not be queried node-88f059ba-
Copy of bug
https:/
INFO 2015-09-27 12:11:19,935 twisted /usr/lib/
Copy of bug
https:/
Took actions against Issue
add member maas to libvirt
# grep ^libvirtd /etc/group
libvirtd:
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:/
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-
dpkg-reconfigure maas-cluster-
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
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: