Red Hat Bugzilla – Bug 1159304
New host form errors after validation error
Last modified: 2016-07-27 04:46:04 EDT
While attempting to create a new host on Sat-6.0.4, I entered a Name "thomasmckay-sam" that had already been taken; proper validation red error box appeared. I then changed the name to "rpi-sam" in the form to a unique one and submitted again. The following appeared <pre> Failed to create a compute rhevm1.satellite.lab.eng.rdu2.redhat.com (RHEV) instance rpi-sam.released-el7.satellite.lab.eng.rdu2.redhat.com: Name must be formed of alphanumeric characters, numbers or "-_.". </pre> This leads, of course, to a situation where the entire new form must be reloaded and all values re-entered. After that the "rpi-sam" name works fine.
Created from redmine issue http://projects.theforeman.org/issues/8230
Created attachment 952509 [details] foreman-debug output
Upstream bug component is Hosts
I could not reproduce in current upstream - attempted to create a host with existing name, got validation error, changed name, host was created with no problem. From upstream discussion appears the second failure (after changing the duplicate name) was caused by an invalid name given to RHEV leading to the failure and was unrelated to the previous failure. Moving to ON_QA for verification.
VERIFIED: # rpm -q foreman foreman-1.11.0.9-1.el7sat.noarch Steps: Please, note here I checked only name "test6-sam" is accepted by the form or not https://cisco-b200m1-03.rhts.eng.bos.redhat.com/hosts/test6-sam.rhts.eng.bos.redhat.com I am not sure whether the instance is created or not properly There was no need to reload the form and re-enter the values
Please note, Here are the steps: Create a host with a name already been taken. It gives error : Name "test7-sam" that had already been taken Then, I changed the name to "test8-sam". There was no need to load the form again All other values were retained
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/RHBA-2016:1500