[13:03] <acheronuk> jbicha: currently sitting in ER room where reliv
[13:04] <acheronuk> Relative taken ill, so may not get ubiquity stuff done for tommorow. Or at least not until late tommorow
[13:05] <jbicha> ok, take care
[13:06] <jbicha> let's try to get it done this week at least
[13:08] <acheronuk> It will be.


[00:18] <mup> Bug #1686244 opened: [web UI] Storage modification message is confusing <docteam> <MAAS:New> <https://launchpad.net/bugs/1686244>
[00:18] <mup> Bug #1686246 opened: [CLI help] set-storage-layout says Allocated when it should say Ready <docteam> <MAAS:New> <https://launchpad.net/bugs/1686246>
[00:49] <mup> Bug #1686248 opened: Node configuration user collisions are possible <docteam> <MAAS:New> <https://launchpad.net/bugs/1686248>
[14:02] <mup> Bug #1686412 opened: Add ability to change PXE boot behavior of a device <MAAS:Triaged> <https://launchpad.net/bugs/1686412>
[14:37] <vasey> mpontillo: i installed python3-pyvmomi, and i'm getting this message when i try to connect : "Error:__init__() takes 1 positional argument but 2 were given"
[14:37] <vasey> as well as a "power error" message when i try to check the power state
[15:03] <vasey> mpontillo: and now i'm seeing that certificate error in my events log for that node: https://pastebin.com/eYzdxecn
[15:37] <xygnal> mpontillo:  I see a code merge for our problem.  is that still being tested?  its quite small so tempted to apply it to ours and see if we can verify the results
[15:54] <roaksoax> xygnal:  i just uploaded to a ppa, if you wanna test from there ?
[15:57] <roaksoax> xygnal: but if you give us some time to test that'd be good
[16:08] <xygnal> roaksoax what kind of time are you looking for to incorporate this into RC3 and release it?  We have about 3 weeks time before we need to be ready for prod deployments and we want to be sure this is wrapped up.
[16:11] <roaksoax> xygnal: it is already in RC3 milestone
[16:11] <roaksoax> just need to test it first
[16:11] <roaksoax> before I can say there's no regressions
[16:11] <xygnal> roaksoax what is the *goal* date for RC3 release?
[16:11] <xygnal> what are you aiming for
[16:12] <roaksoax> xygnal: we are targetting a release for the end of the week. It may be final or it may be rc3
[16:12] <xygnal> roaksoax thanks much.
[17:44] <mup> Bug #1623851 changed: Tables not responsive for mobile <ui> <MAAS:Fix Released> <https://launchpad.net/bugs/1623851>
[17:44] <mup> Bug #1686464 opened: [2.2, API] set-storage-layout fails silently when invoked by a non-admin <api> <api-ux> <docteam> <MAAS:Triaged> <https://launchpad.net/bugs/1686464>
[17:52] <mpontillo> xygnal: I think patching your setup with the diff from that merge proposal would be a low-risk thing to do. please do give it a try.
[17:52] <xygnal> mpontillo: thanks, will test it out this week.
[18:59] <mup> Bug #1686485 opened: cc_ntp fails to work when deploying ubuntu-core <cloud-init:New> <MAAS:Triaged> <https://launchpad.net/bugs/1686485>
[20:26] <mary_> hello I have a problem with maas, for some reason, the rack controller fails
[20:26] <mary_> theyre both on the same machine
[20:29] <mary_> can anyone help me
[20:29] <catbus1> mary_: first post the error message please
[20:30] <mary_> there's no error message just a red cross on the gui in front of the rack controller
[20:30] <roaksoax> mary_: go to the rack controller, and see the status of it
[20:30] <roaksoax> does it show why it is red ?
[20:31] <mary_> on the images status it says region importing and on the boot images status tab it says out of sync
[20:34] <mary_> I dont get it, I did configure the url
[20:35] <mary_> and I did the same steps I did before but last time, it worked
[21:05] <mup> Bug #1686516 opened: [2.2, trunk] Pod remote storage listing shows blank for pods with out remote storage <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1686516>
[21:34] <xygnal> mpontillo: that works, final address is correct
[21:34] <xygnal> mpontillo new problem.  observed address does not go away, so system keeps booting old temporary address,
[21:34] <xygnal> will that fix itself when temporary lease expires?
[21:35] <xygnal> hm...
[21:35] <mup> Bug #1646847 changed: Multi interface issue while charm deployed on centos image <cloud-images:New> <juju:Invalid> <MAAS:Won't Fix> <https://launchpad.net/bugs/1646847>
[21:35] <mup> Bug #1658718 changed: MAAS 2.1.3 Centos 7 image deployment fails <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1658718>
[21:35] <roaksoax> xygnal: is the machine set as 'dynamic' or is it set as 'auto assign' ?
[21:36] <roaksoax> xygnal: and what do you mean by keeps booting ?
[21:36] <xygnal> ah, sorry bad phrasing.  DHCP-aquires the old dynamic range address
[21:36] <xygnal> if you look in that subnets view, you can see that same node has an observed address and automatic address
[21:37] <xygnal> observed is the dynamic
[21:37] <roaksoax> xygnal: that will clear itself automatically
[21:37] <xygnal> yes but wasnt that 2 hours?
[21:37] <xygnal> for the default expire
[21:37] <roaksoax> xygnal: the dynamic range expires 10 minutes
[21:38] <xygnal> oh wow ok, understood
[21:38] <roaksoax> xygnal: what may be failing is dhcp tells maas about a lease expiring
[21:38] <roaksoax> and maas removes that from tracking
[21:38] <roaksoax> xygnal: but has the deployed machine been successfully configuired ?
[21:45] <xygnal> roaksoax maas has correct config, but node boots up with build IP instead of its assigned IP.
[21:45] <xygnal> shutting them down for 10 minutes, power off
[21:45] <xygnal> to verify that clears
[21:45] <roaksoax> xygnal: if e/n/i is configured w/ static IP address, how will it boot from an address it gets from dhcp ?
[21:45] <xygnal> I suspect the pre-existing lease is not given a chance to expire
[21:46] <xygnal> auto-assign
[21:46] <xygnal> your auto-assign is static dhcp, if I recall correctly
[21:46] <roaksoax> xygnal: auto-assign will configure /etc/network/interfaces with 'iface X inet static'
[21:46] <roaksoax> dhcp will configure /e/n/i w/ 'iface X inet dhcp'
[21:46] <xygnal> then its NOT compatibe with a custom image, which I could have sworn mpontillo steered me the other way pon
[21:47] <roaksoax> xygnal: is this an Ubuntu custom image?
[21:47] <xygnal> CentOS only for us
[21:47] <xygnal> cloud-init enabled image
[21:47] <roaksoax> ah right
[21:47] <roaksoax> so MAAS doesn't yet support network config for centos images
[21:48] <roaksoax> but it will do soon
[21:48] <xygnal> alright I thought that before, but somehow got a mixed message
[21:48] <roaksoax> that said
[21:48] <roaksoax> MAAS adds a hostmap
[21:48] <xygnal> then we go back to my plan before that
[21:49] <xygnal> which was using DHCP but changing the IP after deploy (Via post-script) to a reserved range address
[21:49] <roaksoax> xygnal: so if eth0 - auto-assign, MAAS will add a hostmap for eth0's MAC + IP assigned by MAAS
[21:49] <roaksoax> xygnal: but, unless isc-dhcp is ignoring the hostmap
[21:49] <xygnal> hm... what will this hostmap result in?
[21:50] <roaksoax> xygnal: the hostmap should result in the machine obtaining the IP as per 'auto-assign' and not form dynamic range
[21:50] <roaksoax> xygnal: if you do dhclient on your system for eth0... does it get the right IP ?
[21:50] <xygnal> roaksoax: no, it gets the dynamic/observed ip
[21:51] <xygnal> roaksoax but in the UI it has an auto-assigned address in the proper range for auto-assign
[21:51] <xygnal> roaksoax: if that is not supported, why does it pick an auto assign?
[21:51] <wasosa> Hi all. I'm looking for some help deploying a node with maas (just upgraded to 2.1.5+bzr5596-0ubuntu1~16). Though the web UI tells me the node is 'Ready', it also warns me: No storage information. Commissioning this node will gather the storage information.
[21:51] <xygnal> I would expect to be told NO
[21:51] <roaksoax> xygnal: check your isc-dhcp config
[21:52] <roaksoax> xygnal: you should see the hostmap there
[21:52] <roaksoax> xygnal: /var/lib/maas/dhcpd.conf
[21:52] <roaksoax> xygnal: my guess is that isc dhcp is preferring the address from the dynamic range rather than tha hostmap address
[21:52] <roaksoax> xygnal: what if you clean your leases file ?
[21:53] <roaksoax> xygnal: try cleaning the leases file, then force the interface to re-obtain an IP from isc-dhcp and see if it gets the right address ?
[21:53] <xygnal> roaksoax yes
[21:53] <xygnal> there is a host map
[21:53] <xygnal> I powered the nodes down in the hope that the 10 minute lease woud expire
[21:54] <xygnal> if a lease is already alive, a new hostmap wont matter will it?  or should the old lease be overridden?
[21:55] <xygnal> confirmed observed lease is gone
[21:55] <xygnal> powered back up
[22:03] <wasosa> Hi all. I'm looking for some help deploying a node with maas (just upgraded to 2.1.5+bzr5596-0ubuntu1~16). The web UI tells me the node is 'Ready', but warns me: No storage information. Commissioning this node will gather the storage information. As best as I can tell, the block-device output is good. The only hits I found with similar problems had to do with vms rather than real hardware (I'm attempting to deploy an Intel SkullCanyon
[22:03] <wasosa> I'd appreciate any help anyone can provide. Thanks!
[22:05] <roaksoax> xygnal: did it get new IP ?
[22:05] <roaksoax> wasosa: that means that no storage was discovered during commissioning
[22:06] <roaksoax> wasosa: do you have any specific storage in this machine?
[22:06] <xygnal> roaksoax I seem to be a little confused, i was testing two boxes.   Back just one now.  I dont seem to have a hostmap in dhcpd despite deploying as auto-assign
[22:06] <xygnal> there is a hostmap in there for another build that *I* did not build, i am checking to see if that one was different somehow
[22:08] <wasosa> roaksoax: Yes, the machine has one nvme drive, and it looks like that's showing up properly in the 00-maas-07-block-devices.out listed under 'Machine output'
[22:08] <wasosa> roaksoax: (thanks for jumping in, btw)
[22:09] <roaksoax> wasosa: are you commissioning with Xenial? go to the settings page, to the commissioning section, and select xenial for commissioning
[22:11] <wasosa> roaksoax: yes I am, that secion reads: Default Ubuntu release used for commissioning: Ubuntu 16.04 LTS "Xenial Xersus" (and I can't change it).
[22:15] <wasosa> roaksoax: the output of the block devices caputred during commissioning looks sane to me, but I haven't been able to find the problem yet. I can share that output here if you'd like.
[22:17] <xygnal> roaksoax: think i found the problem.  its pxe booting them.  not sure why its responding to taht, as they  are 'deployed' status.
[22:23] <mpontillo> xygnal: currently MAAS will always respond to a PXE boot, but if the machine is deployed the PXE boot payload will instruct the node to boot from its local disk
[22:24] <xygnal> mpontillo: I will verify that behavior, ty
[22:24] <mpontillo> xygnal: when the node PXE boots it should receive the IP address assigned via the static lease installed by auto-assignment
[22:25] <xygnal> mpontillo: that it does not, bit the implied host map in dhcpd.conf is not there either
[22:25] <xygnal> despite that, its in deployed status
[22:25] <xygnal> and has an Assigned up
[22:25] <xygnal> IP*
[22:25] <xygnal> yes i just booted local HD
[22:25] <xygnal> same result
[22:25] <xygnal> there is no hostmap so there is no static entry
[22:26] <xygnal> i do see one that was build yesterday pre-fix that now suddenly has correct addrwess
[22:26] <xygnal> and is working
[22:26] <xygnal> we are slowing down for the day so, we'll do some more exhaustive testing on this and report back tomorrow.  thanks for the help.
[22:27] <mpontillo> xygnal: thanks; I'd investigate if the DHCP configuration is not being properly updated when the IP address is assigned, then. thanks for your testing!


[00:18] <BenC> bdmurray: I'm pushing a change to enable usb persistent, which might help
[00:53] <Kano> hi, why are so many old ide drivers enabled? i prefer a config completely without CONFIG_IDE...
[00:54] <Kano> otherwise some new laptops dont boot at all
[00:54] <BenC> Kano: i haven't seen evidence that an ide driver being enabled keeps a new laptop from booting
[00:54] <BenC> Kano: and not all ide drivers/chipsets are replaced by libata-pata ones
[00:54] <Kano> one new samsung laptop only boots with that specific config
[00:55] <Kano> then the generic pata works in most cases
[00:55] <BenC> point me to a bug report or more information
[00:55] <BenC> Kano: we can't work 'in most cases'
[00:55] <Kano> kanotix thorhammer rc7 used a kernel completly without config_ide and there are only very few bad reports
[00:55] <BenC> especially if 'most cases' == regressions
[00:55] <BenC> oh well, every dist is different
[00:56] <Kano> it is based on ubuntu git 2.6.24 kernel
[00:56] <BenC> i'd much rather find out why the samsung couldn't boot in our current config
[00:56] <BenC> Kano: we are less than 3 months from release, too late to discuss now about disabling ide
[00:57] <Kano> well i do that in my mod then. before you release i use etch as base and only a modified kernel
[00:57] <BenC> if you have specific information about the problem you are talking about, then i can look into it...otherwise this is a waste of time...again
[00:57] <JanC> I have at least one desktop system (P3 on an MSI mobo with Via chipset) that still has /dev/hd* devices in gutsy...
[00:57] <ln-> besides, you cannot expect ubuntu to run on every machine.
[00:58] <Kano> btw. did you test the amd64 desktop iso?
[00:58] <Kano> it does not show any splash
[00:58] <JanC> an from what I can see, this is not uncommon for older systems
[00:58] <Kano> i386 does
[00:58] <BenC> Kano: so you don't have information on this samsung/
[00:59] <BenC> Kano: i tested it today, fresh install, and it has working splash
[00:59] <Kano> BenC: it is not my laptop,but when the user is online i can talk to him
[00:59] <Kano> why fresh install, i talk of the live cd
[01:00] <BenC> Kano: uh, because i did an install of a live cd...was pretty sure that was cleae
[01:00] <Kano> also do you think disabling alsa in the kernel is a good move?
[01:00] <BenC> clear
[01:00] <Kano> maybe depending on your gfx card
[01:00] <Kano> this was x700 se
[01:00] <Kano> ati
[01:00] <BenC> this was an ati as well, don't have the exact chipset, but it was mobility
[01:01] <BenC> Kano: not sure what you mean by disabling alsa
[01:01] <Kano> one of the last changes
[01:01] <Kano> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commit;h=255995ce42b024e084500e570ae3e357f7647480
[01:01] <BenC> if that's been done, it's because alsa will be moved to lum
[01:01] <Kano> yes but lum does not contain all
[01:02] <Kano> also when you compile external modules which would provide alsa sound that will not work
[01:02] <Kano> expect the ones from alsa
[01:03] <BenC> we know this, and are providing the headers for the lum modules separately
[01:03] <Kano> example
[01:03] <Kano> CONFIG_VIDEO_SAA7134_ALSA=m
[01:03] <Kano> this is the sound module for a video card
[01:03] <Kano> not in alsa at all
[01:03] <Kano> same for cx88-alsa (ok, maybe not so often needed as dvb)
[01:04] <BenC> we know this, and are going to work on making sure everything is there
[01:04] <Kano> you could add then em8300 too
[01:04] <BenC> we spent lots of time at uds discussing this exact situation
[01:04] <Kano> maybe let it default to oss
[01:04] <Kano> do you know that module?
[01:05] <BenC> look, without sounding too irritable, i have better things to do than answer a million questions from you right now
[01:05] <Kano>  cvs -z3 -d:pserver:anonymous@dxr3.cvs.sourceforge.net:/cvsroot/dxr3 co -P
[01:05] <Kano> em8300
[01:05] <Kano> needed for dxr3 and similar cards
[01:06] <Kano> modules dir
[01:06] <Kano> you could add the firmware too
[01:06] <BenC> you could spend a little time cloning our tree, adding it, and requesting a pull
[01:07] <BenC> we do have lots of other things to tend to as well
[01:07] <Kano> sure
[01:08] <Kano> that and dmraid45 is missing, then you only need a cooler kernelconfig ;)
[01:09] <Kano> saily there is no official dmraid patch against 2.6.24 yet
[01:10] <Kano> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/97655
[01:10] <ubotu> Launchpad bug 97655 in linux-source-2.6.20 "dmraid45 target please" [Wishlist,Won't fix]
[01:10] <Kano> the changes for dmraid work, but i did it for dmraid rc14, rc13 is outdated
[01:10] <ln-> Kano: you are wasting your time.
[01:11] <Kano> you dont want raid5 ?
[01:11] <ln-> no.
[01:11] <Kano> stupid
[07:44] <kraut> moin
[15:17] <Kano> rtg: Blacklisted bcm43cc and prism54?
[15:17] <Kano> the module is bcm43xx
[15:18] <Kano> also blacklisting would not help for discover
[15:18] <maks_> disabled in debian :)
[15:18] <Kano> yes but not in ubuntu
[15:18] <BenC> I don't think we really use discover
[15:18] <maks_> BenC: you own me an initramfs-tools sync :)
[15:19] <maks_> Kamion dude did the klibc part
[15:19] <Kano> BenC: saidly it is installed by default by live-helper
[15:19] <BenC> maks_: ah, we do need to sync that
[15:19] <maks_> xorg should no longer need that crap
[15:20] <BenC> Kano: used and installed are two different things
[15:20] <maks_> discover usualy comes with an init script
[15:20] <maks_> BenC: yep, that be cool
[15:45] <laga> any ETA on the new kernel upload to hardy?
[15:48] <rtg> laga: been waiting for the Alpha stuff to thaw.
[15:54] <laga> are there daily kernel builds on a ppa or something like that?
[15:54] <laga> otherwise, i'll just do a local build and push to my repo


