Bug 1043221

Summary:	Non-existent group warnings from _at_groupinstall should not be printed when called via yum update
Product:	[Fedora] Fedora	Reporter:	Adam Williamson <awilliam>
Component:	yum	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	admiller, ffesti, firas.alkafri, hugh, jawr, jzeleny, liblit, packaging-team-maint, theo148
Target Milestone:	---	Keywords:	CommonBugs
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	https://fedoraproject.org/wiki/Common_F20_bugs#yum-group-errors
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-29 13:31:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Adam Williamson 2013-12-15 07:02:46 UTC

The function _at_groupinstall in yum/__init__.py logs warnings if it thinks an environment group or group it's called against does not exist. It's often wrong about this, at present: see https://bugzilla.redhat.com/show_bug.cgi?id=1014202 and https://bugzilla.redhat.com/show_bug.cgi?id=1043207 . But even assuming those bugs were fixed, I think these warnings should only be printed in the case where the user actually ran 'yum groupinstall @something'.

That's not the case at present: yum also calls _at_groupinstall when you do a 'yum update', I think to add any new packages for installed groups, and it shows the warnings in this case too. The user may well not know why yum is printing warnings about non-existent groups; it's probably more confusing than helpful.

An alternative would be to make the messages more detailed, I guess.

Comment 1 Adam Williamson 2013-12-15 07:09:01 UTC

of course I meant "should only be printed in the case where the user actually ran 'yum install @something'.

Comment 2 Fedora End Of Life 2015-05-29 09:59:44 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 13:31:43 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
bug.

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