Created attachment 1409593 [details] the video of my screen to explain the problem Description of problem: I 'have 2 ovirt node with HE in version 4.2.1.7-1. If i make a template from a VM's snapshot in the web ui, there is a form ui to enter several parameter if the name of the template is missing and if we clic on the OK button, there is an highlighting red border on the name to indicate the problem. if i enter a long name for the template and if we clic on the OK button, nothing happend, and there is no highlight or error message to indicate there is a problem with the long name. May be a problem with the name ?? Version-Release number of selected component (if applicable): How reproducible: see the video in attachment. Steps to Reproduce: see the video in attachment. Actual results: Expected results: Additional info:
Alexander Wels (awels) said : Interesting, as that name is not long enough to trigger the name length validation. You have 64 characters total for the name. I just tried your scenario on the latest master branch, and it worked as expected, it created the template from the snapshot without issues with that exact same name. I don't see any recent changes to the frontend code for that dialog either. If you look in the engine.log does it say anything? I can only assume some validation is failing, and that validation message is not properly propagated to the frontend, but it should show something in the backend log regardless.
No information in the engine.log during the test.
Could it be browser dependent? Which browser are you using? Is there something special in the name? (lowering severity though - doesn't strike me as a high severity issue)
my test was done on firefox quantum 58.0.1 (64 bits), firefox 45.5 esr, chrome 41 and it is always the same result. no special in the name, i enter : template__windows_2012_stdR2
Hi guys, I've experienced the same issue. The name I wanted to use as a name during creation was something along the line of: aa-bbbbb-ccc-dd-eeee-v1 (obfuscated). This didn't work and there was no feedback other than nothing happening when I clicked the OK button. If I used a shorter name of the "aa-ccc-v1" then it worked fine. I am also perfectly able to rename the alread-created template to the shape "aa-bbbbb-ccc-dd-eeee-v1", but this means I'm not able to create a Sub-Versioned template, even if using the shorter name (probably because the base template name is invalid). If I rename the base template, v1, to aa-ccc-v1, I am able to create a aa-ccc-v2 sub-versioned template using the v1 as the base. Once created I am able to rename the templates to "aa-bbbbb-ccc-dd-eeee-v1" and "aa-bbbbb-ccc-dd-eeee-v2". Keep up the good work :) //Mike
can you please take a look? It's just a medium priority, but let's target it once the issue is understood
(In reply to Michal Skrivanek from comment #6) > can you please take a look? It's just a medium priority, but let's target it > once the issue is understood I tried all mentioned scenarios on master branch (both mentioned names, a name with invalid characters, name longer than 64 chars, an already existing name..) and all worked as expected. I can't reproduce this issue.
(In reply to Michael from comment #5) Hi Michael, since it is not reproduced for us, can you please send the engine log once the issue is reproduced for you?
(In reply to Sharon Gratch from comment #8) > (In reply to Michael from comment #5) > Hi Michael, > since it is not reproduced for us, can you please send the engine log once > the issue is reproduced for you? Hi Sharon, Thank you for looking into the bug. I am no longer able to reproduce the error either. Are you releasing updates every now and then? If not, perhaps the issue was related to something else... mystery! :) I'll keep the bug in mind and refer to it, if I see it happen again. Have a nice day, Michael
Hi Nicolas, Is this issue still reproduced and if so then can you please send the engine log? Maybe we can get some info on the problem from the log...
Hi Sharon, since the bug was reported, i update HE and node. I've not access to the platform this week, but next week i'll take a look to see if the bug disappear or not. See you next week. Nicolas
Hi, sorry for the delay. I have tested again on ovirt 4.2.3, and everything works fine. Can't reproduce. You can closed this issue. Thanks. Nicolas VAYE
(In reply to nicolas vaye from comment #12) > Hi, > > sorry for the delay. > I have tested again on ovirt 4.2.3, and everything works fine. > Can't reproduce. > > You can closed this issue. > > Thanks. > > > Nicolas VAYE Nicolas, thanks for the update. So since it is not reproduced anymore- I'm closing this bug.