[00:43] <nacc> rbasak: i'm thinkning i need to rethink the quiltify and changelogify logic, so feel free to pause that review
[05:28] <cpaelzer> good morning
[07:33] <vinayus> hi guys i have an issue while deploying ubuntu-server via preseed.. same preseed file works fine with ubuntu-server-16.04.2 iso image but not with 16.04.3.. basically all i am trying is to automate postgres server installation.. can anyone help?
[07:33] <vinayus> https://pastebin.com/xDpViuaw
[07:33] <vinayus> https://i.stack.imgur.com/xLvLl.png
[07:34] <vinayus> above links are preseed file and the image.. i would really appreciate if anyone can help me with this.. issue is also seen on daily release builds as well..
[07:38] <vinayus> and to note, these installations are attempted on an isolated environment where connection to internet is not there..
[08:51] <cpaelzer> jamespage: hi, can you see the effects of bug 1720887 or do I have to wait for cnewcomer / freyes to be around to check?
[08:57] <RoyK> hi all. how can I check when bareos first came in to the ubuntu repos?
[09:00] <ikonia> RoyK: packages.ubuntu.com
[09:00] <ikonia> RoyK: it will show you the first time it was in the repos
[09:00] <oerheks> RoyK, launchpad > https://packages.ubuntu.com/search?keywords=bareos  i think Xenial 16.04
[09:00] <RoyK> danke
[09:03] <oerheks> the 1st build support is way back, 8.04 https://github.com/bareos/bareos/tree/master/platforms/ubuntu
[09:04] <RoyK> sure - I was just wondering about when it came in officially
[09:04] <RoyK> I still think it lacks lz4, though, unless newer bareos uses the normal libs
[09:19] <RoyK> hm… it's a bit annoying that libfastlz isn't in the repos
[09:19] <RoyK> why was this again? Bareos uses it for lz4
[09:44] <Jenshae> o7
[09:51] <jamespage> cpaelzer: no I've not directly seen that so we'll need freyes
[09:54] <Jenshae> Is ppa:xorg-edgers known and considered to be safe?
[09:56] <Jenshae> wiki.ubuntu.com/XorgOnTheEdge same thing?
[09:57] <oerheks> i would recommend https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa for testing
[09:58] <Jenshae> Context: Someone managed to yank on a cable so hard that they broke a graphics card port and since all the staff use dual monitor setups, I tossed the Nvidia GeForce 9500 into the archive server I am making. (Will it assist when running virtual machines that do have graphics processing?)
[09:58] <Jenshae> Thank you oerheks I would prefer just a stable driver if possible?
[09:59] <oerheks> yes, for that card i would use the regular drivers in our repos
[09:59] <Jenshae> www.binarytides.com/install-nvidia-drivers-ubuntu-14-04/ is that guide I am following but I was unfamiliar with the PPA they direct me toward.
[09:59] <oerheks> broken port.. we cannot tell you if that affects the use of the card
[10:00] <Jenshae> I think it is just physical damage to the pins.
[10:00] <Jenshae> The card itself seems fine.
[10:01] <oerheks> well, worth a try
[10:01] <Jenshae> I was fiddling with a program that wanted a library, which is found in mesa, so I "updated" the graphics and lost them completely. I forgot it is not longer Intel / AMD and is now Nvidia.
[10:02] <Jenshae> SSH is still working praise the Nix gods!  ;D
[10:05] <Jenshae> Thanks oerheks I didn't even think you would have default repositories for Nvidia. Good stuff.
[10:24] <joelio> RoyK: submit a ITP then?
[11:32] <Jenshae> On the bright side, the graphics are working now, however, getting a lot of message on boot along these lines now, "[FAILED] Failed to start Login Service ... "
[11:34] <Jenshae> ... and ssh now has, "Connection refused."
[11:34] <Jenshae> Is it possible to make a live USB of ubuntu-server?
[11:36] <Jenshae> Seems to have died, hardware is on, disk activity dropped off and screen went blank. Not entirely frozen because the NumLock is going on and off.
[11:44] <Jenshae> Hard reboot has worked for some reason.
[11:46] <Jenshae> I noticed it loaded SMB/CIFS, that is the protocol that was also vulnerable to WannaCry, right? How about the new one, Anubi, is it safe from that one?
[12:09] <lordievader> Good afternoon
[12:52] <freakyy> 18.04 will be the next LTS right? ;D
[12:52] <freakyy> that's cool ;D
[12:53] <freakyy> im running 17.10 right now
[12:53] <freakyy> oh well but not on the server nm ;D
[12:53] <freakyy> on my server i run 16.04 ;D
[12:54] <lordievader> !lts
[12:54] <lordievader> Right, even years. So yes, next is 18.04, then 20.04, etc.
[13:03] <Jenshae> Salutations lordie :)
[13:06] <Jenshae> iostat seems to be weird. Why is the raid volume on a lower kB_read/s than the physical drives?
[13:07] <lordievader> Caching, probably.
[14:44] <mnaser> jamespage coreycb - have you done any recent changes to the neutron packaging?  puppet openstack integration jobs are failing -- http://logs.openstack.org/08/511708/2/check/puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial/ab9e376/logs/neutron/neutron-l3-agent.txt.gz#_2017-10-17_11_29_13_858 (alongside a timeout assigning floating ip to port)
[14:48] <coreycb> mnaser: what release is that?
[14:49] <mnaser> coreycb pike -- http://logs.openstack.org/08/511708/2/check/puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial/ab9e376/logs/dpkg-l.txt.gz
[14:51] <coreycb> mnaser: that's pike-updates (vs pike-proposed) so you should be running with the same versions we released when upstream pike released.
[14:52] <mnaser> coreycb could it be an unrelated packages that broke things (maybe ovs, kernel?)
[14:52] <mnaser> because things were working okay until a week ago where we started noticing that failure
[14:57] <coreycb> mnaser: do you run with the default xenial kernel?
[14:57] <coreycb> mnaser: arp seems to be having issues in your log
[14:59] <mnaser> coreycb the booted kernel is 4.4.0-97-generic
[14:59] <mnaser> which seems to be the latest
[15:13] <coreycb> mnaser: ok i'm deploying xenial-pike and running tempest against it on my end now. i'll double check the kernel version matches.
[15:22] <mnaser> thanks coreycb
[15:52] <Jenshae> I just went through typing "logout" on all the ttys and hit ctrl+alt+F7, discovered there is a graphical login!?
[15:52] <Jenshae> It won't start a session. What is it?
[16:25] <teward> dpb1: sorry for nonresponse earlier.  Got stuck with no Internet because Comcast decided to do 'maintenance'
[16:25] <teward> that schedule *should* be fine, I'll triple check and get back to you.
[16:26] <dpb1> teward: thanks!
[17:10] <mnaser> coreycb sorry to bug you, any update on your side?
[17:11] <coreycb> mnaser: good timing, tests finished.
[17:11]  * mnaser ducks from window behind you :p
[17:11] <coreycb> mnaser: i didn't hit any issues running tempest smoke against a xenial-pike deployment
[17:11] <coreycb> mnaser: confirmed too that the kernel is at 4.4.0-97-generic
[17:12] <mnaser> the failing test is: tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON -- not sure if smoke runs it
[17:12] <mnaser> but it's consistently failing
[17:12] <mnaser> coreycb deployed with ovs?
[17:12] <coreycb> mnaser: yes
[17:13] <mnaser> https://github.com/openstack/puppet-openstack-integration -- scenario001 is failing, rest are all passing
[17:35] <coreycb> mnaser: i don't know if this is related but worth sharing: https://ihrachyshka.com/2017/05/17/gratuitous-arp-for-openstack-neutron/
[17:35] <coreycb> mnaser: search for "bind: Cannot assign requested address"
[17:35] <coreycb> mnaser: are you using router HA?
[17:36] <mnaser> coreycb ran into that exact article but didnt get a chance to start reading the whole thing yet.. will take sometime today.  it is possible we are, i'll have to check the manifests.  but the same manifest works in centos 7
[17:36] <mnaser> https://github.com/openstack/puppet-openstack-integration/blob/master/manifests/neutron.pp
[17:41] <coreycb> mnaser: there's this too https://bugs.launchpad.net/neutron/+bug/1717302
[17:43] <mnaser> oh thats very recent and interesting coreycb
[22:16] <nacc> rbasak: ok, I just force pushed my branch up that seems to work
[22:16] <nacc> rbasak: we'll see if it can pass jenkins