Hide Forgot
Description of problem: Adding new JDBC driver with wrong params does not fail in UI. Version-Release number of selected component (if applicable): 5.7.0.4-alpha1.20161005153002_cfc8a23 How reproducible: always Steps to Reproduce: 1. From UI of Server, select "Add JDBC Driver" menu item. 2. Select some jar file to upload (could be anything) 3. The rest of input params fill some wrong values. 4. Submit. Actual results: In UI it shows success message "JDBC Driver has been installed on this server". But in EAP server.log of course it fails. Expected results: The failure notification should be shown in UI after submitting the form with wrong input values.
Just a note - we have *no* way of knowing that a jar is valid on the MiQ UI, so whatever we will come up with, will be an asynchronous notification of success or failure, while the message after submitting can only mean "yes I have submitted that". Perhaps for this specific BZ, we should just change the toast to something like "JDBC Driver was submitted for installation"
If there will be way to chose JDBC Driver from list, while creating Datasource, then user will see whether driver installation was successful or not.
(In reply to Hayk Hovsepyan from comment #3) > If there will be way to chose JDBC Driver from list, while creating > Datasource, then user will see whether driver installation was successful or > not. BTW there will be a list to choose JDBC Drivers from (I should be done with that today). https://bugzilla.redhat.com/show_bug.cgi?id=1383426
*** Bug 1398398 has been marked as a duplicate of this bug. ***
Added smart JDBC Driver defaults since there really is not much more validation that we can do (required fields is about all that can be done). See: https://github.com/ManageIQ/manageiq-ui-classic/pull/876
Tested on 5.9.0.1.20171004215954_13427ce several things failed to verify: 1. Notification message is "JDBC Driver "XYZ" has been installed on this server.", but should be "JDBC Driver "XYZ" has been submitted to installation on this server." 2. IBM DB2 default driver class should be "com.ibm.db2.jcc.DB2Driver". 3. Sybase default driver class should be "com.sybase.jdbc4.jdbc.SybDriver".
@hayk This is very confusing to me because the BZ is so old. This should definitely be a new BZ as the original BZ is a year old. Please close and create new BZ if you agree.
Agreed, created new one https://bugzilla.redhat.com/show_bug.cgi?id=1501155