Am Freitag, 10. April 2020, 09:25:27 CEST schrieb Andreas Schwab:
On Apr 10 2020, Hans-Peter Jansen wrote:
so the issue boils down to: where does _projectcert.crt come from and how is it injected into the build?
It is the project SSL cert (osc signkey --sslcert), injected by bs_worker:getsslcert.
Well, almost succeeded. But kernel build finished since 75 minutes: [ 8518s] obsserver finished "build kernel-default.spec" at Fri Apr 10 13:34:27 UTC 2020. [ 8518s] [ 8518s] ### VM INTERACTION START ### [ 8521s] [ 8505.440534] sysrq: Power Off [ 8521s] [ 8505.452408] reboot: Power down [ 8524s] ### VM INTERACTION END ### [ 8524s] build: extracting built packages... [ 8541s] RPMS/x86_64/kernel-default-livepatch-devel-5.6.2-2.3.x86_64.rpm [ 8541s] RPMS/x86_64/kernel-default-debugsource-5.6.2-2.3.x86_64.rpm [ 8541s] RPMS/x86_64/kernel-default-debuginfo-5.6.2-2.3.x86_64.rpm [ 8541s] RPMS/x86_64/kernel-default-5.6.2-2.3.x86_64.rpm [ 8541s] RPMS/x86_64/kernel-default-devel-debuginfo-5.6.2-2.3.x86_64.rpm [ 8541s] RPMS/x86_64/kernel-default-devel-5.6.2-2.3.x86_64.rpm [ 8541s] SRPMS/kernel-default-5.6.2-2.3.nosrc.rpm [ 8541s] OTHER/rpmlint.log [ 8541s] OTHER/kernel-source.rpmlintrc [ 8541s] OTHER/_statistics [ 8541s] OTHER/make-stderr.log [ 8541s] OTHER/kernel-default.cpio.rsasign [ 8541s] OTHER/pesign-repackage.spec Kernel is in signing state since being finished: $ oscl r Project:Kernel kernel-default openSUSE_Tumbleweed x86_64 signing openSUSE_Leap_15.2 x86_64 building openSUSE_Leap_15.1 x86_64 building signer finished: $ tail -n2 /srv/obs/log/signer.log signing x86_64/Project:Kernel::openSUSE_Tumbleweed::kernel-default- ef6818441b37cb165bebd9b53b234a6a waiting for an event... since > 80 minutes: $ stat -c%y /srv/obs/log/signer.log 2020-04-10 13:35:01.245182170 +0000 $ date Fri Apr 10 14:58:39 UTC 2020 Relevant BSConfig.pm section: #No package signing server our $sign = "/usr/bin/sign"; #Extend sign call with project name as argument "--project $NAME" #our $sign_project = 1; #Global sign key our $keyfile = "/srv/obs/obs-default-gpg.asc"; our $gpg_standard_key = "/srv/obs/obs-default-gpg.asc"; our $forceprojectkeys = 1; but hey, maybe I'm too simpleminded by unifying $keyfile and $gpg_standard_key. Is $forceprojectkey still useful? /etc/sign.conf seems to be correct. obssigner and obssignd are up and running: $ sc status obssignd obssigner ● obssignd.service - LSB: start the gpg sign daemon Loaded: loaded (/etc/init.d/obssignd; generated; vendor preset: disabled) Active: active (running) since Thu 2020-04-09 13:55:56 UTC; 1 day 1h ago Docs: man:systemd-sysv-generator(8) Process: 1617 ExecStart=/etc/init.d/obssignd start (code=exited, status=0/ SUCCESS) Tasks: 4 CGroup: /system.slice/obssignd.service ├─1702 /usr/bin/perl /usr/sbin/signd -f ├─1745 gpg-agent --homedir /srv/obs/gnupg --use-standard-socket -- daemon └─8314 gpg-agent --homedir /srv/obs/gnupg --use-standard-socket -- daemon Apr 09 13:55:55 obsserver systemd[1]: Starting LSB: start the gpg sign daemon... Apr 09 13:55:56 obsserver obssignd[1617]: Starting gpg sign daemon (signd): ..done Apr 09 13:55:56 obsserver systemd[1]: Started LSB: start the gpg sign daemon. ● obssigner.service - OBS signer service Loaded: loaded (/usr/lib/systemd/system/obssigner.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/obssigner.service.d └─10-srv-obs.conf Active: active (running) since Thu 2020-04-09 13:55:56 UTC; 1 day 1h ago Main PID: 1668 (bs_signer) Tasks: 2 CGroup: /system.slice/obssigner.service └─1668 /usr/bin/perl -w /usr/lib/obs/server/bs_signer --logfile signer.log Apr 09 13:55:56 obsserver systemd[1]: Started OBS signer service. Cheers, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org