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 1353104 - Validation for Domain and OS Parameters tab stopped to work
Summary: Validation for Domain and OS Parameters tab stopped to work
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.2.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: orabin
QA Contact: Renzo Nuccitelli
URL:
Whiteboard:
Depends On: 1296662
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-06 06:26 UTC by Oleksandr Shtaier
Modified: 2019-09-26 16:19 UTC (History)
5 users (show)

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

Attachments (Terms of Use)
Large domain validation on sat 6.3 snap 6 (68.37 KB, image/jpeg)
2016-11-09 19:05 UTC, Renzo Nuccitelli 		no flags Details
Domain with invalid parameter (71.30 KB, image/jpeg)
2016-11-10 08:20 UTC, orabin 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15629 0 None None None 2016-07-08 15:40:13 UTC

Description Oleksandr Shtaier 2016-07-06 06:26:29 UTC 
Description of problem:
When you input invalid values into 'Name' and 'Value' fields for new Domain or Operating System entity and push submit button, parameter entry just disappear without any error shown

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

How reproducible:
Always

Steps to Reproduce:
1. Create new Domain entity
2. Open it and go to 'Parameters' tab
3. Push '+Add Parameter' button
4. Input invalid values (longer than 256 characters) in both fields
5. Push 'Submit' button


Actual results:
Parameter entry is disappeared and no error is shown

Expected results:
Proper (just usual one) error is shown

Additional info:
Comment 1 Oleksandr Shtaier 2016-07-06 06:28:08 UTC 
Regression is introduced in latest SNAP (don't see any errors like that in automation runs for SNAP 17)
Comment 3 jcallaha 2016-07-07 17:58:23 UTC 
The error is shown in production.log, but doesn't make it to the UI.

2016-07-07 13:53:36 [app] [I]   Parameters: {"utf8"=>"✓", "authenticity_token"=>"54c/rNIrD587VYgQAS9monLcGJIf+vwrkafz3n+oKp0=", "domain"=>{"name"=>"google.com", "fullname"=>"", "dns_id"=>"", "domain_parameters_attributes"=>{"1467914013432"=>{"name"=>"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", "value"=>"[FILTERED]", "hidden_value"=>"[FILTERED]", "_destroy"=>"false"}}, "location_ids"=>[""], "organization_ids"=>["", "1"]}, "id"=>"2-google-com"}
2016-07-07 13:53:36 [app] [I] Failed to save: Name is too long (maximum is 255 characters)
Comment 6 Ivan Necas 2016-07-08 15:09:22 UTC 
This beahaviour was introduced by https://bugzilla.redhat.com/show_bug.cgi?id=1296662 and is caused by the fact, that we check the permissions in the form, which causes the data from form not survive the reload in form.
Comment 8 Ivan Necas 2016-07-08 15:40:11 UTC 
Created redmine issue http://projects.theforeman.org/issues/15629 from this bug
Comment 10 Bryan Kearney 2016-07-08 16:14:48 UTC 
Upstream bug component is Provisioning
Comment 11 Bryan Kearney 2016-07-11 08:15:08 UTC 
Upstream bug component is WebUI
Comment 12 Bryan Kearney 2016-07-11 12:15:13 UTC 
Upstream bug assigned to orabin
Comment 13 Bryan Kearney 2016-07-11 12:15:17 UTC 
Upstream bug assigned to orabin
Comment 15 Bryan Kearney 2016-07-12 13:26:08 UTC 
Replacing this with the simpllified version from https://bugzilla.redhat.com/show_bug.cgi?id=1354572. In 6.3 we should re-apply this bug.
Comment 16 Bryan Kearney 2016-07-12 20:15:24 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/15629 has been closed
Comment 19 Renzo Nuccitelli 2016-11-09 19:05:45 UTC 
Created attachment 1219050 [details]
Large domain validation on sat 6.3 snap 6
Comment 20 Renzo Nuccitelli 2016-11-09 19:25:29 UTC 
While verifying this bug the validation is ok. Inputs are red and user is redirected to parameters tab when submitting form. But there is no message explaining what the error actually is. Important noticing the error message appear on log:

[root@foo ~]# grep "Name is too long" /var/log/foreman/production.log 
2016-11-09 20:20:46 0a17d5b6 [app] [I] Failed to save: Name is too long (maximum is 255 characters)

So am setting it back to assigned.
Comment 21 Renzo Nuccitelli 2016-11-09 19:29:13 UTC 
In time: the validation worked on both 6.2.4 and 6.3 snap 6 versions, but without error messages as mentioned on comment 20
Comment 22 orabin 2016-11-10 08:20:34 UTC 
Created attachment 1219241 [details]
Domain with invalid parameter
Comment 25 Satellite Program 2018-02-21 16:44:36 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.