The list of scheduled actions (in pending, completed and archived) doesn't include the system name that the action will be against. Can it?
off-topic, but why is /dev/null part of the cc: list? Sounds like a bugzilla config thingy needs fixing :)
I didn't understand at the time that actions can encompass multiple systems, so this RFE no longer makes sense, unless modified such that for actions where system_list.length == 1, include system name in action table. Your call.
Bret, this is your code, so it's up to you whether to put system name in on the special case or not.
the more I think about this RFE, the less I like the resultant code that would exist. Since the typical cases are 1) new errata, install to lotsa systems or 2) single-system free setup and neither of those benefit from this (#1 has multiple systems, #2 only has one system so the name would be redundant), I'm really talking myself out of this one. Sorry guys.
Hi, Could this RFE be resurrected? I fail to see the point of the Scheduled action page now that there is 1 entry per machine per errata. It is impossible to find meaningful information otherwise. daryl
reopening bug.
Maybe the bug here is that task-o-matic creates 1 entry for each errata per each machine. Back in the old days, each errata would have 1 entry and thus you had a fighting chance. :) Currently, my Pending actions has 4,500 entries, making it impossible to use.
so now there is one action for a bunch of servers--this was done in sprint 8