Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 664680

Summary: Fails to change configuration file's type to Binary.
Product: Red Hat Satellite 5 Reporter: Dimitar Yordanov <dyordano>
Component: WebUIAssignee: Tomas Lestach <tlestach>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: low    
Version: 540   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-04 17:48:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dimitar Yordanov 2010-12-21 10:03:22 UTC
Description of problem:
Fails to change File type to Binary of a configuration file

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

How reproducible:
Always

Steps to Reproduce:
1.Configuration -> Some Conf Channel -> Create new configuration file or directory
1.Create a Configuration file - File Type : Text
3.Fill the rest of the form and press Create Configuration File
4.Change File Type to Binary
5.Press Update Configuration File
  
Actual results:
    * Macro end tag is required.
    * Macro start tag is required.

Expected results:
The File Type is changes.

Additional info:

Comment 1 Tomas Lestach 2010-12-22 10:07:14 UTC
This looks like a dupe of bug 649319. Erratum with the fix was issued on 2010-12-16, but you entered the bug report on 2010-12-21. Did you use the errata packages?

Comment 2 Dimitar Yordanov 2011-01-04 17:43:35 UTC
Yes, both problems described are quite similar. I have not used errata packages when I faced the problem. I guess you can mark it as Duplicated.

Comment 3 Tomas Lestach 2011-01-04 17:48:59 UTC

*** This bug has been marked as a duplicate of bug 649319 ***