| Summary: | dhcpd service disabled by upgrade from F16 to F17 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jonathan Kamens <jik> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | johannbg, jpopelka, metherid, mschmidt, notting, plautrba, systemd-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-04-02 16:21:01 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jonathan Kamens
2012-04-01 14:42:55 UTC
(In reply to comment #0) > The dhcpd service, which was enabled prior to the upgrade, was disabled after > upgrading from F16 to F17 as per > https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum. > > I suspect this is because it was converted from initscripts to systemd. No, this is not the case, the conversion happened in F15. I have no idea what went wrong but changing component to systemd as there could be some bug I'm not aware of. What were the exact versions of the dhcp package before/after the upgrade? You can look into yum history to find out. Did you have the symlink /etc/systemd/system/multi-user.target.wants/dhcpd.service before the upgrade? Did it disappear during the upgrade? (In reply to comment #2) > What were the exact versions of the dhcp package before/after the upgrade? You > can look into yum history to find out. ID | Action(s) | Package ------------------------------------------------------------------------------- 750 | Updated | dhcp-12:4.2.3-18.P2.fc17.x86_64 EE 750 | Update | 12:4.2.3-24.P2.fc17.x86_64 EE 749 | Updated | dhcp-12:4.2.3-6.P2.fc16.x86_64 EE 749 | Update | 12:4.2.3-18.P2.fc17.x86_64 EE > Did you have the symlink > /etc/systemd/system/multi-user.target.wants/dhcpd.service before the upgrade? Yes. > Did it disappear during the upgrade? I don't know if that particular link disappeared, but I do know that when I ran "systemctl enable dhcpd.service" it said that it had created a link. I didn't notice which link it said it had created. In F16 the symlink pointed to /lib/systemd/system/dhcpd.service. In F17 systemctl the target is /usr/lib/systemd/system/dhcpd.service. The service would be started even with the symlink pointing to the old location though. It is possible that "systemctl enable dhcpd.service" said it created the symlink merely because it updated it with the new location. But that should be of no practical significance. Are you sure the service did not start after the upgrade to F17? What exactly made you try running "systemctl enable dhcpd.service"? It appears you're right. It looks like it started up after the upgrade but failed for a different reason, and when systemctl said it was creating the link, it's just because it was changing it to point at /usr/lib instead. Sorry for the false alarm. |