[00:19] <elementofone> !ops
[00:20] <elementofone> !ops
[00:31] <elementofone> !ops
[00:35] <elementofone> !OPS
[00:38] <JanC> elementofone: stop that please
[00:39] <elementofone> !ops janc
[00:39] <elementofone> !ops | JanC
[00:40] <elementofone> !ops | JanC \
[00:55] <elementofone> !ops | JanC \
[08:34] <apw> dsmythies, thanks for the update
[11:45] <NikTh> How can one identify the kernel version from Linus git tree in comparison with the kernel.ubuntu.com/~kernel-ppa/mainline ? This does not help in my case (http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html_
[11:47] <NikTh> I can understand that 3.17-rc4 it's the same version as v3.17-rc4 (in Linus git), and 3.17-utopic = v3.17(in Linus git), but what about 3.17.1-utopic ? which version is this under Linus git ?
[11:48] <smb> NikTh, That is the first stable release from upstream stable compiled with mostly the config from utopic
[11:49] <smb> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
[11:49] <apw> NikTh, as smb says, this is a stable update kerenl, it is therefore _not_ in linus' tree, it is in the stable tree
[11:50] <smb> there ^
[11:50] <apw> NikTh, separatly each of those builds includes a COMMIT file which contains the tag/commit id which was used to build it
[11:54] <NikTh> So, if one wants to bisect an rc kernel upstream, should clone the Linus git, but if wants to bisect lets say 3.17-utopic and 3.17.1-utopic should clone the stable git ?
[11:54] <apw> yes the two tags you need are in there
[11:55] <NikTh> and if the last bad kernel is rc-7 and the next good one is a stable, lets say 3.17-rc7 = the last bad one and 3.17-utopic = the first good one.
[11:56] <apw> well those are both linus' releases, so they are in either
[11:56] <apw> those versions literally represent v<nnnn> tags
[11:56] <NikTh> Yes. Correct apw. Thanks
[11:57] <apw> correct ?
[11:57] <NikTh> The difference would be if the last bad one was , lets say 3.17-utopic and the first good one was 3.17.1-utopic, then one should clone the stable git. Correct ?
[11:58] <apw> well yes, but you would never find that situation, as if you had v3.17-rc7 as bad and v3.17.1 as good, the next test would be v3.17
[11:58] <apw> moving you into one or the other
[12:06] <NikTh> Lets say that the last bad kernel is 3.17-utopic and the exact following is the first good one (3.17.1-utopic). How one can reverse bisect ? From stable git ? Or this situation would never happen ?
[12:07] <apw> stable yes, those tags are both in there
[12:11] <NikTh> apw: Thanks for all the answers and explanations, this is the yet another time helping me :-)
[12:12] <NikTh> smb: same too you
[12:12] <NikTh> if you put a candidate for president and you need my vote, just let me know :P
[12:14] <apw> heh ..
[12:16] <NikTh> Oh, and a last one.. because I don't want to building kernels in vain... I have spotted the bad and good kernels. And I want to start bisecting. I want to build the bad kernel with the first commit from the good one.. will I do "git checkout COMMIT" and then start building ?
[12:22] <apw> NikTh, doesn't "git bisect" offer you a sensible commit to bisect?
[12:23] <NikTh> apw: Yes. It offers me a commit, but I want to build and test the kernel with this commit and particular I'm speaking about a reverse bisection.
[12:24] <apw> it will have check that commit out when it selected it, iirc
[12:24] <NikTh> I've read the wiki, but I'm afraid if I don't understand something.. so I'm asking to be sure.
[12:28] <NikTh> apw: For starters, I did a "git checkout COMMIT" where commit is the offered commit from the bisection and I'm building the bad kernel with this commit. Is that right ?
[12:29] <apw> my memory is the bisect itself checked out the suggested commit for you
[12:31] <NikTh> Ok, but is there something wrong with the procedure I followed? I mean, the "git checkout COMMIT" breaks something maybe ? or building an incorrect kernel ?
[12:31] <apw> if you were on that commit, the git checkout would be a noop
[12:34] <NikTh> noop? sorry, what is noop ? you mean something unnecessary ?
[12:58] <apw> a no-operation indeed
[13:04] <rtg> cking_, would you mind answering this one when you've a moment ? https://bugs.launchpad.net/bugs/1387144
[13:04] <cking_> yup
[13:11] <apw> cking_, it is possible that could be a recommended, so it would be uninstallable, but also remain installed by default, something to consider
[13:12] <cking_> I think that would be better, so users can chose to remove it
[13:13] <rtg> cking_, thermald does bail out on platforms for which it can do no good, right ? like virt instances, etc.
[13:14] <cking_> rtg, it does indeed
[13:14] <cking_> I should add that too to the bug report
[13:16] <cking_> making it a recommended is the best plan, this way users can remove it if thermald is too agressive for there liking and they like seeing their H/W shutdown when it gets too hot
[13:30] <NikTh> As an addition thermald sometimes needs a special configuration in order to identify the components correctly.  https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1367946
[13:34] <cking_> rtg, apw, are you ok to make that change, or do you want me to? (I'm not upto speed with the packaging foo that's needed to do that)
[13:35] <rtg> cking_, you could certainly write the patch and send it on the list.
[13:47] <cking_> rtg, i'm not sure how the original change was made in utopic
[13:47] <rtg> cking_, debian.master/control.stub.in I think
[13:48] <cking_> yep, I grep'd for thermald in that in utopic, I can't see it
[13:48] <rtg> hmm, lemme check
[13:49] <rtg> cking_, its in the Utopic meta package
[13:50] <cking_> hrm, never futzed with that before
[13:58] <apw> yeah that is actually on linux-image-generic meta package ...
[13:58] <apw> cking_, that is more of a "normal" package so you have to edit changelog by hand, no insertchanges help
[14:03] <cking_> apw, hold on, I'm sucked into some phablety issue at the mo
[14:03] <apw> cking_, np
[14:39] <dgadomski> hello everyone
[14:40] <dgadomski> stgraber: do you still have your hardware for bug #1104230?
[14:48] <dgadomski> stgraber: I have provided some kernel builds there for testing, unfortunately I have no hardware to test it by myself so I would appreciate any feedback, thanks!
[15:01] <rtg> apw, i fired up a vivid kernel to the kernel PPA. meta package to follow soon. If testing on various bits of kits seems OK then I'll dump it into the archive (after consulting infinity)
[15:18] <apw> rtg, yeah we need some dkms testing i ugess, which is ... not working right now
[15:19] <rtg> apw, what better way to acquire some launchpad bugs :)
[15:19] <apw> true we don't have very many right now
[19:03] <rtg> tseliot, we've got a 3.18 based kernel for you to test your DKMS packages against in the kernel PPA
[21:22] <JayJ> On ubuntu 14.04 host runing 3.13.0-24-generic kernel, Guests are freezing and I see "BUG: soft lockup - CPU#x stuck for 22s!" Anybody help me narrowing the issue? HW is Supermicro with Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz. I need anybody help.
[21:47] <neoark> JayJ bad hardware?
[21:50] <JayJ> neoark: What I don't understand is that the host is running the same version of ubuntu and kernel. There are no issues with the host. However, teh guest running has all the issues.
[21:51] <NikTh> And why this could ever happen ? Am I noob regarding the reverse commit bisect procedure ? Yes I am, but I've followed the procedure step by step.  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386695/comments/23


