Ticket #3829: PREEMPT==Undefined should be treated as False, not a fatal error
I've probably been bitten by this a dozen times over the years (referenced an attr in my PREEMPT expression that turns out not to exist on one machine for some reason, sending it into the valley of death).
I can't see any reason why PREEMPT==Undefined should be fatal unless you're trying to force admins to discover missing attrs or something, but that seems obnoxious when you could just write a helpful warning to the StartLog instead. With the current behavior, one typo can take a pool down.
Remarks:
2013-Dec-06 13:57:26 by tim:
The issue was resolved by #3869
Properties:
| Type: |
incident |
|
Last Change: |
2013-Dec-06 13:58 |
| Status: |
defer |
|
Created: |
2013-Jul-31 16:25 |
| Fixed Version: |
v080003 |
|
Broken Version: |
v080000 |
| Priority: |
5 |
|
Subsystem: |
DaemonsExecNode |
| Assigned To: |
|
|
Derived From: |
|
| Creator: |
pfc |
|
Rust: |
|
| Customer Group: |
ligo |
|
Visibility: |
public |
| Notify: |
pfcouvar@syr.edu,pcouvare@caltech.edu |
|
Due Date: |
|