=== Daviey_ is now known as Daviey [03:44] jtv: which package were you installing? [03:44] maas-dns [03:45] Actually I was installing lots of packages, but that's where the error happened. [03:45] jtv: let me re-phrase then. What package did you ask apt-get to install? [03:46] Pretty much everything that maas-region-controller depends on, but not maas-region-controller itself. [03:46] jtv: you mean you were manually installing all the dependencies? What was your exact command line [03:46] And not postgres, which was the original point of what I was doing. [03:46] Yes, I was manually installing all the dependencies. [03:47] why? [03:47] Because I was reproducing the postgres installation problem, and wanted to minimise noise. [03:47] ok [03:48] this is arising because maas-dns invokes some tasks, and in the tasks module it has stuff to talk to seamicro [03:48] which is annoying [03:50] Make it a lazy import? [03:50] FWIW installing python-seamicro silenced the error, although of course by that time loads of other dependencies had already been installed — they may have similar problems otherwise. [03:51] If it's just seamicro, I say cut the import chain somewhere and do it in a heavily commented function. [03:51] jtv: move the import inline, perhaps [03:52] yeah here we go, postinst calls "maas-region-admin set_up_dns" === CyberJacob|Away is now known as CyberJacob [07:50] jtv: looks like some validation that happens *after* you set self.broadcast_ip expects that address to be a string indeed… [07:52] OK I can do that now [07:53] getting a lot of errors in celery log [07:54] [2014-03-31 17:53:03,074: ERROR/MainProcess] consumer: Cannot connect to amqp://maas_workers@10.0.0.9:5672//maas_workers: [Errno 104] Connection reset by peer. [07:54] restarted celery and boom, a ton of queued jobs went through [08:02] rvba, jtv, gmb: off to eat. Call in 28m, and I have some fun news. [08:04] OK [08:21] rvba: https://code.launchpad.net/~jtv/maas/fix-default-broadcast-clean/+merge/213414 [08:21] jtv: on it [08:22] Thanks. [08:22] jtv: looks good [08:25] Thanks. [08:28] jtv: bigjools: running another test in the lab with manual fix for the bug jtv is fixing (see above)… so far so good: nodes enlisted okay… commissioning… [08:28] with *a* manual fix. [08:28] :) [08:29] perhaps a dumb question, but i'll ask anyway - what are the valid reasons to recommission a node after it becomes ready? hw changes? [08:29] yes [08:30] including changing nics ? [08:30] or if you add new commissioning scripts. [08:30] ah, right [08:30] changing nics is an interesting one [08:30] gmb, jtv, rvba: I'm on talky [08:31] thanks! [08:31] let's chance our hand [08:31] Wasty.time. [08:31] That's taking a while... [08:33] bigjools: jtv: deploying stuff with juju in the lab… [08:51] bigjools: jtv: test passed [08:54] \o/ [10:43] hi all, got a question regarding maas node installation: it seems to get it's packages from us.archive.ubuntu.com , whatever I do. I would prefer to use a local apt-cacher. has anyone an idea how to configure that? [10:57] Hermes42: you can configure that on the Settings page. By default it goes through a caching proxy on the region controller. [10:57] (This also means that you can install nodes without giving them direct internet access) [10:58] You can also select a different archive on that page. [10:58] Click the cogwheel in the upper right of the UI. [11:09] i tried that. unfortunatly, the clients still want to install from external us.archive... [11:09] additionally, the connection is direct and not over maas [11:10] jtv: i think you talk about /MAAS/settings ; Ubuntu section [11:11] there i have configured http://192.168.100.84:3142/ftp.halifax.rwth-aachen.de/ubuntu/ as the ubuntu archive, still installing from us.archive.ubuntu.com [11:11] ...84:3142 is my apt-cacher proxy on the maas server [11:12] maybe i have to regenerate some images? [11:12] maas-import-ephemerals doesn't seem to do anything anymore... [11:12] We don't generate images, so that's not it... [11:12] No, that script is obsolete. [11:12] ok [11:12] The latest package versions don't even have it. [11:13] I wouldn't configure the proxy as the Ubuntu archive, to be honest; I'd just configure a proxy. [11:13] There's a separate "proxy" field on the settings page. [11:13] jtv: my maas-server is build on 14.04 with maas 1.5 [11:14] also tried that, additional to the archive [11:14] the traffic still seems to go direct [11:14] That is strange. [11:14] rechecking [11:14] If you do nothing at all from a clean install, the nodes should get all their packages from the squid-deb proxy on the region controller. [11:15] testing. [11:15] changing ubuntu source to http://192.168.100.84:3142 [11:15] oops [11:15] the other half ;) [11:16] ftp.halifax.rwth-aachen.de/ubuntu/ [11:16] It's supposed to be a full URL. [11:17] As is the proxy, by the way. [11:17] http://ftp.halifax.... [11:17] OK [11:17] proxy is http://192.168.100.84:8000/ [11:17] That all looks sensible... [11:17] which should be the squid on maas server [11:18] i had problems with the apt-cacher before, the clients wouldnt connect to 3142 [11:18] This is not apt-cacher though. It's squid-deb-proxy. [11:18] And if you want to use the built-in proxy, just leave the proxy field blank. [11:18] had to change /etc/maas/preseeds/generic [11:19] all mirror strings to choose-mirror [11:19] Sounds like it would make a useful bug report. [11:21] yep. [11:22] the freshly installed client still has /etc/apt/sources.list with us.archive.... [11:23] i'll restart the maas and reinstall the client node.... brb [11:31] strange... now it seems to connect to the squid while commisioning, not us.archive, at least that what the download speeds say [11:41] when starting the node it still connects directly to us.archive... [11:42] jtv: where can i configure the mirror for the starting node? I see no traffic on MAAS-Server during client downloading packages (e.g. linux-kernel) [11:42] ok can s.o. tell me a working os / maas / juju combination? I currently try trusty beta [11:43] with the default packages there /maas 1.5 [11:46] Hermes42: from MAAS's point of view there is no difference between your first node and any other ones. [11:46] The kernel is not downloaded as a package; it comes straight from the cluster controller. [11:47] And, if you're getting a fast-path install, the whole boot image comes from there. [11:52] * jtv must be off now. Good night! === lazypower_travel is now known as lazyPower === cmagina-away is now known as cmagina === CyberJacob is now known as CyberJacob|Away === cmagina is now known as cmagina-away === cmagina-away is now known as cmagina [14:21] hello, could someone take a look to https://codereview.appspot.com/82670043/ ? [14:21] It adds basic support for networks listing to testserver === cmagina is now known as cmagina-away === cmagina-away is now known as cmagina [15:18] dimitern: Hi, I'm having a look at bug 1299114. Do you recall the parameters you were using when defining the network? [15:18] bug 1299114 in MAAS "'ValidationError' object has no attribute 'error_dict' when creating a network" [Critical,Triaged] https://launchpad.net/bugs/1299114 [15:21] rvba, I tried different combos, all failed; in the web ui i could see required fields which were left blank to turn red and report validation errors (ip address and netmask I think) [15:22] dimitern: I'm trying to figure out what caused the error… but having the exact data that you submitted would help me. [15:23] dimitern: so far, I'm unable to reproduce the problem :/ [15:24] rvba, once the upload completes, i'll paste a link in the bug to the disk image + xml file for the machine, perhaps that'll help [15:27] roaksoax: python-seamicroclient MIR accepted. What will pull it into main? The next maas upload? Bug 1298130. [15:27] bug 1298130 in python-seamicroclient (Ubuntu) "[MIR] python-seamicroclient" [Critical,Fix committed] https://launchpad.net/bugs/1298130 [15:29] dimitern: you got the failure when using the CLI right? Don't you have the invocation line somewhere in your history? [15:29] rvba, both cli and api; let me check [15:29] rbasak: hey! thanks for taking care of it. And yes, it will be pilled by maas upload [15:30] rvba, example: maas maas-root networks create name=main ip=192.168.50.0 netmask=255.255.255.0 description="Main MAAS network" [15:32] dimitern: works for me in a dev env. http://paste.ubuntu.com/7185307/. I'll try with a package. [15:34] rvba, if you still can't repro it, try upgrading from the daily-ok [15:35] rvba, (i suspect my upgrade might be incomplete or something) [15:35] dimitern: you're getting this with the package from daily-ok? [15:36] rvba, no, that's from the daily-builds r2188, but i originally installed the daily-ok one and upgraded later [15:36] okay [16:05] hi allenap (or anyone), maas nodes when a network is bridged are supposed to talk to the world through a squid proxy, right? [16:06] tych0: Is that the cluster’s network, or the region? [16:07] i don't understand the question :-( [16:07] the cluster and the region are on the same box [16:07] it is the slave nodes that aren't running through a squid [16:07] There’s nothing in MAAS that says a node *must* talk to the world through squid. It is there as a service, and we set the proxy for apt (iirc) to point to it, but MAAS doesn’t enforce anything beyond that. [16:08] ok [16:08] so my nodes aren't talking through the apt proxy either [16:08] should i file a bug? [16:09] tych0: Yeah, that sounds like a bug. [16:09] ok === cmagina is now known as cmagina-away === cmagina-away is now known as cmagina === roadmr is now known as roadmr_afk === roadmr_afk is now known as roadmr === CyberJacob|Away is now known as CyberJacob === cmagina is now known as cmagina-away === cmagina-away is now known as cmagina === cmagina is now known as cmagina-away === cmagina-away is now known as cmagina === CyberJacob is now known as CyberJacob|Away === cmagina is now known as cmagina-away