Hi,
I’ve spent some time looking at this issue and have made some progress.
The issue appears after upgrading from version 5.6.7 to 6.7.6
The issue does NOT appear if i install a new installation of Version 6.7.6
After comparing all the plugins versions, database settings and tables between the fresh install ( which worked) and the upgraded instance ( which didn’t ), the only difference i could find was the following trigger
MySQL [SonarQube]> show triggers;
+-----------+--------+-------+--------------------------------------------------------------------------------------------------------------
---------------------------+--------+------------------------+---------------------+------------------+--------------- -------+-------
--------------+--------------------+
| Trigger | Event | Table | Statement
| Timing | Created | sql_mode | Definer | character_set_ client |
collation_connection | Database Collation |
+-----------+--------+-------+-------------------------------------------------------------------------------------------------------------
--------------------------+--------+------------------------+---------------------+------------------+--------------- -------+--------
-------------+--------------------+
| ins_notif | INSERT | users | INSERT INTO properties (prop_key, text_value, user_id) values
("notification.ChangesOnMyIssue.EmailNotificationChannel","true", NEW.id) | AFTER | 2019-01-04
20:09:14.27 | STRICT_TRANS_TABLES | userAppliSONAR@% | latin1 | latin1_swedish_ci |
utf8_general_ci |
+-----------+--------+-------+-------------------------------------------------------------------------------------------------------------
---------------------------+--------+------------------------+---------------------+------------------+--------------- -------+------
--------------+--------------------+
1 row in set (0.04 sec)
MySQL [SonarQube]>
As a test, i dropped this trigger and then i was able to successfully able to add a new user.
My Questions: Is this ins_notif trigger created by SonarQube?
Is it ok to just drop this trigger, or should it be modified to make it work after the upgrade to 6.7