227513 - default privileges granted to default bugs user aren't enough for creation of shadowdb

Status: RESOLVED FIXED

(Bugzilla :: Administration, task)

Description

[Charlotte Allen]

User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0

When I change the bugzilla parameters to create the shadowdb (after I've
fixed the 'tainted value' bug), the privileges I granted the bugs user as
per the install instructions:

GRANT SELECT,INSERT,UPDATE,DELETE,INDEX, ALTER,CREATE,DROP,REFERENCES ON bugs.*
TO bugs@localhost IDENTIFIED BY '<bugs_password>';

Aren't adequate to create the new shadowdb  

Reproducible: Always

Steps to Reproduce:
1. Install bugzilla on Solaris 9 using the perl in /usr/perl5
(v5.6.1 built for sun4-solaris-64int)
2.Fix bug #227510
3. Log in as the bugzilla administrator
4.Select edit parameters link
5. Enter a name for the shadowdb
6. Turn "queryagainstshadowdb" on
7. Select "submit changes"
8. Reauthenticate as administrator

Actual Results:  
Get this error message:
Saving new parameters
 
DBD::mysql::st execute failed: Access denied for user: 'bugs@localhost' to
database 'backupbugs' at globals.pl line 271. [Thu Dec 4 14:03:06 2003]
doeditparams.cgi: DBD::mysql::st execute failed: Access denied for user:
'bugs@localhost' to database 'backupbugs' at globals.pl line 271. Content-type:
text/html
Software error:

CREATE DATABASE backupbugs: Access denied for user: 'bugs@localhost' to database
'backupbugs' at globals.pl line 276.

For help, please send mail to this site's webmaster, giving this error message
and the time and date of the error. [Thu Dec 4 14:03:06 2003] doeditparams.cgi:
CREATE DATABASE backupbugs: Access denied for user: 'bugs@localhost' to database
'backupbugs' at globals.pl line 276. 

Expected Results:  
Create the shadowdb

Comment 1

[Dave Miller [:justdave]]

The shadow database feature of Bugzilla (as far as Bugzilla itself maintaining
the shadow) is deprecated and no longer supported.  We recommend using MySQL's
built-in replication as it's much more accurate and less error prone.  If you're
on an installation which is having enough performance problems to require using
a shadow database you should really be running 2.17.4 or later because there are
other significant performance improvements as well.

That said, the permissions for the database need to be granted on the MySQL
server.  The same permissions should be granted as were granted to the Bugzilla
user for the primary Bugzilla database.  This is a deficiency in the
installation documentation as the person who installed Bugzilla would need to
have known this, and it isn't described anywhere in the documentation.

Comment 2

[Dave Miller [:justdave]]

Jake is leaving for a while (Reserve unit got called up), and we don't have a
new docs owner yet.  Anyone interested in helping out, please add
[e-mail] to your watch list in your email preferences in Bugzilla.

Comment 3

[Dave Miller [:justdave]]

Moving this back to Administration...  Since shadowdb is deprecated, I opted to
fix this by putting the relevant information into the parameter description on
the editparams page.

Old text:

If non-empty, then this is the name of another database in which Bugzilla will
keep a shadow read-only copy of everything.  This is done so that long slow
read-only operations can be used against this db, and not lock up things for
everyone else.  Turning on this parameter will create the given database; be
careful not to use the name of an existing database with useful data in it!

New text:

If non-empty, then this is the name of another database in which Bugzilla will
keep a shadow read-only copy of everything.  This is done so that long slow
read-only operations can be used against this db, and not lock up things for
everyone else.  Turning on this parameter will create the given database; be
careful not to use the name of an existing database with useful data in it! The
db_user you defined in the localconfig file must already have permission to
access and write to the new database name before entering the name here, or the
database creation will fail.  The same permissions should be granted as for the
primary database used by Bugzilla.

Comment 4

[Dave Miller [:justdave]]

Attachment: Patch v1

Comment 5

[Myk Melez [:myk] [@mykmelez]]

Comment on attachment 139306 [details] [diff] [review]
Patch v1

r=myk

Comment 6

[Dave Miller [:justdave]]

Checking in defparams.pl;
/cvsroot/mozilla/webtools/bugzilla/defparams.pl,v  <--  defparams.pl
new revision: 1.73.2.8; previous revision: 1.73.2.7
done