[03:28] <mup> Bug #1573982 opened: LVM boot problem - volumes not activated after upgrade to Xenial <lvm2 (Ubuntu):Confirmed> <maas (Ubuntu):New> <https://launchpad.net/bugs/1573982>
[15:52] <bladernr> Hey, can someone help me debug a commissioning issue w/ MAAS 2.3.0~beta2??
[15:53] <bladernr> I'm trying to commission a node but commissioning fails because it's getting 401 errors from $MAAS_IP/MAAS/metadata/2012-03-01/
[15:53] <bladernr> I can access that page via a browser and the message returned is: No authorization header received.
[15:54] <bladernr> I've seen a few bugs via the goog that have hte same error message, but they all look like they have different causes, so not terribly helpful (that I could determine).
[16:02] <roaksoax> bladernr: i'd recommend you to upgrade to beta3
[16:03] <roaksoax> bladernr: the second, check that /etc/maas/rackd.conf points to the rgith IP and it is an IP that the machines can talk to
[16:05] <bladernr> roaksoax, ok, upgrading first. thanks
[16:15] <dnegreira> Hi everyone, I am hitting exactly the same issue as a bug that was closed: https://bugs.launchpad.net/maas/+bug/1583093. I do currently have several VLANS on the interface but mtu is 1500. I can see the nodes getting DHCP and I can ping them from the MAAS but I am unable to ssh into the nodes.
[16:15] <dnegreira> current maas version is 2.2.2-6099-g8751f91-0ubuntu1~16.04.1
[16:18] <dnegreira> if I  try to ssh from the maas controller towards the nodes I always get a connection reset
[16:21] <dnegreira> and I am currently unable to login via console as well so its difficult to troubleshoot from a node point of view :/
[16:48] <roaksoax> dnegreira: the way maas makes a machine deployed is when cloud-init, after booting for the first time to maas, contacts MAAS and gathers the user data
[16:48] <roaksoax> dnegreira: what could be happening is that your amchine is not contacting maas, hence, making it failed deployment
[16:48] <roaksoax> dnegreira: are you adding any user data? do you see any errors on regiond.log ?
[16:50] <dnegreira> I am even embarassed to say what was wrong
[16:50] <dnegreira> wrong gateway on the vlan definition :)
[16:51] <dnegreira> sorry for the noise..
[16:53] <roaksoax> no worries :)
[17:20] <mup> Bug #1730456 opened: Cannot commission node due to 401 errors fetching metadata. <MAAS:Incomplete> <https://launchpad.net/bugs/1730456>
[18:20] <mup> Bug #1730474 opened: [2.x] MAAS region startup sequence leads to race conditions <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1730474>
[18:52] <roaksoax> c/win 3
[19:20] <mup> Bug #1730481 opened: [2.3, HWTv2] When 'other' test fails, node listing incorrectly shows two icons <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1730481>
[19:20] <mup> Bug #1730485 opened: [2.2+, HWT] badblocks fails with LVM <internal> <MAAS:New> <https://launchpad.net/bugs/1730485>
[19:35] <mup> Bug # changed: 1418044, 1696122, 1716328, 1718044, 1718776, 1718779, 1721827, 1721887, 1722665, 1723944, 1724402, 1724627, 1727360, 1727576, 1727962, 1728300, 1728302, 1729857, 1729902
[19:44] <mup> Bug # opened: 1418044, 1696122, 1716328, 1718044, 1718776, 1718779, 1721827, 1721887, 1722665, 1723944, 1724402, 1724627, 1727360, 1727576, 1727962, 1728300, 1728302, 1729857, 1729902
[19:50] <mup> Bug # changed: 1418044, 1696122, 1716328, 1718044, 1718776, 1718779, 1721827, 1721887, 1722665, 1723944, 1724402, 1724627, 1727360, 1727576, 1727962, 1728300, 1728302, 1729857, 1729902
[20:05] <mup> Bug #1573982 opened: LVM boot problem - volumes not activated after upgrade to Xenial <MAAS:New> <lvm2 (Ubuntu):Confirmed> <https://launchpad.net/bugs/1573982>
[20:05] <mup> Bug #1573982 changed: LVM boot problem - volumes not activated after upgrade to Xenial <MAAS:New> <lvm2 (Ubuntu):Confirmed> <https://launchpad.net/bugs/1573982>
[20:17] <mup> Bug #1573982 changed: LVM boot problem - volumes not activated after upgrade to Xenial <MAAS:New> <lvm2 (Ubuntu):Confirmed> <https://launchpad.net/bugs/1573982>
[20:17] <mup> Bug #1573982 opened: LVM boot problem - volumes not activated after upgrade to Xenial <MAAS:New> <lvm2 (Ubuntu):Confirmed> <https://launchpad.net/bugs/1573982>
[20:20] <mup> Bug #1573982 opened: LVM boot problem - volumes not activated after upgrade to Xenial <MAAS:New> <lvm2 (Ubuntu):Confirmed> <https://launchpad.net/bugs/1573982>
[20:20] <mup> Bug #1730493 opened: MAAS is dropped in grub menu when booting in UEFI mode, and Secure Boot not working  <MAAS:New> <https://launchpad.net/bugs/1730493>
[20:20] <mup> Bug #1573982 changed: LVM boot problem - volumes not activated after upgrade to Xenial <MAAS:New> <lvm2 (Ubuntu):Confirmed> <https://launchpad.net/bugs/1573982>
[20:29] <mup> Bug #1730493 changed: MAAS is dropped in grub menu when booting in UEFI mode, and Secure Boot not working  <MAAS:New> <https://launchpad.net/bugs/1730493>
[20:35] <mup> Bug #1730493 opened: MAAS is dropped in grub menu when booting in UEFI mode, and Secure Boot not working  <MAAS:New> <https://launchpad.net/bugs/1730493>
[23:05] <mup> Bug #1730524 opened: Failed commissioning leaves machine completely cut off from MAAS <hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1730524>
[23:08] <mup> Bug #1730525 opened: maas 2.2.2 unable to disk erase artful deployment  <MAAS:New> <https://launchpad.net/bugs/1730525>
[23:11] <mup> Bug #1730525 changed: maas 2.2.2 unable to disk erase artful deployment  <MAAS:New> <https://launchpad.net/bugs/1730525>
[23:17] <mup> Bug #1730525 opened: maas 2.2.2 unable to disk erase artful deployment  <MAAS:New> <https://launchpad.net/bugs/1730525>


