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

Lingering container instances are sometimes left on the system #902

Open
wkz opened this issue Jan 22, 2025 · 1 comment
Open

Lingering container instances are sometimes left on the system #902

wkz opened this issue Jan 22, 2025 · 1 comment
Assignees
Labels
bug Something isn't working cn:styx
Milestone

Comments

@wkz
Copy link
Contributor

wkz commented Jan 22, 2025

Current Behavior

In during regression testing, a few tests failed because yanger did not handle the containers that were created but not running. That issue will be fixed separately, but it also prompted this issue: Namely:

Sometimes, even though no containers are configured on the system, created instances (presumably from some earlier test run) still remain in the system.

Here we see that confd reports no containers being configured, while podman lists three created instances:

root@C:~$ sysrepocfg -f json -X -d running -m infix-containers
{

}
root@C:~$ podman ps --all
CONTAINER ID  IMAGE                                                COMMAND               CREATED       STATUS      PORTS                  NAMES
584a280b9070  localhost/curios-nftables-oci-arm64-v24.11.0:latest  /usr/sbin/nft-hel...  17 hours ago  Created                            firewall
266b16ae8b0d  localhost/curios-httpd-oci-arm64-v24.11.0:latest     /usr/sbin/httpd -...  17 hours ago  Created     0.0.0.0:36959->91/tcp  container-A
cc33eb4b50a2  localhost/curios-httpd-oci-arm64-v24.11.0:latest     /usr/sbin/httpd -...  17 hours ago  Created                            container-B

Expected Behavior

When removing all containers from running-config, there should be no lingering created instances in the system.

Steps To Reproduce

No response

Additional information

No response

@wkz wkz added bug Something isn't working triage Pending investigation & classification (CCB) labels Jan 22, 2025
wkz added a commit that referenced this issue Jan 22, 2025
Due to #902 (which has not been root caused at this time), podman may
indicate the existance of an interface that yanger is not able to
locate in any namespace. Therefore, make sure that we verify that the
interface was actually found before trying to create the operational
data for it.
@troglobit troglobit added this to the Infix v25.02 milestone Jan 23, 2025
@troglobit troglobit added cn:styx and removed triage Pending investigation & classification (CCB) labels Jan 23, 2025
@troglobit troglobit modified the milestones: Infix v25.02, Infix v25.03 Jan 30, 2025
@troglobit troglobit self-assigned this Feb 4, 2025
@troglobit troglobit moved this to In progress in Infix & C:o Feb 4, 2025
@troglobit
Copy link
Contributor

troglobit commented Feb 7, 2025

  • Related to Container reconfiguration is broken #930
  • Relocate container cleanup from sysrepo plugin to Finit post: script
  • Verify volumes are unaffected when stopping and restarting a container, e.g., for upgrade
  • Update documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cn:styx
Projects
Status: In progress
Development

No branches or pull requests

2 participants