[05:21] <mup> Bug #1431145 was opened: Commissioning failures due to transaction errors <MAAS:New> <https://launchpad.net/bugs/1431145>
[05:27] <mup> Bug #1431145 changed: Commissioning failures due to transaction errors <MAAS:New> <https://launchpad.net/bugs/1431145>
[05:39] <mup> Bug #1431150 was opened: While trying to load the node details page, logfile shows weird error <maas (Ubuntu):New> <https://launchpad.net/bugs/1431150>
[05:39] <mup> Bug #1431145 was opened: Commissioning failures due to transaction errors <MAAS:New> <https://launchpad.net/bugs/1431145>
[06:10] <mup> Bug #1431156 was opened: When a custom image is added, multiple OS entries are created for it <MAAS:New> <https://launchpad.net/bugs/1431156>
[11:10] <mup> Bug #1431279 was opened: MAAS python scripts do not show the line numbers and the script name when errors are encountered <maas (Ubuntu):New> <https://launchpad.net/bugs/1431279>
[13:14] <mup> Bug #1431347 was opened: Changing cluster interface details in web UI leads to rdnc failure <MAAS:New> <https://launchpad.net/bugs/1431347>
[13:16] <murphyslaw_> Hi, is this the right place to ask about openstack-juju?
[13:23] <rbasak> murphyslaw_: in relation to MAAS. Otherwise maybe #ubuntu-server or #juju?
[13:23] <murphyslaw_> well im trying to install maas using openstack-juju
[13:25] <murphyslaw_> rbasak: juju doesn;t honor the http proxy setting, nor the agent-metadata-url: or image-metadata-url: setting in environments.yaml
[13:26] <murphyslaw_> rbasak: i’d like to try the unstable version but not sure where to start. should i try and compile the cloudinit stuff from source, or use the unstable tree?
[13:27] <murphyslaw_> rbasak: alternatiovely i could try and generate my own tools directory, but i can’t find any documentation on how to do that
[13:28] <rbasak> murphyslaw_: are you sure this is a Juju issue? What do you mean by "doesn't honor"? There are many stages during bootstrap, and it's worth being completely clear on what component is doing what.
[13:29] <rbasak> If for example Juju requests a node from MAAS, then initially it's MAAS' HTTP proxy setting that is important, not Juju's
[13:30] <rbasak> OTOH once the machine is booted, then it's up to Juju.
[13:30] <murphyslaw_> rbasak: environments.yaml contains: environments->maas-> and then a dict with: apt-http-proxy: 'http://172.25.138.248:3128/'   — agent-metadata-url: http://streams.canonical.com/tools — image-metadata-url: http://cloud-images.ubuntu.com/releases
[13:31] <rbasak> I'm not sure, sorry.
[13:32] <murphyslaw_> yes both proxies are set
[13:32] <murphyslaw_> rbasa: is there a way to set a proxy for juju apart from the apt one?
[13:33] <murphyslaw_> rbasak: juju then runs this: Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP %{http_code}; time %{time_total}s; size %{size_download} bytes; speed %{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz <[https://streams.canonical.com/juju/tools/releases/juju-1.21.3-trusty-amd64.tgz]>
[13:34] <murphyslaw_> oh wait a minute
[13:34] <rbasak> murphyslaw_: oh, OK. That's definitely a Juju thing then if it's asking for tools. People in #juju may know more.
[13:34] <murphyslaw_> cool thanks
[13:34] <rbasak> murphyslaw_: but, note that you may need a different setting for HTTPS.
[13:34] <rbasak> Usually it's a separate key/env variable.
[13:35] <murphyslaw_> yh i just dont’t know how to set it
[13:35] <murphyslaw_> ok i’ll head over to #juju many thanks
[13:36] <rbasak> murphyslaw_: https-proxy
[13:36] <rbasak> murphyslaw_: from https://jujucharms.com/docs/config-general
[13:38] <murphyslaw_> nice
[13:38] <murphyslaw_> Tx!
[13:53] <mup> Bug #1431360 was opened: maas cli writes deprecation warning to stdout <MAAS:New> <https://launchpad.net/bugs/1431360>
[14:06] <kiko> murphyslaw_, did that work?
[14:10] <murphyslaw_> kiko: it got a bit further :)
[14:11] <murphyslaw_> kiko: now battling with NTP time and date
[14:11] <murphyslaw_> kiko: 2015-03-12 13:40:14 ERROR juju.cmd supercommand.go:323 gomaasapi: got error back from server: 401 OK (Authorization Error: 'Expired timestamp: given 1426167614 and now 1426168272 has a greater difference than threshold 300')
[14:23] <mup> Bug #1431379 was opened: cannot add boot-source-selections immediately after boot-source <MAAS:New> <https://launchpad.net/bugs/1431379>
[14:44] <murphyslaw_> kiko: I can now bootstrap the environment. but how do i get the Landscape OpenStack Autopilot installed on the bootstrapped machine?
[14:46] <murphyslaw_> kiko: when I use openstaclk-install I have no way to specify http-proxy or https-proxy
[14:47] <murphyslaw_> kiko: the command I’m running is: “sudo openstack-install -c ~/.cloud-install/config.yaml --http-proxy 'http://sj-il-control.cisco.com:3128/' --https-proxy='http://sj-il-control.cisco.com:3128/'” but the command line options are installed, and setting them from config.yaml isn’t working
[14:48] <murphyslaw_> kiko: command line options are *ignored* i mean
[15:28] <AskUbuntu_> Landscape is not running after a reboot with juju-core 1.20.x | http://askubuntu.com/q/596004
[22:03] <mup> Bug #1421377 changed: "MAAS failed to start" recurs if postgresql is stopped <MAAS:Triaged> <maas (Ubuntu):Confirmed> <https://launchpad.net/bugs/1421377>
[22:03] <mup> Bug #1421377 changed: "MAAS failed to start" recurs if postgresql is stopped <MAAS:Triaged> <maas (Ubuntu):Confirmed> <https://launchpad.net/bugs/1421377>
[22:03] <mup> Bug #1431578 was opened: maas is showing all interfaces with active ethernet link as connected after commissioning <oil> <MAAS:New> <https://launchpad.net/bugs/1431578>