ipatests: Increase timeout value in test_getcert_list_profile_using_subca #4924
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
…ubca test_getcert_list_profile_using_subca test had a timeout value of 50 waiting for the cert to be in MONITORING state, this has now been replaced with 300, since the certmonger request was in state SUBMITTING instead of MONITORING causing the test to fail.
|
Hi @menonsudhir |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
The azure failure is linked to tomcat update, please see https://bugzilla.redhat.com/show_bug.cgi?id=1857043 |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
The test is green, please remove the temp commit. |
|
ACK when PR-CI completes. |
flo-renaud
added
ack
|
master:
|
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.
test_getcert_list_profile_using_subca test had a timeout value of 50 waiting for the cert to be in MONITORING state, this has now been replaced with 300, since the certmonger request was in state SUBMITTING instead of MONITORING causing the test to fail.