Bug 752541 - service startup not migrated to systemd on upgrade
Summary: service startup not migrated to systemd on upgrade
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: i686
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-09 19:47 UTC by Alex Williamson
Modified: 2011-11-09 19:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-09 19:57:28 UTC
Type: ---


Attachments (Terms of Use)

Description Alex Williamson 2011-11-09 19:47:03 UTC
Description of problem:
Upgrading a system from F15 to F16 that previously started nfsd, dnsmasq, and cups by default results in none of those services running after upgrade.

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

How reproducible:
1/1

Steps to Reproduce:
1. Upgrade system
2.
3.
  
Actual results:
Get super frustrated, throw things, switch to other distros because basic services you relied on didn't get migrated during upgrade and now you have to learn more about systemd than you care to to start them again.

Expected results:
Peace, harmony, and printing.

Additional info:
systemctl enable cups.service
systemctl enable dnsmasq.service
systemctl enable nfs-server.service

Comment 1 Chris Lumens 2011-11-09 19:57:28 UTC
This needs to be filed with the individual programs themselves, since those programs need to handle their own portion of the upgrade process.  If we just did this in anaconda, then you wouldn't be helped at all if you did a yum upgrade of those packages - you'd have to get it fixed in the package then too.


Note You need to log in before you can comment on or make changes to this bug.