[21:50] <infinity> slangasek: ^-- New base-files for your point release.
[21:55] <phillw> infinity: do you know if linux-ppc [powerpc] (saucy-proposed) [3.11.0-0.1] is the kernel that will get ppc desktops back working?
[21:56] <infinity> phillw: Should do, yes.
[21:56] <infinity> phillw: I just smoketested it on my G3 and G5, and both work.
[21:56] <phillw> great, so the cron build tomorrow should put the ppc-lubuntu testers back in the chase?
[21:57] <infinity> phillw: Depending on how quickly I get it migrated, but probably yes.
[21:58] <phillw> infinity: scheduled to start at 16:29 (UTC)  is that enough time for you?
[21:59] <phillw> or would you prefer an extra 24 hours?
[22:00] <infinity> Oh, indeed, it's almost a day until the next build.  Yeah, that one should be fine.
[22:01] <phillw> infinity: okies, if you are sure, I will email the testers, obviously they are chomping on the bit to get back to work!
[22:02] <infinity> I make no guarantees that various DRM/KMS drivers are working (I don't run consoles on any of my PPC machines, they're all servers), but these kernels at least boot on all my kit, which is a step up from the previous version. :P
[22:03] <phillw> there's one sure fire way to check :P
[22:03] <infinity> 3.11 includes a pretty massive changeset to the radeon driver, so that could cut both ways.  Maybe it's drastically improved, or maybe it has a ton of new bugs that break it on !x86... We'll see.
[22:04] <phillw> as always, we rely on the testers to let us know :) That the promise to have a kernel that at least stood a chance of working has been kept, they will be happy and do not 'rant' over bugs.
[22:05] <infinity> Well, I can nearly guarantee that it should boot on pretty much any hardware we've supported before.  Between Ben and I, we have a pretty wide array of stuff to boot and stress test on.
[22:05] <infinity> It's just that he and I both only run headless servers.
[22:05] <infinity> So, we'll see. :)
[22:07] <phillw> the graphics cards that apple used were and are always an issue... they have gotten used to workarounds, only by letting it into the wild can these issues with the graphics cards be started to be investigated :)
[22:07] <phillw> infinity: many thanks to you and ben for this work, I do know ppc for desktops is a low priority :)
[22:07] <infinity> It's not the cards, per se, it's that the radeon driver has become very x86-centric, and very few people care about fixing the PPC bugs with it.
[22:08] <infinity> nouveau seems to suffer fewer of those issues (for whatever reason), so the nvidia cards that Apple shipped with later G5s seem to be in better shape.
[22:09] <phillw> we're still working with G3's and g4's... as long as the darn thing will boot, the graphics cards could be seen as nearly a seperate branch of their own.
[22:10] <infinity> Yeah, I haven't tried running X on the ATi Rage128 in my G3 for, like, a decade.
[22:10] <infinity> I assume it probably sort of works.  But I have no idea, and don't care, as it's a headless router/firewall in my house. :P
[22:11] <infinity> Though, the offb driver would work for boring old 2D X.  You'd just get zero acceleration.
[22:11] <phillw> Well, we should have some results in ~ 24 hours.
[22:13] <phillw> oh, is it still one kernel? i.e. will the ISO still be CD sized? this is important for some of them. Julien has held back awaiting for a working kernel to be released.


[01:12] <waltman> Tonight's the night I upgrade to 18.04. Wish me luck!
[01:18] <rmg51> good luck
[01:24] <waltman> Looks like they've gone from neomutt back to mutt.
[01:25] <waltman> Starting from this version, we switch mutt to the default source package obtained on mutt.org. Due to incompatible formatting changes the previous neomutt patch became bigger than the package itself and adopting it and naming it 'mutt' was not possible because the maintainer of Mutt objected on legal grounds.
[01:26] <waltman> It'll be interesting to see what that breaks.
[09:50] <teddy-dbear> Morning peoples, critters and everything else


[20:10] <philipballew> I I want to encrypt the hard drive my server's os (Debian) is installed on, is there a way to enter the paraphrase without a monitor hooked up?
[22:08] <nhaines> With an attached keyboard.