grafana: Fix wrong scheduler command variables of grafana in cloud env (#15833)#15936
Conversation
Signed-off-by: Connor1996 <zbk602423539@gmail.com>
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
|
/hold |
ref tikv#15832 Signed-off-by: Neil Shen <overvenus@gmail.com>
|
/unhold |
|
/merge |
|
@Connor1996: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 852cf18 |
|
@ti-chi-bot: Your PR was out of date, I have automatically updated it for you. If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
This is an automated cherry-pick of #15833
What is changed and how it works?
Issue Number: Close #15832
What's Changed:
We use regex
/type="([^"]+)"/to grep the command variables. In cloud env, there is a field calledinstance_typeapart fromtype. So it would accidentally grep the name ofinstance_type.Related changes
Check List
Tests
Before
After
Release note