Bug 1126167 - clear command in yum.conf/main/excludes fails
Summary: clear command in yum.conf/main/excludes fails
Alias: None
Product: Fedora
Classification: Fedora
Component: augeas
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: lutter@watzmann.net
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-08-03 00:45 UTC by Chad Feller
Modified: 2015-06-29 21:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-29 21:55:06 UTC

Attachments (Terms of Use)
output from print /augeas//error (38.02 KB, text/plain)
2014-08-03 00:46 UTC, Chad Feller
no flags Details

Description Chad Feller 2014-08-03 00:45:49 UTC
Description of problem:
Attempting to clear the 'exclude' option in yum.conf using augeas fails in Fedora 20.  It does not fail in RHEL6.  I initially noticed this as I'm using augeas in conjunction with puppet.

After testing on the Fedora 20 box individually using augtool, I noticed that I can set the 'exclude' option to anything else, but if I attempt to 'clear' it, I get the attached error.  Doing the same thing on my EL6 boxes does not yield an error.

My first guess is that this may just be a bug with the yum lens as the version of augeas in Fedora 20 is newer than what is on my EL6 boxes. (The version of augeas in EL6 is currently at 1.0.0-5).  So I manually copied yum.aug from my EL6 box, replacing the version on my F20 box with it.  

Upon doing so, I am now able to clear the exclude option in yum.conf using augeas.

I realize that there is probably a narrow set of use cases where someone would want to 'clear' this particular option, and in this case as a workaround I could just use 'rm' instead of 'clear', but since clear was working in a previous version of augeas I'm assuming this is a bug.

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

Comment 1 Chad Feller 2014-08-03 00:46:45 UTC
Created attachment 923537 [details]
output from print /augeas//error

Comment 2 Fedora End Of Life 2015-05-29 12:33:05 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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 3 Fedora End Of Life 2015-06-29 21:55:06 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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

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.