[04:30] <riegersn> what type of devices can ubuntu mobile be installed on? anything available now?
[08:49] <tkamppeter> Anyone here who packages bluez-libs or bluez-utils
[09:04] <persia> tkamppeter: A few people have touched it.  What do you seek?
[09:04] <tkamppeter> bug 206579
[09:05] <tkamppeter> persia I have to change the title: s/long/infinite/
[09:08] <davmor2> tkamppeter: probably a daft question but do you have a time comparison?  I.E. how long does it take for your phone or other device to connect?
[09:15] <tkamppeter> davmor2, as you can see in the bug report the bluetooth backend exits after 10 seconds if there is at least one Bluetooth printer present.
[09:16] <tkamppeter> davmor2, if there is no Bluetooth printer at all, the bluetooth backend never exits (I have left it running up to around 12 minutes and then killed it).
[09:17] <tkamppeter> davmor2, this makes general device discovery always taking more than 30 seconds, as CUPS kills backends not exiting after 30 seconds.
[09:38] <davmor2> :(
[15:28] <st23am> exit
[19:00] <Maxro> hi guys .. could anybody say me if its possible to get a pda working with ubuntu mobil ?! .. :-[
[19:08] <Maxro> ?!
[19:18] <GrueMaster> Maxro:  Read the FAW listed at the top of the IRC channel.
[19:18] <GrueMaster> S/FAW/FAQ
[19:19] <Maxro> thanks
[20:03] <Mapping> Any knows will ubuntu mid works with tabletpc devices
[21:34] <energY> Hello
[21:34] <energY> I need to know what the cheapest ubuntu mobile is!
[21:36] <energY> HTC Touch Diamond
[21:36] <energY> Can I have it on it?


[19:06] <highvoltage> mhall119: what was that font you suggessted we install in edubuntu by default? I noted it in multiple places, but I also added more fonts to the list so now I can't remember which one it is :)
[19:08] <mhall119> Andika
[19:08] <mhall119> though I asked about it in #ubuntu-accessibility, and some there thought it maybe wasn't as helpful as advertised
[19:08] <highvoltage> hmm, that certainly sounds familiar bit it's on none of my lists :)
[19:08] <highvoltage> *adds*