OCPBUGS-2325: Add E2E test cases for ingress

Signed-off-by: Martin Kennelly<EMAIL_ADDRESS>/cc @msherif1234
More to come but this is a start.

mkennell@mkennell ~/repos/ingress-node-firewall (some_e2es)
$make test-e2e
which: no operator-sdk in (/home/mkennell/.cargo/bin:/home/mkennell/.local/bin:/home/mkennell/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/usr/local/go/bin:/usr/local/go/bin:/home/mkennell/go/bin)
/home/mkennell/repos/ingress-node-firewall/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..."
 output:crd:artifacts:config=config/crd/bases
cp bundle/manifests/* manifests/stable
rm -rf /tmp/test_validation_logs/
mkdir -p /tmp/test_validation_logs/
go test --tags=validationtests -v ./test/e2e/validation -ginkgo.v -junit /tmp/test_validation_logs/ -report /tmp/test_validation_logs/
=== RUN   TestValidation
Running Suite: Ingress Node Firewall Operator Validation Suite
==============================================================
Random Seed:<PHONE_NUMBER>
Will run 4 of 4 specs

IngressNodeFirewall IngressNodeFirewall
  should have the IngressNodeFirewall Operator deployment in running state
  /home/mkennell/repos/ingress-node-firewall/test/e2e/validation/tests/validation.go:30
•
------------------------------
IngressNodeFirewall IngressNodeFirewall
  should have the IngressNodeFirewallConfig CRD available in the cluster
  /home/mkennell/repos/ingress-node-firewall/test/e2e/validation/tests/validation.go:52
•
------------------------------
IngressNodeFirewall IngressNodeFirewall
  should have the IngressNodeFirewall CRD available in the cluster
  /home/mkennell/repos/ingress-node-firewall/test/e2e/validation/tests/validation.go:58
•
------------------------------
IngressNodeFirewall IngressNodeFirewall
  should have the IngressNodeFirewallNodeState CRD available in the cluster
  /home/mkennell/repos/ingress-node-firewall/test/e2e/validation/tests/validation.go:64
•
JUnit report was created: /tmp/test_validation_logs/validation_junit.xml

Ran 4 of 4 Specs in 0.023 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped

You're using deprecated Ginkgo functionality:
=============================================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
  - For instructions on using the Release Candidate visit https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta
  - To comment, chime in at https://github.com/onsi/ginkgo/issues/711

  You are using a custom reporter.  Support for custom reporters will likely be removed in V2.  Most users were using them to generate junit or teamcity reports and this functionality will be merged into the core reporter.  In addition, Ginkgo 2.0 will support emitting a JSON-formatted report that users can then manipulate to generate custom reports.

  If this change will be impactful to you please leave a comment on https://github.com/onsi/ginkgo/issues/711
  Learn more at: https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#removed-custom-reporters

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=1.16.5

--- PASS: TestValidation (0.03s)
PASS
ok  	github.com/openshift/ingress-node-firewall/test/e2e/validation	0.063s
rm -rf /tmp/test_e2e_logs/
mkdir -p /tmp/test_e2e_logs/
go test --tags=e2etests -v ./test/e2e/functional -ginkgo.v -junit /tmp/test_e2e_logs/ -report /tmp/test_e2e_logs/
=== RUN   TestE2E
Running Suite: Ingress Node Firewall Operator E2E Suite
=======================================================
Random Seed:<PHONE_NUMBER>
Will run 34 of 34 specs

Ingress Node Firewall Platform Check
  should be either Kubernetes or OpenShift platform
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:68
•
------------------------------
Ingress Node Firewall IngressNodeFirewall deploy
  should run Ingress node firewall DaemonSet
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:107
STEP: checking Ingress node firewall daemonset is in running state
STEP: checking Ingress Node Firewall Config CR status is set

• [SLOW TEST:8.044 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  IngressNodeFirewall deploy
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:76
    should run Ingress node firewall DaemonSet
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:107
------------------------------
Ingress Node Firewall IngressNodeFirewall deploy
  should run Ingress node firewall apply rules and check the actions
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:157
STEP: get nodes IP addresses with matching labels and ping their IPs
STEP: creating ingress node firewall rules
STEP: checking Ingress node firewall rules resource is created
STEP: checking ingress node firewall nodeState resource is created
STEP: checking Ingress node firewall rules deny ping packets
STEP: checking ingress node firewall events are generated
STEP: checking Ingress node firewall rules resource is deleted
STEP: checking Ingress node firewall nodeState resource is deleted when firewall rules object is deleted

• [SLOW TEST:52.117 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  IngressNodeFirewall deploy
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:76
    should run Ingress node firewall apply rules and check the actions
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:157
------------------------------
Ingress Node Firewall [TCP] Rules
  block a single port
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:425

• [SLOW TEST:17.337 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [TCP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:368
    block a single port
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:425
------------------------------
Ingress Node Firewall [TCP] Rules
  update to remove the blocked port
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:436

• [SLOW TEST:16.362 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [TCP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:368
    update to remove the blocked port
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:436
------------------------------
Ingress Node Firewall [TCP] Rules
  update to block target port in a port range
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:460

• [SLOW TEST:16.361 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [TCP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:368
    update to block target port in a port range
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:460
------------------------------
Ingress Node Firewall [TCP] Rules
  update to block port in non-first order rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:484

• [SLOW TEST:16.353 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [TCP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:368
    update to block port in non-first order rule
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:484
------------------------------
Ingress Node Firewall [TCP] Rules
  block new target with update to sourceCIDRs
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:512

• [SLOW TEST:21.382 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [TCP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:368
    block new target with update to sourceCIDRs
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:512
------------------------------
Ingress Node Firewall [TCP] Rules
  multiple ingress will block new target
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:541

• [SLOW TEST:24.474 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [TCP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:368
    multiple ingress will block new target
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:541
------------------------------
Ingress Node Firewall [TCP] Rules
  multiple Ingress Node Firewall objects with one ingress that contains identical sourceCIDRs will merge and block
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:582

• [SLOW TEST:17.348 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [TCP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:368
    multiple Ingress Node Firewall objects with one ingress that contains identical sourceCIDRs will merge and block
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:582
------------------------------
Ingress Node Firewall [UDP] Rules
  block a single port
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:661

• [SLOW TEST:16.348 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [UDP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:604
    block a single port
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:661
------------------------------
Ingress Node Firewall [UDP] Rules
  update to remove the blocked port
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:672

• [SLOW TEST:16.339 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [UDP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:604
    update to remove the blocked port
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:672
------------------------------
Ingress Node Firewall [UDP] Rules
  update to block target port in a port range
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:696

• [SLOW TEST:16.310 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [UDP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:604
    update to block target port in a port range
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:696
------------------------------
Ingress Node Firewall [UDP] Rules
  update to block port in non-first order rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:720

• [SLOW TEST:17.334 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [UDP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:604
    update to block port in non-first order rule
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:720
------------------------------
Ingress Node Firewall [UDP] Rules
  block new target with update to sourceCIDRs
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:748

• [SLOW TEST:20.402 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [UDP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:604
    block new target with update to sourceCIDRs
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:748
------------------------------
Ingress Node Firewall [UDP] Rules
  multiple ingress will block new target
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:777

• [SLOW TEST:28.459 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [UDP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:604
    multiple ingress will block new target
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:777
------------------------------
Ingress Node Firewall [UDP] Rules
  multiple Ingress Node Firewall objects with one ingress that contains identical sourceCIDRs will merge and block
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:818

• [SLOW TEST:16.349 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [UDP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:604
    multiple Ingress Node Firewall objects with one ingress that contains identical sourceCIDRs will merge and block
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:818
------------------------------
Ingress Node Firewall [SCTP] Rules
  block a single port
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:902

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [SCTP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:839
    block a single port [BeforeEach]
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:902

    SCTP tests are disabled. Enable by setting environment variable 'ENABLE_SCTP_TESTS=true'. Ensure kernel modules are enabled.

    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:858
------------------------------
Ingress Node Firewall [SCTP] Rules
  update to remove the blocked port
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:916

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [SCTP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:839
    update to remove the blocked port [BeforeEach]
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:916

    SCTP tests are disabled. Enable by setting environment variable 'ENABLE_SCTP_TESTS=true'. Ensure kernel modules are enabled.

    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:858
------------------------------
Ingress Node Firewall [SCTP] Rules
  update to block target port in a port range
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:943

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [SCTP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:839
    update to block target port in a port range [BeforeEach]
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:943

    SCTP tests are disabled. Enable by setting environment variable 'ENABLE_SCTP_TESTS=true'. Ensure kernel modules are enabled.

    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:858
------------------------------
Ingress Node Firewall [SCTP] Rules
  update to block port in non-first order rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:970

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [SCTP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:839
    update to block port in non-first order rule [BeforeEach]
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:970

    SCTP tests are disabled. Enable by setting environment variable 'ENABLE_SCTP_TESTS=true'. Ensure kernel modules are enabled.

    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:858
------------------------------
Ingress Node Firewall [SCTP] Rules
  block new target with update to sourceCIDRs
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1001

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [SCTP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:839
    block new target with update to sourceCIDRs [BeforeEach]
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1001

    SCTP tests are disabled. Enable by setting environment variable 'ENABLE_SCTP_TESTS=true'. Ensure kernel modules are enabled.

    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:858
------------------------------
Ingress Node Firewall [SCTP] Rules
  multiple ingress will block new target
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1033

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [SCTP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:839
    multiple ingress will block new target [BeforeEach]
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1033

    SCTP tests are disabled. Enable by setting environment variable 'ENABLE_SCTP_TESTS=true'. Ensure kernel modules are enabled.

    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:858
------------------------------
Ingress Node Firewall [SCTP] Rules
  multiple Ingress Node Firewall objects with one ingress that contains identical sourceCIDRs will merge and block
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1077

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [SCTP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:839
    multiple Ingress Node Firewall objects with one ingress that contains identical sourceCIDRs will merge and block [BeforeEach]
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1077

    SCTP tests are disabled. Enable by setting environment variable 'ENABLE_SCTP_TESTS=true'. Ensure kernel modules are enabled.

    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:858
------------------------------
Ingress Node Firewall [ICMP] Rules
  block echo replies
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1154

• [SLOW TEST:16.355 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [ICMP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1101
    block echo replies
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1154
------------------------------
Ingress Node Firewall [ICMP] Rules
  allows connectivity when updated to allow echo replies
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1164

• [SLOW TEST:16.333 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  [ICMP] Rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1101
    allows connectivity when updated to allow echo replies
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1164
------------------------------
Ingress Node Firewall Statistics
  should expose at least one endpoint via a daemon metrics service
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1219

• [SLOW TEST:5.033 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  Statistics
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1188
    should expose at least one endpoint via a daemon metrics service
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1219
------------------------------
Ingress Node Firewall Statistics
  should expose daemon metrics
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1246

• [SLOW TEST:40.222 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  Statistics
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1188
    should expose daemon metrics
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1246
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall TCP rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1388
•
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall UDP rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1399
•
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall ICMPV4 rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1410
•
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall ICMPV6 rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1421
•
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall SCTP rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1432
•
------------------------------
Ingress Node Firewall Webhook
  should block any rules which conflict with failsafe rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1443

• [SLOW TEST:5.637 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:65
  Webhook
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1358
    should block any rules which conflict with failsafe rules
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1443
------------------------------

JUnit report was created: /tmp/test_e2e_logs/e2e_junit.xml

Ran 27 of 34 Specs in 425.471 seconds
SUCCESS! -- 27 Passed | 0 Failed | 0 Pending | 7 Skipped

You're using deprecated Ginkgo functionality:
=============================================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
  - For instructions on using the Release Candidate visit https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta
  - To comment, chime in at https://github.com/onsi/ginkgo/issues/711

  You are using a custom reporter.  Support for custom reporters will likely be removed in V2.  Most users were using them to generate junit or teamcity reports and this functionality will be merged into the core reporter.  In addition, Ginkgo 2.0 will support emitting a JSON-formatted report that users can then manipulate to generate custom reports.

  If this change will be impactful to you please leave a comment on https://github.com/onsi/ginkgo/issues/711
  Learn more at: https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#removed-custom-reporters

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=1.16.5

--- PASS: TestE2E (425.49s)
PASS
ok  	github.com/openshift/ingress-node-firewall/test/e2e/functional	425.519s

Test output:
$OO_INSTALL_NAMESPACE=openshift-ingress-node-firewall NODE_INTERFACE=genev_sys_6081 make test-e2e
which: no operator-sdk in (/home/mkennell/.cargo/bin:/home/mkennell/.local/bin:/home/mkennell/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/usr/local/go/bin:/usr/local/go/bin:/home/mkennell/go/bin)
/home/mkennell/repos/ingress-node-firewall/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..."
 output:crd:artifacts:config=config/crd/bases
cp bundle/manifests/* manifests/stable
rm -rf /tmp/test_validation_logs/
mkdir -p /tmp/test_validation_logs/
go test --tags=validationtests -v ./test/e2e/validation -ginkgo.v -junit /tmp/test_validation_logs/ -report /tmp/test_validation_logs/
=== RUN   TestValidation
Running Suite: Ingress Node Firewall Operator Validation Suite
==============================================================
Random Seed:<PHONE_NUMBER>
Will run 4 of 4 specs

IngressNodeFirewall IngressNodeFirewall
  should have the IngressNodeFirewall Operator deployment in running state
  /home/mkennell/repos/ingress-node-firewall/test/e2e/validation/tests/validation.go:30
•
------------------------------
IngressNodeFirewall IngressNodeFirewall
  should have the IngressNodeFirewallConfig CRD available in the cluster
  /home/mkennell/repos/ingress-node-firewall/test/e2e/validation/tests/validation.go:52
•
------------------------------
IngressNodeFirewall IngressNodeFirewall
  should have the IngressNodeFirewall CRD available in the cluster
  /home/mkennell/repos/ingress-node-firewall/test/e2e/validation/tests/validation.go:58
•
------------------------------
IngressNodeFirewall IngressNodeFirewall
  should have the IngressNodeFirewallNodeState CRD available in the cluster
  /home/mkennell/repos/ingress-node-firewall/test/e2e/validation/tests/validation.go:64
•
JUnit report was created: /tmp/test_validation_logs/validation_junit.xml

Ran 4 of 4 Specs in 0.904 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped

You're using deprecated Ginkgo functionality:
=============================================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
  - For instructions on using the Release Candidate visit https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta
  - To comment, chime in at https://github.com/onsi/ginkgo/issues/711

  You are using a custom reporter.  Support for custom reporters will likely be removed in V2.  Most users were using them to generate junit or teamcity reports and this functionality will be merged into the core reporter.  In addition, Ginkgo 2.0 will support emitting a JSON-formatted report that users can then manipulate to generate custom reports.

  If this change will be impactful to you please leave a comment on https://github.com/onsi/ginkgo/issues/711
  Learn more at: https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#removed-custom-reporters

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=1.16.5

--- PASS: TestValidation (1.39s)
PASS
ok  	github.com/openshift/ingress-node-firewall/test/e2e/validation	1.908s
rm -rf /tmp/test_e2e_logs/
mkdir -p /tmp/test_e2e_logs/
go test -timeout 20m --tags=e2etests -v ./test/e2e/functional -ginkgo.v -junit /tmp/test_e2e_logs/ -report /tmp/test_e2e_logs/
2022/10/12 19:56:43 SCTP tests are disabled
=== RUN   TestE2E
Running Suite: Ingress Node Firewall Operator E2E Suite
=======================================================
Random Seed:<PHONE_NUMBER>
Will run 17 of 17 specs

Ingress Node Firewall Ingress
  block a port with a single rule defining the targets port
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6

• [SLOW TEST:23.967 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:120
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:136
    block a port with a single rule defining the targets port
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
------------------------------
Ingress Node Firewall Ingress
  block a port using a range when multiple source CIDRs exist
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-two" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-two" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to pod "e2e-inf-server-one" for IPV4 and IPV6

• [SLOW TEST:33.510 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:120
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:136
    block a port using a range when multiple source CIDRs exist
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
------------------------------
Ingress Node Firewall Ingress
  block multiple ports
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-two" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-two" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to pod "e2e-inf-server-two" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to pod "e2e-inf-server-two" for IPV4 and IPV6

• [SLOW TEST:32.430 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:120
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:136
    block multiple ports
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
------------------------------
Ingress Node Firewall Ingress
  block port when rules for a source CIDR are located in multiple IngressNodeFirewall objects
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6

• [SLOW TEST:20.306 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:120
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:136
    block port when rules for a source CIDR are located in multiple IngressNodeFirewall objects
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
------------------------------
Ingress Node Firewall Ingress
  merges transport protocol rules when source CIDRs overlap in multiple IngressNodeFirewalls and the count of source CIDRs for each policy is different
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-two" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-two" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to pod "e2e-inf-server-one" for IPV4 and IPV6

• [SLOW TEST:34.634 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:120
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:136
    merges transport protocol rules when source CIDRs overlap in multiple IngressNodeFirewalls and the count of source CIDRs for each policy is different
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
------------------------------
Ingress Node Firewall Ingress
  merges multiple IngressNodeFirewalls which contain multiple ingress entries with protocol rules for all protocols
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm ICMP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm ICMPv6 protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-two" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-two" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm ICMP protocol connectivity from test pod "e2e-inf-client-two" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm ICMPv6 protocol connectivity from test pod "e2e-inf-client-two" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-three" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-three" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm ICMP protocol connectivity from test pod "e2e-inf-client-three" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm ICMPv6 protocol connectivity from test pod "e2e-inf-client-three" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-four" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-four" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm ICMP protocol connectivity from test pod "e2e-inf-client-four" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm ICMPv6 protocol connectivity from test pod "e2e-inf-client-four" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-two" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-two" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-three" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-three" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-three" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-three" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-four" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-four" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-four" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-four" to pod "e2e-inf-server-one" for IPV4 and IPV6

• [SLOW TEST:149.874 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:120
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:136
    merges multiple IngressNodeFirewalls which contain multiple ingress entries with protocol rules for all protocols
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
------------------------------
Ingress Node Firewall Ingress
  block port when rules for a source CIDR are located in multiple IngressNodeFirewall objects
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6

• [SLOW TEST:26.303 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:120
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:136
    block port when rules for a source CIDR are located in multiple IngressNodeFirewall objects
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
------------------------------
Ingress Node Firewall Ingress
  merges transport protocol rules when source CIDRs overlap in multiple IngressNodeFirewalls but the number of source CIDRs in each policy is different
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm TCP protocol connectivity from test pod "e2e-inf-client-two" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm UDP protocol connectivity from test pod "e2e-inf-client-two" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to pod "e2e-inf-server-one" for IPV4 and IPV6

• [SLOW TEST:34.055 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:120
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:136
    merges transport protocol rules when source CIDRs overlap in multiple IngressNodeFirewalls but the number of source CIDRs in each policy is different
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
------------------------------
Ingress Node Firewall Ingress
  block ICMP echo request
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
STEP: Confirm ICMP protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm ICMPv6 protocol connectivity from test pod "e2e-inf-client-one" to pod "e2e-inf-server-one" before IngressNodeFirewall policy application for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6
STEP: Confirm IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-one" to pod "e2e-inf-server-one" for IPV4 and IPV6

• [SLOW TEST:31.426 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:120
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:136
    block ICMP echo request
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:753
------------------------------
Ingress Node Firewall Statistics
  should expose at least one endpoint via a daemon metrics service
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:950
•
------------------------------
Ingress Node Firewall Statistics
  should expose daemon metrics
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:977

• [SLOW TEST:45.901 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:120
  Statistics
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:920
    should expose daemon metrics
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:977
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall TCP rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1120
•
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall UDP rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1132
•
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall ICMPV4 rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1144
•
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall ICMPV6 rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1156
•
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall SCTP rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1168
•
------------------------------
Ingress Node Firewall Webhook
  should block any rules which conflict with failsafe rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1180
•
JUnit report was created: /tmp/test_e2e_logs/e2e_junit.xml

Ran 17 of 17 Specs in 436.941 seconds
SUCCESS! -- 17 Passed | 0 Failed | 0 Pending | 0 Skipped

You're using deprecated Ginkgo functionality:
=============================================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
  - For instructions on using the Release Candidate visit https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta
  - To comment, chime in at https://github.com/onsi/ginkgo/issues/711

  You are using a custom reporter.  Support for custom reporters will likely be removed in V2.  Most users were using them to generate junit or teamcity reports and this functionality will be merged into the core reporter.  In addition, Ginkgo 2.0 will support emitting a JSON-formatted report that users can then manipulate to generate custom reports.

  If this change will be impactful to you please leave a comment on https://github.com/onsi/ginkgo/issues/711
  Learn more at: https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#removed-custom-reporters

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=1.16.5

--- PASS: TestE2E (437.46s)
PASS
ok  	github.com/openshift/ingress-node-firewall/test/e2e/functional	437.976s

@msherif1234 When youre back, PTAL.

why we no longer check event logging for the deny rules ?

why we no longer check event logging for the deny rules ?

I didn't think it was the right way to test success or failure. I wanted to rely on a connection being allowed or denied and not what the XDP program was reporting via events.

why we no longer check event logging for the deny rules ?

I didn't think it was the right way to test success or failure. I wanted to rely on a connection being allowed or denied and not what the XDP program was reporting via events.

We need both making sure events is emitted is very important part of this feature

/Jira refresh

/jira refresh

/cherry-pick 4.12

Test output for run on OCP:
$ make test-e2e
which: no operator-sdk in (/home/mkennell/.cargo/bin:/home/mkennell/.local/bin:/home/mkennell/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/usr/local/go/bin:/usr/local/go/bin:/home/mkennell/go/bin)
/home/mkennell/repos/ingress-node-firewall/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..."
 output:crd:artifacts:config=config/crd/bases
cp bundle/manifests/* manifests/stable
rm -rf /tmp/test_validation_logs/
mkdir -p /tmp/test_validation_logs/
go test --tags=validationtests -v ./test/e2e/validation -ginkgo.v -junit /tmp/test_validation_logs/ -report /tmp/test_validation_logs/
=== RUN   TestValidation
Running Suite: Ingress Node Firewall Operator Validation Suite
==============================================================
Random Seed:<PHONE_NUMBER>
Will run 4 of 4 specs

IngressNodeFirewall IngressNodeFirewall
  should have the IngressNodeFirewall Operator deployment in running state
  /home/mkennell/repos/ingress-node-firewall/test/e2e/validation/tests/validation.go:33
•
------------------------------
IngressNodeFirewall IngressNodeFirewall
  should have the IngressNodeFirewallConfig CRD available in the cluster
  /home/mkennell/repos/ingress-node-firewall/test/e2e/validation/tests/validation.go:55
•
------------------------------
IngressNodeFirewall IngressNodeFirewall
  should have the IngressNodeFirewall CRD available in the cluster
  /home/mkennell/repos/ingress-node-firewall/test/e2e/validation/tests/validation.go:61
•
------------------------------
IngressNodeFirewall IngressNodeFirewall
  should have the IngressNodeFirewallNodeState CRD available in the cluster
  /home/mkennell/repos/ingress-node-firewall/test/e2e/validation/tests/validation.go:67
•
JUnit report was created: /tmp/test_validation_logs/validation_junit.xml

Ran 4 of 4 Specs in 1.333 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped

You're using deprecated Ginkgo functionality:
=============================================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
  - For instructions on using the Release Candidate visit https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta
  - To comment, chime in at https://github.com/onsi/ginkgo/issues/711

  You are using a custom reporter.  Support for custom reporters will likely be removed in V2.  Most users were using them to generate junit or teamcity reports and this functionality will be merged into the core reporter.  In addition, Ginkgo 2.0 will support emitting a JSON-formatted report that users can then manipulate to generate custom reports.

  If this change will be impactful to you please leave a comment on https://github.com/onsi/ginkgo/issues/711
  Learn more at: https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#removed-custom-reporters

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=1.16.5

--- PASS: TestValidation (1.89s)
PASS
ok  	github.com/openshift/ingress-node-firewall/test/e2e/validation	2.482s
rm -rf /tmp/test_e2e_logs/
mkdir -p /tmp/test_e2e_logs/
go test -timeout 20m --tags=e2etests -v ./test/e2e/functional -ginkgo.v -junit /tmp/test_e2e_logs/ -report /tmp/test_e2e_logs/
2022/10/18 11:56:14 SCTP tests are disabled
=== RUN   TestE2E
Running Suite: Ingress Node Firewall Operator E2E Suite
=======================================================
Random Seed:<PHONE_NUMBER>
Will run 17 of 17 specs

Ingress Node Firewall Ingress
  block a port with a single rule defining the destinations port
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created

• [SLOW TEST:23.659 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:107
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:123
    block a port with a single rule defining the destinations port
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
------------------------------
Ingress Node Firewall Ingress
  block a port using a range when multiple source CIDRs exist
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created

• [SLOW TEST:45.447 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:107
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:123
    block a port using a range when multiple source CIDRs exist
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
------------------------------
Ingress Node Firewall Ingress
  block multiple ports
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-two"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-two"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-two"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-two"
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-two"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-two"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-two"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-two"
STEP: [IPV6] Checking if drop events created

• [SLOW TEST:37.405 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:107
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:123
    block multiple ports
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
------------------------------
Ingress Node Firewall Ingress
  block port when rules for a source CIDR are located in multiple IngressNodeFirewall objects
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created

• [SLOW TEST:28.306 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:107
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:123
    block port when rules for a source CIDR are located in multiple IngressNodeFirewall objects
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
------------------------------
Ingress Node Firewall Ingress
  merges transport protocol rules when source CIDRs overlap in multiple IngressNodeFirewalls and the count of source CIDRs for each policy is different
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created

• [SLOW TEST:45.400 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:107
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:123
    merges transport protocol rules when source CIDRs overlap in multiple IngressNodeFirewalls and the count of source CIDRs for each policy is different
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
------------------------------
Ingress Node Firewall Ingress
  merges multiple IngressNodeFirewalls which contain multiple ingress entries with protocol rules for all protocols
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-three" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-three" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-three" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-three" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-three" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-three" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-four" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-four" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-four" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-four" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-four" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-four" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-three" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-three" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-three" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-three" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-three" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-three" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-four" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-four" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-four" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-four" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-four" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-four" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created

• [SLOW TEST:161.728 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:107
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:123
    merges multiple IngressNodeFirewalls which contain multiple ingress entries with protocol rules for all protocols
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
------------------------------
Ingress Node Firewall Ingress
  block port when rules for a source CIDR are located in multiple IngressNodeFirewall objects
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created

• [SLOW TEST:29.040 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:107
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:123
    block port when rules for a source CIDR are located in multiple IngressNodeFirewall objects
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
------------------------------
Ingress Node Firewall Ingress
  merges transport protocol rules when source CIDRs overlap in multiple IngressNodeFirewalls but the number of source CIDRs in each policy is different
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol TCP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol UDP from pod "e2e-inf-client-two" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created

• [SLOW TEST:36.956 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:107
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:123
    merges transport protocol rules when source CIDRs overlap in multiple IngressNodeFirewalls but the number of source CIDRs in each policy is different
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
------------------------------
Ingress Node Firewall Ingress
  block ICMP echo request
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
STEP: [IPV4] Confirm connectivity before IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Confirm connectivity before IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Confirm IngressNodeFirewall policy application for protocol ICMP from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV4] Checking if drop events created
STEP: [IPV6] Confirm IngressNodeFirewall policy application for protocol ICMPv6 from pod "e2e-inf-client-one" to destination pod "e2e-inf-server-one"
STEP: [IPV6] Checking if drop events created

• [SLOW TEST:39.085 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:107
  Ingress
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:123
    block ICMP echo request
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:742
------------------------------
Ingress Node Firewall Statistics
  should expose at least one endpoint via a daemon metrics service
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:964
•
------------------------------
Ingress Node Firewall Statistics
  should expose daemon metrics
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:991

• [SLOW TEST:40.981 seconds]
Ingress Node Firewall
/home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:107
  Statistics
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:934
    should expose daemon metrics
    /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:991
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall TCP rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1144
•
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall UDP rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1156
•
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall ICMPV4 rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1168
•
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall ICMPV6 rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1180
•
------------------------------
Ingress Node Firewall Webhook
  should allow valid ingressnodefirewall SCTP rule
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1192
•
------------------------------
Ingress Node Firewall Webhook
  should block any rules which conflict with failsafe rules
  /home/mkennell/repos/ingress-node-firewall/test/e2e/functional/tests/e2e.go:1204
•
JUnit report was created: /tmp/test_e2e_logs/e2e_junit.xml

Ran 17 of 17 Specs in 493.048 seconds
SUCCESS! -- 17 Passed | 0 Failed | 0 Pending | 0 Skipped

You're using deprecated Ginkgo functionality:
=============================================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
  - For instructions on using the Release Candidate visit https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta
  - To comment, chime in at https://github.com/onsi/ginkgo/issues/711

  You are using a custom reporter.  Support for custom reporters will likely be removed in V2.  Most users were using them to generate junit or teamcity reports and this functionality will be merged into the core reporter.  In addition, Ginkgo 2.0 will support emitting a JSON-formatted report that users can then manipulate to generate custom reports.

  If this change will be impactful to you please leave a comment on https://github.com/onsi/ginkgo/issues/711
  Learn more at: https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#removed-custom-reporters

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=1.16.5

--- PASS: TestE2E (493.71s)
PASS
ok  	github.com/openshift/ingress-node-firewall/test/e2e/functional	494.370s

/cherry-pick release-4.12

/lgtm
/approve


Implement persist command

As per https://redis.io/commands/persist and http://redis-py.readthedocs.io/en/latest/#redis.StrictRedis.persist.

@srikalyan could you please be so kind as to merge this and make a new release? Currently mockredispy is broken with rq, because it uses persist. Thank you!


grantlee: 5.1.0 -> 5.2.0

Motivation for this change
Regular update. Will be required for Qt 5.14.x.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Ran nix-review:
https://github.com/NixOS/nixpkgs/pull/84621
2 package marked as broken and skipped:
evilvte pinboard-notes-backup

1 package failed to build:
subsurface

51 package built:
akregator cutelyst digikam grantlee5 kaddressbook kdeApplications.akonadi-calendar kdeApplications.akonadi-contacts kdeApplications.akonadi-import-wizard kdeApplications.akonadiconsole kdeApplications.calendarsupport kdeApplications.eventviews kdeApplications.grantleetheme kdeApplications.incidenceeditor kdeApplications.kalarm kdeApplications.kalarmcal kdeApplications.kcalutils kdeApplications.kdepim-addons kdeApplications.kdepim-apps-libs kdeApplications.kdepim-runtime kdeApplications.kgpg kdeApplications.khelpcenter kdeApplications.kidentitymanagement kdeApplications.kleopatra kdeApplications.kmail kdeApplications.kmail-account-wizard kdeApplications.knotes kdeApplications.kontact kdeApplications.korganizer kdeApplications.kpimtextedit kdeApplications.ktnef kdeApplications.libgravatar kdeApplications.libkdepim kdeApplications.libkleo kdeApplications.libksieve kdeApplications.mailcommon kdeApplications.mailimporter kdeApplications.mbox-importer kdeApplications.messagelib kdeApplications.pim-data-exporter kdeApplications.pim-sieve-editor kdeApplications.pimcommon kdeApplications.rocs kdev-php kdev-python kdevelop kdevelop-unwrapped kmymoney skrooge trojita virtlyst zanshin

The subsuface build failure is not new, it fails with the same error on master.


DO NOT MERGE - Re-register comm targets when reopening nb or restarting kernel

For #10807
For #10798
@rchiodo Not planning on merging into this branch.
Will merge into Master, had to create a PR so I dont lose this also the work is done.

Closing in favor of https://github.com/microsoft/vscode-python/pull/10816


Error reported after configuring Postgresql connection

Use the master branch to deploy through code, and after configuring the Postgres connection information, the following error is reported:
Cannot read properties of undefined (reading 'current_schema')

Hi @luxingxiao, thanks for reporting this issue. Can you give me more information about your database? Are you using a normal Postgres database or a Doltgres database (with version control?) And does your database already have schema or is it empty?

Hi @luxingxiao, thanks for reporting this issue. Can you give me more information about your database? Are you using a normal Postgres database or a Doltgres database (with version control?) And does your database already have schema or is it empty?

Hi @tbantle22 ,  thanks for your reply。I am using a Doltgres database (with version control). My database schema is empty.

Ah okay, Doltgres is currently in development and is still missing some
features that will allow it to work with this workbench. We are actively
working on it and as soon as it’s ready I’ll let you know!
On Thu, Mar 28, 2024 at 18:08 路兴晓 @.***> wrote:

Hi @luxingxiao https://github.com/luxingxiao, thanks for reporting this
issue. Can you give me more information about your database? Are you using
a normal Postgres database or a Doltgres database (with version control?)
And does your database already have schema or is it empty?
Hi @tbantle22 https://github.com/tbantle22 , thanks for your reply。I am
using a Doltgres database (with version control). My database schema is
empty.
—
Reply to this email directly, view it on GitHub
https://github.com/dolthub/dolt-workbench/issues/143#issuecomment-2026421350,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHAUI6VCYLEBRPWPFZUVDZ3Y2S5I3AVCNFSM6AAAAABFMHQUZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRWGQZDCMZVGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@tbantle22 Thank you very much for your reply. The Dolt project is great and I will continue to pay attention.

If you're okay with MySQL the workbench does work with MySQL-flavored Dolt. But if not I will keep you updated on Doltgres support


RFID/IR support?

I've basically heard about this today and immediately found this, and am really interested in this, now I noticed that the NFC module used in this project also supports RFID, would this also be the case with the device itself or would a separate integration need to be written into the firmware? I also wanted to ask, since I've looked through the schematics, would it be possible to use 2 of the 6 unoccupied pins on the RP2040 to add an infrared diode and infrared photoresistor to add infrared capabilities?
An additional idea of mine would be to route some power output pins, ground pins and the remaining 4 GPIO pins outside the board for a sort of expansion header for some stuff the end user might want to make, would these ideas be possible in theory?

Hi, there is no official FW for the Hackbat, it is a HW platform for experiment with your own FW using the Arduino IDE or the RP2040 IDE so, if the NFC board supports the protocol you need you can use it without problem.
Regarding the IR, yes, you can, but both UART ports are already in use for the ESP programming and the external USB-UART converter. Maybe the best would be eliminate the external USB-UART connector and use it for the IR.
And of course, you can add an external port with the unused pins.
Thanks!

noted, I'll see what I myself can do about adding IR to the board, having all of the schematics provided, plus the KiCAD files will help, thanks!


presets panel refinements

resolve:

style as per design #843
fix issue where dragging over a panel was closing the wrong panel
#884
fix issue where switching tabs would result in an empty list #944
fix keyboard scrolling in search results #1003
fix Y offset in dragging presets&nodes out #1004
fix paste offset #1002

lgtm


Adding hvac_mode operation list from konradb3's.

The code is not mine. It's taken from konradb3's source. This way the Thermostat Card now shows the "Follow Schedule" button near "Heat" and "Off" buttons.

Thank you for your contribution. Fixed this in pyit600.

Thank you for your contribution. Fixed this in pyit600.


Paging broken

Might not be. This HTTP header Link thing is weird.

Check out https://github.com/kylef/WebLinking.swift, that might help.

Heh, small lib. I think I'm doing exactly the same thing basically, its just that GH sometimes does and does-not send the Link header...


R fix metric shape

Reshape label and predictions for regression use cases to handle more general cases where there are multiple output. Fix for #12431

@ankkhedia @anirudhacharya Looping you guys in to review this!
@jeremiedb Thank you for your fixing the issue!
@mxnet-label-bot [pr-awaiting-review]


[FEATURE] SocialRepo Logo Variants for different sizes

Description
As part of improving the visual consistency and scalability of the SocialRepo extension, we need to create logo variants in various sizes to ensure optimal display across different contexts and screen resolutions.
You only need to create different size logos for logo.png
Tasks
Create logo variants in the following sizes:

[ ] 16x16 pixels
[ ] 32x32 pixels
[ ] 48x48 pixels
[ ] 128x128 pixels

After creating the logos, add them in assets/logos folder.
Resources
You can resize logo from this website.
https://imresizer.com/download
P.S: Make sure the logo should be transparent.

Hi @Param302
I can do this. Can you assign me this issue

Hey @Param302  , I can do this! If the issue is not resolved, can you assign me this issue?

Hi @Param302 I can do this. Can you assign me this issue

Hey @fabiomughilan ,
I saw you've already contributed and completed this issue, I am merging your PR to main branch.
Thanks for contributing!
Although from next time, please wait for the maintainers to assign you the issue before doing the PR, as it will help us (the maintainers) keep the track.

Hey @Param302 , I can do this! If the issue is not resolved, can you assign me this issue?

Hey this issue is completed, you can work on other issues listed here.


Fix isue #3506 for IE11 and Edge support

Signed-off-by: Ru Chern Chong<EMAIL_ADDRESS>

Thanks!

@Fyrd Sorry about that day.


Add createProvider Documentation.

Fixes https://github.com/reactjs/react-redux/issues/738
Open to Grammar, Capitalization & Style changes. Also can squash, rebase etc.

LGTM. Thanks!