[Release 0.97] bump multus-dynamic-networks v0.3.6

[RamLavi]

What this PR does / why we need it:
This PR is a manual bump of multus-dynamic-networks to v0.3.6

Special notes for your reviewer:

Release note:

NONE

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[RamLavi]

/retest

[oshoval]

Thanks

[oshoval]

Hi @ashokpariya0
can be related to multi arch ?
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_cluster-network-addons-operator/1983/pull-cluster-network-addons-operator-unit-test-release-0.97/1879450504979812352#1:build-log.txt%3A5461
exec container process /bin/sh: Exec format error

[ashokpariya0]

Hi @ashokpariya0 can be related to multi arch ? https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_cluster-network-addons-operator/1983/pull-cluster-network-addons-operator-unit-test-release-0.97/1879450504979812352#1:build-log.txt%3A5461 exec container process /bin/sh: Exec format error

let me check.

[ashokpariya0]

Hi @ashokpariya0 can be related to multi arch ? https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_cluster-network-addons-operator/1983/pull-cluster-network-addons-operator-unit-test-release-0.97/1879450504979812352#1:build-log.txt%3A5461 exec container process /bin/sh: Exec format error

let me check.

The command CNAO_VERSION=99.0.0 ./hack/components/bump-linux-bridge.sh is failing during the creation of the multi-architecture image.

The issue is unclear, especially since all previous PRs worked fine after the multi-architecture change for the linux-bridge, and even the last PR passed the unit tests successfully. so not sure why it started failing now, It seems the problem might be related to the node where the build is occurring. Specifically, the node could be running an older version of Podman, which may not support multi-architecture builds, causing the failure ???

may be to unblock we remove platform=all for linux-bridge, we already have multi-arch image so should be okay??

[oshoval]

lets first indeed unblock please, we don't need multi arch on release 0.97
can you do it please?

maybe it was forked before all the changes were merged ?
next we can debug it on main, if it happens

Thanks

[ashokpariya0]

Kindly rebase the PR.

[oshoval]

/retest

prow auto rebase
thanks

[oshoval]

/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: oshoval

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [oshoval]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubevirt-bot]

@RamLavi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-e2e-cnao-lifecycle-k8s-release-0.97	0182acd	link	unknown	/test pull-e2e-cnao-lifecycle-k8s-release-0.97
pull-e2e-cnao-workflow-k8s-release-0.97	0182acd	link	unknown	/test pull-e2e-cnao-workflow-k8s-release-0.97

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[oshoval]

i wonder if this was just one timer flake or repeats
#1983 (comment)