467107 - Imported database on chat-support staging incomplete

Status: RESOLVED INCOMPLETE

(mozilla.org Graveyard :: Server Operations, task)

Description

[Matthew Middleton (:zzxc)]

Attachment: Openfire log from staging

The database set up for Openfire on pm-chat-stage01 seems to be incomplete; many queries (see below) are returning only the default information rather than the hundreds of rows on production.  This server was set up for bug 466601.

From the attached logfile, it seems that the database schema was never upgraded.  I'm not sure if this was caused by an installation issue, or by an incomplete import.  The database should be imported before the new Openfire is installed to /opt/openfire to match the situation that will happen on production.  These are some queries ran on staging that should be returning lots of information:


Your query: select * from ofUser;

Your response:
username	plainPassword	encryptedPassword	name	email	creationDate	modificationDate
admin	null	118ea9ff327ee2ae5c6b6d98adf1b75221ea1326aac8f62f56024a03ce41342e	Administrator	[e-mail]	0	0
demo	null	b9024fa88147b2861e32e1e97806e7a15b663397e8206871	Fastpath Demo Account	[e-mail]	001227742624223	001227742624223


-----------



Your query: select * from fpSession limit 10;

Your response:
sessionID	userID	workgroupID	transcript	startTime	endTime	queueWaitTime	state	caseID	status	notes
ix3cv43	Fh93mlSE4s	2	rawr

Comment 1

[Aravind Gottipati [:aravind]]

From our conversation, this was not clear to me that the db should have been imported prior to the openfire installation.  Since there was never a staging server setup for this, I started with a clean database.  I can redo this stuff and start with a full db this time.

Comment 2

[Aravind Gottipati [:aravind]]

Is this still needed?

Comment 3

[Matthew Middleton (:zzxc)]

This will be needed if we need to make changes to the Openfire core code, which would require pushing out a fully custom Openfire build to production.  We probably won't need it in the short term, since Openfire plugins can be tested and upgraded without IT's involvement.

This should still be fixed eventually, so that we can test builds with the production database if necessary.  I'm reducing the severity to minor - no bugs targeted for 2008 require it.

Comment 4

[Aravind Gottipati [:aravind]]

Since this is not needed right now, I am going to close it.  Please re-open (or open a new bug) when you need us to import this data.