=== kentb-mtg is now known as kentb-out [12:58] I'm trying to use maas (1.2+bzr1360+dfsg-0ubuntu1~ppa1 ) behind a proxy [12:58] I enabled "apt_proxy: http://{{server_host}}:8000/" in /usr/share/maas/preseeds/enlist_userdata , and was able to enlist and commission a node. [12:58] Then i try to bootstrap, the node starts, but the installation fail: [12:58] wget -q http://archive.ubuntu.com/ubuntu/dists/precise/Release -O - | grep -E '^(Suite|Codename):' [12:58] mirror does ot support the specified release (precise) [12:58] any idea what i may have missed ? [13:17] from a tcpdump i can see the zookeeper downloading the installer, the preseed file (with the proxy set in it) [13:17] but then, it fail. and the funny thing is, i do not see any trace of a wget to archive.ubuntu.com [13:17] nor a name resolution attempt. [13:17] no idea exactly where to look at. === kentb-out is now known as kentb === chuck_ is now known as zul [14:49] hmmm, on the preseed file the proxy is syppose to be the maas node on port 8000 [14:49] but there s nothing listening on port 8000 on my maas box [14:50] hmm, squid deb proxy was not started.... [14:53] still, same behaviour [16:18] melmoth: checkl if squid-deb-proxy is actually running [16:18] but that's it [16:19] proxy refers to the region controller [16:19] and it does work [16:19] tail -f /var/log/squid-deb-proxy/access.log [16:20] roaksoax, the problem was due to the fact that the maas box itself is behind a proxy. [16:20] when zookeeper asked maas's proxy for http://archive.ubuntu.com/ubuntu/dists/precise/Relase, it was not able to get the page. [16:21] at least it had a problem with the lab's proxy itself. [16:21] that';yeah [16:21] yeah [16:22] next thing i try is to put the lab proxy for apt_proxy: in the enlist_userdata file. [16:22] and see what happens. [20:48] Just install MAAS on Ubuntu 12.10 in a VirtualBox VM. Trying to hit the web portal, and I get a 500 error. /var/log/apache2/error.log shows some python errors. Suggestions?