[08:19] <anpok> alf__: i could also just avoid the rethrow as a workaround
[08:19] <anpok> and just test that the exception handler gets called with !=nullptr exception
[08:20] <alf__> anpok: sounds good
[08:21] <anpok> hm there is a fixed version of rethrow attached to the bug report
[14:38] <anpok> alf__: are errors like "terminated without an active excpetion" other symptoms of this error?
[14:39] <alf__> anpok: ENOCONTEXT
[14:40] <alf__> anpok: which is "this error"?
[14:42] <anpok> the wrong active exception counter
[14:42] <anpok> caused by rethrow_exception..
[16:24] <duflu> mterry: https://code.launchpad.net/xmir
[17:00] <duflu> attente_: Noticed you're keeping GTK up to date with lp:mir. Thanks for that. Is much improvement happening or just fixes?
[17:02] <attente_> duflu: just fixes. is there any new api available we can use in gtk?
[17:03] <duflu> attente_: Yes. You can now set the window title, and resize yourself. Possibly more
[17:04] <attente_> duflu: nice, i'll take a look into using that
[17:06] <duflu> attente_: Also while you want (if you want) to do your own title bar, try setting surface type freestyle and we'll update the demo shells to not add titlebars to them
[19:38] <duflu> mterry ...
[19:38] <duflu> /usr/include/features.h:364:25: fatal error: sys/cdefs.h: No such file or directory
[19:38] <duflu>  #  include <sys/cdefs.h>
[19:38] <duflu>                          ^
[19:39] <mterry> duflu, libc6-dev
[19:47] <duflu> mterry: lib32gcc-4.9-dev
[20:29] <mterry> duflu, http://www.tweaking4all.com/software/linux-software/use-xrdp-remote-access-ubuntu-14-04/
[20:29] <mterry> duflu, nano /etc/xrdp/startwm.sh


