[08:15] good mornin' folks. why in the world is MAAS running...two DHCP servers...? [08:19] should I use 14.04 LTS for Ubuntu Cloud Images? or 15.10? [08:35] Razva: ps aux | grep dhcp | curl -sF "file=@-" https://0x0.st [08:35] mornin' haasn [08:36] https://0x0.st/X0i.txt [08:36] haasn at this point I've reinstalled Ubuntu [08:36] just a sec to setup networking [08:37] well that machine is clearly running 0 DHCP servers :p [08:37] yup, right now yes [08:38] can you please take a look at https://github.com/Razva/newbadmin/blob/master/firewall/nat.sh ? [08:38] it's a script one of the good folks here provided for NAT [08:38] I've slighly modified it [08:38] looks ok? [08:38] (for NAT) [08:51] Razva: seems reasonable, not sure if the MASQUERADE line would benefit from an extra -i "$INTIF" or not but if it works it works [08:53] any idea how to retain this after reboot...? :| [08:54] Razva: iptables-save and iptables-restore can be used to save the current settings to a file (and do the opposite). Most distros provide some sort of init script for automatically doing that [08:55] got it [08:56] haasn: https://0x0.st/X0K.txt < that ps aux you've requested [08:56] seems that only MAAS is running, right? [08:56] seems to only be running one [08:57] on interface enp0s25 (this is your private interface, I take it?) [08:57] weird, last time it was i*something-dhcp-server running also... :| [08:57] exactly, it's the lan [08:57] now, let's try to PXE boot [08:57] Razva: when stuff like that happens it's a good idea to look at the -f option, in this case /var/lib/maas/dhcpd.conf [08:57] If that's /etc/dhcp/dhcpd.conf or something like that then it's probably some “default” system-wide dhcpd service running accidentally [08:57] do you recommend 14 LTS or 15, for Ubuntu Cloud? [08:58] I have no idea. I use 14 LTS because I haven't had a reason to change [08:59] does Liberty works with 14? [09:00] yup, it successfully booted, no idea why last time it basically started two DHCP servers...it was a fresh install... [10:14] haasn except "Allow SSH access and prevent machine from powering off", should I check the other two boxes? [10:14] Retain network & Retain storage? [10:15] What those checkboxes mean is that if you're commissioning a node that you've already comissioned in the past, any storage/network configuration you made manually will be preserved instead of reset back to the default [10:15] If this is your first time commissioning that node they do nothing [10:15] aaand if I didn't ever commisioned them...I suppose that I should just "SSH and prevent machine from powering off", right? [10:17] I don't see any reason to set that unless you're trying to debug something that went wrong [10:18] yay, ok [10:19] the only "wrong" thing until now is that MAAS is seeing "power on" even if the machine is 100% powered off :| [10:20] any idea why> [10:21] Razva: the power status is not checked all the time but polled at regular intervals (every few minutes), you can click ‘check now’ to force an update [10:21] haasn did it 3 times, they still point as being on [10:21] Checking power -> Power on [10:21] Razva: What power type? [10:22] even tried to "shutdown" them from MAAS [10:24] IPMI. they are Dell servers [10:25] Razva: try asking ipmipower -D LAN_2_0 -h HOST -u maas -p PASS --stat what it thinks of your host [10:26] Power State OFF [10:26] haasn any idea what's the pass? :)) [10:27] Razva: you can check in the maas GUI [10:27] It should have created a new account/password when enlisting [10:27] If ipmipower works but MAAS does not, seems like a bug to me [10:27] got it, just a sec to see [10:28] HOST = IP or host.maas ? [10:28] It should be the same hostname as in the maas power configuration [10:29] paltry-cave < who in the world is generating these names? :) [10:30] 95.154.222.13: connection timeout [10:31] interesting. [10:36] Razva: you could also try logging in via SSH [10:38] I'm power cycling both machines, see what's the result [10:39] long live iDRAC :) [10:39] the machines are not even commisioned, so I cannot really SSH in... [10:40] oook both are not booting via PXE [10:42] ssh key bla bla... [10:43] both are waiting here: http://screencast.com/t/LvFwpbHIaBnK [10:43] ^ is that "normal"? [10:44] aaaand they seem to be stuck at that point :| [10:50] Razva: SSH to the service processor (IPMI interface), not the host OS [10:54] SSH seems to be working, but I cannot login [10:57] Razva: with the maas username/password? [10:58] what about root? [11:02] haasn yup, with the maas u/p, I cannot login [11:02] I'll try to login with root now [11:02] 95.154.222.13: connection timeout < from ipmipower [11:03] root@95.154.222.13's password: < ssh works [11:03] /admin1-> < root worked [11:03] any hints now? :D [11:12] Razva: set the root un/pw in maas and be done with it? :p [11:13] oh, connection timeout from ipmipower with root p/w too? [11:13] Razva: try ipmitool -I lanplus -U root -P ... -H ... user list [11:14] If ssh works but ipmipower does not, then you might need to specify a firmware-specific workaround flag (via -W) [11:14] e.g. I need -W sun20 for some of my old sun servers [11:17] haasn exactly [11:17] haasn but I cannot even reset IPMI [11:18] ipmitool -H 95.154.222.13 mc reset warm [11:18] Password: [11:18] Error: Unable to establish LAN session [11:18] did you try the ipmitool command I suggested? [11:18] nope, just a sec [11:19] ipmitool -I lanplus -U root -H -H 95.154.222.13 user list [11:19] Password: [11:19] Address lookup for -H failed [11:19] Could not open socket [11:20] (same with minus the extra -H) [11:20] ipmitool -I lanplus -U root -H 95.154.222.13 user list [11:20] Password: [11:20] Error: Unable to establish IPMI v2 / RMCP+ session [11:21] but I can SSH login... [11:21] sh root@95.154.222.13 [11:21] root@95.154.222.13's password: [11:21] /admin1-> [11:26] Razva: maybe something here will help? https://www.gnu.org/software/freeipmi/freeipmi-bugs-issues-and-workarounds.txt [11:27] also see man ipmipower (scroll down to workarounds) [11:31] I've contacted the data-center...maybe they can do a power-cycle/reset... [11:31] doubt it will help [11:36] its their server, so I should be able to list users...at least. [16:52] hey guys. I have no idea why but maas refuses to interpret the right status from IPMI... [16:52] the server is powered down, I can see that via DRAC and console.. [16:52] but still maas reports the server as being online. any hints...? [17:23] hi, im having some trubles with unmanaged networks [17:23] im trying to let my local dhcp and dns to manage this network [17:24] but for some reason /etc/resolv.conf is setting maas ip address as DNS [17:24] i double check my local dhcp setting and everything seems fine [17:25] so, why maas is putting herself as DNS of an unmanaged network? [17:28] redelmann no idea, but that's what maas does (at least on my setup) [17:30] Razva, ok, thank. It little strange, i was supposing that unmanaged network is UNmanaged :P [17:30] Razva, i think juju bootstrap fail in my setup because of this [17:40] redelmann I have a very weird issue. MAAS reports power on, even if power is off (I can see in iDRAC that power is off, and console shows No power) [17:41] Razva, it's that for me? [17:42] redelmann yes [17:42] maybe you have any ideas... [17:43] Razva, noup. [17:43] Razva, im playing with maas for 2 weeks to now [17:44] Razva, so im not the most indicated person [17:44] haha, I'm playing for ehm...2 days :D [17:44] I've successfully setup 3 machines, everything PXE boots, but this single darn machine doesn't wants to boot.... [17:45] or whatever...boots but doesn't wants to report power as it should [17:45] Razva, maybe hardware problem? [17:46] no idea... [17:46] do you use IPMI or...? [17:46] IPMI and virsh [17:47] i'am mixing virtual nodes with intel hardware [17:47] I have only intel / Dell hardware, but no idea why the heck I cannot control it... [17:47] im just testing maas for a full implementation [17:48] well...I didn't had any issues with it until now, only problem was that - at first install - Ubuntu installed a separate DHCP server as well. no idea why, but a clean install solved everything [17:49] Power on < I'm gonna kill somebody. [17:49] Razva, you are installing MAAS from apt? [17:49] the server is off god damnit... [17:50] Razva, try with "check now" link :P [17:50] Razva, or manually power on the server [17:50] yeah if I manually power on it works, but this is not the way to do it... [17:50] Razva, after manually power on, swith to off with maas [17:51] how...? [17:51] I cannot manually set power off in maas [17:51] Razva, i know but maybe yoy can "sync" what maas think about node and rearl node state [17:51] please do me a favor [17:51] Razva, take action -> power off? [17:52] ipmipower -D LAN_2_0 -h SOME-IPMI-IP -u root -p THE-ROOT-PASSWORD --stat [17:52] does it works for you? [17:55] Razva, im in home rigth know. [17:55] Razva, i dont know why cant ssh to cluster [17:56] Razva, give me a second [17:57] Razva, but usually thats the command i use to check the whole cluster power status without problem [17:58] Razva, i never use -D, only -h ip [18:01] Razva, did you try with --debug? [18:01] well...what command do you use, usually? [18:03] (ipmipower_powercmd.c, _retry_packets, 1214): host = 95.154.222.13; p = 1; Sending retry, retry count=24 [18:09] redelmann are you deploying OpenStack or just MaaS? [18:09] Razva, just MAAS [18:09] Razva, ipmipower -h ip -u root -p THE-ROOT-PASSWORD --stat [18:09] Razva, i let ipmipower to decide ipmi version [18:10] 95.154.222.13: connection timeout [18:10] but the interesting thing is that I can ssh to it [18:11] /admin1-> [18:12] Razva, ipmipower --version? [18:13] Razva, some old ipmipower utilitis had a bug with -p options i think [18:14] redelmann via SSH? [18:14] Razva, no, just ipmipower --version in machine you are trying to connect [18:15] Razva, maas server i suppose [18:15] ipmipower - 1.1.5 [18:16] you? [18:16] Razva, look at this: https://lists.gnu.org/archive/html/freeipmi-users/2005-11/msg00018.html [18:17] Razva, its old [18:17] Razva, forget about it, ipmipower 0.1.3 its the problem [18:18] Razva, ipmipower - 1.1.5 [18:18] Razva: do you have logs from /var/log/maas/ , it is probably telling why it cannot connect to IPMI [18:18] if that's the case [18:20] redelmann: maas doens't really support external DHCP/DNS anymore. But eventhen, MAAS is the defautl DNS server unless you set it differently for each subnet [18:21] Razva, did you try ipmiping [18:22] roaksoax, http://paste.ubuntu.com/15060537/ [18:22] roaksoax, i set DNS on my maas-eth0 [18:22] redelmann: what version of MAAs are you using? [18:22] roaksoax, it's that no enough? [18:23] 1.9 [18:23] roaksoax, 1.9 [18:23] roaksoax, it's testing purpose [18:23] redelmann: right, so when you deploy, is the interface of the machine configured to do what? DHCP ? [18:24] roaksoax, exactly [18:24] redelmann: right, so DHCP should be setting the DNS server right? [18:24] roaksoax, rigth [18:24] redelmann: also, can you get the curtin config ? [18:26] redelmann: maas node get-curtin-config [18:26] roaksoax, ohh THANK, i was losing my head [18:28] roaksoax, http://paste.ubuntu.com/15060721/ [18:29] roaksoax, /etc/resolv.conf contain: 192.168.100.1 (my lan DNS) and 192.168.100.10 (my mass server lan ip) [18:30] roaksoax, i was expecting to have only 192.168.100.1 [18:30] redelmann: Yeah I see. is the NIC on your system connected to 'maas-eth0' subnet ? [18:31] redelmann: i think the problem here is that since MAAS is not configure eth0, it is ont telling /etc/network/interfaces to set the DNS of maas-eth0 [18:32] redelmann: eitherway DHC{P should be setting it [18:32] and it doesn't seem like it is ? [18:33] roaksoax, maas server and node have a NIC on 'maas-eth0' [18:33] redelmann: right, but MAAS is not managing DHCP/DNS< and my *guess* is that because of that, DNS server of maas-eth0 is not being set [18:33] redelmann: on the config [18:35] roaksoax, that's rigth [18:35] right [18:35] redelmann: so, yif you could file a bug, I'll discuss it with my guys and see if we can fix that [18:36] cause I think we porbably should [18:37] redelmann: please attach both, the maas-eth0 subnet and the curtin config [18:37] to the bug report [18:37] roaksoax, great, between my poor English and my mass-newby it's hard to explain. i will do my best [18:37] roaksoax, ok [18:38] redelmann: don't worry, just file it, and I'll fix the wording if need by [18:38] be* [19:23] roaksoax, https://bugs.launchpad.net/maas/+bug/1545500 [19:24] roaksoax, hope you can understand the whole idea/problem :P [19:26] roaksoax, thank for you [19:26] roaksoax, thank for your time [19:43] Bug #1545500 opened: MAAS unmanaged network set wrong DNS information [21:56] Hopefully somebody reads this: If you're thinking of managing maas hosts with juju, use ansible instead! My life is so much happier and it's easier to set up, maintain and interact with :) [22:12] somehow I don’t see juju bootstrap being that difficult a command to use === blahdeblah_ is now known as blahdeblah