/srv/irclogs.ubuntu.com/2018/09/05/#ubuntu-server.txt

lamontahasenack: interestingly, livecd + packages seems to work, but I don't think it did the dlopen call.  same kernel on my installed desktop still results in failure.  Now comes the fun of looking at file diffs. sigh.00:40
lamontahasenack: turns out that error 610 from virtualbox is bitching about non-root owner of /usr /usr/lib or /usr/lib/vitualbox.  Thanks for the classy error messages, Oracle.01:02
cpaelzergood morning05:04
jamespagecoreycb: newer snapshots of py2.7, 3.6 and 3.7 all generate that same hacking test failure in nova10:40
jamespagecoreycb: life is to short so I've skipped it across all versions10:40
jamespagebut something changed10:40
coreycbjamespage: ok11:52
coreycbjamespage: there are some dep8 failures due to curl not being available in arm. i'll fix those up.11:56
coreycbjamespage: it seems that some of the nasty py3.7 bugs may be fixed in py3.7 itself.  i'll check and work with doko on it. i was hitting similar ones to this on a handful of projects: https://storyboard.openstack.org/#!/story/200318612:00
jamespagecoreycb: have you worked on any py3 switchovers for components yet?12:04
jamespagein the charms that is12:04
coreycbjamespage: not for the charms yet, but planning to start once rocky cleanup is done12:04
jamespagecoreycb: ok I'll start poking on a few - cinder first12:04
coreycbjamespage: ok, thanks12:05
ahasenackhmm12:25
ahasenack /tmp/autopkgtest.cRVUhE/build.cWY/src/debian/tests/ldap-user-group-krb5-auth: 57: /tmp/autopkgtest.cRVUhE/build.cWY/src/debian/tests/ldap-user-group-krb5-auth: debian/tests/login.exp: Permission denied12:25
ahasenackit has +x12:25
ahasenackmaybe it's mounted as noexec12:28
ahasenackit worked locally in qemu/kvm12:28
cpaelzermaybe it looses +x on the way?12:29
cpaelzercan you for testing chmod it before calling?12:29
cpaelzeror pass it like $ expect -f foo.exp12:29
ahasenackthe latter would be my next attempt12:30
ahasenackbut it worked here12:30
ahasenackkvm and lxd12:30
cpaelzerodd12:30
cpaelzerI also thought that there should be no difference12:30
ahasenackalso worked in a debian lxd12:30
cpaelzerwhich architecture was the fail ahasenack12:30
ahasenackall12:31
cpaelzerwow12:31
ahasenackhttps://bileto.ubuntu.com/excuses/3399/cosmic.html12:31
ahasenackhm, maybe I need -f in the shebang line12:33
cpaelzermaybe dash/bash/sh is different there?12:33
cpaelzeris expect a test dependency?12:33
cpaelzerhmm, yes it is12:34
cpaelzerahasenack: http://paste.ubuntu.com/p/Q3gXJv5zGB/ ?12:36
ahasenackyeah12:36
ahasenackbetter go all the way, or else verifying all alternatives will take a whole day12:37
cpaelzeryep12:37
cpaelzerI also found the -- in the man page12:37
cpaelzerso I added i12:37
cpaelzert12:37
ahasenackcpaelzer: snapper upstream took the armhf build fix patch12:57
ahasenackanother delta will bite the dust, soon12:57
jamespagecoreycb: ok so cinder looks promising - got all but on of the tempest.api.volume tests to pass first run13:02
coreycbjamespage: not bad13:03
jamespagecoreycb: https://review.openstack.org/60002713:03
cpaelzerahasenack: \o/13:08
coreycbjamespage: commented13:09
jamespagecoreycb: good question about clearing out the py2 cruft13:13
jamespagecoreycb: we can purge out any python-* packages from the original installed pkgs; however we'll need an autoremove helper to then purge out any deps!13:16
coreycbjamespage: ick13:16
jamespagecoreycb: meh it kinda needs to happen13:16
jamespagecoreycb: for example python-cinder would still be installed, but is not mention anywhere in the charm13:16
coreycbjamespage: worth noting this is likely just a rockey issue. stein will be easier. we can just make py3 alternatives have precedence.13:18
coreycbrocky13:18
jamespageagreed13:18
kstenerudahasenack: Is there more to do with logwatch re: getting debian's attention?13:30
cpaelzerkstenerud: does "knowing the maintainer well" count?13:31
ahasenackkstenerud: did you create a merge request?13:32
ahasenackkstenerud: good morning :)13:32
ahasenackkstenerud: while I have you, keep an eye on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html13:32
ahasenackkstenerud: your bind9 sponsored upload is in there13:32
jamespagecoreycb: https://github.com/juju/charm-helpers/pull/20913:51
ahasenackkstenerud: I think you can move the 1769440 card to done, bind9 migrated. Did you check that proposed-migration page in time, while bind9 was still in there? Just so you know the process14:12
kstenerudahasenack: Yes I saw it with tests passed and expected fails yellow14:17
ahasenackok14:17
ahasenackkstenerud: that bind9 bug, it needs an sru to bionic now :)14:17
ahasenackfeel free to use the same card I mentioned above, or create a new one for the sru work14:18
jamespagecoreycb: do you think missing curl might be the issue on the glance autopkgtest failures as well?14:18
coreycbjamespage: yes that's the problem. i have a couple pkgs testing here: https://bileto.ubuntu.com/#/ticket/312514:18
jamespagecoreycb: ack will leave in your more than capable hands!14:25
coreycbjamespage: ha!14:26
dpb1kstenerud: did we hear back from debian on logwatch?14:35
kstenerudNo, I hadn't done the change in their git repo. Working on that now14:37
kstenerudahasenack: Is there a special procedure for making patches to salsa? Like tests to run etc?14:39
ahasenackkstenerud: nothing standard14:40
ahasenackif there are dep8 tests in the package, then I would run them14:40
ahasenackotherwise, I would show how the change was tested14:40
ahasenackdon't forget it's debian, not ubuntu, when copying logs and such14:40
kstenerudSo basically I just fork, make the same 2 commits, then merge req?14:40
ahasenackluckily it's easy to use a debian container14:40
ahasenackyeah, and I would leave the debian release as "UNRELEASED" in d/changelog, since the commit is not necessarily tied to a new upload14:41
ahasenacklet them sort that out14:41
ahasenackbut do use dch, and format d/changelog approprietly14:41
ksteneruddch?14:42
ahasenacktry it :)14:43
kstenerudoh hah cool :)14:44
ahasenackI suggested dch this time, instead of git-ubuntu.reconstruct-changelog, because git-ubuntu wouldn't work in a debian container14:44
ahasenacknot out-of-the-box at least14:44
kstenerudOh, the version is labeled logwatch (7.4.3+git20161207-2ubuntu1)14:45
kstenerudshould it have the ubuntu1 at the end?14:45
ahasenacknope14:45
ahasenackwell, not in a debian merge request for sure14:45
ahasenackand, if the current d/changelog already has an entry with UNRELEASED, then don't create a new (versioned) one, just add your bit to the existing one14:46
ahasenackthere is a format for that, you can find it on other changelog files if you look, it's like [Some Name]\n  * change14:46
kstenerudOK so I'm basically doing:14:49
kstenerud  * sshd: ignore disconnected from user USER. (closes: 855539)14:49
kstenerud855539 being their bug report on this14:50
ahasenackkstenerud: yes, but please mention the file you are changing14:54
ahasenacklike, full path14:54
dpb1kstenerud: (just curious on logwatch, since we hadn't reached out before)15:07
ahasenackcpaelzer: sea of green! https://bileto.ubuntu.com/excuses/3399/cosmic.html15:12
ahasenackcpaelzer: calling expect -f <script>15:13
ahasenackinstead of <script> directly15:13
cpaelzerok, then that shall be the solution15:20
SuperLagI'm trying to set up an Ubuntu VM on my local machine. It'll use NAT, and share the existing connection, but I'd like to make it a static IP, so when the term opens and my SSH-on-open command runs, it connects automatically. I'm not sure how do set up a static IP during the install process.16:08
subvhomeCan someone direct me to a resource that can help me configure my ubuntu server to login automatically (no GUI)16:24
subvhomenevermind figured it out :)16:27
dpb1SuperLag: are you using the 18.04.1 LTS server install?16:30
SuperLagyes16:58
SuperLagdpb1: yes16:58
dpb1SuperLag: in the network config screen, you can choose a static IP17:25
ahasenackkstenerud: in your logwatch salsa mp,17:56
ahasenackkstenerud: the file you should mention in d/changelog is the patch file you are adding, not the file that the patch itself is changing17:56
ahasenackkstenerud: so, it should be d/p/ssh-ignore-disconnected.patch17:57
ahasenack(or debian/patches/...)17:57
kstenerudah ok17:58
kstenerudahasenack: For the strongswan repro case, I'm going to have to set up a fairly complicated thing with config files and scripts. How would I fit that to the bug report and MP?18:03
ahasenackkstenerud: strongswan related to logwatch?18:03
ahasenackor that other mp which was started by a community member?18:04
kstenerudthe other mp18:04
kstenerudI'll need to set up a vpn server and client in separate machines and then test with different versions on the client side18:04
ahasenackit is complicated indeed. I would suggest to just run the dep8 tests, they cover a lot already18:04
ahasenackI mean,18:05
ahasenacknot the depp8 tests18:05
ahasenackthe qa-regression-tests18:05
ahasenackhttps://launchpad.net/qa-regression-testing18:05
ahasenackinside the scripts directory, there is a test-strongswan.py script18:05
ahasenackwith instructions18:05
ahasenackthis mp of mine, from some days ago, went through them. The description of the mp has pastebins showing these scripts being run: https://code.launchpad.net/~ahasenack/ubuntu/+source/strongswan/+git/strongswan/+merge/35364218:07
ahasenackkstenerud: btw, your logwatch salsa mp, you still have the old s/s/ path in the changelog entry, not sure if you saw that. I see you changed the mp title18:10
kstenerudahasenack: how were you able to see the diffs on salsa? I can't find a button for it18:14
kstenerudalso, for that entry, I was copying from previous entries in the changelog, like: s/s/amavis: Fix perl warning "redundant argument in sprintf".18:16
kstenerudshould I change it to the other style in changelog?18:18
ahasenackkstenerud: there are three tabs in the MR page18:26
ahasenackdiscussion, commits, changes18:26
ahasenackit defaults to discussion18:26
ahasenackkstenerud: about s/s, hm, I see the previous entries. It looks odd18:29
ahasenackI'm fine either way then, as you prefer18:29
kstenerudahasenack: How do I initiate a qa-regression test?18:48
ahasenackkstenerud: branch that code, cd into scripts/18:49
ahasenackthere is a readme file in that dir18:49
ahasenackstart with     $ sudo ./install-packages test-foo.py18:49
ahasenackthat will install dependencies needed by that particular test-<foo>.py script18:50
ahasenackthen read instructions on that script test18:50
ahasenacker, test script18:50
kstenerudAll I see are a bunch of *.c files in scripts18:51
kstenerudfind . -name install-packages returns nothing18:52
ahasenackkstenerud: "that code" -> https://launchpad.net/qa-regression-testing18:57
ahasenackis that what you branched?18:57
ahasenackhttps://code.launchpad.net/qa-regression-testing18:57
kstenerudahasenack: Is this meant to be cloned and run from within a vm?19:09
ahasenackkstenerud: yes, and it's meant to be run on the machine where the software you are testing is installed19:09
ahasenackso a vm or lxd is best, yes19:10
sdezielcpaelzer: re LP: #1789551, I'm not sure don't understand why Xenial would be harder to tackle than Bionic. Isn't is just a matter of calling "seccomp_attr_set(ctx, > SCMP_FLTATR_CTL_TSYNC, 1)" irrespective of whitelist vs blacklist?20:09
ubottuLaunchpad bug 1789551 in qemu (Ubuntu Bionic) "qemu: CVE-2018-15746: seccomp: blacklist is not applied to all threads" [High,Triaged] https://launchpad.net/bugs/178955120:09
ahasenackkstenerud: in the command line from that MP I pasted you earlier,20:41
ahasenacksudo ./test-strongswan.py $test 192.168.122.78 10.0.2.0/24 192.168.122.42 10.0.1.0/24 -v20:41
ahasenack192.x.x.x is the libvirt network where the vm is on20:41
ahasenack10.0.2 and 10.0.1 are made up networks, no config at all. the test script will set that up20:42
kstenerudok20:42
ScottEOh boy, this is going to be fun... We're finding users who upgrade to openssh 7.8 can no longer ssh to our ubuntu servers due to some strictness in the new openssh version. I created https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1790963 with links to the same issue found in other Linux distro. It's unclear what the right fix is, but thought I would mention it here because it's likely to have20:49
ubottuLaunchpad bug 1790963 in openssh (Ubuntu) "Unable to connect with openssh 7.8 client" [Undecided,Confirmed]20:49
ScottEwide blast radius.20:49
blackflowScottE: not sure I see this problem here20:54
blackflowScottE: hmmm, wait, 7.8 clients when connecting to older clients, you say?20:55
ScottEblackflow Basically the 7.8 client is not (fully) compatible with openssh version <7.820:57
TJ-ScottE: according to the release notes, the breakage should only occur in non-default configurations. Is that the case here, or is the Ubuntu default for 7.6/7.7 causing the issue20:58
blackflowScottE: yea I thought I was running 7.8 but I'm not, it's 7.6. I'm gonna test now with 7.8 from Fedora21:00
ScottEYou very well could be correct there TJ- we're still in the process of trying to figure that out21:00
TJ-here, on 18.04 with v7.6, "sshd -T" with no sysadmin over-ride shows "hostbasedacceptedkeytypes ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa"21:03
TJ-And pubkeyacceptedkeytypes ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa21:04
TJ-seems like a daft change for openssh to make though; keeping the option name with *KeyTypes but changing the semantics to mean *SignatureAlgorithms! Recipe for confusion there21:07
ScottEYeah, it's looking very likely that our custom server config (with the intent to improve security) is causing the breakage here. I never did suspect it to be an Ubuntu bug per se21:08
ahasenackso the option is still called PubkeyAcceptedKeyTypes, but now its value is a signature algorithm instead of a key type?21:10
blackflowScottE: yeah, default configs work just fine21:11
blackflow7.8p1 client from Fedora connecting to 7.6 Ubuntu and 7.2 FreeBSD21:11
ScottEblackflow great, thanks for the confirmation on that - that will greatly limit who runs into this right there21:12
TJ-ahasenack: that's seems to be correct21:13
TJ-ahasenack: I guess (some of) the values were always signature algorithms, not key-types21:13
TJ-ScottE: well, your changes did improve security - no-one could connect :)21:14
kstenerudahasenack: None of the tests fail in bionic. I'm not really sure how to cause the issue21:14
ScottETJ- haha21:14
ahasenackkstenerud: did you see apparmor denied messages in dmesg?21:15
kstenerudnope21:15
ahasenackkstenerud: then ok, proceed with just the dep8 results, we will rely on the reporter for this one21:15
kstenerudok21:15
TJ-did I see mention of a possible strongswan problem? (wondering if it's something I've hit recently!)21:17
ahasenackTJ-: https://code.launchpad.net/~fermulator/ubuntu/+source/strongswan/+git/strongswan/+merge/35342321:22
ahasenackbug being #178625021:22
ahasenackkstenerud: wait, was apparmor even enabled for strongswan? It might be an optional apparmor profile21:23
TJ-ahasenack: hmmm, I think I've been seeing NetworkManager reporting the same21:23
kstenerudHow do I check?21:23
sdezielstrongswan's apparmor is enabled by default IIRC21:24
sdezielkstenerud: aa-status21:24
sdezielyou should see charon as being confined21:25
TJ-ahhh, no, slightly different. I've been seeing: <warn>  [1536149701.2078] error requesting auth for org.freedesktop.NetworkManager.enable-disable-connectivi21:25
TJ-ty-check: Authorization check failed: Failed to open file “/proc/1554/status”: No such file or directory21:25
TJ-I see "enforced" for /usr/lib/ipsec/charon21:26
kstenerudsdeziel: It says charon is unconfined21:30
ScottESo this openssh issue might be only when using certificates (which we do) - compiling 7.8 with the same config works fine - so it appears not our customization - I'll update the bug with specific mention around certificates21:31
=== keithzg_ is now known as keithzg
SuperLagRHEL has a kickstart configurator that'll give you at the very least a template to work from for kickstart files. Is there an Ubuntu equivalent for preseed files?23:57

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!