Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[container_checker] Use Feature table to get running containers #7474

Merged
merged 9 commits into from
May 7, 2021

Conversation

renukamanavalan
Copy link
Contributor

Why I did it

Finding running containers through "docker ps" breaks when kubernetes deploys container, as the names are mangled.

How I did it

The data is is available from FEATURE table, which takes care of kubernetes deployment too.

How to verify it

Deploy a feature via kubernetes and don't expect error from container_check.

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012

Description for the changelog

A picture of a cute animal (not mandatory but encouraged)

…ta from "docker ps"

2) Use python-docker for always-enabled
@isabelmsft
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

1 similar comment
@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

See if it helps with test_monit_status.py failure.
…upport.

Hence resort to dockers, if this table is not available.
isabelmsft
isabelmsft previously approved these changes May 5, 2021
yozhao101
yozhao101 previously approved these changes May 6, 2021
yozhao101
yozhao101 previously approved these changes May 6, 2021
@renukamanavalan renukamanavalan merged commit 7a575b3 into sonic-net:master May 7, 2021
daall pushed a commit that referenced this pull request May 10, 2021
Why I did it
Finding running containers through "docker ps" breaks when kubernetes deploys container, as the names are mangled.

How I did it
The data is is available from FEATURE table, which takes care of kubernetes deployment too.

How to verify it
Deploy a feature via kubernetes and don't expect error from container_check.
raphaelt-nvidia pushed a commit to raphaelt-nvidia/sonic-buildimage that referenced this pull request May 23, 2021
…c-net#7474)

Why I did it
Finding running containers through "docker ps" breaks when kubernetes deploys container, as the names are mangled.

How I did it
The data is is available from FEATURE table, which takes care of kubernetes deployment too.

How to verify it
Deploy a feature via kubernetes and don't expect error from container_check.
@renukamanavalan renukamanavalan deleted the ctr_check branch July 19, 2021 16:57
carl-nokia pushed a commit to carl-nokia/sonic-buildimage that referenced this pull request Aug 7, 2021
…c-net#7474)

Why I did it
Finding running containers through "docker ps" breaks when kubernetes deploys container, as the names are mangled.

How I did it
The data is is available from FEATURE table, which takes care of kubernetes deployment too.

How to verify it
Deploy a feature via kubernetes and don't expect error from container_check.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants