=== guillaumedsde012 is now known as guillaumedsde01
=== jelly-home is now known as jelly
=== apw_ is now known as apw
=== kinghat2 is now known as kinghat
=== markthomas_ is now known as markthomas
=== genpaku_ is now known as genpaku
=== OliPicard_ is now known as OliPicard
=== falcojr6 is now known as falcojr
=== Ps1-Jack is now known as Psi-Jack
[15:37] <avernos> hi, im trying to setup to network interfaces on the same server. on boot the network interface name gets assigned to different hardware. how should i call the interfaces on the config files for services such as dhcp
[15:38] <avernos> two networks, not to *
[16:18] <kyle__> What types of names are you seeing?
[16:18] <kyle__> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
[16:26] <giaco_> hello
=== powersj_ is now known as powersj
[16:28] <giaco_> I have remote ubuntu server that has been running for months no issues, then today suddenly it went offline so I asked to remote human being to reboot it. It come back online for minutes, then in went offline again and I had to pick up car and rush to rack. What I see with dmesg? "PM: suspend entry (s2idle)"
[16:29] <giaco_> so ubuntu server goes standby
[16:29] <giaco_> this is just silly
[16:49] <giaco_> just did "systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target", but I haven't installed any desktop component nor I have updated my ubuntu server manually. So something has changed automatically
[18:26] <smoser> giaco_: what release are you running ?
[18:26] <smoser> if that were a regression to a stable release, then it seems you would not be the only one screaming.
[18:28] <smoser> you can see changes that went into ubuntu stable releases at
[18:28] <smoser>  https://lists.ubuntu.com/archives/focal-changes/2021-March/thread.html
[18:29] <smoser> giaco_: not to disagree, ubuntu server should definitely not just suspend itself. I'm just saying that there are *lots* of ubuntu instances on cloud and bare metal all over the world.
=== arooni_team_b is now known as arooni
[19:12] <giaco_> smoser: Ubuntu 20.04.1 LTS
[20:08] <smoser> giaco_: well.. ih ave some systems running 20.04 and updated, and i have not seen it.
[20:12] <giaco_> I only know that it suddenly decided to go sleeping after months without any system modification, apart from unattended security upgrades
[20:13] <smoser> well, then the list of things that ubuntu sent you is in 'focal-changes' (and you could look in apt logs also i think).
[22:11] <bradm> hi all!  are there any plans to get https://bugs.launchpad.net/neutron/+bug/1883089 backported to Focal?  I'm hitting that bug on our Ussari juju deployed cloud
[22:11] <ubot3> Launchpad bug 1883089 in neutron "[L3] floating IP failed to bind due to no agent gateway port(fip-ns)" [Medium, Fix Released]
[22:14] <sarnold> bradm: it's probably worth filing a new bug report about it with ubuntu-bug and mentioning the number in the description; if there's no ubuntu bug about it, there's probably nothing planned
=== gpiccoli_ is now known as gpiccoli
[22:26] <bradm> sarnold: I originally filed https://bugs.launchpad.net/neutron/+bug/1917409 about the issue, it was marked a dup of the above.
[22:26] <ubot3> Launchpad bug 1883089 in neutron "[L3] floating IP failed to bind due to no agent gateway port(fip-ns)" [Medium, Fix Released] [duplicate: 1917409]
[22:26] <bradm> can I add an also affects to ubuntu on there?
[22:27] <bradm> my LP workflow is a bit rusty
[22:28] <sarnold> bradm: aha, that was filed against neutron the upstream project, not neutron the ubuntu package
[22:28] <sarnold> bradm: using ubuntu-bug to file the bug would target the package in ubuntu, not the upstream package
[22:34] <bradm> sarnold: ahh, cool, I wasn't sure the right place to target it at the time, been over 3 years since I've filed bugs in anger.
[22:34] <bradm> so I should use ubuntu-bug to file another one?  to just also affects the package?
[22:34] <bradm> don't mind either way, whatever will get it to the right place
[22:34] <bradm> er, s/to/or/
[22:34] <sarnold> bradm: I tried fiddling the bug statuses but I may have made it wrose for the upstream neutron project. sigh :)
[22:36] <bradm> sarnold: ah well, thanks for adding it to the bug for me.  you'll probably start seeing more bugs from us on things, we're working on production juju deployed clouds at my company now.
[22:36] <sarnold> bradm: nice :D
[22:37] <bradm> I'm ex-Bootstack, so I know a bit about workflows, but its been a while.
[22:40] <bradm> although that term seems expunged from Canonical website these days.
[22:41] <sarnold> hehe, a recent returner was asking questions about things that he once knew, and there was a moment when I had that "oh it'd be kinda nice to forget some of this" :)
[22:41] <bradm> I'm having that kind of moment on a occasional basis about things I'm re-remebering too.
[22:42] <bradm> but it is good to see things have moved on as well, stuff has definitely improved over time in a few ways
[22:43] <bradm> I ended up with a deployemnt script that's pretty much hands off and deploys our QA cloud of 6 nodes in about 2 hours, with some workarounds for bugs in it.
[22:43] <sarnold> yeah, it does seem like most things are improving most of the time :)
[22:43] <bradm> running a script and coming back to a working cloud later is still nice.
[22:43] <sarnold> :D
=== ivo_cavalcante_ is now known as ivo_cavalcante
=== misuto1 is now known as misuto