Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release/7.0] Correct minimum memory size value from 200MB to 20MB #77787

Merged
merged 1 commit into from
Nov 11, 2022

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 2, 2022

Backport of #77682 to release/7.0

/cc @akoeplinger @nealef

Customer Impact

Typo caused value to be 200MB instead of 20MB which caused an incorrect calculation of the cgroup minimum memory size. This prevented mono on s390x from observing memory limits when running inside containers.

Testing

CI testing.

Risk

Low.

IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.

@carlossanlop
Copy link
Member

carlossanlop commented Nov 3, 2022

@akoeplinger @vargaz this needs to go through Tactics. Can one of you please fill out the template and send the email to request approval?

@carlossanlop
Copy link
Member

And when ready, please add the servicing-consider label.

@akoeplinger akoeplinger added this to the 7.0.x milestone Nov 7, 2022
@steveisok steveisok added the Servicing-consider Issue for next servicing release review label Nov 7, 2022
@rbhanda rbhanda modified the milestones: 7.0.x, 7.0.1 Nov 10, 2022
@rbhanda rbhanda added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Nov 10, 2022
@carlossanlop
Copy link
Member

carlossanlop commented Nov 11, 2022

The re-run came mostly green. The only CI failure seems to be an unrelated nuget download problem with the following error, which I reported to FR, and I was told this is another instance of dotnet/arcade#10885 :

Response status code does not indicate success: 500 (Internal Server Error - Request was blocked due to exceeding usage of resource 'Concurrency' in namespace 'IPAddress'. For more information on why your request was blocked, see the topic "Rate limits" on the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=823950). (DevOps Activity ID: F690A076-90B8-4339-B8EA-8E574E74539B)).

Aside from that: Signed off by area owner, approved by Tactics, no need for OOB package authoring changes. Ready to merge. :shipit:

@carlossanlop carlossanlop merged commit e473891 into release/7.0 Nov 11, 2022
@carlossanlop carlossanlop deleted the backport/pr-77682-to-release/7.0 branch November 11, 2022 00:19
@ghost ghost locked as resolved and limited conversation to collaborators Dec 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-VM-meta-mono Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants