Bug 214816
Summary: | Many to many scheduled diff actions | ||
---|---|---|---|
Product: | [Retired] Red Hat Network | Reporter: | Ken Ganong <kganong> |
Component: | RHN/Web Site | Assignee: | Máirín Duffy <duffy> |
Status: | CLOSED NOTABUG | QA Contact: | Beth Nackashi <bnackash> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rhn500 | CC: | rhn-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-02-15 20:34:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 192224 |
Description
Ken Ganong
2006-11-09 16:52:40 UTC
I think #1 is fine. It gives users a one-click shortcut to verifying all the files on the systems subscribed to the channel. While a UI to schedule diffs from a channel is an interesting idea, I think the primary usecase for diffing would be what we currently handle - diff all files in the channel against all systems subscribed to the channel. If a user wanted a finer-grained section of files against all of those systems, they could just ignore the files they didn't care about in the diff results. If they only wanted diff results for multiple systems for one or a small number of files, they can easily schedule those from the files themselves. I'm going to close this NOTABUG. If it turns out to be something customers end up wanting to use, I think we should reopen this bug a reevaluate Ken's suggestion #3. |