Closed Bug 1282789 Opened 9 years ago Closed 9 years ago

Investigate why some files on s3 have a name ending with colon

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mdoglio, Assigned: whd)

Details

A job failure reported in bug 1282441 was caused by a filename ending with semicolon. We should investigate how that file was created with such a name.
Assignee: nobody → whd
Points: --- → 1
Priority: -- → P1
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.