Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 163868

Summary: yum cron auto update new feature request
Product: [Fedora] Fedora Reporter: Frank Liu <gfrankliu>
Component: yumAssignee: Jeremy Katz <katzj>
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: katzj, lmacken
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-07-22 16:11:56 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 Frank Liu 2005-07-21 18:22:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Description of problem:
This is a feature request, as discussed in the fedora mailing list:

I have two major issues (system won't boot) after the nightly yum
auto update, caused by the "new" selinux-policy-targeted and kernel, within the past month. I am not blaming the team for bad QA, but I just want to know
that is it still a good idea to enable the nightly auto update? or is
it better to do it manually?

Another solution would be to have a hybrid of the two. The reason
I wanted auto update is so I won't miss a critical security fix.
This definitely needs to be installed in a timely manner. But
for other non security related updates, we can wait to do it manually,
with a scheduled window. In order for this "hybrid" to work,
all updates need to be tagged with "security" or "non-security" related.
or maybe tagged with "emergency" or "normal". Then the nightly
yum update can have a flag to do "all" updates, or just "emergency/security"

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

How reproducible:

Steps to Reproduce:
1. see description.

Additional info:

Comment 1 Seth Vidal 2005-07-22 16:11:56 UTC
to just apply 'security' updates we'll need more metadata than we currently
have. Specifically we need someone to classify which of the packages resolve
security issues and which just resolve bugs.

it is something being worked on but for the moment it's not possible.