fedora-infrastructure

#12698 [FMTS] TLS certificate for distrobuildsync-cs service is about to expire in 30 days
Closed: Fixed with Explanation by kevin. Opened by firmitas-automata.

Closed: Fixed with Explanation
Reopen Issue

This is to inform that the TLS certificate for distrobuildsync-cs service will expire in about 30 day(s) from now on 2025-09-01 21:24:08 UTC. The following are information relevant to the associated TLS certificate.

  • Service name - distrobuildsync-cs (Certificate stored as distrobuildsync-cs.crt)
  • Issuing authority - RabbitMQ PRODUCTION CA (#227343185236119015267094592673252953670)
  • Validity starting - 2023-05-30 21:24:08 UTC (796 day(s) passed since beginning)
  • Validity ending - 2025-09-01 21:24:08 UTC (29 day(s) left before expiring)

The point of contact for the service have been tagged into this ticket and notified about the same. It is strongly recommended to promptly renew the TLS certificate for the service before the existing one expires.

This issue ticket was automatically created by the Firmitas notification service. Please contact Fedora Infrastructure team if you believe that this notification is mistaken.

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee
- Issue tagged with: high-gain, low-trouble

This cert already expired, @kevin do you know what this is used for?

See ansible 377edfb74a7 it was something eln folks were thinking about using, but haven't ever decided to.

So, IMHO we can just drop this cert for now.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)
Metadata

automate firmitas high-gain low-trouble notifier

None
None
Normal
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.