pmatulishow do i deploy a node using the cli?02:31
mupBug #1518226 opened: Option to add ipmipower args via webUI <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1518226>09:46
caribouHello, is anyone familiar with how the booloading (BIOS/UEFI) is handled in Maas ?09:52
nagyzhi guys10:32
nagyzI'm trying to figure out what happens when I have a server on two MAAS-managed networks (one provisioning, one "public")10:32
nagyzit seems to be that the default gateway will be set based on which interface is the first one in the alphabet :-)10:33
nagyzsame for DNS10:33
matt_dupreHi: I've just upgraded from 1.5 to 1.8.3, but I'm now seeing 503 errors trying to connect to http://<server>/MAAS/12:17
matt_dupreThe apache error log says "Connection refused [...] attempt to connect to (localhost) failed".  Nothing's listening on port 5240.  Does anyone have any ideas what this could be?12:18
Harishello all13:45
Hariswhat's maas for ubuntu ?13:45
Harisis it something like .. if I needed running 2 or more VMs on the same machine, and I didn't have vmware, I'd use maas to do it ?13:45
Harisos is it like a PXE ?13:47
roaksoaxHaris: MAAS is a deployment tool, that not only deploys Ubuntu but other operating systems13:54
Harisso, its a PXE ?13:54
Harisreplacement ?13:54
roaksoaxHaris: it does PXE, UEFI, Grub net booting13:55
roaksoaxHaris: but it is not a "PXE replacement"13:55
roaksoaxHaris: PXE is an underlying technology13:55
HarisI see13:56
Harisis maas a web tool ?13:56
Harisor just the front end13:56
roaksoaxHaris: maas provides a WebUI and a CLI, so you can do the same thing via those two interfaces13:59
roaksoaxHaris: so it is a software tool that incorporates other technologies (PXE, DHCP, DNS< Proxy), and provides users with a WebUI and a CLI Interface to control it14:00
Harisah ok14:00
mupBug #1518226 changed: Option to add ipmipower args via webUI <canonical-bootstack> <MAAS:Opinion> <https://launchpad.net/bugs/1518226>14:14
mupBug #1518226 opened: Option to add ipmipower args via webUI <canonical-bootstack> <MAAS:Opinion> <https://launchpad.net/bugs/1518226>14:20
Haristhank you all14:31
mupBug #1518226 changed: Option to add ipmipower args via webUI <canonical-bootstack> <MAAS:Opinion> <https://launchpad.net/bugs/1518226>14:32
matt_dupreSo I figured by problem above out: /var/log/maas/maas.log was owned by syslog, but the user responsible for logging changed during the upgrade to maas, so maas-regiond was unable to write to the log15:08
losHas anyone ever noticed that when you do dpkg-reconfigure on a cluster controller (without a regional) to point to a regional somewhere else....it might "ignore" your URL to the API and try the lo and another address
losI can lynx the API and get a login from this VM, no problem, but the logs don't mention failing to connect to my URL I put into the reconfigure.15:42
los...and dpkg-reconfigure maas-cluster-controller takes a really long time to initially start and get into the CUI, if that's a clue15:43
losThe is one of the local interfaces15:47
=== jfarschman is now known as MilesDenver
roaksoaxlos: do you have an examepl?15:55
roaksoaxlos: or a pb ?15:55
losroaksoax: 2015-11-20 09:55:56-0600 [Uninitialized] Event-loop maasr6:pid=1101 ( Connection was refused by other side: 111: Connection refused. 2015-11-20 09:55:56-0600 [Uninitialized] Event-loop maasr6:pid=1101 ( Connection was refused by other side: 111: Connection refused. 2015-11-20 09:56:26-0600 [-] Event-loop maasr6:pid=1101 ( User timeout caused connection failure.15:57
losEven though I've set the MAAS API URL to something totally different, its not in those clusterd.log 's15:57
losroaksoax: Even though I can Lynx to that URL no problem, login, see stuff etc. from that same host15:58
losroaksoax: the cluster-only host has that address15:58
losroaksoax: I read the logs as "I'm gonna connect to localhost on a few ports to see a regional, and I'll try my own IP"15:59
losroaksoax: But I can't find that IP in any grep-able file15:59
roaksoaxlos: /etc/maas/clusterd.conf is where the cluster knows where to contact the region controller16:00
roaksoax.win 2216:00
losroaksoax: looking16:01
losroaksoax: It has the right URL.  I will bounce server.16:02
losroaksoax: .win 22 = Old Yeller Headache?16:02
losroaksoax: as one pal of my says, "Kevork it"16:02
roaksoaxlos: so it has the right URL where to connect to MAAS Region ?16:06
losroaksoax: yep16:06
roaksoaxlos: did you add a shared secret ?16:06
losroaksoax: yep, even the right one :)16:06
los(this time)16:06
roaksoaxlos: that's strange there, shows that it failed due to a timeout16:07
losroaksoax: I thought the key part that was interesting is that the 10.13.x.x host I have the regional+cluster ("R+C1") is not mentioned.  This is the 2nd attempted cluster controller ("C2")16:11
losroaksoax: I'm assuming "if you can lynx it and get a login, you're good"16:11
losroaksoax: Ohhhhhhh I bet the API doesn't work with the port specifier?16:13
losroaksoax: (If that's the case the logging is bugged)16:13
roaksoaxlos: what does your clusterd.conf show ?16:21
losroaksoax: cluster_uuid: eea5c60a-4fcc-41a4-b141-30ca1b77c177 maas_url:
los(two lines)16:22
roaksoaxhttp:// ->
losroaksoax: clusterd.conf owned root, group maas, 64016:23
roaksoaxlos: or:
losroaksoax: 8946->8016:26
losroaksoax: Its in a VM under Vbox, I know, not supported, but its what I got :)16:26
roaksoaxlos: right so the region binds to 5240, buyt apache is there to proxy from 80->514016:27
roaksoaxlos: right so the region binds to 5240, buyt apache is there to proxy from 80->524016:27
losroaksoax: ok, cool, so I'm forwarding in 8946 on the vmhost to the vm's 80...should I forward more?  Is there some reverse DNS problem?  Why is the clusterd not logging a connection attempt?  (no sign it "sees" the MAAS API Url as set by dpkg-reconfigure)16:28
losIs it a problem that the clusterd is otherwise not configured....aka, the 2nd interface on the C2 VM hasn't been setup yet16:30
roaksoaxlos: my guess is that the forwarding is interfering here16:35
losroaksoax: Can you give me an idea of the forwarding requirements?  5240->5240?16:36
roaksoaxlos: yeah I'd do that16:37
losroaksoax: using iptraf: can see local socket connection attempts to local ip on ports 5250, 5253, now 525216:42
losroaksoax: I have those forwarded on the R+C1 vm, but, that's the wrong IP.  Its "ignoring my MAAS API" and trying local16:43
losroaksoax: On the R+C1 vm host, I have 5250-3 forwarded into the R+C1 vm but no traffic on that16:43
mupBug #1518067 changed: multi-network node could get wrong default gateway that prevents deploy <MAAS:Invalid> <https://launchpad.net/bugs/1518067>16:44
losroaksoax: This is interesting:16:46
los│┌                                            =       5           300   S---      eth0     │ │└                                          =       0             0   ----      eth0     │16:46
los│└                                          =       0             0   ----      eth0     │16:46
losiptraf shows it making a connection from the NAT side network, to an address that I've used for things before but don't have in /etc/network/interfaces at all16:47
losroaksoax: I have eth0, enp0s8, and lo....s8 is totally unconfigured.16:48
losroaksoax: Ok, I configured the enp0s8 network (That will be the private MaaS network) now I'm getting the connection refused msgs 1/sec, but just the two last ones, the 'refused by other side'16:51
losroaksoax: The third (first showing) message with "Timeout" is gone16:51
losroaksoax: And...now the dpkg-reconfigure maas-cluster-configure is not slow to start!  Aha!16:53
losroaksoax: Changed the URL to and now I get a fast fail from twisted.... 40416:53
losroaksoax: Aha, totally different clusterd.log, after changing the URL to and having the 5240->5240 mapping16:55
los2015-11-19 13:41:08-0600 [-] Site starting on 5248 2015-11-19 13:41:08-0600 [-] TFTP starting on 69 2015-11-19 13:41:08-0600 [-] Starting protocol <tftp.protocol.TFTP instance at 0x7f06b03b8998> 2015-11-19 13:41:08-0600 [-] TFTP Listener started at 2015-11-19 13:41:08-0600 [-] TFTP starting on 69 2015-11-19 13:41:08-0600 [-] Starting protocol <tftp.protocol.TFTP instance at 0x7f06b03b8cf8> 2015-11-19 13:41:08-0600 [-] TFTP Lis16:55
los2015-11-19 13:41:08-0600 [Uninitialized] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at http://localhost:5240/MAAS/rpc/)16:56
losroaksoax: iptraf now shows its reaching out to the right!  Closer!16:56
losroaksoax: On the R+C1 machine, Apache says: Nov 20 11:03:39 maasr6 sh[1091]: 2015-11-20 11:03:39 [-] - - [20/Nov/2015:17:03:38 +0000] "GET /MAAS/rpc/ HTTP/1.0" 2 00 364 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"17:04
losroaksoax: 2015-11-20 11:06:29-0600 [Uninitialized] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at
losBetter...but not good17:06
roaksoaxlos: right, so that means the cluster, for whatever reason, can't reach to the region17:08
losroaksoax: On the R+C1 machine, when I curl localhost:5240 I get <html>     <head>         <meta http-equiv="refresh" content="0;URL=MAAS/">     </head>     <body bgcolor="#FFFFFF" text="#000000">     <a href="MAAS/">click here</a>     </body> </html>17:08
roaksoaxlos: might be the forwarding17:08
losroaksoax: On C2 machine I get ConnRefused so I'm baffled but on it17:08
losFor the good of all MaaSKind, lolz17:08
roaksoaxlos: this is what happens, the cluster connects to region on that IP/port, and the Region tells the cluster "this are my 4 endpoints, on different ports, because I have multiple daemons running"17:09
roaksoaxlos: so that's the problem I'd think17:09
roaksoaxlos: the cluster cannot connect to the endpoints17:09
losroaksoax: Do I need to forward a range of ports, 5240-X -> 5240-X?17:09
roaksoaxlos: "Firewall ports for Region and Cluster controller communication17:13
roaksoaxThe communication between Region and Cluster controller is now limited to use the ports between 5250 and 5259. For all of those users who are using a remote cluster (not running on the same machine as the MAAS Region Controller), need to ensure that these ports are open in the firewall."17:13
losroaksoax: Aha, forsooth!17:13
losroaksoax: Ok, curl to the 5240 is getting me the "click here" html"17:16
losroaksoax: Ok, I get this msg 3x: 2015-11-20 11:26:04-0600 [Uninitialized] Event-loop maasr6:pid=1096 ( Connection was refused17:26
losroaksoax: ...but the IP changes: I get back a, which is (I'm thinking) dispensed by the regional, which is an unroutable17:27
losroaksoax: So, "Oh, I contact the regional, and it gave me an address and I'm gonna connect and its no good, try these other interfaces address he gave me and loopback too"17:27
roaksoaxbladernr_: ^^17:27
roaksoaxblake_r: ^^17:27
losroaksoax: I appreciate the help: I recognize this is all virtualbox hooey17:28
roaksoaxblake_r: any ideas? seems that region might be sending back loopback to cluster ?17:28
losroaksoak: I changed the local private maas nets on both the R+C1 machine and C2 machines to non-192.168.66.x addresses (.44 and .88) and then it went bonkers.  Log ceased...a couple timeouts...long pauses...so I'm bouncing both hosts17:32
losroaksoax: Ok, this is cool: the .88 address is showing up in the C2 machine's logs, so R+C1 machine is dispensing it back to the C2 machine, ergo, this is all a consequence of the virtual box and unroutables17:35
losroaksoax: Clear as a day, the Regional is passing back ALL the interfaces addresses that are non-loopback, and then the Cluster controller is trying them all....I see iptraf on the C machine attempting to connect out to, which is the R+C1 machines private MaaS network for the "dummies" to boot off.17:36
losRoaksoax: taking lunch.  Will work this more when I get back.  Will be looking at netstat to see what's listening on the R+C1 box, etc.17:43
mupBug #1518414 opened: NVMe model info/serial number is not seen <MAAS:New> <https://launchpad.net/bugs/1518414>18:12
mupBug #1518414 changed: NVMe model info/serial number is not seen <MAAS:New> <https://launchpad.net/bugs/1518414>18:15
mupBug #1518414 opened: NVMe model info/serial number is not seen <MAAS:New> <https://launchpad.net/bugs/1518414>18:18
losroaksoax: So my region controller is just happy as can be: 2015-11-20 13:35:03 [-] - - [20/Nov/2015:19:35:02 +0000] "GET /MAAS/rpc/ HTTP/1.0" 200 364 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"19:35
losroaksoax: should that be on the loopback?19:36
losroaksoax: hahahaha the R+C1 machine has localhost:5240 in its cluster controller config!19:40
losroaksoax: Wow: I provisioned the R+C1 machine with two interfaces, and I config'd the maas-region-controller with that (NAT outbound) interface up and the other one (MaaS private) unconfigured and its my bad...MaaS picked the only up network as the private one19:44
losroaksoax: I get one of these when I trigger a restart through dpkg: 2015-11-20 13:53:20-0600 [HTTPPageGetter,client] Region is not advertising RPC endpoints.19:54
mupBug #1518440 opened: tgt fails to install in LXD <MAAS:Triaged> <tgt:New> <tgt (Ubuntu):New> <https://launchpad.net/bugs/1518440>20:06
mupBug #1518440 changed: tgt fails to install in LXD <MAAS:Triaged> <tgt:New> <tgt (Ubuntu):New> <https://launchpad.net/bugs/1518440>20:09
losroaksoax: Doc bug: right above this link, the sentence just.... https://maas.ubuntu.com/docs/install.html#disc-install20:10
mupBug #1518440 opened: tgt fails to install in LXD <MAAS:Triaged> <tgt:New> <tgt (Ubuntu):New> <https://launchpad.net/bugs/1518440>20:12
mupBug #1518440 changed: tgt fails to install in LXD <MAAS:Triaged> <tgt:New> <tgt (Ubuntu):New> <https://launchpad.net/bugs/1518440>20:15
mupBug #1518440 opened: tgt fails to install in LXD <MAAS:Triaged> <tgt:New> <tgt (Ubuntu):New> <https://launchpad.net/bugs/1518440>20:18
nagyzcan someone enlighten me how would you manage DNS if you have two different subnets, like an internal and an external?22:33
nagyzif a node has IPs on both... currently MAAS only registers the A record for the alphabetically first interface22:34

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!