[01:21] <mup> Bug #1510746 opened: Colorblind users can't tell which nodes are on or off in node list <MAAS:New> <https://launchpad.net/bugs/1510746>
[01:30] <mup> Bug #1510746 changed: Colorblind users can't tell which nodes are on or off in node list <MAAS:New> <https://launchpad.net/bugs/1510746>
[01:33] <mup> Bug #1510746 opened: Colorblind users can't tell which nodes are on or off in node list <MAAS:New> <https://launchpad.net/bugs/1510746>
[04:22] <mup> Bug #1489988 changed: Invalid BMC credentials on an already commissioned machine <cisco> <landscape> <MAAS:Expired> <https://launchpad.net/bugs/1489988>
[09:45] <dimitern> does anyone know how I can make my maas 1.9.0 (beta1+bzr4417) display "15.10" or "wily" boot images (i.e. I want to be able to use them)
[09:45] <dimitern> ?
[09:46] <dimitern> mpontillo, blake_r_, roaksoax, kirkland, ^^
[11:17] <mup> Bug #1503530 changed: [1.9.0 alpha3] allow users to view and edit MTU rate <networking> <ui> <ux> <MAAS:Won't Fix> <https://launchpad.net/bugs/1503530>
[11:17] <mup> Bug #1510891 opened: hover state on node networking no longer working (regression) <ui> <MAAS:Triaged by ricgard> <https://launchpad.net/bugs/1510891>
[11:23] <mup> Bug #1510891 changed: hover state on node networking no longer working (regression) <ui> <MAAS:Triaged by ricgard> <https://launchpad.net/bugs/1510891>
[11:23] <mup> Bug #1503530 opened: [1.9.0 alpha3] allow users to view and edit MTU rate <networking> <ui> <ux> <MAAS:Won't Fix> <https://launchpad.net/bugs/1503530>
[11:26] <mup> Bug #1503530 changed: [1.9.0 alpha3] allow users to view and edit MTU rate <networking> <ui> <ux> <MAAS:Won't Fix> <https://launchpad.net/bugs/1503530>
[11:26] <mup> Bug #1510891 opened: hover state on node networking no longer working (regression) <ui> <MAAS:Triaged by ricgard> <https://launchpad.net/bugs/1510891>
[11:29] <mup> Bug #1510891 changed: hover state on node networking no longer working (regression) <ui> <MAAS:Triaged by ricgard> <https://launchpad.net/bugs/1510891>
[11:29] <mup> Bug #1503530 opened: [1.9.0 alpha3] allow users to view and edit MTU rate <networking> <ui> <ux> <MAAS:Won't Fix> <https://launchpad.net/bugs/1503530>
[11:30] <alexlist> Hi... I have just upgraded my MAAS to 15.10, and wonder when boot resources for 15.10 will be available... http://maas.ubuntu.com/images/ephemeral-v2/releases/ only goes as far as vivid...
[11:32] <mup> Bug #1503530 changed: [1.9.0 alpha3] allow users to view and edit MTU rate <networking> <ui> <ux> <MAAS:Won't Fix> <https://launchpad.net/bugs/1503530>
[11:32] <mup> Bug #1510891 opened: hover state on node networking no longer working (regression) <ui> <MAAS:Triaged by ricgard> <https://launchpad.net/bugs/1510891>
[11:38] <lathiat> alexlist: for the moment there are daily images; http://maas.ubuntu.com/images/ephemeral-v2/daily/wily/amd64/20151019.2/
[11:38] <lathiat> no idea about the release images
[11:45] <alexlist> lathiat: thx
[12:29] <mup> Bug #1510917 opened: updating/modifying/assigning vlans, spaces, fabrics, subnets doesn't allow specifying names and lock to ID"s <MAAS:New> <https://launchpad.net/bugs/1510917>
[12:48] <Guest4327> my maas dashboard doesn't shows the enlisted nodes
[12:48] <Guest4327> in private network
[12:53] <dimitern> "More than one boot source is providing Ubuntu images. Image selection cannot be performed using the WebUI."
[12:53] <dimitern> that sucks pretty heavily :/
[12:59] <Guest4327> sorry i can able to access maas dashboard from public Ip
[12:59] <Guest4327> But whenever i tru to access it from maas server prinvate network i am gettin the error
[13:03] <dimitern> Guest4327, make sure both your maas cluster controller and the client machine you're accessing the dashboard from can access the private network
[13:08] <Guest4327> yes i can able to access all the private network
[13:09] <Guest4327> From private network i can able to open the MAAS server dashboard  but , it doen't show the enlisted nodes. Even i can able to see the cluster , image and network settings.
[13:10] <jam> dimitern: maybe you know. now that subnets can't be configured via the UI how do you enable management of a subnet in MaaS 1.9?
[13:10] <jam> In the old one you could select the network and tell it to do DNS and DHCP there
[13:10] <dimitern> jam, only with the CLI
[13:10] <jam> dimitern: sure, but *how*&
[13:10] <dimitern> jam, I'll tell you in a moment - checking
[13:11] <Guest4327> i configured all DHCP and DNS via web UI
[13:12] <jam> Guest4327: that was before maas 1.9
[13:12] <jam> they added a lot of richness to networking awareness, but didn't get the edit working via the web ui
[13:12] <Guest4327> i am using MAAS Version 1.8.2
[13:12] <dimitern> jam, hmm - looking at the CLI it seems there's no way at the moment - using the web ui on the cluster interfaces should work I think
[13:13] <jam> dimitern: ah, I was expecting something off of subnets, not cluster
[13:14] <dimitern> jam, it's quite confusing yeah
[13:15] <Guest4327> I have installed the ubuntu landscape auto pilot mode , there , i am getting the following error at least three machines with more than one HDD has been commioned
[13:15] <Guest4327> Even though i have 3 machines with 2 HDD
[13:17] <dimitern> Guest4327, are they commissioned and showing with 2 disks in the node listing?
[13:17] <Guest4327> yes it is showing all 2 HDD
[13:24] <dimitern> Guest4327, which version of maas is that?
[13:25] <Guest4327> MAAS Version 1.8.2
[13:29] <mup> Bug #1503530 opened: [1.9.0 alpha3] allow users to view and edit MTU rate <networking> <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1503530>
[13:30] <dimitern> Guest10359, I might be wrong, but I think autopilot needs maas 1.9+ (latest is beta1) to do proper storage management, rather than just listing
[13:32] <mup> Bug #1503530 changed: [1.9.0 alpha3] allow users to view and edit MTU rate <networking> <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1503530>
[13:35] <mup> Bug #1503530 opened: [1.9.0 alpha3] allow users to view and edit MTU rate <networking> <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1503530>
[13:36] <roaksoax> marka13: any luck?
[13:40] <roaksoax> marka13: 1. Do you have a proxy setting set in the MAAS Settings. If not, when you commission, what about tail -f /var/log/maas/proxy/*.log. Does commissioning try to obtain any packages that hit the proxy?
[13:40] <roaksoax> 2. What's the config in /etc/maas/regiond.conf and /etc/maas/clusterd.conf ?
[13:41] <mup> Bug #1510111 changed: Can't edit bond, LVM, bcache parameters <ui> <ux> <MAAS:Triaged by carlaberkers> <https://launchpad.net/bugs/1510111>
[13:46] <roaksoax> marka13: what's the output of: maas admin maas get-config name=http_proxy
[15:23] <marka13> roaksoax:  http://paste.ubuntu.com/12990270/
[15:24] <marka13> No I'm not behind a proxy
[15:26] <marka13> in cloud-init.log I am still seeing:  Oct 28 10:08:55 os-juju [CLOUDINIT] cc_rightscale_userdata.py[DEBUG]: Failed to get raw userdata in module rightscale_userdata
[15:27] <marka13> looks like the node is communicating with MAAS
[15:27] <marka13> tcp        0      0 10-0-0-20.maas:55273    10.0.0.10:iscsi-target  ESTABLISHED
[15:29] <marka13> should the server have a DNS entry at this point?  like node.maas A record
[15:43] <roaksoax> marka13: I wonder if this is the real error: TCP_MISS_ABORTED
[15:44] <marka13> but it is connected and I can ssh into the machine?
[15:44] <marka13> what would be causing that issue?
[15:44] <roaksoax> marka13: yeah, so, the squid proxy 1446045602.149 120026 10.0.0.20 TCP_HIT_ABORTED/000 0 GET http://archive.ubuntu.com//ubuntu/dists/trusty-updates/InRelease - HIER_DIRECT/2001:67c:1360:8c01::18 -
[15:49] <marka13> what would cause that?
[15:57] <roaksoax> marka13: asking internally
[15:59] <roaksoax> marka13: "Squid shows TCP_HIT_ABORTED (which means that the file was found in the cache, but the client aborted before completing the transfer):"
[16:00] <roaksoax> marka13: are the nodes VM's or physical hardware?
[16:01] <roaksoax> marka13: if they are VM's, how much RAM do they have?
[16:09] <mpontillo> jam: right, marking a subnet 'managed' from the subnet itself is something we want to do in the not-so-distant future
[16:11] <mpontillo> dimitern: I'm assuming you figured out that you need the images from 'releases' to 'daily' - though now that 15.10 is released, I suppose that shouldn't be necessary much longer!
[16:20] <dimitern> mpontillo, yeah - took me some time, but I managed to add the daily images as a new boot-source, added a new boot-source-selection for wily using that new source, and (eventually) all images were imported ok
[16:41] <roaksoax> marka13: i'm starting to think that the VM's don't have enough RAM
[16:45] <mup> Bug #1511027 opened: No DNS record added for deployed machine <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1511027>
[17:06] <SpeeR> I'm trying to setup a virtual maas node, after I start the installation and give the new VM the IP of the maas controller, it starts commissioning, reboots and says no bootable devices
[17:16] <roaksoax> SpeeR: commissioning doesn't caus eit to reboot. It tells it to poweroff the machine
[17:16] <roaksoax> SpeeR: you mean install ?
[17:18] <SpeeR> I can't start a commissioning with the machine in a running state for a vm
[17:19] <SpeeR> so I have to power it off first, and then tell it to commission the node which powers it on
[17:20] <SpeeR> this is definitely not a typical setup that I'm trying, I'm running maas on the bare metal, and trying to run a qemu node from the same server
[17:20] <marka13> Redsoax:  The VM's have 10GB of ram and these are the same nodes that were commissioning previously
[17:30] <marka13> the only difference in build is 1.9 beta 4 which I upgraded to beta 5 yesterday and then it broke
[17:40] <roaksoax> marka13: you mean alpha5 ?
[17:40] <roaksoax> marka13: maas 1.9.0beta1 was released tuesday
[17:44] <marka13> maybe that was it
[17:44] <marka13> MAAS Version 1.9.0 (beta1+bzr4417)
[17:47] <roaksoax> marka13: ok, so the issue might be that something is killing apt
[17:47] <roaksoax> marka13: i first thought this might be due to lack of ram memory
[17:47] <roaksoax> but if you say they have 10GB, then idk
[17:48] <roaksoax> but this: "1446045602.149 120026 10.0.0.20 TCP_HIT_ABORTED/000 0 GET http://archive.ubuntu.com//ubuntu/dists/trusty-updates/InRelease - HIER_DIRECT/2001:67c:1360:8c01::18 -"
[17:48] <roaksoax> might be telling that for whatever reason, the apt-get install that's done
[17:48] <roaksoax> is being aborted
[17:48] <roaksoax> or maybe, a networking issue
[17:48] <roaksoax> marka13: this is all IPv4 right?
[17:48] <roaksoax> marka13: no other DHCP server on the network?
[17:50] <roaksoax> marka13: if you do, on the commissioning environment: sudo apt-get -f install does something happen? what if you do: sudo apt-get update && sudo apt-get -f install
[17:52] <marka13> nope it's all internal on 1 esx machine
[17:54] <marka13> ubuntu@os-juju:~$ sudo apt-get -f install
[17:54] <marka13> sudo: unable to resolve host os-juju
[17:54] <marka13> Reading package lists... Done
[17:54] <marka13> Building dependency tree
[17:54] <marka13> Reading state information... Done
[17:54] <marka13> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[17:54] <marka13> ubuntu@os-juju:~$ sudo apt-get update
[17:54] <marka13> sudo: unable to resolve host os-juju
[17:54] <marka13> E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
[17:54] <marka13> E: Unable to lock directory /var/lib/apt/lists/
[17:55] <roaksoax> marka13: ok, so something is holding the apt lock
[17:55] <roaksoax> marka13: ps faux | grep apt
[17:55] <roaksoax> marka13: or ps faux | grep dpkg
[17:56] <marka13> ubuntu@os-juju:~$ ps faux | grep apt
[17:56] <marka13> ubuntu    1528  0.0  0.0  10460   936 pts/0    S+   17:56   0:00              \_ grep --color=auto apt
[17:56] <marka13> root      1406  0.0  0.0  29004  2324 ?        S    17:47   0:00      \_ apt-get --assume-yes -q update
[17:56] <marka13> root      1409  0.0  0.0  26676  1764 ?        S    17:47   0:00          \_ /usr/lib/apt/methods/http
[17:57] <marka13> it has internet connectivity too
[17:58] <roaksoax> marka13: so apt-get --assume-yes -q update -> that's still running
[18:00] <roaksoax> narindergupta: so it seems that the script is running
[18:00] <roaksoax> err
[18:00] <roaksoax> marka13: so it seems the script is running that, as it should
[18:01] <narindergupta> roaksoax, which issue we are discussing?
[18:01] <marka13> ya just not sure what happened between the two versions
[18:02] <roaksoax> narindergupta: typo!
[18:02] <narindergupta> roaksoax, so no worries
[18:03] <roaksoax> marka13: looking at the commit long, i don't see anything that should be affected
[18:03] <roaksoax> marka13: what does ifconfig show ?
[18:04] <marka13> it shows the ip which was leased from MAAS
[18:04] <marka13> IPv4
[18:04] <roaksoax> marka13: so, what about trying to clearing maas-proxy's cache and restarting it?
[18:04] <roaksoax> marka13: the cache is in /var/spool/maas-proxy/*
[18:05] <roaksoax> marka13: so cd /var/spool/maas-proxy/ && rm -rf *
[18:05] <roaksoax> marka13: then sudo service maas-proxy restart
[18:05] <roaksoax> marka13: that should clear the proxy cache
[18:05] <roaksoax> marka13: and then tail -f /var/log/maas/proxy/access.log while the node is commissioning and let's see what happens
[18:13] <marka13> Booted up and didn't see anything new in the access log
[18:14] <marka13> 1446056049.446 120100 10.0.0.20 TCP_MISS_ABORTED/000 0 GET http://archive.ubuntu.com//ubuntu/dists/trusty/InRelease - HIER_DIRECT/2001:67c:1360:8c01::19 -
[18:14] <marka13> that just showed up
[18:21] <roaksoax> marka13: ok, so that just seems like apt might be hanging for some reason and causing that
[18:26] <stokachu> marka13: can you post a screenshot of your entire /MAAS/settings page?
[18:27] <stokachu> roaksoax: he's still using 1.9 beta 5 as well
[18:27] <stokachu> not sure if any proxy code was changed between beta 4 - 5
[18:29] <roaksoax> stokachu: he is using beta1
[18:30] <roaksoax> stokachu: there's a proxy bug for beta2, or beta3, but won't affect operation actually
[18:31] <stokachu> ok
[18:33] <roaksoax> stokachu: seems that apt might just be getting stuck somewhere
[18:41] <roaksoax> marka13: do you have console logs?
[18:47] <roaksoax> marka13: did you set an upstream DNS ?
[18:47] <mup> Bug #1511071 opened: No way to disable the use of maas-proxy <MAAS:New> <https://launchpad.net/bugs/1511071>
[18:50] <mup> Bug #1511071 changed: No way to disable the use of maas-proxy <MAAS:New> <https://launchpad.net/bugs/1511071>
[18:53] <mup> Bug #1511071 opened: No way to disable the use of maas-proxy <MAAS:New> <https://launchpad.net/bugs/1511071>
[18:57] <marka13> Sorry, had to jump on a call
[18:57] <marka13> you want dmesg?
[19:01] <marka13> the settings page is pretty much stock I haven't touched anything except to ephemeral images to the dailies version
[19:02] <marka13> I do have an upstream dns
[19:02] <marka13> should I remove it?
[19:20] <marka13> The following NEW packages will be installed:
[19:20] <marka13>   freeipmi-common freeipmi-tools ipmitool libfreeipmi12 libipmiconsole2
[19:20] <marka13>   libipmidetect0 libopenipmi0 libperl5.18 libsensors4 libsnmp-base libsnmp30
[19:20] <marka13>   openipmi
[19:20] <marka13> 0 upgraded, 12 newly installed, 0 to remove and 0 not upgraded.
[19:20] <marka13> Need to get 3,612 kB of archives.
[19:20] <marka13> After this operation, 17.0 MB of additional disk space will be used.
[19:21] <marka13> WARNING: The following packages cannot be authenticated!
[19:21] <marka13>   libsensors4 libperl5.18 freeipmi-common ipmitool libopenipmi0 openipmi
[19:21] <marka13>   libfreeipmi12 libipmiconsole2 libipmidetect0 freeipmi-tools
[19:21] <marka13> E: There are problems and -y was used without --force-yes
[19:21] <marka13> saw that when I manually ran /var/lib/cloud/instance/scripts/user_data.sh
[19:36] <marka13> I'm looking in the upstart logs - see quite a few instances of can't resolve host <hostname>
[19:36] <marka13> I digged against the maas dns and no entry for my host
[19:37] <marka13> does it get registered in DNS on commissioning when it's dhcp boot?
[20:04] <marka13> Request to http://10.0.0.10/MAAS/metadata//2012-03-01 failed   http error 400 bad request
[20:04] <marka13> What causes that?  I was able to get past the cloud-init part
[20:04] <marka13> but doesn't seem to be downloading and applying patches like it would normally
[20:05] <marka13> looks like it hits those bad requests and it proceeds to shutdown
[20:14] <marka13> ubuntu@os-juju:~$ wget http://10.0.0.10/MAAS/metadata//2012-03-01/
[20:14] <marka13> --2015-10-28 15:08:25--  http://10.0.0.10/MAAS/metadata//2012-03-01/
[20:14] <marka13> Connecting to 10.0.0.10:80... connected.
[20:14] <marka13> HTTP request sent, awaiting response... 401 UNAUTHORIZED
[20:36] <roaksoax> 16:10 < marka13> Request to http://10.0.0.10/MAAS/metadata//2012-03-01 failed   http error 400 bad request -> running manually you don't have the correct credentials that are owned by cloud-init
[20:36] <roaksoax> marka13: but the issue is apt getting stuck some were
[20:36] <roaksoax> marka13: i think the issue is this: 15:27 < marka13> WARNING: The following packages cannot be authenticated!
[20:41] <marka13> well I got the process to move along further by disabling IPv6
[20:42] <marka13> but now I see those error messages
[20:44] <marka13> looks like cloud init finishes now.  But the HTTP 400 was during cloud init, I manually ran it and ya I would expect the 401 then
[20:44] <marka13> curious why it's a bad request?
[20:44] <marka13> Be back tomorrow, have to head home
[20:44] <marka13> thanks for the help roaksoax
[20:45] <roaksoax> marka13: no prob!
[23:37] <RustyChapin> hey there
[23:37] <RustyChapin> is anyone alive?