/srv/irclogs.ubuntu.com/2017/12/07/#ubuntu-server.txt

jlambstill having a problem... with a second NIC on my server02:20
jlambI added emp0s8:`n addresses: [192.168.1.1/24] to my 01-netcfg.yaml file02:21
jlamband ran sudo netplan apply02:21
jlamband sudo ip link set enp0s8 up02:22
jlambbut, ip addr still doesn't show the ip4 address for emp0s802:22
=== SmokinGrunts is now known as SG_Sleeps
lordievaderGood morning07:06
cpaelzerlate hi everybody08:08
ahasenackcpaelzer: hi, iproute2 sru has been accepted, now we need to click on the reds in the excuses page11:45
ahasenack:/11:45
ahasenacklet me check that they are the same errors we saw before in bionic11:46
ahasenackwho is chrony's maintainer?11:48
ahasenackhe/she is bound to have seen these frequent dep8 test failures11:48
EraserPencilHi! Anyone has a guide to how I could achieve Dropbox style server without using owncloud or nextcloud?12:06
cpaelzerahasenack: ping me once you checked which ones seem flaky tests ok?12:17
ahasenackcpaelzer: systemd dep8 errors in s390: http://autopkgtest.ubuntu.com/packages/s/systemd/artful/s390x12:59
ahasenackmine is at the top (iproute), but others have failed in the same way12:59
ahasenackFileNotFoundError: [Errno 2] No such file or directory: '/boot/grub/grub.cfg' is the error13:00
ahasenackany idea about that?13:00
ahasenackit seems the systemd-fsckd test was skipped in the one lonely success13:01
ahasenack"systemd-fsckd        SKIP Test requires machine-level isolation but testbed does not provide that"13:01
cpaelzerahasenack: ther eis no grub on s390x13:01
cpaelzerand never will be13:01
cpaelzerlike 640k will be enough forever13:01
ahasenackthere seem to be two "threads" writing to stdout in the failed test13:02
ahasenackI see lines like13:02
ahasenack(Reading database ... 95%13:02
ahasenackwith "Setting up util-linux (2.30.1-0ubuntu4.1) ..." in between13:02
ahasenacklet's see why that test isn't being skipped13:03
cpaelzerahasenack: I re-triggered the others, but the two s390x issues need to be resolved or skipped13:03
cpaelzerwell firejail might ahve been a race with another upload with some luck13:04
cpaelzeror other out of date-ness13:04
ahasenackfirejail failed like that before13:04
ahasenackbut let me get to that in due time13:04
cpaelzerahasenack: once the others re-ran you can check then13:05
cpaelzerahasenack: if no others are left ask for overrides in #ubuntu-release13:05
cpaelzerFYI ahasenackthese will eventually go into http://bazaar.launchpad.net/~ubuntu-sru/britney/hints-ubuntu-artful/changes13:07
ahasenackcpaelzer: the s390 tests were always in a vm, right13:09
ahasenackxnox: around?13:10
cpaelzerahasenack: no13:11
cpaelzerahasenack: they were in a container up until recently13:11
cpaelzerahasenack: which might be why they now are considered regressiosn13:11
ahasenackah, that explains it13:11
ahasenackI didn't know you could do containers in s39013:11
cpaelzerahasenack: that is what I fixed a few of last week13:11
cpaelzerjust as well as everywhere13:11
ahasenackso now that it's a vm, the machine-isolation constraint works and the test is run13:12
ahasenackbut it uses grub, and that fails13:12
ahasenackso I need to skip that test in s39013:12
ahasenacksounds reasonable?13:12
* ahasenack looks for the dep8 spec13:13
ahasenack"Such specific HW need seems rare and there is no e.g. autopkgtest feature to limit Architectures."13:18
ahasenackprobably need to add the skip to the test itself then, have it return a fake success13:19
ahasenackcpaelzer: I'm looking at your dpdk dep8 https://bugs.launchpad.net/bugs/1551158 fix13:28
ubottuLaunchpad bug 1551158 in dpdk (Ubuntu) "DPDK dep8 tests failing on non supported platforms" [High,Fix released]13:28
ahasenackyou added debian/tests/check-dpdk-supported-arch.sh and you source that in the tests13:28
ahasenackbut you also added arch-specific bits to the depends line13:28
ahasenackDepends: dpdk [amd64 i386] <--13:28
rbasakahasenack: any ETA on the my MySQL merge review please?13:28
cpaelzerahasenack: yes and yes13:29
ahasenackrbasak: gonna start after I solve these iproute2 migration issues13:29
cpaelzerahasenack: the arch qualifier will ensure it doesn't run at all13:29
cpaelzeras it doesn't qualify13:29
ahasenackcpaelzer: is the latter necessary? Without the former, the arch qualifier would just lead to a failed test?13:29
rbasakahasenack: no problem thanks!13:29
cpaelzerthe checker is mostly if even on an arch there are needs like cpu features13:29
cpaelzerahasenack: it is a double cahnce for error13:30
cpaelzerahasenack: without arch qualifier it will try to install and might fail13:30
cpaelzerahasenack: so you have to mark where you expect THE INSTALL to work13:30
cpaelzerahasenack: of the package13:30
ahasenackcpaelzer: the dpdk package does not exist in these other arches?13:31
cpaelzerahasenack: only afterwards the script will run and you can sort out and skip tests13:31
cpaelzeryes13:31
ahasenackok, so you also had an install failure that you are fixing here13:31
cpaelzeryes13:31
ahasenackok,thx13:32
cpaelzerand check-dpdk-supported-arch.sh then does any in depth checks13:32
cpaelzerlike cpu features13:32
cpaelzeror experimental arches like for a while ppc64el had the packages but was not meant to work13:32
cpaelzerwell that sounds bad13:32
cpaelzerit worked13:32
cpaelzerbut was meant to be experimental/tech-preview13:33
cpaelzerahasenack: the story even went further, until s390x had KVM execution the isolation-machine blocked it13:34
ahasenackright13:34
ahasenackthat's my case13:34
ahasenackit started failing about 3w ago, with several packages13:34
ahasenackI mean, other packages that triggered the systemd dep8 test suite13:35
cpaelzeryep13:35
ahasenackI'm filing a bug and putting up an mp for it13:35
ahasenackI wonder how the bionic upload passed (of iproute2)13:35
cpaelzerahasenack: for the case to complete the story the final change then was https://gerrit.fd.io/r/gitweb?p=deb_dpdk.git;a=commitdiff;h=b179808726394c63b97747b31ca603392c18216813:36
cpaelzerbecause since KVM exec it ran into said package-install-issue13:36
cpaelzeras we didn't have the arch qualifier on that yedt13:36
ahasenackcan't you negate an arch there?13:36
cpaelzerI don't know13:37
cpaelzersry13:37
ahasenackok13:37
ahasenackcpaelzer: hm, "zipl" is an s390 thing, no?13:44
* ahasenack looks around for didrocks13:45
cpaelzerahasenack: yes13:46
cpaelzerahasenack: zipl is the lilo of s390x13:46
ahasenackI think this test was meant to work on s39013:46
ahasenackI might be out of my depth here then13:46
ahasenack    if platform.processor() == 's390x':13:46
ahasenack        enable_plymouth_zipl(enable)13:46
ahasenack    else:13:46
ahasenack        enable_plymouth_grub(enable)13:46
cpaelzeryeah, there is some intention here13:46
* ahasenack hops on an s390 to check what platform.processor() returns13:47
ahasenackit's correct13:47
cpaelzerit is13:48
ahasenackok, I need to actually run this test there then13:48
ahasenackcpaelzer: am I supposed to be able to run autopkgtest-buildvm-ubuntu-cloud on s1lp5? Or do I need to use nested vm?13:52
ahasenackubuntu@s1lp5:~/andreas$ autopkgtest-buildvm-ubuntu-cloud -r artful -o adt-images13:52
ahasenackERROR: no permission to write /dev/kvm13:52
cpaelzerahasenack: I thik lp4 is the one we share13:59
cpaelzerahasenack: but long story short no14:00
cpaelzerahasenack: the tests won't work14:00
cpaelzerthere is a lot of console magic in autopkgtest which doesn't apply14:00
cpaelzerahasenack: create a VM with uvtool, then run the test in that VM (without the autopkgtest around it)14:01
cpaelzeronly go the last steps to try inside if you really really need it14:01
ahasenackit must be platform.processor() returning something else over there14:04
cpaelzeryep14:04
cpaelzermaybe it fails in a VM?14:04
ahasenackthe test clearly ran     plymouth_enabled = 'splash' in open('/boot/grub/grub.cfg').read(), which is only in enable_plymouth_grub()14:04
ahasenackyeah, let's start ismple. Bring up the vm and run that platform.processor()14:04
cpaelzerdoing that atm14:05
ahasenackcpaelzer: hm, there is no uvt-kvm in that s1lp5 host, should I switch to that lp4 one you mentioned? You gave me access to lp5 once upon a time, maybe before lp4 was ready for us?14:05
cpaelzerlp5 is mostly mine for the more sinister experiments14:06
ahasenackthere used to be uvt-kvm, since I ran it before there14:06
ahasenackah, ok14:06
cpaelzerlp4 is meant to be the somewhat stable shared host14:06
ahasenackbetter remove me from lp5 then :)14:06
cpaelzerit is s390x on a KVM guest as well14:07
cpaelzertrying to run the full test14:08
ahasenack"s1lp4 purpose: jenkins node" :)14:08
ahasenacks1lp3 seems to be the one to use14:08
cpaelzerI wrote it in the wiki14:09
cpaelzeryep s1lp314:09
ahasenackah, found it14:20
ahasenackit's a fix that went into bionic14:22
ahasenack    New changelog entries:14:22
ahasenack      * systemd-fsckd: Fix ADT tests to work on s390x too.14:22
ahasenacksomehow I missed that changelog entry14:22
ahasenackcpaelzer: it's a bug in artful's package, fixed in bionic. We probably don't sru dep8 fixes, or do we?14:23
cpaelzerahasenack: we soemtimes do sometimes not14:29
cpaelzerdepends on the case14:29
cpaelzerbut systemd uploads are grouped by xnox anyway14:30
cpaelzeryou know he collects a bunch and groups them for tests14:30
cpaelzerso he might have a plan or nack already14:30
cpaelzerI guess you are safe to ask for an override on the current version thou14:30
cpaelzerahasenack: ^^14:30
ahasenackthanks, I'm asking in #ubuntu-release14:31
cpaelzerif you want you can explain so in a bug, release team members like to reference something with more context14:31
cpaelzeras it is just a lin in the britney hints14:31
ahasenackcpaelzer: I have a bug, can you accept the artful nomination? https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/173695514:33
ubottuLaunchpad bug 1736955 in systemd (Ubuntu) "dep8 test systemd-fsckd fails on s390" [Undecided,Fix released]14:33
rbasakahasenack: I don't think we'd usually SRU a test fix on its own, but bundling one with an SRU is absolutely fine.14:36
ahasenacksounds reasonable14:37
cpaelzerapproved14:37
cpaelzerit is correct to have that bug task14:37
cpaelzerand you can refer to it for the override14:37
ahasenackcpaelzer: thx14:38
=== nitemare is now known as trobotham
ahasenackcpaelzer: one more task, zesty is also affected: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/173695515:51
ubottuLaunchpad bug 1736955 in systemd (Ubuntu Artful) "dep8 test systemd-fsckd fails on s390" [Medium,Triaged]15:51
ahasenackxenial and trusty are fine (no systemd dep8 tests being run in their migrations)15:51
pmatulisfor the no_proxy environment variable, i often see addresses and hostnames. the docs say categorically that hostnames should be used. also, i often see both address and name for the local system: 127.0.0.1, localhost. is this necessary?16:04
ahasenackpmatulis: surprisingly I've seen many cases where an app would send a request to localhost via the proxy16:07
ahasenackI don't know why that's not the default16:07
joeliono_proxy has always seemed partially implemented to me16:19
boxrickI have the following lines in my preseed postinstall script to upgrade and configure ansible to the latest version.17:05
boxrickhttps://gist.github.com/boxrick/ae85da1eedd485930a37a3dfd6e0832917:05
boxrickBut I wish for this to happen in the preseed itself and not the post install17:05
boxrick3Any ideas?17:05
pmatulisahasenack, thanks17:06
m15kDoes this make any sense? https://gist.github.com/asbachb/9fceeb1d0a00114eec31c6af82ca980518:34
m15kIs 2001:470:4242:1042::1/64 the same as 2001:470:4242:1042::1/56 ?18:40
ahasenackm15k: yes, ifup/down will only work with interfaces defined in /etc/network/interfaces18:40
m15kahasenack: Any idea howto remove the interface?18:41
ahasenackm15k: what ubuntu is this?18:41
m15k16.0418:41
ahasenackm15k: does "lxc network list" list that interface?18:42
m15kahasenack: yes. but "lxc network delete lxcbr0" results in "error: not found"18:43
ahasenackis managed "no" for it?18:43
m15kyes it's no18:43
ahasenackthat interface was created when you first installed lxc (not lxd: then it would have been lxdbr0). Are you sure you want to remove it? Do you use lxc or lxd?18:45
m15kYes I am sure. I think I created it manully via brctl18:45
ahasenackdoes /etc/default/lxd or /etc/default/lxc (or a name like that) reference it still?18:46
m15kahasenack: I think that's it. lxc-net bridge was enabled and referenced to lxcbr018:47
ahasenackyou can probably change its details in that /etc/default/ file18:48
m15kahasenack: thanks. that was the right hint! :)18:48
ahasenackcool18:49
=== LudusLight is now known as Ludus
m15kahasenack: Are you familiar with lxd?18:53
=== Ludus is now known as LudusLight
ahasenackm15k: somewhat18:53
ahasenackI use it a lot18:54
m15kI wonder what "Would you like LXD to NAT IPv6 traffic on your bridge?" actually means18:54
boxrickHello! I am currently using the following line in preseed on Xenial 16.04 LTS d-i base-installer/kernel/altmeta string hwe-16.0418:55
boxrickSo I have have the more up to date kernel18:55
m15kI know what NATting is, but I'm a little bit unsure what's the difference in ipv6 context.18:55
boxrickHowever this causes all sorts of inconsistencies within my preseed postinstall chroot environment where I need correct libraries18:55
boxrickIs there any way to install *just* the new kernel rather than do the thing it seems to where it installs the old one then updates it later?18:56
ahasenackm15k: well, it depends if you have global addresses in your lxds or not19:00
ahasenackif you don't, and you want to use ipv6 to reach the internet from that container, then you will probably need ipv6 nat, but also a global ipv6 on your host19:01
m15kahasenack: So when I've a public ipv6 subnet I should disable NAT?19:01
ahasenackif your containers get a slice of that and have global addresses, probably yes19:01
ahasenackI have never natted ipv6, tbh19:01
ahasenackI just get one /6419:01
m15kahasenack: You assign a public ipv6 to your containers?19:02
ahasenackno19:02
ahasenackI don't use ipv6 in them19:02
m15kI currently try that. Because of that I play a little bit around with these bridges.19:03
m15kWhen I type "resolvconf -u" there are dns servers in /etc/resolv.conf that are not configured in "/etc/resolvconf/resolv.conf.d" any ideas how they get into the generation?21:39
geniiProbably by dhcp21:39
rbasakpowersj: congrats!21:58
powersjrbasak: thank you :)21:58
dpb1oh, it happened?22:15
dpb1nice22:15
Neo1who know my server can access server sysadmin?22:54
Neo1does sysadmin of server can access my server?22:55
Neo1I mean files on my server22:55
dpb1root can generally access anything that is not encrypted.22:57
sarnoldand if the data is ever decrypted on the server, root can access that too.22:58

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