[MTV-1801] [RFE] Non informative message #1462
Open
Conversation
This file contains 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
Signed-off-by: Jeff Puzzo <jpuzzo@redhat.com>
|
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #1462 +/- ##
==========================================
- Coverage 36.81% 36.32% -0.50%
==========================================
Files 158 156 -2
Lines 2548 2522 -26
Branches 599 588 -11
==========================================
- Hits 938 916 -22
- Misses 1428 1601 +173
+ Partials 182 5 -177 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📝 Links
https://issues.redhat.com/browse/MTV-1801
📝 Description
Improve message to point users to the "Mappings" tab, indicating editing is required to solve specific Critical condition type error responses for plans.
The JIRA issue suggests including more information in the alert, and we can figure out which storage and network maps are missing, but that information is more readily available in the Mappings tab, and it seems like that is the best place to call those missing mappings out. How we do that exactly is a question for UXD, which can be a separate enhancement follow-up to this solution.
🎥 Demo
Screen.Recording.2025-02-05.at.2.47.57.PM.mov