[SERVER-11915] block_check_supported.js failing on linux-64 AMI Created: 02/Dec/13  Updated: 11/Jul/16  Resolved: 04/Dec/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 2.5.5

Type: Bug Priority: Major - P3
Reporter: Adinoyi Omuya Assignee: Adinoyi Omuya
Resolution: Done Votes: 0
Labels: build-failure
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

MCI Logs here: http://mci.10gen.com/ui/task/mongodb_mongo_master_linux_64_debug_024a6739ac52ce669bff42b8782484f27a8cbc34_13_12_02_14_14_05_js_linux_64

Buildlogger: http://buildlogs.mongodb.org/mci_0.9_linux_64_debug/builds/19721/test/js_0/block_check_supported.js

The test does a check for the "name" field from db.hostInfo().os which appears to have been a temporary fix pending SERVER-9325. On our linux-64 AMI, this field is unset and thus causes the test to fail (even though the commands being tested are supported). I don't think this code path is necessary any longer.



 Comments   
Comment by Matt Kangas [ 04/Dec/13 ]

LGTM. MCI seems clear on this issue now.

Comment by Adinoyi Omuya [ 03/Dec/13 ]

I think that failure is before the fix went it.

Comment by Matt Kangas [ 03/Dec/13 ]

Example of block_check_supported.js failing via dur_passthrough.js. Still on Linux-64.

2013/12/02 • ae5d69aff2bc Linux 64-bit • durability
http://buildlogs.mongodb.org/mci_0.9_linux_64/builds/23973/test/durability_0/dur_passthrough.js

         Test : jstests/block_check_supported.js ...
Testing workingSet and indexCounters portions of serverStatus
Testing db.serverStatus({workingSet:1}).workingSet on "" (Solaris?) -- expecting {  "info" : "not supported" }
assert: [{ "info" : "not supported" }] != [{
	"note" : "thisIsAnEstimate",
	"pagesInMemory" : 238,
	"computationTimeMicros" : 3170,
	"overSeconds" : 10
}] are not equal : Test FAILED: db.serverStatus({workingSet:1}).workingSet did not return the expected value

Comment by Githook User [ 03/Dec/13 ]

Author:

{u'username': u'deafgoat', u'name': u'Wisdom Omuya', u'email': u'deafgoat@gmail.com'}

Message: SERVER-11915: ensure that lsb-release information is sufficient and add centos-release to hostInfo search path

Signed-off-by: Ian Whalen <ian.whalen@gmail.com>
Branch: master
https://github.com/mongodb/mongo/commit/3a374cb5d0c13d1e7b376d316da6b8652b99738d

Comment by Adinoyi Omuya [ 02/Dec/13 ]

Good idea. I'll put up a cr for this.

Comment by Eric Milkie [ 02/Dec/13 ]

Alternatively, we could change the test to look at .type instead of .name, and look for the OS types we're interested in. It would still be a good idea to get the distro name working if we can.

Comment by Eric Milkie [ 02/Dec/13 ]

The hostInfo() information is checked in several other test files besides this one. It needs to work.

The information for Linux comes from one of:
/etc/lsb-release, /etc/system-release, /etc/redhat-release, /etc/gentoo-release, /etc/novell-release, /etc/gentoo-release, /etc/SuSE-release, /etc/SUSE-release, /etc/sles-release, /etc/debian_release, /etc/slackware-version

If there is a different file for the MCI hosts, we can add it to the list.

Generated at Thu Feb 08 03:27:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.