[07:20] <lordievader> Good moning
[08:49] <tumbleweed> xenial amd64 images seem to be missing in AWS us-east-1: curl -s https://cloud-images.ubuntu.com/query/xenial/server/released.current.txt | grep 'amd64.*us-east'
[08:49] <tumbleweed> (vs bionic)
[09:14] <tumbleweed> filed https://bugs.launchpad.net/cloud-images/+bug/1808304
[10:03] <tobias-urdin> coreycb: in cloud-archive bionic-updates/stein the aodh-api seems to not be dropping the apache config but postinst tries to a2ensite it
[10:14] <tobias-urdin> coreycb: nvm, is probably my fault when puppet purges all configs :)
[10:35] <tobias-urdin> coreycb: might need to bump python3-eventlet to > 0.21, upper-constraints says 0.24.1 is max, eventlet https is broken so for example glance running under https fails
[10:38] <tobias-urdin> coreycb: seems like fedora bumped that to python3-eventlet to 0.24 for stein python3, i'm in pto tomorrow but maybe you could look into it
[10:38] <tobias-urdin> let me know if you want a bug report to track it
[10:41] <tobias-urdin> got info that https glance might not even work with eventlet 0.24 either, so maybe it doesn't matter, guess we'll have to disable glance https for now
[10:45] <kstenerud> Has anyone ever had the situation where a freshly checked out repo has unstaged changes?
[10:50] <tobias-urdin> coreycb: quoting a RDO packager "some issues are fixed in 0.24"
[10:54] <ahasenack> good morning
[11:29] <hays> cant figure out on this system why <IP_ADDRESS> is somehow getting to another machine on the network
[11:29] <hays> tcpdump filtered by port doesn't show it leaving any interfaces, but I see it on the receiving end--i think on lo of all place
[11:30] <hays> no ssh clients running (no tunnels i don't think)
[11:30] <hays> iptables-save is blank, ufw is disabled
[11:31] <hays> im pretty stumped
[11:41] <peetaur2> hays: try nethogs and then send lots of data there to make it come up in nethogs
[11:43] <tomreyn> hays: what are the facts you have so far about "<IP_ADDRESS> is somehow getting to another machine on the network"?
[11:44] <hays> tomreyn: both the machines are running a process that returns a GUID through a REST API
[11:44] <hays> On machine 1 I can connect to that API on localhost and get the GUID for machine 2, but if I give the actual IP address of the machine, I get machine 1
[11:45] <hays> localhost, <IP_ADDRESS>, <IP_ADDRESS>, ::1 all go to machine 2
[11:47] <tomreyn> you connect (API consumer) using CLI utilities or web browsers?
[11:48] <hays> it is a library called python requests
[11:48] <bipul> How would i know my cloud init is diabled or not?
[11:48] <bipul> I tried with echo "network: {config: disabled}" > /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg , but failed to do so..
[11:50] <hays> tomreyn: i have a script that uses the python requests API
[11:50] <hays> ive used it before, its pretty well tested
[11:54] <tomreyn> hays: i see. if you can make the API log its responses, too, add the source of the information (hostname), maybe this will help. i'm puzzled, too. i'd say check arp tables (ip neigh), make sure the MAC addresses point to the right systems and check both systems' routing tables (ip route).
[11:56] <tomreyn> my guess is on a caching issue due to an earlier (since resolved) misconfiguration on node 1.
[11:56] <hays> ill keep digging.  i didnt see anything obvious with ip route or arp, but i honestly dont know exactly how to decode some of the more obscure routes, e.g., ip route show table lo
[11:58] <hays> oddly, i've seen something eerily similar to this on another machine, but for some reason it was only ipv4
[11:59] <hays> never figured out root cause
[11:59] <tomreyn> there should be no table for lo in the first place.
[11:59] <hays> that was a fedora box
[12:00] <hays> tomreyn: try typing ip route show table local
[12:01] <hays> this is the table i am not sure i understand
[12:02] <hays> i think ip route show filters out some routes from display normally
[12:07] <tomreyn> hays: as ip-route(8) explains, this will show the destinations assigned to the this very system. Packets addressed to these IP addresses, when handled by the systems' routing code (kernel), are looped back and delivered locally.
[14:37] <muhaha> Anyone has experinece with SCEP and certmonger?
[19:06] <kinghat> does livepatch work on ubuntu server?
[19:06] <nacc> kinghat: yes, it'
[19:07] <nacc> kinghat: yes, it's about the kernel, not the installation type, afaik
[19:07] <kinghat> ah
[19:07] <kinghat> how do you feel about snaps on server?
[19:08] <nacc> kinghat: if you need an app that is packaged as a snap, then use it.   But they have their uses.
[19:09] <lordcirth_> The problem is when people bundle their apps in a snap with the version of libraries they developed with, and then never update it.  And then your app is running with openssl way out of date.
[19:12] <nacc> lordcirth_: the store automatically scans for stuff like that, fwiw
[19:12] <nacc> and emails the owners
[19:13] <lordcirth_> Ah, that's good
[19:13] <nacc> citing "some...contention" is really not a way to discuss it
[19:14] <nacc> specific issues would be good, otherwise, do some research
[21:17] <teward> anyone got the bug about how LVM sets up only a 4GB LV inside the PV and doesn't autoset it to expand with subiquity?
[21:17] <teward> I forget the exact bug number
[21:20] <powersj> teward, https://bugs.launchpad.net/subiquity/+bug/1785321
[21:28] <teward> powersj: thank you kindly.
[21:28] <ahasenack> teward: you just remembered the approximate bug number? :)
[21:28] <ahasenack> starts with 1? :)
[21:28] <teward> ahasenack: lol.
[21:28] <teward> ahasenack: that's 90% of the bugs I work with xD
[21:28] <ahasenack> wonder when we will reach 2
[21:28] <teward> i have a few that start with 9 but :P
[21:29] <ahasenack> yeah, precious old bugs


