Description of problem:
Create a rule to unset disabled flag, for example errata-3.1 flag, and when I roll back the changes made by the rule. I found the flag can not be set to these bugs (it is expected as this flag already been disabled), and no any warning show for the rollback operation. In the comment of the bug, we can see inline history as following:
Rule Engine 2014-08-12 23:43:40 EDT
Rules Engine Rule: disableflag
Rule Engine 2014-08-12 23:45:21 EDT
Rules Engine Rule: disableflag(strickthrough)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.create a rule to unset one disabled flag
2. roll back the changes made by above rule
the rollback action did well from the output message of the roll back
I hope there will be some message to let user know the roll back does not take effect. Or we at least give clarification to the rules engine documentation.
In the real world™, we would hope that (a) the roll back feature is never used and (b) if it is, the old flag states would still be available.
Having said that, at the time we add the bugs to the rollback queue, there is no easy way to tell if there are flags that cannot be changed. Therefore, I recommend that the best thing we can do is disable a warning on the create a rollback page about changing flags.
(In reply to Simon Green from comment #1)
> Therefore, I recommend that the best thing we can do is disable a warning
> on the create a rollback page about changing flags.
I presume you mean "display" rather than "disable", in which case I agree with you.
Change this bug to verified as one warning note added in the roll back page. Thanks.