Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1920231 - Global Registration: Registering client to capsule shows "ERROR: Validation failed: Name can't be blank, Name hostname can contain only lowercase letters, numbers, dashes and dots according to RFC921, RFC952 and RFC1123" .
Summary: Global Registration: Registering client to capsule shows "ERROR: Validation f...
Keywords:
Status: CLOSED DUPLICATE of bug 1900694
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Registration
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.9.0
Assignee: satellite6-bugs
QA Contact: Stephen Wadeley
URL:
Whiteboard:
: 1924229 1924863 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-25 20:59 UTC by soham
Modified: 2021-02-12 09:03 UTC (History)
5 users (show)

Fixed In Version: foreman-2.3.1.5-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-12 09:03:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description soham 2021-01-25 20:59:15 UTC 
Description of problem:
Registering client to capsule with global registration template shows "ERROR: Validation failed: Name can't be blank, Name hostname can contain only lowercase letters, numbers, dashes and dots according to RFC921, RFC952 and RFC1123" .

Though the client registers fine but it throws this error message.

This message is not thrown when registered to satellite with the global registration template or with the capsule using subscription-manager register command.

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


How reproducible:

Always


Steps to Reproduce:
1. Pick a client like vm249-175.gsslab.pnq2.redhat.com or vm253-200.gsslab.pnq2.redhat.com

2. Register it with the capsule server using global registration template.

3.

Actual results:
The system has been registered with ID: 6dacbe98-b794-4722-891e-cec36a69dc88
The registered system name is: vm253-200.gsslab.pnq2.redhat.com
Installed Product Current Status:
Product Name: Red Hat Software Collections (for RHEL Server)
Status:       Subscribed

Product Name: Red Hat Enterprise Linux Server
Status:       Subscribed

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   241  100   177  100    64    696    251 --:--:-- --:--:-- --:--:--   696
ERROR: Validation failed: Name can't be blank, Name hostname can contain only lowercase letters, numbers, dashes and dots according to RFC921, RFC952 and RFC1123



Expected results: The below message should not show up.

ERROR: Validation failed: Name can't be blank, Name hostname can contain only lowercase letters, numbers, dashes and dots according to RFC921, RFC952 and RFC1123


Additional info:
Comment 1 Leos Stejskal 2021-02-05 13:03:06 UTC 
*** Bug 1924229 has been marked as a duplicate of this bug. ***
Comment 2 Leos Stejskal 2021-02-05 13:25:52 UTC 
*** Bug 1924863 has been marked as a duplicate of this bug. ***
Comment 3 Leos Stejskal 2021-02-05 15:46:47 UTC 
Hi,
I'm trying to reproduce the issue, but on latest snap (12) registration through proxy works fine.

My pkg versions: foreman-2.3.1.5-1.el7sat.noarch & foreman-proxy-2.3.1-1.el7sat.noarch

My guess is that problem could be in global registration template, there were some changes to this issue,
can you check that you using default (latest) version of the template?

If you can still reproduce the issue, please attach:
- application log 
- smart proxy log
- global registration template content

Thank you!
Comment 4 soham 2021-02-05 18:17:04 UTC 
Hello Leos,

My pkg versions were:
foreman-2.3.1.2-1.el7sat.noarch and foreman-proxy-2.3.1-1.el7sat.noarch . Its probably fixed in foreman-2.3.1.5-1.el7sat.noarch since you tested it out already.

- Soham Majumdar
Comment 5 Peter Ondrejka 2021-02-11 14:44:32 UTC 
Probably a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1900694
Comment 6 Leos Stejskal 2021-02-12 09:03:24 UTC 

*** This bug has been marked as a duplicate of bug 1900694 ***
Note You need to log in before you can comment on or make changes to this bug.