MAAS node Power Error

Bug #1607736 reported by sivarama prasad Ravipati
8
This bug affects 2 people
Affects Status Importance Assigned to Milestone
maas-deployer
New
Undecided
Unassigned

Bug Description

Hi. I am Using MAAS 1.9.3 on Ubuntu 14.04[trusty]. One of my MAAS client node Often facing power error while enlisting. I used DELL PowerEdge R610. Power type is IPMI. Power driver as LAN_2_0[IPMI 2.0]. Client node PXE booted under MAAS to enlist itself in MAAS UI. But it was giving Power Error.

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.

->From MAAS UI [From enlisted node]
  =================================
List Of Events
---------------
Failed to query node's BMC - Power state could not be queried: 192.168.2.162: connection timeout Wed, 27 Jul. 2016 19:00:00

->Contents of /var/log/maas/*
  ===========================
maas.log
---------

Jul 27 18:59:38 maas-node1 maas.api: [INFO] outstanding-crown: Enlisted new node
Jul 27 18:59:38 maas-node1 maas.dns: [INFO] Generating new DNS zone file for maas
Jul 27 18:59:38 maas-node1 maas.dns: [INFO] Generating new DNS zone file for 10.168.192.in-addr.arpa
Jul 27 19:00:00 maas-node1 maas.power: [ERROR] Power state could not be queried: 192.168.2.162: connection timeout
Jul 27 18:59:45 maas-node1 maas.power: [ERROR] Power state could not be queried: 192.168.2.162: connection timeout
Jul 27 18:59:45 maas-node1 maas.power: [ERROR] secret-cracker: Could not query power state: 192.168.2.162: connection timeout#012.
Jul 27 19:05:15 maas-node1 maas.power: [ERROR] Power state could not be queried: 192.168.2.162: connection timeout
Jul 27 19:05:15 maas-node1 maas.power: [ERROR] secret-cracker: Could not query power state: 192.168.2.162: connection timeout#012.
Jul 27 19:05:40 maas-node1 maas.import-images: [INFO] Started importing boot images.
Jul 27 19:05:40 maas-node1 maas.import-images: [INFO] Finished importing boot images, the region does not have any new images.
Jul 27 19:10:45 maas-node1 maas.power: [ERROR] Power state could not be queried: 192.168.2.162: connection timeout
Jul 27 19:10:45 maas-node1 maas.power: [ERROR] secret-cracker: Could not query power state: 192.168.2.162: connection timeout#012.
Jul 27 19:16:15 maas-node1 maas.power: [ERROR] Power state could not be queried: 192.168.2.162: connection timeout
Jul 27 19:16:15 maas-node1 maas.power: [ERROR] secret-cracker: Could not query power state: 192.168.2.162: connection timeout#012.

vedams@maas-node1:/var/log/maas$ sudo tail -f clusterd.log
[sudo] password for vedams:
2016-07-27 18:57:22+0530 [-] (UDP Port 43487 Closed)
2016-07-27 18:57:22+0530 [-] Stopping protocol <tftp.bootstrap.RemoteOriginReadSession instance at 0x7f976015cab8>
2016-07-27 18:57:22+0530 [-] RemoteOriginReadSession starting on 53040
2016-07-27 18:57:22+0530 [-] Starting protocol <tftp.bootstrap.RemoteOriginReadSession instance at 0x7f9761e46b48>
2016-07-27 18:57:25+0530 [-] Timed during option negotiation process
2016-07-27 18:57:25+0530 [-] (UDP Port 53379 Closed)
2016-07-27 18:57:25+0530 [-] Stopping protocol <tftp.bootstrap.RemoteOriginReadSession instance at 0x7f976015c7a0>
2016-07-27 18:57:36+0530 [RemoteOriginReadSession (UDP)] Final ACK received, transfer successful
2016-07-27 18:57:36+0530 [-] (UDP Port 53040 Closed)
2016-07-27 18:57:36+0530 [-] Stopping protocol <tftp.bootstrap.RemoteOriginReadSession instance at 0x7f9761e46b48>

^Cvedams@maas-node1:/var/log/maas$ sudo tail -f regiond.log
2016-07-27 19:15:52 [-] 127.0.0.1 - - [27/Jul/2016:13:45:51 +0000] "GET /MAAS/rpc/ HTTP/1.1" 200 296 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"
2016-07-27 19:16:22 [-] 127.0.0.1 - - [27/Jul/2016:13:46:21 +0000] "GET /MAAS/rpc/ HTTP/1.1" 200 296 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"
2016-07-27 19:16:52 [-] 127.0.0.1 - - [27/Jul/2016:13:46:51 +0000] "GET /MAAS/rpc/ HTTP/1.1" 200 296 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"
2016-07-27 19:17:22 [-] 127.0.0.1 - - [27/Jul/2016:13:47:21 +0000] "GET /MAAS/rpc/ HTTP/1.1" 200 296 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"
2016-07-27 19:17:52 [-] 127.0.0.1 - - [27/Jul/2016:13:47:51 +0000] "GET /MAAS/rpc/ HTTP/1.1" 200 296 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"
2016-07-27 19:18:22 [-] 127.0.0.1 - - [27/Jul/2016:13:48:21 +0000] "GET /MAAS/rpc/ HTTP/1.1" 200 296 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"
2016-07-27 19:18:52 [-] 127.0.0.1 - - [27/Jul/2016:13:48:51 +0000] "GET /MAAS/rpc/ HTTP/1.1" 200 296 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"
2016-07-27 19:19:22 [-] 127.0.0.1 - - [27/Jul/2016:13:49:21 +0000] "GET /MAAS/rpc/ HTTP/1.1" 200 296 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"
2016-07-27 19:19:52 [-] 127.0.0.1 - - [27/Jul/2016:13:49:51 +0000] "GET /MAAS/rpc/ HTTP/1.1" 200 296 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"
2016-07-27 19:20:22 [-] 127.0.0.1 - - [27/Jul/2016:13:50:21 +0000] "GET /MAAS/rpc/ HTTP/1.1" 200 296 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"

vedams@maas-node1:/var/log/maas$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================================-===============================-============-===============================================================================
ii maas 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS server provisioning libraries

Please provide me the solution for solving this issue?

summary: - MAAS Power Error
+ MAAS node Power Error
Changed in maas:
assignee: nobody → sivarama prasad Ravipati (sivar-y)
assignee: sivarama prasad Ravipati (sivar-y) → nobody
affects: maas → maas-deployer
information type: Private Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.