Bug 1436863

Summary: Katello backup uses special characters in directory name
Product: Red Hat Satellite 6 Reporter: John Mitsch <jomitsch>
Component: Backup & RestoreAssignee: John Mitsch <jomitsch>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.8CC: bbuckingham, bkearney, dlobatog, jcallaha, mmccune
Target Milestone: UnspecifiedKeywords: PrioBumpField, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: katello-3.4.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:54:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description John Mitsch 2017-03-28 21:16:04 UTC
Description of problem:

katello-backup creates a directory named something like "katello-backup-2017-03-28T15:18:13-04:00", these special characters can cause problems for certain file types and programs (i.e yaml, scp) here are some guidelines on what is acceptable in a file or directory: 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.katello-backup /path/

Actual results:
directory has special characters

Expected results:
No special characters in directory

Additional info:

Comment 1 John Mitsch 2017-03-28 21:17:56 UTC
Created redmine issue http://projects.theforeman.org/issues/19054 from this bug

Comment 2 pm-sat@redhat.com 2017-03-29 14:02:24 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19054 has been resolved.

Comment 5 Daniel Lobato Garcia 2017-08-09 13:19:22 UTC

Tested on:


The directory created does only contain hyphen, letters and numbers: Creating backup folder /tmp/backup/katello-backup-20170809091815

Comment 12 pm-sat@redhat.com 2018-02-21 16:54:37 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> > 
> > For information on the advisory, and where to find the updated files, follow the link below.
> > 
> > If the solution does not work for you, open a new bug report.
> > 
> > https://access.redhat.com/errata/RHSA-2018:0336