[18:28] <ahoneybun> I see you got a use out of the picture mhall119 :)
[20:09] <mhall119> ahoneybun: yup, I appreciate the image, I didn't have anything good to use there
[20:15] <ahoneybun> no problem
[20:16] <ahoneybun> I also sent out a tweet about the Ubuntu Hour Keith and I are doing
[20:16] <ahoneybun> also put it on Google+
[20:19] <ahoneybun> if you could share and tweet those please mhall119
[20:20] <ahoneybun> nice :)
[20:21] <mhall119> ahoneybun: done
[20:21] <ahoneybun> thanks mhall119


[08:27] <sterfield> hey there
[08:28] <sterfield> I have a question, hope it’s not a stupid one
[08:28] <sterfield> I can see that cloud-init is grabing metadata and userdata from different sources, (EC2, nocloud, etc..)
[08:29] <sterfield> but is it possible to use those metadata / userdata in scripts ? I mean, they are pulled by cloud-init at boot time, so are they available ?
[08:30] <sterfield> or is it only for cloud-init internal configuration, like default hostname etc…
[08:30] <sterfield> ?
[08:30] <waldi> take a look into /var/lib/cloud/instance
[08:31] <sterfield> oh ok
[08:33] <sterfield_> sorry about that
[08:33] <sterfield_> I guess I was D/C at the wrong moment :x
[08:33] <sterfield_> so you were telling me to look in /var/lib/cloud/instance
[08:34] <sterfield_> which is a link to the instance/ID folder, which contains all the information pulled by cloud-init, right ?
[08:37] <waldi> smoser: any news on https://bugs.launchpad.net/cloud-init/+bug/1536961 and https://bugs.launchpad.net/cloud-init/+bug/1536964 ?
[08:41] <sterfield> Out of the 4 steps of cloud-init (init —local, init, config and final), I understood the last three and can see the modules called by each phase. However, I’m not fully understand the —local phase. This is a phase called at very early stage in the boot process, where network for example is not available. However, I don’t understand what’s done during this phase, and also how it is configured.