[DOCS-14878] [SERVER] Investigate changes in SERVER-56731: Consider running server tests on newer SLES 12 service pack Created: 19/Oct/21  Updated: 29/Oct/23  Resolved: 16/Jun/22

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2.0, 5.1.0-rc2, 5.0.8

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Ian Fogelman
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
backported by DOCS-15226 [BACKPORT] [v5.0] Consider running se... Closed
Documented
documents SERVER-56731 Consider running server tests on newe... Closed
Participants:
Days since reply: 1 year, 33 weeks, 1 day ago

 Description   
Downstream Change Summary

Suse 12 builds are now using Suse12 sp5 to compile binaries so it might not run on sp4 and older.

Description of Linked Ticket

There have been several hangs observed in Evergreen when running on the suse12-large distro related to pthread_mutex_lock waiting to acquire a mutex which the core dump reports as not being owned by any thread. It is strongly suspected to be an issue with the platform itself given that we haven't observed similar hangs on any other Linux distro. This has led to duplicative effort across multiple subteams to diagnose what are ultimately believed to be false positives and has led to an increase in distrust of server hangs reported on SLSE 12 in general.

We appear to be running tests on SLES 12 (SP0) which has been unsupported since 01 July 2019. SLES 12 SP3 appears to be the oldest currently supported release of SLES 12. https://www.suse.com/lifecycle

> cat /etc/SuSE-release
SUSE Linux Enterprise Server 12 (x86_64)
VERSION = 12
PATCHLEVEL = 0

My understanding is that we intentionally compile on unsupported versions to avoid breaking our minimum supported version. This doesn't mean we must also test on those same unsupported versions, especially when there is evidence to suggest that an issue exists with the platform itself. My request is that we run server tests on a newer SLES 12 service pack in hopes it addresses the pthread_mutex_lock issues we've seen.



 Comments   
Comment by Githook User [ 21/Jun/22 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: DOCS-14878-add-footnote-for-SLES12-SPs (#1212)

  • update footnote
  • CR1 Feedback
Comment by Githook User [ 15/Jun/22 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: DOCS-14878 v4.4 (#1269)

  • update footnote
  • CR1 Feedback
Comment by Githook User [ 15/Jun/22 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: DOCS-14878 v5.0 (#1268)

  • update footnote
  • CR1 Feedback
Comment by Githook User [ 15/Jun/22 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: DOCS-14878 v5.3 (#1267)

  • update footnote
  • CR1 Feedback
Comment by Githook User [ 15/Jun/22 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: DOCS-14878-add-footnote-for-SLES12-SPs (#1212)

  • update footnote
  • CR1 Feedback
Comment by April Schoffer [ 17/May/22 ]

Reopening this issue since we do need docs updates reflect Suse12 SP5 for 5.0+.
Please let us know if this is already captured elsewhere so we can link up our SERVER tickets for tracking posterity. TY!

Comment by Andrew Morrow (Inactive) [ 09/May/22 ]

ian.fogelman@mongodb.com - You can see that in the change that upgraded 5.0, for example, the change was to move to a new distro type that had sp5 in the name: https://github.com/mongodb/mongo/commit/509f187473262cd3b0e87f66eb96ea6176be60ba

If v4.4 is still on distros that don't say sp5, I think it still using the image without the service pack for builds. You would need to ask zakhar.kleyman@mongodb.com why we decided not to backport to v4.4 and v4.2.

Comment by Ian Fogelman [ 09/May/22 ]

andrew.morrow@mongodb.com Right for 5.0+ it would be SP5, but for other LTS versions 4.4 for instance : https://github.com/mongodb/mongo/blob/v4.4/etc/evergreen.yml#L11566 shows just says "suse12-test", is it safe to assume that all SUSE 12 tests are being ran on Service pack 5 for all versions? The way the platform support matrix setup, "SLES 12" is 1 row which spans across all versions, so I dont want to mislead the users if the 4.4 and 4.2 branches are tested on a different service pack.

Comment by Andrew Morrow (Inactive) [ 09/May/22 ]

ian.fogelman@mongodb.com -

  • I think updating the matrix to say "SUSE 12 SP5" would be fine.
  • Based on the BACKPORT tickets linked to SERVER-56731 I believe this only applies to v5.0+.
Comment by Jess Mokrzecki [ 11/Apr/22 ]

Fix Version updated for upstream SERVER-56731:
5.2.0, 5.1.0-rc2, 5.0.8

Comment by PM Bot [ 19/Oct/21 ]

Downstream changes updated for upstream SERVER-56731:
Suse 12 builds are now using Suse12 sp5 to compile binaries so it might not run on sp4 and older.

Generated at Thu Feb 08 08:11:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.