Remove legacy MTU feature #4578
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hlipsig
requested review from
bennerv,
cadenmarchese,
hawkowl,
jharrington22,
kimorris27,
mociarain,
mrWinston,
rogbas,
sankur-codes,
tiguelu,
tsatam,
wanghaoran1988 and
yjst2012
as code owners
shubhadapaithankar
approved these changes
Jan 30, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue this PR addresses:
Fixes
ARO-22749
What this PR does / why we need it:
Deletes MTU installatin time. Feature Flag from RP. But keeps the MTU monitor since it's a valid day2 operation
Test plan for issue:
Removed the MTU related tests (that are not monitors) and ran unit tests locally. All passed. Green e2e Signal is all that's needed.
Is there any documentation that needs to be updated for this PR?
BU will need to inform the 1 customer who was using this that his has been removed, however they were already made aware of this.
How do you know this will function as expected in production?
It should remove a rarely used code path, normal operations should continue.