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
{{ message }}
This repository was archived by the owner on Aug 26, 2022. It is now read-only.
* Fix timeout (#663)
* Bug fix for the NodeSelector handler. (#664)
+ Some traces fixed in the networking ts.
* Diagnostic mode fix: close debug oc sessions before removing node lab… (#666)
* Diagnostic mode fix: close debug oc sessions before removing node labels.
This commit tries to fix the crash that happens when running the
container in diagnostic mode: race condition when the program finishes,
as the oc debug session were not closed before the labels are being
removed from the nodes.
* Revert "Fix timeout (#663)"
This reverts commit 8710512.
Co-authored-by: Salaheddine Hamadi <[email protected]>
* Timeout for debug pods increased to 5mins. (#669)
+ Retry interval also increased to 5 secs.
* Container testing log level set to trace. (#665)
Co-authored-by: Brandon Palm <[email protected]>
* lifecycle's terminationGracePeriod TC removed. (#667)
Due to the issues on both the original and current implementation,
the terminationGracePeriod TC will be removed.
A new and improved version of this TC should be done, checking that
after the configured (or defaulted) value, the pods were removed without
any error code.
Co-authored-by: Brandon Palm <[email protected]>
* Solution for issue on Nokia (#671)
* Solution for issue on Nokia
* Fixed the error
Co-authored-by: Your Name <[email protected]>
* Update Go to 1.17.9 (#668)
* Fix missed version changes (#670)
Co-authored-by: edcdavid <[email protected]>
Co-authored-by: Gonzalo Reyero Ferreras <[email protected]>
Co-authored-by: Salaheddine Hamadi <[email protected]>
Co-authored-by: Shimrit Peretz <[email protected]>
Co-authored-by: Your Name <[email protected]>
Suggested Remediation|In most cases, Pod's should not specify their host Nodes through nodeSelector or nodeAffinity. However, there are cases in which CNFs require specialized hardware specific to a particular class of Node. As such, this test is purely informative, and will not prevent a CNF from being certified. However, one should have an appropriate justification as to why nodeSelector and/or nodeAffinity is utilized by a CNF.
223
223
Best Practice Reference|[CNF Best Practice V1.2](https://connect.redhat.com/sites/default/files/2021-03/Cloud%20Native%20Network%20Function%20Requirements.pdf) Section 6.2
224
-
#### pod-termination-grace-period
225
-
226
-
Property|Description
227
-
---|---
228
-
Test Case Name|pod-termination-grace-period
229
-
Test Case Label|lifecycle-pod-termination-grace-period
Description|http://test-network-function.com/testcases/lifecycle/pod-termination-grace-period tests whether the terminationGracePeriod is CNF-specific, or if the default (30s) is utilized. This test is informative, and will not affect CNF Certification. In many cases, the default terminationGracePeriod is perfectly acceptable for a CNF.
233
-
Result Type|informative
234
-
Suggested Remediation|Choose a terminationGracePeriod that is appropriate for your given CNF. If the default (30s) is appropriate, then feel free to ignore this informative message. This test is meant to raise awareness around how Pods are terminated, and to suggest that a CNF is configured based on its requirements. In addition to a terminationGracePeriod, consider utilizing a termination hook in the case that your application requires special shutdown instructions.
235
-
Best Practice Reference|[CNF Best Practice V1.2](https://connect.redhat.com/sites/default/files/2021-03/Cloud%20Native%20Network%20Function%20Requirements.pdf) Section 6.2
0 commit comments