Bug 1506000

Summary: imapd service not coming up because of wrong httpmodule name in stock configuration
Product: [Fedora] Fedora Reporter: Philip Prindeville <philipp>
Component: cyrus-imapdAssignee: Pavel Zhukov <pzhukov>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 26CC: code, dan, j, philipp, pokorra.mailinglists, pzhukov, vanmeeuwen+fedora, zdohnal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: cyrus-imapd-3.0.4-2.fc26 cyrus-imapd-3.0.4-2.fc27 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-07 22:16:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Trivial fix for typo in httpmodules list in /etc/imapd.conf none

Description Philip Prindeville 2017-10-24 18:57:24 UTC
Created attachment 1342930 [details]
Trivial fix for typo in httpmodules list in /etc/imapd.conf

Description of problem:

When starting the service, it fails to come up on F26 because of this line:

httpmodules: caldav carddav domainkey freebusy isschedule jmap rss tzdist webdav

which ends up causing the following errors:

Oct 24 11:48:52 mail master[24698]: invalid value 'isschedule' for httpmodules in line 55
Oct 24 11:48:52 mail master[24698]: exiting

and the service fails.


Version-Release number of selected component (if applicable):

cyrus-imapd-3.0.4-1.fc26.x86_64

How reproducible:

Install and start stock RPM.

Steps to Reproduce:
1.
2.
3.

Actual results:

Oct 24 11:48:52 mail master[24698]: invalid value 'isschedule' for httpmodules in line 55

Expected results:

Oct 24 11:50:20 mail cyrus/ctl_cyrusdb[24715]: skiplist: clean shutdown file mis
sing, updating recovery stamp
Oct 24 11:50:20 mail cyrus/ctl_cyrusdb[24715]: recovering cyrus databases
Oct 24 11:50:20 mail cyrus/ctl_cyrusdb[24715]: done recovering cyrus databases
Oct 24 11:50:20 mail cyrus/ctl_cyrusdb[24716]: checkpointing cyrus databases
Oct 24 11:50:20 mail cyrus/ctl_cyrusdb[24716]: done checkpointing cyrus database
s
Oct 24 11:51:04 mail cyrus/imaps[24717]: inittls: Loading hard-coded DH paramete
rs
Oct 24 11:51:04 mail cyrus/imaps[24717]: TLS server engine: No client CA certs s
pecified. Client side certs may not work

Additional info:

Comment 1 Fedora Update System 2017-10-24 21:18:59 UTC
cyrus-imapd-3.0.4-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-9e6fba1670

Comment 2 Fedora Update System 2017-10-24 21:19:09 UTC
cyrus-imapd-3.0.4-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-fb1180651b

Comment 3 Fedora Update System 2017-10-25 15:25:22 UTC
cyrus-imapd-3.0.4-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-9e6fba1670

Comment 4 Fedora Update System 2017-10-26 01:33:35 UTC
cyrus-imapd-3.0.4-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-fb1180651b

Comment 5 Fedora Update System 2017-11-07 22:16:11 UTC
cyrus-imapd-3.0.4-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2017-11-11 03:04:23 UTC
cyrus-imapd-3.0.4-2.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.