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 1461016 - UI / Host Collection / Copy page missing validation
Summary: UI / Host Collection / Copy page missing validation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Host Collections
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Walden Raines
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-13 11:18 UTC by Stanislav Tkachenko
Modified: 2019-08-12 16:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot (130.86 KB, image/png)
2017-06-13 11:18 UTC, Stanislav Tkachenko
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 20011 0 None None None 2017-06-13 22:13:28 UTC

Description Stanislav Tkachenko 2017-06-13 11:18:10 UTC
Created attachment 1287236 [details]
Screenshot

Description of problem:
When creating host collection copy with invalid name (e.g. 300 chars long), pressing on `Create` button does nothing, there are no visible validation messages. Only console shows that POST request (POST https://sat6.com/katello/api/v2/host_collections/16/copy) returned `422 Unprocessable Entity`.

Version-Release number of selected component (if applicable):
Sat 6.3.0 Snap 2.0:
* satellite-6.3.0-15.0.beta.el7sat.noarch
* foreman-1.15.0-1.el7sat.noarch
* katello-3.4.0-3.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Navigate to Hosts / Host Collection
2. Select any exising host collection or create one
3. Select Action / Copy Host Collection
4. Insert invalid new name
5. Press create
6. Check for validation messages and/or browser console for logs

Actual results:
Clicking on create button does nothing

Expected results:
Visible validation message

Additional info:

Comment 2 Samir Jha 2017-06-13 22:13:26 UTC
Created redmine issue http://projects.theforeman.org/issues/20011 from this bug

Comment 3 Satellite Program 2017-06-19 14:07:34 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20011 has been resolved.

Comment 4 Walden Raines 2017-08-02 14:05:40 UTC
Verified on 6.3.0 snap 9, I now see:

Validation failed: Name is too long (maximum is 255 characters)

Comment 6 Satellite Program 2018-02-21 16:54:17 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


Note You need to log in before you can comment on or make changes to this bug.