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
Conversation
Thanks for your PR. The following commands are available:
|
Codecov Report
@@ 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
Flags with carried forward coverage won't be shown. Click here to find out more.
|
c6d3682
to
7aca18d
Compare
build/images/ovs/apply-patches.sh
Outdated
@@ -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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed. Thanks!
7aca18d
to
e601e44
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
build/images/ovs/apply-patches.sh
Outdated
@@ -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 |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
build/images/ovs/apply-patches.sh
Outdated
# After the patch is merged into OVS upstream, we should remove this workaround to apply the patch | ||
# here. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Revised the comments. Check.
bbdb99c
to
7571e5a
Compare
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.
7571e5a
to
ec5242f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/test-all |
/test-networkpolicy |
…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.
…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.
…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.
…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.
…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.
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.