Bug 850837 - RFE Rescue DAGs should not be a complete DAG file
RFE Rescue DAGs should not be a complete DAG file
Status: CLOSED WONTFIX
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor (Show other bugs)
Development
All Linux
low Severity medium
: ---
: ---
Assigned To: grid-maint-list
MRG Quality Engineering
: FutureFeature, TestOnly
Depends On:
Blocks: 845292
  Show dependency treegraph
 
Reported: 2012-08-22 10:04 EDT by Timothy St. Clair
Modified: 2016-05-26 15:13 EDT (History)
3 users (show)

See Also:
Fixed In Version: condor-7.8.2-0.2
Doc Type: Rebase: Enhancements Only
Doc Text:
Important: if this rebase also contains *bug fixes* (or contains only bug fixes), select the correct option from the Doc Type drop-down list. Rebase package(s) to version: condor-7.8 series Highlights and notable enhancements: condor_dagman writes a partial DAG file for a rescue DAG, as opposed to a full DAG file. The Rescue DAG file is parsed in combination with the original DAG file, meaning that any changes to the original DAG input file take effect when running a Rescue DAG.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-05-26 15:13:11 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Condor 2165 None None None 2012-08-22 10:04:22 EDT

  None (edit)
Description Timothy St. Clair 2012-08-22 10:04:22 EDT
condor_dagman should writing a partial DAG file for a Rescue DAG, as opposed  to a full DAG file. The Rescue DAG file is parsed in combination with  the original DAG file, meaning that any changes to the original DAG  input file take effect when running a Rescue DAG.
Comment 4 Anne-Louise Tangring 2016-05-26 15:13:11 EDT
MRG-G is in maintenance only and only customer escalations will be addressed from this point forward. This issue can be re-opened if a customer escalation associated with this issue occurs.

Note You need to log in before you can comment on or make changes to this bug.