Open ykulazhenkov opened 3 weeks ago
Thanks for your PR, To run vendors CIs, Maintainers can use one of:
/test-all
: To run all tests for all vendors./test-e2e-all
: To run all E2E tests for all vendors./test-e2e-nvidia-all
: To run all E2E tests for NVIDIA vendor.
To skip the vendors CIs, Maintainers can use one of:
/skip-all
: To skip all tests for all vendors./skip-e2e-all
: To skip all E2E tests for all vendors./skip-e2e-nvidia-all
: To skip all E2E tests for NVIDIA vendor.
Best regards.Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | ||
---|---|---|---|---|---|
api/v1/helper.go | 14 | 23 | 60.87% | ||
controllers/sriovnetworknodepolicy_controller.go | 33 | 47 | 70.21% | ||
<!-- | Total: | 47 | 70 | 67.14% | --> |
Totals | |
---|---|
Change from base Build 11576125023: | 0.2% |
Covered Lines: | 6708 |
Relevant Lines: | 14863 |
CI failure is not related to the change. The same failure occurs on the PR with dummy changes https://github.com/k8snetworkplumbingwg/sriov-network-operator/pull/800
@e0ne @adrianchiris I addressed your comments. I also changed behavior a bit to completely avoid any delay in case if STALE_NODE_STATE_CLEANUP_DELAY_MINUTES
env is explicitly set to 0
Update controller logic to handle stale SriovNetworkNodeState CRs with delay
STALE_NODE_STATE_CLEANUP_DELAY_MINUTES
environment variable to configure the required delay in minutes (default is 30 minutes).This functionality especially useful when the OFED container is in use. As the OFED driver loads on the host, the sriov-config-daemon is removed from this node (achieved using configDaemon nodeselector). Since loading the driver can take a considerable amount of time, we want to ensure that the SriovNetworkNodeState is not lost during this process.