Fixed container status check #1
Merged
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
rapatchi
reviewed
Mar 13, 2020
| found_running = found_running + 1 | ||
| time.sleep(2) | ||
| if pod.metadata.name.startswith('connect-agent'): | ||
| for container_status in pod.status.container_statuses: |
There was a problem hiding this comment.
Is is possible to merge checking container status and container availability into one step ?
| if pod.metadata.name.startswith('connect-agent'): | ||
| for container_status in pod.status.container_statuses: | ||
| if container_status.name == 'connect-agent': | ||
| connect_agent_state = container_status.state.running |
There was a problem hiding this comment.
could you explain what are the possible values of container_status.state.running ?.
Owner
Author
There was a problem hiding this comment.
Its is 'None' if the container is not running. If container is running, it contains the start-time of the container
rapatchi
approved these changes
Mar 16, 2020
akashkeshari
pushed a commit
that referenced
this pull request
Apr 21, 2020
akashkeshari
pushed a commit
that referenced
this pull request
Jan 22, 2021
) * Push updates to k8sconfiguration keys and fix issue with known hosts * Remove print statement * Increase CLI version and add to changelog * Remove deprecated CLIError and reduce history.rst text * Joinnis/add validators (#1) * Push updates to k8sconfiguration keys and fix issue with known hosts * Add validations for naming * Remove print statement * Add validator testing to the set of tests * Add unit testing and greater scenario test coverage * Delete test_kubernetesconfiguration_scenario.py * Remove dots from the regex for naming * Add the scenario tests back * Add good key scenario test to scenarios * Remove numeric checks for configurations * Reduce scneario testing * Move validation of configuration name into creation command * Add table formatting for list and show * Update version * Update the error message for validation failure * Update the test cases for the new error messages * Change error message and regex check * Add proper formatting to code files * Updated final formatting checks * Updated error messages * Update error message and help text * Final update to error messaging * Update test_validators.py * Update based on PR comments Co-authored-by: Jonathan Innis <[email protected]>
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.
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally?For new extensions: