Project

General

Profile

Bug #3673

Zero-length frontend_status.xml throws exception

Added by Burt Holzman over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
Frontend
Target version:
Start date:
04/05/2013
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

In glideinFrontendMonitorAggregator.aggregateStatus:

    for group in monitorAggregatorConfig.groups:
        # load group status file
        status_fname=os.path.join(os.path.join(monitorAggregatorConfig.monitor_dir,'group_'+group),
                                  monitorAggregatorConfig.status_relname)
        try:
            group_data=xmlParse.xmlfile2dict(status_fname)
        except IOError:
            continue # file not found, ignore

If the frontend_status.xml in the group directory is zero-length or corrupt, the underlying XML libraries throw an
uncaught exception (ExpatError). We should catch this in addition to IOError, log the error, remove the offending file.

Actually, we should have xmlParse catch and rethrow its own exception so we can change out the underlying XML parser library without affecting the higher-level calls.

History

#1 Updated by Burt Holzman over 6 years ago

  • Status changed from Assigned to Feedback
  • Assignee changed from Burt Holzman to Parag Mhashilkar
  • Occurs In deleted (v3_1)

Fixed in commit:0e37715.

#2 Updated by Parag Mhashilkar over 6 years ago

  • Status changed from Feedback to Resolved
  • Assignee changed from Parag Mhashilkar to Burt Holzman
  • Target version changed from v2_7_x to v2_7_1

Looks ok. Was straightforward so merged it back to the respective release branches

#3 Updated by Parag Mhashilkar over 6 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF