Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix strongSwan configuration file with strongSwan >= version 5.7.0 #1191

Merged
merged 1 commit into from Sep 2, 2020

Conversation

jianjuns
Copy link
Contributor

@jianjuns jianjuns commented Sep 1, 2020

Starting from version 5.7.0, strongSwan no more supports to specify a
configuration paramter with the path delimited by dots in a
configuration file. This change breaks ovs-ipsec-monitor which writes
strongSwan configuration parameters with the dotted paths.
This commit applies an ovs-monitor-ipsec patch to fix the issue, as a
workaround before the patch is merged to OVS upstream.

@antrea-bot
Copy link
Collaborator

Thanks for your PR.
Unit tests and code linters are run automatically every time the PR is updated.
E2e, conformance and network policy tests can only be triggered by a member of the vmware-tanzu organization. Regular contributors to the project should join the org.

The following commands are available:

  • /test-e2e: to trigger e2e tests.
  • /skip-e2e: to skip e2e tests.
  • /test-conformance: to trigger conformance tests.
  • /skip-conformance: to skip conformance tests.
  • /test-whole-conformance: to trigger all conformance tests on linux.
  • /skip-whole-conformance: to skip all conformance tests on linux.
  • /test-networkpolicy: to trigger networkpolicy tests.
  • /skip-networkpolicy: to skip networkpolicy tests.
  • /test-windows-conformance: to trigger windows conformance tests.
  • /skip-windows-conformance: to skip windows conformance tests.
  • /test-windows-networkpolicy: to trigger windows networkpolicy tests.
  • /skip-windows-networkpolicy: to skip windows networkpolicy tests.
  • /test-hw-offload: to trigger ovs hardware offload test.
  • /skip-hw-offload: to skip ovs hardware offload test.
  • /test-all: to trigger all tests (except whole conformance).
  • /skip-all: to skip all tests (except whole conformance).

@codecov-commenter
Copy link

codecov-commenter commented Sep 1, 2020

Codecov Report

Merging #1191 into master will increase coverage by 14.69%.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff             @@
##           master    #1191       +/-   ##
===========================================
+ Coverage   41.60%   56.30%   +14.69%     
===========================================
  Files          74      105       +31     
  Lines       10508    11529     +1021     
===========================================
+ Hits         4372     6491     +2119     
+ Misses       5780     4469     -1311     
- Partials      356      569      +213     
Flag Coverage Δ
#integration-tests 47.53% <ø> (?)
#unit-tests 41.63% <ø> (+0.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
pkg/k8s/name.go 50.00% <0.00%> (ø)
pkg/agent/interfacestore/types.go 52.00% <0.00%> (ø)
pkg/agent/cniserver/ipam/ipam_delegator.go 2.00% <0.00%> (ø)
pkg/agent/proxy/types/groupcounter.go 0.00% <0.00%> (ø)
pkg/agent/metrics/prometheus.go 39.53% <0.00%> (ø)
pkg/querier/querier.go 0.00% <0.00%> (ø)
pkg/features/antrea_features.go 100.00% <0.00%> (ø)
pkg/apis/system/v1beta1/register.go 84.61% <0.00%> (ø)
pkg/ovs/ovsctl/interface.go 0.00% <0.00%> (ø)
pkg/agent/util/ethtool/ethtool_linux.go 0.00% <0.00%> (ø)
... and 46 more

@@ -80,8 +80,16 @@ if version_get "$OVS_VERSION" "2.13.0" && version_lt "$OVS_VERSION" "2.14.0" ; t
git apply
fi

# Starting from version 5.7.0, strongSwan no more supports to specify a configuration parameter with
# the path delimited by dots in a configuration file. This patch fixes the strongSwan confiugration
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# the path delimited by dots in a configuration file. This patch fixes the strongSwan confiugration
# the path delimited by dots in a configuration file. This patch fixes the strongSwan configuration

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed. Thanks!

