|
Bugzilla – Full Text Bug Listing |
| Summary: | dkimproxy broken after upgrade to Leap 15.4/conversion to systemd services | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Robert Munteanu <rombert> |
| Component: | Other | Assignee: | Robert Munteanu <rombert> |
| Status: | NEW --- | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | rombert, varkoly |
| Version: | Leap 15.4 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | openSUSE Leap 15.4 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
https://build.opensuse.org/request/show/1123690 contains a fix that works on my Leap 15.4 VM. Note that the SR that I submitted seems to be incomplete, the /run/dkmiproxy directory is no re-created after a restart. https://build.opensuse.org/request/show/1124303 contains the needed follow-up fixes. This is an autogenerated message for OBS integration: This bug (1216919) was mentioned in https://build.opensuse.org/request/show/1124837 Backports:SLE-15-SP4+Backports:SLE-15-SP5 / dkimproxy Hi Robert, since you already submitted the request and fixed this issue, so I assign it to you, thanks. openSUSE-RU-2023:0406-1: An update that has one recommended fix can now be installed. Category: recommended (low) Bug References: 1216919 CVE References: JIRA References: Sources used: openSUSE Backports SLE-15-SP5 (src): dkimproxy-1.4.1-bp155.4.3.1 openSUSE Backports SLE-15-SP4 (src): dkimproxy-1.4.1-bp154.3.3.1 |
I have upgrade to Leap 15.4 to find my dkimproxy setup broken. I noticed the following things: 1. there was one dkimproxy service, now there are two dkimproxy-in and dkimproxy-out. The new services are disabled even though the old one was enabled 2. The dkimproxy_in.service file references the /run/sysconfig/dkimproxy environment file 2a. The dkimproxy_env.sh script is supposed to create that file, but /run/sysconfig is not created at all to that script fails 2b. The dkimproxy_env.sh sets "HFQHN=$( hostname -f )" dkimproxy-in.service uses --hostname=${FQHN} While problem 1 is a one-time fix, the problems from 2 are more persistent and are ideally solved in the package. Note: systemd integration was contributed in bug #1116007