DevHeads.net

signing status

Just wanted to update everyone on our current status.

As you know from the other thread:

* The mass rebuild happened and finished.
* The mass rebuild side tag was merged into the f30-pending tag
(to make sure everything was signed).
* In the middle of the night our autosign box stopped processing.
* The next morning this was noticed and a request for a replacement
motherboard was sent.
* Since that was going to take a day, we setup another machine to do
autosigning.
* That machine started processing the backlog, but also stopped
processing a few times (waiting on koji).
* Finally we set back up the normal listening process and I retagged all
the f30-pending builds to it would "see" they needed processing.

Currently it's processing along pretty fast, but it does make sure koji
has the signed rpms written out, which can take a few seconds on larger
packages.

I'm hopeful that it will catch back up today and we can go back to normal.

There will likely be a short outage next week to move back to the now
replaced hardware, but that should be only a few minutes.

kevin

Comments

Re: signing status

By =?UTF-8?Q?Bj=c3... at 02/09/2019 - 07:48

Am Freitag, den 08.02.2019, 08:41 -0800 schrieb Kevin Fenzi:

Thank you for the extra work, Kevin and all other being involved with
it!

Just asking as this came to my mind from a different thread:

Has that issue been adressed already, too?

Björn

Re: signing status

By =?UTF-8?B?TWlyb... at 02/09/2019 - 05:00

On 08. 02. 19 17:41, Kevin Fenzi wrote:
Is this somehow relevant?

<a href="https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190209.n.1/logs/global/pungi.global.log" title="https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190209.n.1/logs/global/pungi.global.log">https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-201902...</a>

2019-02-09 08:44:00 [ERROR ] Compose run failed: RPM(s) not found for sigs:
['CFC659B9']. Check log for details. Unsigned packages:
dar-2.6.0-2.fc30
dar-debuginfo-2.6.0-2.fc30
dar-debugsource-2.6.0-2.fc30
electrum-3.3.2-3.fc30
libdar-2.6.0-2.fc30
libdar-debuginfo-2.6.0-2.fc30
libdar-devel-2.6.0-2.fc30
mysqltuner-1.7.19-2.git.59e5f40.fc30
openscap-1.3.0_alpha2-2.fc30
openscap-containers-1.3.0_alpha2-2.fc30
openscap-debuginfo-1.3.0_alpha2-2.fc30
openscap-debugsource-1.3.0_alpha2-2.fc30
openscap-devel-1.3.0_alpha2-2.fc30
openscap-engine-sce-1.3.0_alpha2-2.fc30
openscap-engine-sce-debuginfo-1.3.0_alpha2-2.fc30
openscap-engine-sce-devel-1.3.0_alpha2-2.fc30
openscap-perl-1.3.0_alpha2-2.fc30
openscap-perl-debuginfo-1.3.0_alpha2-2.fc30
openscap-python3-1.3.0_alpha2-2.fc30
openscap-scanner-1.3.0_alpha2-2.fc30
openscap-scanner-debuginfo-1.3.0_alpha2-2.fc30
openscap-utils-1.3.0_alpha2-2.fc30
openscap-utils-debuginfo-1.3.0_alpha2-2.fc30
python-oslo-messaging-8.0.0-1.fc29
python-oslo-messaging-doc-8.0.0-1.fc29
python2-oslo-messaging-8.0.0-1.fc29
python2-oslo-messaging-tests-8.0.0-1.fc29
python3-oslo-messaging-8.0.0-1.fc29
python3-oslo-messaging-tests-8.0.0-1.fc29

Re: signing status

By Alexander Bokovoy at 02/08/2019 - 14:11

On pe, 08 helmi 2019, Kevin Fenzi wrote:
And now I have a build without any tags.

Re: signing status

By Kevin Fenzi at 02/08/2019 - 16:32

...snip...

No, that all looks normal, the build was tagged into f30-pending as
expected. So once the autosigner gets to it, it will be signed and moved
to f30. So yeah, that is delayed due to the signing queue, but otherwise
it looks ok to me.

<a href="https://koji.fedoraproject.org/koji/buildinfo?buildID=1206959" title="https://koji.fedoraproject.org/koji/buildinfo?buildID=1206959">https://koji.fedoraproject.org/koji/buildinfo?buildID=1206959</a>

kevin