Bug 2416688

Summary: cyrus-imapd service cannot be first-time started due to sscg error
Product: [Fedora] Fedora Reporter: Eduard Vopicka <eduard.vopicka>
Component: cyrus-imapdAssignee: Martin Osvald 🛹 <mosvald>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 43CC: fhrdina, jorton, j, mosvald, pavel, zdohnal
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cyrus-imapd-3.8.3-16.fc44 cyrus-imapd-3.8.3-16.fc43 cyrus-imapd-3.8.3-12.fc42 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-12-03 00:53:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eduard Vopicka 2025-11-23 23:07:32 UTC
A start job for unit cyrus-imapd-init.service has begun execution.
â–‘â–‘ 
â–‘â–‘ The job identifier is 3657.
Nov 23 23:26:16 2001-1ae9-1fc-2b00-cfc4-89d7-4345-cf8e.ip6.tmcz.cz sscg[5771]: Invalid option --package: unknown option


Reproducible: Always

Steps to Reproduce:
1. Make sure these certificates DO NOT exist:
ConditionPathExists=!/etc/pki/cyrus-imapd/cyrus-imapd.pem
ConditionPathExists=!/etc/pki/cyrus-imapd/cyrus-imapd-key.pem
ConditionPathExists=!/etc/pki/cyrus-imapd/cyrus-imapd-ca.pem

2. systemctl start cyrus-imapd

Actual Results:
cyrus-imapd.service fails because of cyrus-imapd-init.service fails

Expected Results:
Service should start normally for the first time

Additional Information:
--package has been removed in sscg-4.0
https://sgallagh.wordpress.com/2025/10/23/sscg-4-0-0-release-announcement/

Comment 2 Fedora Update System 2025-11-24 09:27:01 UTC
FEDORA-2025-1a3d3a9090 (cyrus-imapd-3.8.3-16.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-1a3d3a9090

Comment 3 Fedora Update System 2025-11-24 09:31:21 UTC
FEDORA-2025-cbdd9eb047 (cyrus-imapd-3.8.3-16.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-cbdd9eb047

Comment 4 Fedora Update System 2025-11-24 09:31:48 UTC
FEDORA-2025-8b492e4d7f (cyrus-imapd-3.8.3-12.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-8b492e4d7f

Comment 5 Fedora Update System 2025-11-24 09:40:14 UTC
FEDORA-2025-1a3d3a9090 (cyrus-imapd-3.8.3-16.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2025-11-25 01:59:33 UTC
FEDORA-2025-cbdd9eb047 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-cbdd9eb047`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-cbdd9eb047

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2025-11-25 02:22:54 UTC
FEDORA-2025-8b492e4d7f has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-8b492e4d7f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-8b492e4d7f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2025-12-03 00:53:13 UTC
FEDORA-2025-cbdd9eb047 (cyrus-imapd-3.8.3-16.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2025-12-03 01:06:24 UTC
FEDORA-2025-8b492e4d7f (cyrus-imapd-3.8.3-12.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.