[00:40] <shubjero> Hey all, my entire cloud is down because of this: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1927868
[00:40] <shubjero> Any way to get the 16.3.0 packages?
[00:41] <sarnold> shubjero: yeah, launchpad has them all https://launchpad.net/ubuntu/+source/neutron/+publishinghistory
[00:42] <shubjero> sarnold: hmm, how can i grab these with apt?
[00:43] <sarnold> shubjero: if it's still listed on https://launchpad.net/ubuntu/+source/neutron then you should be able to apt install neutron=version_number_here  .. but if it's not referenced by any of these, then it'll probably have been reaped from the mirrors and isn't reachable via apt commands any more
[00:47] <shubjero> sarnold: I don't really understand how to roll back without the package being published on a repository
[00:47] <shubjero> At the very least 16.3.1 needs to be pulled from app repositories immediately
[00:47] <shubjero> this bug puts entire openstack deployments offline
[00:48] <shubjero> I  had tested 16.3.0 but by the time i installed prod 16.3.1 had been released and i didnt test it
[00:48] <shubjero> this is terrible
[00:48] <sarnold> shubjero: wget <url> ; dpkg -i ./neutron_whatever.deb
[00:49] <shubjero> I am running 18.04 bionic with cloud archive repo for ussuri
[00:49] <shubjero> i dont see where these deb's are hosted on launchpad
[00:54] <sarnold> hmm that's strange, there's nothing listed under ussari here https://launchpad.net/cloud-archive/+packages
[00:55] <sarnold> I wonder where those live
[00:55] <sarnold> maybe if you use ubuntu-bug neutron   to file a bug on neutron, the bug itself willhave breadcrumbs to where the packages live
[00:57] <shubjero> im trying 16.3.2 from the proposed repo
[00:57] <shubjero> i have no idea why ubuntu prunes previous versions from repositories so agressively
[00:57] <shubjero> its dangerous
[01:07] <shubjero> does not appear to be fixed in 16.3.2 :(
[01:08] <sarnold> :(
[01:56] <shubjero> sarnold: I was able to find debs for 16.0 that seem to work at http://archive.ubuntu.com/ubuntu/pool/main/n/neutron/ I installed them manually and neutron l3 agents are now coming alive
[01:56] <shubjero> i need a stiff fucking drink
[01:59] <sarnold> shubjero: woot
[02:00] <shubjero> Hopefully I can chat with coreycb tomorrow and let him know my late night fun
[05:25] <PaulePanter> sdeziel: I will do it, but SYSRQ is not really needed in QEMU/KVM environment. But it’s probably the easiest solution.
[07:58] <BraveheartBSD> I have ubnuntu server installed, how do I access the 12gb share?
[11:50] <uluntu1> I have set up isc-dhcp-server over Ubuntu server 20.04. Isc-dhcp-server starts well. But when I plug a network cable to link the server to the switch, I get the following message: network failed - Connection activation failed. Problem described here: https://askubuntu.com/questions/1345088/ubuntu-server-20-04-set-ip-isc-dhcp-server-network-failed
[12:19] <rbasak> uluntu1: "network failed - Connection activation failed" -- where does that message appear?
[12:25] <uluntu1> @rbasak: It appears on the server. On client side no display message but same sign.
[12:31] <rbasak> uluntu1: I don't understand. Where and how does it appear? Is your server actually a desktop?
[12:48] <uluntu1> @rbasak: yes server is a Desktop
[12:51] <rbasak> uluntu1: the desktop assumes that your network will be "roaming" by default, which generally won't work if you want to run a DHCP server. Normally you'd configure your network and IP statically on the DHCP server. I'm not sure how that interacts with Network Manager (that's typically a desktop-only thing) especially when you log out of the desktop session, etc.
[12:51] <rbasak> uluntu1: I'm sure what you want can be achieved, but trying to do it on a desktop makes things much more complicated.
[17:21] <PaulePanter> How can I reassign https://bugs.launchpad.net/ubuntu/+source/procps/+bug
[19:27] <sarnold> PaulePanter: can you rephrase your question?
[20:13] <DK3> /j/join #centos
[21:02] <ndubois> quit
[21:40] <ra>