Bug 915667 - alternatives could call systemctl enable with -f option
Summary: alternatives could call systemctl enable with -f option
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: chkconfig
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lukáš Nykrýn
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-26 09:55 UTC by Jaroslav Škarvada
Modified: 2014-02-05 23:16 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 23:16:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Proposed patch (763 bytes, patch)
2013-02-26 09:56 UTC, Jaroslav Škarvada
no flags Details | Diff

Description Jaroslav Škarvada 2013-02-26 09:55:50 UTC
Description of problem:
While resolving bug 850310 I encountered on some boxes the following (harmless) message during the "yum upgrade sendmail":
Failed to issue method call: File exists

This seems to be caused by alternatives --set mta /usr/sbin/sendmail.sendmail

Which calls systemctl -q enable.

There was:
/etc/systemd/system/multi-user.target.wants/sendmail.service -> /lib/systemd/system/sendmail.service

So the link to /lib was wrong (but working), it was probably the artefact of previous system upgrade.

The message gone if called systemctl -qf enable

Version-Release number of selected component (if applicable):
chkconfig-1.3.59-2.fc18.x86_64

How reproducible:
Always

Steps to Reproduce (on 64 bit):
1. ln -fs /lib/systemd/system/sendmail.service /etc/systemd/system/multi-user.target.wants/sendmail.service
2. alternatives --set mta /usr/sbin/sendmail.sendmail
  
Actual results:
Failed to issue method call: File exists

Expected results:
No message

Additional info:
The configuration of the affected boxes were wrong probably due to some previous bug. But I think using the -f option is harmless and may resolve other similar problems, from the man:
--force, -f
           When used with enable, overwrite any existing conflicting symlinks.

Comment 1 Jaroslav Škarvada 2013-02-26 09:56:28 UTC
Created attachment 702742 [details]
Proposed patch

Comment 2 Lukáš Nykrýn 2013-02-26 10:52:25 UTC
Thanks for the patch, I will include it in next release of chkconfig.

Comment 3 Fedora End Of Life 2013-12-21 15:38:58 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2014-02-05 23:16:00 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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