Bug 12780 - Update candidate to mongodb: update clobber user configuration
Summary: Update candidate to mongodb: update clobber user configuration
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: has_procedure MGA4-32-OK MGA4-64-OK a...
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2014-02-15 13:59 CET by Philippe Makowski
Modified: 2014-02-21 19:24 CET (History)
5 users (show)

See Also:
Source RPM: mongodb-2.4.6
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Philippe Makowski 2014-02-15 13:59:24 CET 
Description of problem:

During test of mga#12251 it was found that upgrade of mongod-server package clobber user configuration and tempfiles dir were not correctly handled.

Updated packages in core/updates_testing:
========================
mongodb-2.4.6-2.1.mga4
mongodb-server-2.4.6-2.1.mga4

from SRPMS:
mongodb-2.4.6-2.1.mga4.src.rpm


procedure can be to install mongodb server, change /etc/mongod.conf for example, set noprealloc = true to disable the preallocation of data files

update mongodb-server

additionnal test can be to start mongodb-server, open mongo shell and do a :
db.test.insert({"\x16\x00\x00\x00\x05hello\x00\x010\x00\x00\x00world\x00\x00" : "world"})

it should me rejected

more example to simple tests are here :
http://docs.mongodb.org/v2.4/tutorial/getting-started/



Reproducible: 

Steps to Reproduce:
Philippe Makowski 2014-02-15 14:00:22 CET

Whiteboard: (none) => has_procedure

Samuel Verschelde 2014-02-15 14:15:52 CET

CC: (none) => stormi
Summary: Update clobber user configuration => Update candidate to mongodb: update clobber user configuration

Comment 1 Lewis Smith 2014-02-20 13:05:10 CET 
Tested MGA4 64-bit real hardware. OK.

Before update:
Followed all the simple tests referred to in Description. They all worked as expected.
The specific additional test cited above *failed* (not sure whether it should have):
 Thu Feb 20 12:39:46.437 Error: JavaScript property (name) contains a null char   which is not allowed in BSON. {} at src/mongo/shell/collection.js:201

Changed /etc/mongod.conf as suggested & added a comment line.

After update from Core Update Testing to:
 mongodb-2.4.6-2.1.mga4
 mongodb-server-2.4.6-2.1.mga4
Re-ran the simple tests from after data creation. Results again as expected.
The extra specific test failed again as noted previously (NUL character).

/etc/mongod.conf *retained* the prior modification.

CC: (none) => lewyssmith
Whiteboard: has_procedure => has_procedure MGA4-64-OK

Comment 2 claire robinson 2014-02-21 13:36:23 CET 
Needs testing mga4 32 to validate please.
Comment 3 Rémi Verschelde 2014-02-21 17:42:59 CET 
Testing complete Mageia 4 i586.

CC: (none) => remi
Whiteboard: has_procedure MGA4-64-OK => has_procedure MGA4-32-OK MGA4-64-OK

Comment 4 Rémi Verschelde 2014-02-21 17:54:51 CET 
Validating update, advisory uploaded. Please push to 4 core/updates.

Keywords: (none) => validated_update
Whiteboard: has_procedure MGA4-32-OK MGA4-64-OK => has_procedure MGA4-32-OK MGA4-64-OK advisory
CC: (none) => sysadmin-bugs

Comment 5 Thomas Backlund 2014-02-21 19:24:26 CET 
Update pushed:
http://advisories.mageia.org/MGAA-2014-0060.html

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.