tnqn
tnqn previously approved these changes Sep 1, 2020
Copy link
Member

@tnqn tnqn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -80,8 +80,16 @@ if version_get "$OVS_VERSION" "2.13.0" && version_lt "$OVS_VERSION" "2.14.0" ; t
git apply
fi

# Starting from version 5.7.0, strongSwan no more supports to specify a configuration parameter with
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/strongSwan no more supports to specify a configuration/strongSwan no longer supports specifying a configuration

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

Comment on lines 86 to 87
# After the patch is merged into OVS upstream, we should remove this workaround to apply the patch
# here.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The first step will be to change the URL for the patch actually, so:

After the patch is merged into OVS upstream, we should change the URL to an upstream one.

We won't be able to remove this altogether until there is a new OVS release with the patch.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Revised the comments. Check.

Starting from version 5.7.0, strongSwan no longer supports specifying a
configuration parameter with the path delimited by dots in a
configuration file. This change breaks ovs-ipsec-monitor which writes
strongSwan configuration parameters with the dotted paths.
This commit applies an ovs-monitor-ipsec patch to fix the issue, as a
workaround before the patch is merged to OVS upstream.
Copy link
Contributor

@antoninbas antoninbas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@antoninbas
Copy link
Contributor

/test-all

@jianjuns
Copy link
Contributor Author

jianjuns commented Sep 2, 2020

/test-networkpolicy

@tnqn tnqn merged commit 2ec50c0 into antrea-io:master Sep 2, 2020
antoninbas pushed a commit to antoninbas/antrea that referenced this pull request Sep 3, 2020
…ntrea-io#1191)

Starting from version 5.7.0, strongSwan no longer supports specifying a
configuration parameter with the path delimited by dots in a
configuration file. This change breaks ovs-ipsec-monitor which writes
strongSwan configuration parameters with the dotted paths.
This commit applies an ovs-monitor-ipsec patch to fix the issue, as a
workaround before the patch is merged to OVS upstream.
antoninbas pushed a commit to antoninbas/antrea that referenced this pull request Sep 3, 2020
…ntrea-io#1191)

Starting from version 5.7.0, strongSwan no longer supports specifying a
configuration parameter with the path delimited by dots in a
configuration file. This change breaks ovs-ipsec-monitor which writes
strongSwan configuration parameters with the dotted paths.
This commit applies an ovs-monitor-ipsec patch to fix the issue, as a
workaround before the patch is merged to OVS upstream.
antoninbas pushed a commit to antoninbas/antrea that referenced this pull request Sep 3, 2020
…ntrea-io#1191)

Starting from version 5.7.0, strongSwan no longer supports specifying a
configuration parameter with the path delimited by dots in a
configuration file. This change breaks ovs-ipsec-monitor which writes
strongSwan configuration parameters with the dotted paths.
This commit applies an ovs-monitor-ipsec patch to fix the issue, as a
workaround before the patch is merged to OVS upstream.
antoninbas pushed a commit that referenced this pull request Sep 3, 2020
…1191)

Starting from version 5.7.0, strongSwan no longer supports specifying a
configuration parameter with the path delimited by dots in a
configuration file. This change breaks ovs-ipsec-monitor which writes
strongSwan configuration parameters with the dotted paths.
This commit applies an ovs-monitor-ipsec patch to fix the issue, as a
workaround before the patch is merged to OVS upstream.
GraysonWu pushed a commit to GraysonWu/antrea that referenced this pull request Sep 22, 2020
…ntrea-io#1191)

Starting from version 5.7.0, strongSwan no longer supports specifying a
configuration parameter with the path delimited by dots in a
configuration file. This change breaks ovs-ipsec-monitor which writes
strongSwan configuration parameters with the dotted paths.
This commit applies an ovs-monitor-ipsec patch to fix the issue, as a
workaround before the patch is merged to OVS upstream.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants