You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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, whilepodman
lists three created instances: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
The text was updated successfully, but these errors were encountered: