releng

#9534 ELN bulds are (sometimes?) not signed.
Closed: Fixed by mohanboddu. Opened by jkaluza.

Closed: Fixed
Reopen Issue

RPM builds tagged into "eln-rebuild" should be signed automatically by robosignatory. This robosignatory rule already exists and worked in the past.

Recently, we've started seeing broken ELN composes caused by unsigned RPM builds. First case was the atlas-3.10.3-11.eln101 build. I've asked @humaton to untag it from eln-rebuild and tag it into eln-rebuild again. This re-triggered signing.

I thought this was one-time issue, but today we see more unsigned builds like this:

2020-06-17 04:01:30 [ERROR   ] Compose run failed: RPM(s) not found for sigs: ['9570FF31', 'D300E724']. Check log for details. Unsigned packages:
dnf-4.2.21-1.eln100.0
dnf-automatic-4.2.21-1.eln100.0
dnf-data-4.2.21-1.eln100.0
dnf-plugins-core-4.0.15-1.eln100.0
python3-dnf-4.2.21-1.eln100.0
python3-dnf-plugin-post-transaction-actions-4.0.15-1.eln100.0
python3-dnf-plugin-versionlock-4.0.15-1.eln100.0
python3-dnf-plugins-core-4.0.15-1.eln100.0
yum-4.2.21-1.eln100.0
yum-utils-4.0.15-1.eln100.0

I have not tested if re-tagging will fix this issue, since I don't have permissions to tag/untag builds.

Can you please check if there is anything wrong in the robosignatory or Koji configuration which could be causing this, or we just have bad luck with infrastructure move?

We need to update the koji gc policy

How long do you think we should keep the builds around?

From the irc chat, we are going with the last tagged build.

That is keeping the latest tagged build
Edited by mohanboddu 
[09:27:12] 04<sgallagh04>04 mboddu: What would you suggest?
[09:27:41] 20<192428sgallagh20> What is the Rawhide policy?
[09:27:43] 04<jkaluza04>04 mboddu: can we keep last tagged for each package? koji-gc allows that, right?
[09:28:09] 20<192428jkaluza20> (talking about "eln" tag)
[09:33:50] 19<28+19mboddu> jkaluza: Yes, either by number of days old or last tagged or both
[09:34:47] 19<28+19mboddu> sgallagh: Rawhide uses the default, that is keeping the last 2 tagged builds
[09:34:54] 19<28+19mboddu> Uh no, last 3 tagged builds
[09:35:10] 20<192428sgallagh20> I think ELN probably only needs the last one.

https://pagure.io/fedora-infra/ansible/pull-request/138

https://pagure.io/fedora-infra/ansible/pull-request/138

Has been deployed. Closing the ticket, please reopen if it happens again.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.