[01:18] <groupers> Hi, can someone tell me how to configure a static IP in 18.04? I tried installing nmtui but apparently network manager has been replaced with netplan? I need to create a yaml file now or what?
[01:24] <RoyK> iirc it should be possible to use /etc/network/interfaces
[01:24] <RoyK> backwards compatibility
[02:09] <tomreyn> groupers: ubuntu server uses systemd-networkd rather than network-manager by default. netplan is a management abstraction which can handle both. the goal is to make confioguration easier.
[02:11] <tomreyn> that's on 18.04
[02:12] <mybalzitch> oh right I should get back to debugging systemd-networkd not assigning my vlan interfaces ip's
[02:19] <cryptodan> the Interfaces File was far easier
[02:22] <RoyK> surprise ;)
[02:27] <trippeh_> there are too damn many ways to configure networking! *makes one more* ;)
[02:30] <trippeh_> I know people who really like netplan though, so shrug, wont judge :)
[02:31] <cryptodan> interfaces was easy as heck the file existed all you had to do was add a few lines and change dhcp to static and bam instant static ip after restarting
[02:37] <groupers> I guess netplan is fine I just hate learning yet another way
[02:41] <xrandr_mac> I am looking to permenantly add additional ip addresses to my server. I see that /etc/network/interfaces is no longer used... what is the new way?
[02:41] <cryptodan> yup continuing to break things or add things where things arent broken
[02:46] <xrandr_mac> so...thoughts?
[02:47] <mybalzitch> xrandr_mac: netplan
[02:47] <mybalzitch> xrandr_mac: or read the interfaces file header and go back to ifupdown
[02:50] <cryptodan> so just curious if I had 5 interfaces in my PC and 5 different connections I would need a netplan file for each interface?
[02:51] <mybalzitch> you'd need a single yaml file
[02:51] <mybalzitch> read the docs
[02:51] <cryptodan> wow okay
[02:51] <mybalzitch> it's on the netplan.io site, example configs
[02:51] <mybalzitch> https://netplan.io/examples
[02:52] <cryptodan> so much more work then interfaces file
[02:54] <mwhudson> i lost it with ifupdown when i realised that it was parsing an entirely made up format with a custom c parser
[02:54] <mwhudson> which is not entirely rational but there you go
[03:49] <xrandr_mac> mybalzitch, thanks :)
[05:57] <lordievader> Good morning
[10:44] <jamespage> coreycb: hey so I finished https://review.openstack.org/#/c/600027 - rewrote the action to fork out to cinder-manage rather than use cinder internals
[12:26] <ironhalik> Hello
[12:26] <ironhalik> anyone with some iscsi + mpio experiance?
[12:28] <ironhalik> I'm trying to create a mpio device from multiple iscsi targets :) For some reason my hw array shows four targets that turn into a single block device. The problem is, in such a setup, mpio doesn't see it as a candidate for a device
[12:29] <ironhalik> and I'm a relative newbie in storage world, have no idea how it should work or wether its some issue with the storage array configuration
[13:05] <kstenerud> If I have a conn entry in /etc/ipsec.conf, I should be able to call ipsec up <name> right?
[13:06] <kstenerud> When I do, it says it can't find it...
[13:08] <sdeziel> kstenerud: yes, could you pastebin your ipsec.conf file?
[13:09] <kstenerud> https://pastebin.ubuntu.com/p/PZnnpySk7Z/
[13:11] <coreycb> jamespage: cool will take a look in a bit
[13:11] <sdeziel> kstenerud: add "auto=route" to the net-net conn
[13:15] <sdeziel> kstenerud: there is otherwise an implicit "auto=ignore"
[13:16] <kstenerud> ok
[15:27] <powersj> kstenerud, it looks like there has only been one version in cosmic
[15:28] <powersj> so since you are testing the upgrade path, you could grab the earlier version in bionic and continue using that
[15:28] <powersj> that would be the simplest way
[15:28] <dpb1> another strategy is, create a new package with just a changelog change
[15:28] <kstenerud> so
[15:28] <kstenerud> apt install -y postfix=3.3.0-1 postfix-mysql=3.3.0-1 mysql
[15:28] <kstenerud> would work in cosmic as well?
[15:28] <powersj> no, you would need to grab the deb itself
[15:29] <powersj> https://packages.ubuntu.com/bionic/amd64/postfix-mysql/download
[15:29] <powersj> kstenerud, dpb1's suggestion should work to. You could make the change log change and upload to a ppa with an earlier version
[15:30] <dpb1> or a newer version?
[15:30] <dpb1> right?
[15:30] <powersj> oh yeah upgrade
[15:30] <powersj> doh :)
[15:31] <kstenerud> hmm so I'd need a ppa1 to demonstrate brokenness, ppa2 with the fix in place, ppa3 to demonstrate that it's fixed?
[15:33] <powersj> upgrading to ppa2 with the fix in place, won't demonstrate it?
[15:33] <powersj> only the next upgrade would prevent the issue?
[15:33] <kstenerud> oh right yeah should only need 2
[15:34] <kstenerud> so I'd need 2 ppa repos for the tester to verify, one with just a version bump, and one that's an actual fix upping the ubuntu version right?
[15:34] <powersj> yeah
[15:36] <kstenerud> ok, and for the strongswan issue, do I just say in the MP that I've been unable to verify the fix?
[15:36] <kstenerud> er unable to replicate the bug
[15:46] <powersj> kstenerud, yeah update with your findings, what you tried, and move on
[15:52] <kstenerud> hmm that's weird... suddenly git-ubuntu is failing on both my machines
[15:52] <kstenerud> fatal: could not read Username for 'https://git.launchpad.net': terminal prompts disabled
[15:53] <kstenerud> oh wait no. It's because there's no postfix-mysql?
[15:53] <kstenerud> ERROR:Unable to find an imported repository for postfix-mysql. Please request an import by e-mailing usd-import-team@lists.launchpad.net
[15:55] <powersj> smoser, ^ is that something you can help with
[16:11] <sdeziel> it looks like postfix-mysql is from the postfix package itself
[16:11] <sdeziel> https://packages.ubuntu.com/source/cosmic/postfix
[16:13] <smoser> kstenerud: its because you do not have a postfix-mysql in your personal namespace
[16:14] <smoser> ah. ok.. i can import it. sorry for noise.
[16:16] <smoser> kstenerud: sorry... even *more* noise.
[16:16] <smoser> you have to give it a source package name, not a binary.
[16:17] <smoser> git ubuntu clone postfix
[16:17] <smoser> that works for me.
[16:17] <kstenerud> ah ok
[16:17] <smoser> initially i thoguht you were just worried about:
[16:17] <smoser>  fatal: could not read Username for 'https://git.launchpad.net': terminal prompts disabled
[16:18] <smoser> which looks "fatal" , but really is just saying "https://git.launchpad.net/~smoser/ubuntu/+source/postfix does not exist".
=== jdstrand_ is now known as jdstrand
[17:01] <kstenerud> Anybody know what would cause this on a git ubuntu build-source?
[17:01] <kstenerud> ERROR:Command exited 100: /usr/bin/lxc exec prime-ant -- apt-get install -y devscripts equivs sudo
[17:01] <kstenerud> ERROR:stderr: E: Package 'equivs' has no installation candidate
[17:02] <sdeziel> kstenerud: this operation is usually retried
[17:02] <sdeziel> and here, it succeeds on the second try
[17:04] <kstenerud> It did about 10 retries or so
[17:05] <kstenerud> https://pastebin.ubuntu.com/p/rNWpyv5D8m/
[17:13] <kstenerud> Next try failed in a different way: https://pastebin.ubuntu.com/p/wbFXH9t5ws/
[17:14] <nacc> kstenerud: let me look
[17:14] <nacc> kstenerud: what version of ubuntu?
[17:15] <nacc> kstenerud: and can you do something like: `lxc launch -e cda42780ccea`, `lxc exec <container> -- apt-get update; lxc exec <container> -- apt-get install -y devscript equivs sudo` ?
[17:15] <kstenerud> cosmic-daily from 20180906
[17:15] <nacc> kstenerud: to be clear, the first log, it did two sets of 6 retries
[17:15] <nacc> because it tried two different builds
[17:16] <nacc> because it failed to build with the orig tarball from pristine-tar
[17:16] <nacc> g-u doesn't know *why* it failed to build, in that it will fail the same way the second time
[17:16] <nacc> although that it wasn't the same both times is weird
[17:18] <bdx> hello all
[17:18] <kstenerud> hmm interesting. the network isn't running
[17:19] <bdx> few things I wanted to bring to light as I'm hitting them installing ubuntu server
[17:19] <kstenerud> there's an ipv6 link but no ipv4
[17:19] <kstenerud> I'll try a different daily and see if there's a difference
[17:19] <nacc> kstenerud: yep
[17:20] <bdx> http://cdimage.ubuntu.com/ubuntu-server/bionic/daily/current/ - the bionic-server-amd64.iso image found here seems far less problematic then what I'm finding here at the releases endpoint http://releases.ubuntu.com/18.04.1/
[17:21] <bdx> this https://paste.ubuntu.com/p/S5rxQ3xkjx/, is from an ubuntu-18.04.1-desktop-amd64.iso      install from the releases endpoint
[17:21] <bdx> lol
[17:22] <bdx> I have been hitting oddity after oddity similar but different to ^
[17:22] <bdx> ooops shoot
[17:22] <bdx> s/ubuntu-18.04.1-desktop-amd64.iso/ubuntu-18.04.1-live-server-amd64.iso /   ^^^
[17:23] <bdx> so, when I install ubuntu-server from http://cdimage.ubuntu.com/ubuntu-server/bionic/daily/current/
[17:24] <bdx> everything is where I would expect it to be and works as expected (packages found, correct source repos) on first boot
[17:24] <bdx> I didn't understand what was going on at first, and I still really don't
[17:25] <bdx> I just have users pegging me with these issues of like, "I installed ubuntu-server from http://releases.ubuntu.com/18.04.1/ and its totally broken"
[17:25] <bdx> I had to run through it for myself to get a first hand experience and get in touch with you guys
[17:26] <bdx> either way
[17:26] <bdx> it seems http://releases.ubuntu.com/18.04.1/ is pushed as the path to get ubuntu-server from
[17:26] <bdx> this totally sucks because its the one that "seems broken"
[17:27] <bdx> as opposed to the one found at http://cdimage.ubuntu.com/ubuntu-server/bionic/daily/current/
[17:27] <bdx> not sure if there is anything you guys can do about this, or if its intended or what
[17:27] <bdx> just wanted to share the experience from the user perspective
[17:27] <bdx> sorry to spam your channel, but I thought it was worth bringing up
[17:28] <bdx> thx thx
[17:28] <mybalzitch> ubuntu.com/download/server lists 18.04.1 as the version of choice too
[17:45] <kstenerud> OK, I'm now using a daily from Aug 29th, but that fails in a different way :/
[17:45] <kstenerud> https://pastebin.ubuntu.com/p/JwHJMhYCVh/
[17:52] <nacc> bdx: did you read the release notes?
[17:52] <nacc> kstenerud: can you keep the container and see what the permissions are?
[17:53] <bdx> nacc: no, I'm sure there is something I've missed here .... I was just expecting there to be consistency between the two
[17:53] <nacc> bdx: it's a totally different installer
[17:53] <nacc> bdx: please read the release notes :)
[17:53] <bdx> nacc: I see that,  thanks
[17:54] <nacc> bdx: it even points to the alternate installer
[17:54] <bdx> yeah I know I know
[17:54] <nacc> bdx: ok :)
[17:54] <bdx> that shouldn't mean the user experience is totally different following install though
[17:55] <nacc> bdx: the experience issues, you might want to file bugs about
[17:56] <bdx> right ... I was hoping this is something you guys might be more on top of .... consistency has been great across different platforms and series previously
[17:57] <bdx> possibly you shouldn't break that for a new installer
[17:59] <bdx> nacc: could you link me to where I can file a bug on this please?
[18:01] <nacc> dpb1: --^ ?
[18:01] <kstenerud> hmm that's odd
[18:01] <kstenerud> root@moved-mutt:~# ls -l /tmp/tmptsr1sluv.tar.gz
[18:01] <kstenerud> -rw------- 1 1001 1001 4673602 Sep  7 18:00 /tmp/tmptsr1sluv.tar.gz
[18:01] <nacc> bdx: probably subiquity as the source
[18:01] <nacc> kstenerud: strange
[18:01] <kstenerud> Tried that an two different versions of cosmic
[18:02] <nacc> kstenerud: i am about to be eod early; if you want, you can file a bug and i can try and reproduce it on monday. Give me the git repo/branch you are using too
[18:02] <kstenerud> ok