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

Bug 1261239

Summary: Unable to create a channel in Spacewalk that starts with 'Red Hat' or 'RHN'
Product: [Community] Spacewalk Reporter: PixelDrift.NET Support <devnull>
Component: ServerAssignee: Tomas Lestach <tlestach>
Status: CLOSED WONTFIX QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.3   
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: 2015-09-09 06:33:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1484117    

Description PixelDrift.NET Support 2015-09-09 02:22:35 UTC 
Description of problem:
When attempting to create a new base channel with a name starting with 'Red Hat', Spacewalk advises that channel names must not start with 'red hat' and does not create the channel.

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

How reproducible:
Always

Steps to Reproduce:
1. From the UI select Channels -> Manage Software Channels -> Create New Channel
2. Create channel name such as 'Red Hat Source RPMs'

Actual results:
Spacewalk returns the error "Channels names must not start with 'red hat'"


Expected results:
Channel created without error.


Additional info:
The offending regex is here:
https://github.com/spacewalkproject/spacewalk/blob/master/java/code/src/com/redhat/rhn/manager/channel/CreateChannelCommand.java#L53

Which also restricts channels from starting with 'RHN'.

I discovered this issue when attempting to add Red Hat source RPMs to a Spacewalk server in a package development/build environment. Is this some form of license enforcement? I haven't seen anything specifically forbidding users from hosting Red Hat content locally (please clarify?).

I understand the RHN capabilities have been removed from Spacewalk, but I am interested to know why this regex enforcement still exists. Is it a hang over from Satellite, or specifically added to Spacewalk?
Comment 1 Tomas Lestach 2015-09-09 06:33:35 UTC 
This constraint prevents the user to get into issues, for cases when he would create a custom channel like 'Red Hat Enterprise Linux Server (v. 7 for 64-bit x86_64)' and then would like to sync Red Hat channel of the same name (through the satellite-sync).
Even if this is probably not used too often, it's a valid scenario.
This behavior is expected and not planned to be removed. I'm closing the BZ as WONTFIX.
Comment 2 PixelDrift.NET Support 2015-09-09 07:14:46 UTC 
Tomas,

The scenario you propose is only an issue in Satellite as satellite-sync for Red Hat channels from RHN is removed from the OS Spacewalk release. Is there a way to have this channel name restriction removed from the OS Spacewalk build?
Comment 3 Tomas Lestach 2015-09-09 08:39:55 UTC 
There was no such thing removed from Spacewalk. If you activate Spacewalk using a Satellite certificate, you're able to satellite-sync Red Hat content like in Red Hat Satellite 5.
There're users, who make use of it.
As I wrote, there are no plans to change this behavior.
Comment 4 Eric Herget 2017-09-28 18:06:27 UTC 
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.