cpaelzergood morning05:21
* bryceh waves05:31
utkarsh2102cpaelzer: o/06:04
cpaelzerhi utkarsh210206:13
cpaelzerThis isn't selective unfairness, b_ryceh I already spoke with in other channels :-)06:14
mirespacegood morning07:28
cpaelzerhi mirespace07:30
mirespacehi :)07:31
utkarsh2102mirespace: o/07:32
cpaelzermirespace: I heard in the news another pack of sahara sand is sent our way - since last time we had like 4 days delay and 1/4 let me ask if this one passed you again and how it was compared to last time?07:33
mirespacewe had the second on last Thursday and it ended on Saturday07:34
mirespaceIt was less orange07:34
mirespacewe had muddy rains, but less dense07:35
cpaelzerhmm, ok then the delay stays the same it started here with slightly odd colored low clouds07:35
mirespace:) Yes, the feeling when walking through the street was better than the first07:36
mirespaceAnd now is raining a lot07:36
mirespacein the news here : "did you believe the spring had arriven? No! take off your coat from the wardrobe.. winter is coming !"07:37
cpaelzeryeah we seem to have the same predictions over here07:39
yurtesenIn Ubuntu, rsyslogd runs as syslog:syslog by default. This cause problems with packages imported from Debian which expect syslog can set file ownerships correctly as it runs as root in Debian.10:48
yurtesencan rsyslogd user be changed?10:49
athosgood morning :)11:59
ahasenackkanashiro_: resource-agents-extra is in main, according to rmadison12:14
ahasenackboth in impish and jammy12:14
ahasenack resource-agents-extra | 1:4.7.0-1ubuntu5 | impish | amd64, arm64, armhf, ppc64el, riscv64, s390x12:14
ahasenack resource-agents-extra | 1:4.7.0-1ubuntu6 | jammy  | amd64, arm64, armhf, ppc64el, riscv64, s390x12:14
kanashiro_ahasenack, ah okay, src:resource-agents and its binaries were in main before we start the current work to split agents12:27
kanashiro_I think fence-agents-extra is not in main12:27
ahasenackif they remained in main, then either they are seeded, or something is still pulling them in12:28
ahasenackbin:resource-agents-extra I mean12:28
kanashiro_yes, fence agents has what I was expecting:12:29
kanashiro_ fence-agents-extra | 4.7.1-1ubuntu7 | impish/universe | amd64, arm64, armhf, ppc64el, riscv64, s390x12:29
kanashiro_ fence-agents-extra | 4.7.1-1ubuntu8 | jammy/universe  | amd64, arm64, armhf, ppc64el, riscv64, s390x12:29
kanashiro_we should demote bin:resource-agents-extra12:29
ahasenackcan you check what is holding it in main?12:30
kanashiro_ahasenack, I think nothing, src:resource-agents and bin:resource-agents were in main, then we split the agents into resource-agent-base and resource-agents-extra, and now everything is in main12:31
kanashiro_cpaelzer, what should I do to demote only bin:resource-agents-extra?12:32
ahasenackpacemaker-resource-agents is in main, and suggests resource-agents-extra, but depends on resource-agents-base12:38
ahasenackso that's not it12:38
ahasenackoh, resource-agents depends on resource-agents-extra12:39
ahasenackand resource-agents is in main12:39
ahasenackkanashiro_: ^12:39
ahasenack$ apt-cache show resource-agents|grep Depends12:39
ahasenackDepends: resource-agents-base (>= 1:4.7.0-1ubuntu6), resource-agents-extra (>= 1:4.7.0-1ubuntu6)12:39
kanashiro_ahasenack, hum, yes, resource-agents depends on -base and -extra indeed12:40
kanashiro_but it still the issue I mentioned, everything provided by src:resource-agents is in main12:41
kanashiro_we need to demote bin:resource-agents and bin:resource-agents-extra then12:42
kanashiro_fence-agents is correct:12:44
kanashiro_ fence-agents        | 4.7.1-1ubuntu8 | jammy          | source12:44
kanashiro_ fence-agents        | 4.7.1-1ubuntu8 | jammy/universe | all12:44
kanashiro_ fence-agents-base   | 4.7.1-1ubuntu8 | jammy          | all12:44
kanashiro_ fence-agents-common | 4.7.1-1ubuntu8 | jammy          | amd64, arm64, armhf, ppc64el, riscv64, s390x12:44
kanashiro_ fence-agents-extra  | 4.7.1-1ubuntu8 | jammy/universe | amd64, arm64, armhf, ppc64el, riscv64, s390x12:44
cpaelzerhi kanashiro_ only started to read this now ...12:45
ahasenackresource-agents reverse tree: https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.jammy/rdepends/resource-agents/resource-agents12:46
ahasenackpacemaker-cli-utils (in main) depends on resource-agents12:46
cpaelzeralso resource-agents itself (transitional) is in main still it seems and depends on it as well12:47
cpaelzerandreas already found it12:47
cpaelzermaybe that dep can/should be changed to resource-agents-base?12:48
kanashiro_meh, yes, I think I forgot to update pacemaker-cli-utils runtime deps12:49
kanashiro_the other pacemaker binaries are ok12:49
kanashiro_cpaelzer, yes, I'll do that12:49
ahasenackare we sure it does not need or expect the bits in resource-agents-extra?12:51
ahasenackcpaelzer: why not do a proper merge with debian for libtpms?12:58
ahasenackthey are at 0.9.3 too12:59
ahasenackmy eyes deceived me, they are at 0.9.2-312:59
cpaelzerahasenack: that plus we have no properly split delta yet AND they have changes we are not needing atm (post FF)13:00
cpaelzerahasenack: I replied in the libtpms MR13:37
cpaelzerahasenack: but to make this quick let me ask here - I could make it ppc64 only, but I used it int he way it was in debian already (proven to work) instead of modifying it13:37
cpaelzerahasenack: do you think it worth and/or important to make it ppc64-only?13:38
ahasenackI'm ok with that, just replied (but didn't submit yet)13:38
ahasenackjust doing a quick install check13:38
ahasenackcpaelzer: done13:40
cpaelzerthank you , having a look13:40
cpaelzerThanks, I'll be waiting what foundations says before an upload (and also beta-freeze)13:42
kanashirodo I need the release team blessing to upload pacemaker fixing the resource-agents dependency?14:35
kanashiroAFAICS it is not seeded14:37
ahasenackI'm unsure, it's a change in behavior for "apt-get install resource-agents"14:48
kanashiro"apt-get install resource-agents" will pull in the same set of packages than before, the difference is that not all of them will not be in main14:49
kanashiros/will not/will/14:50
brycehlvoytek, for the SRU reviews on mysql, I've been keeping my eye out for them to show up at https://code.launchpad.net/~canonical-server/+activereviews.15:59
lvoytekThat's fair, I think they disappeared because the canonical-server slot was consumed, I'll re-add them16:00
brycehdo I recall correctly that it's the two for lp: #1964969?16:01
ubottuLaunchpad bug 1964969 in mysql-8.0 (Ubuntu Impish) "mysql error log always contains errors with mysqlx when installing/upgrading" [Undecided, In Progress] https://launchpad.net/bugs/196496916:01
lvoytekyeah in combo with lp: #189924816:02
ubottuLaunchpad bug 1899248 in mysql-8.0 (Ubuntu Impish) "mysql server crashes during install/update: Error: Unable to shut down server with process id X" [High, In Progress] https://launchpad.net/bugs/189924816:02
sbeattiecpaelzer: hey, what needs to happen for the nftables seed change merge to happen?16:58
ahasenacksbeattie: is there an mp up?17:05
ahasenackkanashiro: so, to recap, what is the plan again? bin:resource-agents-base in main, bin:resource-agents-extra in universe?17:19
ahasenackand what about bin:resource-agents (the meta package), that will have to be in universe too, no? Because it pulls in -base and -extra17:20
ahasenackrbasak: is "network-online-ordering" the correct tag? I get only one bug with it: https://bugs.launchpad.net/ubuntu/+source/rsync/+bugs?field.tag=network-online-ordering17:43
ahasenackI thought we had more17:43
ahasenack(hence the desire for a tag)17:43
ahasenackmaybe they were closed17:43
* ahasenack does a broader search17:43
ahasenackstill just that one17:43
kanashiroahasenack, yes, bin:resource-agents should be in universe, and ideally removed in the future17:51
ahasenackkanashiro: and some time ago, before you started working on the HA stack, it was a real package with a lot of agents in it, right?17:52
ahasenackyou split it17:52
ahasenackis that the tl;dr history?17:52
rbasakahasenack: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=network-online-ordering - you have to remove the rsync package filter18:18
cpaelzersbeattie: you'd need a seed change and/or something in main that depends on nftables18:31
cpaelzerthat will pull it into component mismatches18:31
cpaelzerand then it can be promoted18:31
cpaelzersbeattie: do you intend to replace iptables (a lot of potential effort and churn late in the cycle) or only to support nftables along side it (for now) ?18:32
cpaelzersbeattie: also - do you want it to be auto-installed?18:33
ahasenackah, duh18:33
cpaelzersbeattie: oh I see it was explained int he bug18:34
cpaelzer* iptables will be switching to nftables backend, but18:34
cpaelzeriptables availability and usage will probably continue for18:34
cpaelzerforseeable future.18:34
cpaelzerok then18:34
cpaelzersbeattie: something like https://paste.ubuntu.com/p/VtcgvsDh8Z/ on https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform18:35
cpaelzerthat will also install it by default in everything using the standard seed. If you do not want it installed by default, the change would be in a different place 18:36
ahasenackcpaelzer: iptables is already using the nft backend, fwiw18:37
cpaelzersbeattie: I'm no more around :-/ but I hope this helps, and if in doubt e.g. ahasenack / bryceh can also answer most questions you might have18:37
ahasenack /etc/alternatives/iptables -> /usr/sbin/iptables-nft18:37
cpaelzerahasenack: if you read the initial statement in the MIR bug you'll see it18:37
cpaelzerthis is like "start supporting nftables, but do not replace iptables yet"18:38
cpaelzerso given how far in the cycle we are this is no funcitonal change, but declaring nftables supported18:38
ahasenackyeah, it's like ifconfig vs ip18:38
cpaelzerand then in coming cycles more and more changes can happen to swicth over18:38
ahasenackip is nftables in this comparison18:38
cpaelzerwhich also needed to both be around for a while18:38
cpaelzerif/once sbeattie is back try to help him ahasenack / bryceh18:39
cpaelzerand if help worked feel free to nudge him for glusterfs :-)18:39
cpaelzer(most subtle comment ever)18:39
brycehguessing sbeattie's lunching (I just finished myself)18:49
sarnoldmmm, lunch18:50
* ahasenack had a snack18:50
sbeattiecpaelzer: sorry was in meetings plus lunch, was trying to figure out what needed to happen wrt https://code.launchpad.net/~alexmurray/ubuntu-seeds/+git/ubuntu-seeds/+merge/417621 19:01
ahasenacksbeattie: I can take a look19:41
ahasenackserver team, do you recall a service where we changed the systemd unit file from Type=simple to Type=forking so we could detect config file errors at startup?19:50
ahasenackIIRC we did it somewhat recently for a package19:50
ahasenackwell, this year, not like this month19:50
ahasenackathos: did you work on that perhaps? Do you remember?19:50
bryceh'forking' not ringing a bell for me19:51
sarnoldas in, deliberately introduce a mistake into a systemd unit file so you could try to find it as a mistake later?19:53
ahasenackit was a service where "systemctl start <service>" would not tell you if it started or not19:54
ahasenackand that seems to be the common case for Type=simple and Type=exec19:54
ahasenackimagine scripts starting stuff, they most of the time rely on "systemctl start <foo>" telling them if <foo> started or not19:55
ahasenackType=notify works well,19:55
ahasenackssh being an example19:56
ahasenacklike here: https://pastebin.ubuntu.com/p/2pwsJwpcPM/19:56
ahasenackah, I think it was bind919:57
sdezielahasenack: yeah https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/189990219:57
ubottuLaunchpad bug 1899902 in bind9 (Ubuntu) "systemd unit service file does not wait for bind9 to be ready" [Undecided, Fix Released]19:57
ahasenack    - d/bind9.named.service: use systemd Type=forking to signal daemon init.19:58
ahasenack      This fixes a regression of #900788 where services whose startup depend19:58
ahasenack      on name resolutions may fail due to bind9 not being ready (LP #1899902).19:58
ahasenackso it wasn't about a failure19:58
ahasenackjust timing19:58
ahasenackand with forking, systemd had to wait for named to be really running19:58
sdezieland upstream wants to go to Type=notify (https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1899902) so that should be even better19:59
ubottuLaunchpad bug 1899902 in bind9 (Ubuntu) "systemd unit service file does not wait for bind9 to be ready" [Undecided, Fix Released]19:59
sdezielhttps://gitlab.isc.org/isc-projects/bind9/-/merge_requests/5514 <= proper link19:59
ubottuMerge 5514 in isc-projects/bind9 "Add support for reporting status via sd_notify()" [Opened]19:59
ahasenackand as a result, they are implementing notify: https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/5514 ^19:59
* ahasenack subscribes to that PR20:01
athoswell, I guess I came late to the party, ahasenack 20:03
ahasenackI just didn't find the part where I realized this would help with detecting config file errors20:03
athosyou even found the upstream follow-ups though!20:04
ahasenacksdeziel did first :P20:05
sdezielahasenack: for config check, nginx uses ExecStartPre=20:07
ahasenackdoes it behave the same wrt Type=exec|simple|notify?20:07
ahasenackrsync (my case) doesn't have a "-t" option to check the config20:08
ahasenackand in this particular case, the config syntax fine, it's the ip it's told to bind to that doesn't exist20:08
ahasenackyeah, ExecStartPre won't help in this case20:10
sdezielright and I don't think Type=notify would either since rsync wants to fail if the configured address is missing20:10
ahasenackoh, it does fail20:11
ahasenackthe issue is sytemd not detecting it at start time, I'm thinking scripts20:11
ahasenacksystemctl status knows it failed20:11
sdezielisn't it restarting it?20:11
ahasenackso type=notify would work20:11
ahasenackno, I don't think it is, but that could be another workaround for one particular scenario, boot ordering, when eventually the selected ip becomes available20:12
ahasenackin any case, it's a specific situation, I don't see a way to make it generic other than was said in the bug (btw, #1774788)20:12
sdezielahasenack: agreed on the "site-specific" nature of the problem. That said, to make things recover on their one, `Restart=on-failure` should be added to the systemd unit20:20
ahasenackcan you add this suggestion there?20:21
kanashiroahasenack, could you take a final look at the resource-agents MP? I'd like to upload it today20:21
sdezielahasenack: sure20:21
ahasenackkanashiro: I thought you uploaded it already20:21
* ahasenack checks his notifications20:21
kanashiroI uploaded pacemaker :)20:21
ahasenacksee, pings are valuable20:22
ahasenackkanashiro: which package holds the deprecated agents, -extra?20:24
kanashirothank you20:25
sdezielahasenack: I also updated the upstream bug with an alternative solution (`RestartForceExitStatus=10`)20:27
ahasenackdo you know if rsync uses 10 for something else?20:27
ahasenack10 seems to be a generic "Error in socket I/O"20:28
ahasenackso network in general?20:28
ahasenackgood tip in any case20:28
ahasenacksomeone can decide to apply that locally20:29
sdezielman systemd.service: "Setting this to on-failure is the recommended choice for long-running services"20:33
=== ajfriesen9 is now known as ajfriesen

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