[dev.icinga.com #9340] icinga2 ido mysql misspelled database username

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/9340

Created by darkdragon on 2015-05-31 18:30:12 +00:00

Assignee: formorer
Status: Resolved (closed on 2015-10-20 12:46:26 +00:00)
Target Version: 2.3.11
Last Update: 2015-10-20 12:46:26 +00:00 (in Redmine)

Icinga Version: 2.3.4
Backport?: No
Include in Changelog: 1

---

When installing icinga2-ido-mysql via Ubuntu console, the username created via the setup is "icinga2-ido-mysq" (note the missing small "L" at the end).

[icinga-migration]

Updated by mfrosch on 2015-06-01 07:11:38 +00:00

• Category changed from DB IDO to Packages
• Status changed from New to Assigned
• Assigned to set to mfrosch

This is a problem in the Debian package definitions, we should change the default db user and database to icinga2.

[icinga-migration]

Updated by formorer@formorer.de on 2015-06-01 07:45:08 +00:00

On Mon, 01 Jun 2015, development@icinga.org wrote:

Issue #9340 has been updated by lazyfrosch.

Category changed from DB IDO to Packages
Status changed from New to Assigned
Assignee set to lazyfrosch

This is a problem in the Debian package definitions, we should change the default db user and database to icinga2.
I don't think so. Changing this would be a nightmare.

Alex

[icinga-migration]

Updated by mfrosch on 2015-06-03 18:41:26 +00:00

formorer@formorer.de wrote:

I don't think so. Changing this would be a nightmare.

Not when you only change the dbconfig-common defaults, this will not change any existing installation...

[icinga-migration]

Updated by TwizzyDizzy on 2015-10-19 09:46:13 +00:00

lazyfrosch wrote:

formorer@formorer.de wrote:
> I don't think so. Changing this would be a nightmare.

Not when you only change the dbconfig-common defaults, this will not change any existing installation...

I second that.

The underlying problem is, that the "User" column in mysql.user table is of type "char(16)" - unfortunately, "icinga2-ido-mysql" is 17 chars.

This leads to the dbconfig-dialogue to show "icinga2-ido-mysql" as username while the user being created is truncated to "icinga2-ido-mysq". This is utterly misleading.

So I, too, would suggest changing the username to "icinga2idomysql" (just like the database) in the defaults.

Cheers
Thomas

[icinga-migration]

Updated by formorer on 2015-10-19 10:12:22 +00:00

• Assigned to changed from mfrosch to formorer
• Done % changed from 0 to 100
• Backport? changed from TBD to No

TwizzyDizzy wrote:

lazyfrosch wrote:
> formorer@formorer.de wrote:
> > I don't think so. Changing this would be a nightmare.
>
> Not when you only change the dbconfig-common defaults, this will not change any existing installation...

I second that.

The underlying problem is, that the "User" column in mysql.user table is of type "char(16)" - unfortunately, "icinga2-ido-mysql" is 17 chars.

This leads to the dbconfig-dialogue to show "icinga2-ido-mysql" as username while the user being created is truncated to "icinga2-ido-mysq". This is utterly misleading.

So I, too, would suggest changing the username to "icinga2idomysql" (just like the database) in the defaults.
For all future new installations database and user are set to icinga2.

See
http://anonscm.debian.org/cgit/pkg-nagios/pkg-icinga2.git/commit/?id=b9e26af96a1492120939a99bb80550fb12d02074

[icinga-migration]

Updated by mfriedrich on 2015-10-20 12:46:26 +00:00

• Status changed from Assigned to Resolved
• Target Version set to 2.3.11

Please update the issue for which target version this change will happen in the future. That way such changes can be incorporated into the Changelog. Thanks.