e2e: add Kusto query for HostedCluster conditions #3875
Conversation
|
/lgtm |
|
/test integration |
|
/test test-unit |
1 similar comment
|
/test test-unit |
When debugging what HyperShift is doing once we create the HostedCluster object, it's necessary to review the status of the HostedCluster object. We are able to glean a narrow view into this through the logging of ManifestWork brought back by Maestro. Signed-off-by: Steve Kuznetsov <stekuznetsov@microsoft.com>
stevekuznetsov
force-pushed
the
skuznets/kusto-conditions
branch
from
fed3296 to
3f47e9e
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, stevekuznetsov The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/override e2e-parallel |
|
@stevekuznetsov: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. DetailsIn response to this:
Instructions 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 kubernetes-sigs/prow repository. |
|
/override ci/prow/e2e-parallel |
|
@stevekuznetsov: Overrode contexts on behalf of stevekuznetsov: ci/prow/e2e-parallel DetailsIn response to this:
Instructions 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 kubernetes-sigs/prow repository. |
|
@stevekuznetsov: The following test failed, say
Full PR test history. Your PR dashboard. 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 kubernetes-sigs/prow repository. I understand the commands that are listed here. |
When debugging what HyperShift is doing once we create the HostedCluster object, it's necessary to review the status of the HostedCluster object. We are able to glean a narrow view into this through the logging of ManifestWork brought back by Maestro.