[02:14] <smoser> designated, your error is probably true.
[02:14] <smoser> it couldn't get a lock because the process running (that never completeded) had it locke
[02:14] <smoser> you could strace that process and probably get some more info
[02:15] <smoser> maybe you have outbound internet access blocked ?
[02:19] <designated> smoser, it's not blocked, maas is not recognizing the domain as being managed even though it's configured correctly and forwarding the dns request to the configured dns forwarder
[02:19] <smoser> the sudo error is not relevant.
[02:20] <smoser> it happens any time dns resolution of 'hostname' fails.
[02:20] <smoser> which is fine.
[02:20] <designated> smoser, correct but that's what I'm trying to explain.
[02:20] <smoser> thats fine though.
[02:20] <smoser> if you're apt-get update hung, then thats the problem.
[02:20] <designated> apt-get update is hanging because of a dns issue and never completing enlistment.
[02:20] <smoser> no. i don't think so.
[02:20] <smoser> dns resolution of `hostname` is fialing
[02:21] <designated> it is because if i kill the process it finishes enlistment immediately
[02:21] <smoser> can you verify it works for anything else ?
[02:21] <smoser> and resolution would *fail* not hang.
[02:21] <smoser> you're on the system now?
[02:21] <designated> yes
[02:21] <smoser> do 'ping archive.ubuntu.com'
[02:21] <smoser> i think you'll get dns resolution
[02:21] <smoser> or if you dont, then yes, dns is the issue.
[02:22] <designated> it will resolve that
[02:22] <designated> apt-get update doesn't succeed because it cannot resolve it's own hostname
[02:22] <smoser> doesn't care.
[02:22] <smoser> thats not why its hanging. i'm certain of that.
[02:23] <smoser> you can replicate that anywhere like this:
[02:23] <designated> this process is running: root      1384  0.0  0.0  31064  2380 ?        S    20:13   0:00 /usr/bin/apt-get --option=Dpkg::Options::=--force-confold --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet update
[02:23] <designated> if i kill it, enlistment will finish
[02:23] <smoser> strace it
[02:23] <smoser> what is it doing.
[02:23] <smoser> or even just tail /var/log/cloud-init-output.log
[02:23] <smoser> sudo strace -p 2380
[02:24] <designated> $ sudo strace -p 1384
[02:24] <designated> sudo: unable to resolve host maas-enlisting-node
[02:24] <designated> Process 1384 attached
[02:24] <designated> select(8, [6 7], [], NULL, {0, 23729})  = 0 (Timeout)
[02:24] <designated> select(8, [6 7], [], NULL, {0, 500000}) = 0 (Timeout)
[02:24] <designated> select(8, [6 7], [], NULL, {0, 500000}) = 0 (Timeout)
[02:24] <designated> select(8, [6 7], [], NULL, {0, 500000}) = 0 (Timeout)
[02:25] <designated> Ign http://archive.ubuntu.com trusty-updates InRelease
[02:25] <designated> Err http://security.ubuntu.com trusty-security Release.gpg
[02:25] <designated>   Connection failed
[02:27] <designated> smoser, mackrel is working with me on this issue
[02:27] <designated> just letting you know so he can ask questions about the same issue
[02:28] <designated> smoser, could it be an issue with the proxy server on maas?
[02:28] <smoser> designated, see, its timing out on a network connection.
[02:29] <smoser> you set a proxy in maas ?
[02:29] <designated> smoser, no but i thought by default the apt-get requests got proxied through maas
[02:29] <smoser> you can see if that was correctly written into /etc/apt (grep -r Proxy /etc/apt)
[02:30] <designated> under maas gui there is an option to configure proxy server, it says if you leave it blank "This will also be passed onto provisioned nodes instead of the default proxy (the region controller proxy)."
[02:30] <smoser> it could be an issue then on the squid proxy on the maas region controller
[02:30] <smoser> try:
[02:30] <designated> /etc/apt/apt.conf.d/95cloud-init-proxy:Acquire::HTTP::Proxy "http://192.168.168.7:8000/";
[02:31] <smoser>  http_proxy=http://your.maas.ip.addr:3128 wget http://security.ubuntu.com
[02:31] <smoser> i suspect that will hang similarly.
[02:31] <smoser> er... s/3128/8000/
[02:33] <designated> Resolving your.maas.ip.addr (your.maas.ip.addr)... failed: Name or service not known.
[02:33] <designated> wget: unable to resolve host address âyour.maas.ip.addrâ
[02:33] <designated> shit...just a sec
[02:33] <smoser> :)
[02:33] <mackrel> smoser, designated, yes it is stalling.
[02:33] <smoser> yeah, thats not going to work :)
[02:33] <designated> noobing it up tonight
[02:34] <designated> just hangs
[02:34] <designated> Connecting to 192.168.168.7:8000... connected.
[02:34] <designated> Proxy request sent, awaiting response...
[02:34] <designated> i wonder how squid proxy got jacked up
[02:38] <mackrel> sudo service squid-deb-proxy status squid-deb-proxy start/running, process 1005
[02:39] <designated> i show squid-deb-proxy as well as squid3 installed.  are both of these needed?
[02:40] <designated> squid3 is listening on TCP/8000
[02:40] <designated> proxy     1005  0.0  0.1 127620 30736 ?        Ssl  18:30   0:01 /usr/sbin/squid3 -N -f /etc/squid-deb-proxy/squid-deb-proxy.conf
[02:40] <designated> proxy     1233  0.0  0.1 113348 20260 ?        Ss   18:32   0:00 /usr/sbin/squid3 -N -YC -f /etc/squid3/squid.conf
[02:43] <smoser> is squid proxy simply blocked on outbound network connections ?
[02:43] <smoser> ie, from maas sytem can you hit archive.ubuntu.com ?
[02:43] <designated> smoser, it's not blocked
[02:43] <designated> smoser, yes i can
[02:43] <smoser> can you try the wget above on the maas region controller ?
[02:44] <smoser> maybe just try restarting squid. that doesn't give you warm fuzzies, but id ont know.
[02:45] <designated> smoser, the wget from the controller succeeds but not when i proxy the request through itself.
[02:47] <designated> mackrel, didn't we have a similar problem in the lab?
[02:47] <smoser> right.
[02:47] <smoser> so yeah, squid is messed up. did you try restarting it ?
[02:47] <designated> i did
[02:47] <designated> no difference
[02:47] <smoser> i know thats a hack.
[02:47] <smoser> but i dont know why it would be hung.
[02:47] <smoser> you can look at its logs for some info.
[02:49] <mackrel> yes.  we experienced this issue before but this was working and has deteriated to this
[02:52] <designated> mackrel, right, no changes were made to squid.  everything was working, then it stopped.  i rebuilt maas from scratch today and we're still seeing this issue.
[02:53] <smoser> so see if there is anything in squid error or access logs that gives you any hiints
[02:54] <smoser> the only guess i have a this point is that squid's dns resolution is borked. suspecting something to do with maas taking over dns on that system.
[02:54] <smoser> but i dont have a lot of faith in that theory
[02:54] <designated> 1401936515.205   4723 192.168.168.7 TCP_MISS_ABORTED/000 0 GET http://security.ubuntu.com/ - HIER_DIRECT/2001:67c:1562::15 -
[02:54] <designated> i don't understand why there are two squid processes running
[02:54] <designated> proxy     8372  0.0  0.1 115640 22480 ?        Ss   20:45   0:00 /usr/sbin/squid3 -N -f /etc/squid-deb-proxy/squid-deb-proxy.conf
[02:54] <designated> proxy     8464  0.0  0.1 113216 19956 ?        Ss   20:48   0:00 /usr/sbin/squid3 -N -YC -f /etc/squid3/squid.conf
[02:55] <smoser> well, yeah, that is kind of silly. :)
[02:55] <smoser> but one of them is squid deb proxy and one is just squid.
[02:55] <designated> maas uses squid-deb-proxy...no?
[02:55] <smoser> squid deb proxy actually i think probably runs on 3128
[02:55] <smoser> err.
[02:55] <smoser> i might be rwong
[02:55] <smoser> i am wrong
[02:55] <smoser> 8000 is squid deb proxy
[02:55] <mackrel> sudo netstat -tanpo | grep 3128
[02:56] <mackrel> tcp6       0      0 :::3128                 :::*                    LISTEN      8464/squid3      off (0.00/0/0)
[02:56] <designated> tcp6 not 4
[02:56] <designated> both of them say tcp6
[02:56] <mackrel>  sudo netstat -tanpo | grep 8000
[02:56] <mackrel> tcp6       0      0 :::8000                 :::*                    LISTEN      8372/squid3      off (0.00/0/0)
[02:57] <mackrel> one process is listening 3128 and another on 8000
[02:59] <smoser> you're saying squid just isn't listening on ipv4 ?
[02:59] <smoser> telnet localhost 8000 ?
[03:00] <designated> smoser, it connects
[03:00] <designated> does squid get installed as a depend of maas-dns?
[03:01] <mackrel> localhost resolves to ::1 in /etc/hosts, so I imagine when squid starts it binds itself to localhost and resolve ipv6.  we can probably comment that out, restart squid and it would list on ipv4
[03:01] <smoser> probably not maas-dns. prbobaly maas region controller
[03:04] <designated> mackrel, any ideas?
[03:08] <mackrel> designated, not really.  dns resolution was first step but now it is proxy... seems pretty weird we got three dozen nodes to register before and now kaput
[03:18] <designated> smoser, thanks for your help.  we're going to have to figure out wth squid is doing
[03:38] <smoser> designated, sorry couldn't get you past that issue.
[08:57] <rvba> gmb: I'm marking your fix-commissioning-page-distro-list-bug-1312844 branch "needs fixing".  The problem I describe could have gone unnoticed because the testing coverage is not complete in this area.  Happy to help you with this when you're back from your mini sprint.
[08:57] <gmb> rvba: Merci. Yeah, you’re right… I kind of knew I was on a bit of a wing and a prayer tests-wise :)
[08:58] <gmb> anyway
[08:58]  * gmb -> sprinting
[09:02] <rvba> bigjools: why do you think it's best to set it in start_nodes()?
[09:02] <bigjools> rvba: lol
[09:03] <bigjools> rvba: because I figured chaining the jobs would be better, but as you just pointed out we need host entries for other types too
[09:03] <bigjools> the other job being the power_on
[09:03] <bigjools> hmmm
[09:04] <bigjools> I'll add it tomorrow.
[09:04] <bigjools> in claim_static_ip() I mean
[09:04] <rvba> Sounds good.
[09:05] <bigjools> we have to hope celery gets to it before the power_on :)
[09:06] <rvba> This is a bit of a gamble.
[09:06] <bigjools> quite
[09:07] <bigjools> hence my question
[09:07] <bigjools> it's not so cut and dry
[09:11] <rvba> bigjools: we can't reasonably take that risk.
[09:12] <bigjools> rvba: yeah, and I think in terms of abstraction it makes sense to leave it out
[09:13] <rvba> I would have preferred to have the change in the DB and the setting of the host entry in one place.  Because they are the two sides of the same coin (one part is internal the other is external).
[12:43] <JayJ> I need help debugging MaaS. The node (VM) fails to Commission
[12:49] <Jay_> I need help to debug MaaS. Anyone?
[12:50] <Jay_> I posted the question in askubuntu: http://askubuntu.com/questions/477028/maas-fails-to-commission-nodes
[13:11] <rvba> Hi Jay_; thanks for the question.  I'll have a look at the logs you provided in a short while.  I'll get back to you when I do (probably on askubuntu.com).
[13:14] <Jay_> rvba: Thank you very much
[13:42] <Jay_> rvba: Please let me know if you need any more logs from the box.
[13:46] <rvba> Jay_: I suggest you have a look at the machine's logs (syslog & co) when it fails to get its IP address.  Maybe you'll find a hint as to why it failed commissioning.
[13:52] <Jay_> rvba: Do these logs make any sense?
[13:52] <Jay_> Jun  4 20:03:56 maas dhcpd: DHCPNAK on 50.50.50.13 to 08:00:27:b9:e6:16 via eth0
[13:52] <Jay_> Jun  4 20:04:12 maas dhcpd: DHCPDISCOVER from 08:00:27:b9:e6:16 via eth0
[13:52] <Jay_> Jun  4 20:04:12 maas dhcpd: DHCPOFFER on 50.50.50.58 to 08:00:27:b9:e6:16 via eth0
[13:52] <Jay_> Jun  4 20:04:12 maas dhcpd: DHCPREQUEST for 50.50.50.13 (50.50.50.3) from 08:00:27:b9:e6:16 via eth0: lease 50.50.50.13 unavailable.
[13:53] <rvba> Jay_: the "lease <ip> unavailable" doesn't look too good.
[13:54] <Jay_> rvba: That's where I think MaaS messing up something. Don't know how to proceed as I know little about MaaS
[13:56] <rvba> Jay_: can you share the content of the lease file? /var/lib/maas/dhcp/dhcpd.leases
[13:56] <rvba> leases* even
[13:59] <rvba> Jay_: The DHCPNAK message also seems to indicate something is wrong with the network config/the DHCP config.
[13:59] <Jay_> rvba: Copied here: https://www.dropbox.com/s/fwu0db3orphz2jk/dhcp-leases
[14:00] <Jay_> rvba: Appears that MaaS assigns an IP and binds MAC during enlistment. Then it is getting confused during Commissioning!
[14:04] <rvba> Jay_: yes, the assignment is made the first time MAAS sees a node.  It should be used throughout a node's lifecycle so that the IP doesn't change.
[14:05] <Jay_> makes sense. I thought so too. However, the VM PXE boots again during Commissioning, whcih is when it is getting confised
[14:57] <magicrobotmonkey> which tool do you use to change the volume quotas?
[14:59] <magicrobotmonkey> cinder!
[16:34] <designated> blake_r, do you know of a quick way to restart all maas services?
[16:36] <blake_r> designated: i just normally restart them one at a time
[16:51] <designated> blake_r, so just restart everything in /etc/init/maas-* one at a time?
[16:52] <blake_r> yes
[16:52] <blake_r> and apache2
[16:52] <blake_r> and tgt
[17:28] <designated> blake_r, thank you.
[18:20] <designated> blake_r, do you know of a way to disable maas forcing the nodes to use the maas controller as a proxy?  during enlistment, squid-deb-proxy doesn't seem to be functioning correctly, I've been troubleshooting it for a couple of days now with no success.  I keep getting:
[18:20] <designated> Err http://security.ubuntu.com trusty-security Release.gpg
[18:20] <designated>   Connection failed
[18:21] <designated> all of my nodes have direct internet access.
[18:53] <designated> smoser, who is responsible for working on the squid-deb-proxy portion of maas and can assist in troubleshooting this issue?
[18:56] <smoser> well squid-deb-proxy is just an ubuntu package. maas depends on it. you can file a bug against squid-deb-proxy using 'ubuntu-bug squid-deb-proxy'.
[18:58] <smoser> and you can probably turn up debug info in squid
[18:58] <smoser> http://www.squid-cache.org/Doc/config/debug_options/
[18:59] <designated> smoser, do you know a way to prevent maas from forcing the nodes to proxy the apt requests?
[19:08] <smoser> designated, grep through /etc/maas -r for http_proxy or just proxy and see if you see anything
[19:09] <smoser> i think it should show up there.
[19:09] <smoser> and i think you should be even able to set the proxy in the maas web ui
[19:10] <designated> smoser, i don't want a proxy
[19:10] <smoser> right. i suspec tyou'll see it set to some value
[19:10] <smoser> and you can unset it
[19:19] <designated> smoser, I'll try that.  thank you
[20:11] <designated> smoser, the file /etc/maas/preseeds/commissioning only contains {{preseed_data}}.  Does that get pulled in from 'generic' and 'preseed_master'?
[20:12] <smoser> probably rendered in maas internal.
[20:12] <smoser> i'd hvae to look at it.
[20:13] <smoser> i dont really know., anyone know how to globally disable the squid proxy ?
[20:16] <designated> i successfully disabled the proxy server during enlistment and it enlisted perfectly.  now trying to go the same for commissioning
[20:23] <designated> smoser, I think I found it here: /etc/maas/templates/commissioning-user-data/user_data_config.template