Bug 1030869 - ipsec is redirected to nonexistent init script
Summary: ipsec is redirected to nonexistent init script
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libreswan
Version: 7.0
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Paul Wouters
QA Contact: Aleš Mareček
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-15 10:10 UTC by Aleš Mareček
Modified: 2014-06-18 08:31 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 09:56:07 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Aleš Mareček 2013-11-15 10:10:03 UTC
Description of problem:
$ ipsec setup --start
Redirecting to: /etc/init.d/ipsec start
/usr/libexec/ipsec/setup: line 92: /etc/init.d/ipsec: No such file or directory


Version-Release number of selected component (if applicable):
libreswan-3.6-1.el7

How reproducible:
Always

Steps to Reproduce:
1. ipsec setup --start


Actual results:
Redirecting to: /etc/init.d/ipsec start
/usr/libexec/ipsec/setup: line 92: /etc/init.d/ipsec: No such file or director

Expected results:
ipsec_setup: Starting Openswan IPsec <some version info>...
ipsec_setup: /usr/libexec/ipsec/addconn Non-fips mode set in /proc/sys/crypto/fips_enabled
ipsec_setup: /usr/libexec/ipsec/addconn Non-fips mode set in /proc/sys/crypto/fips_enabled
ipsec_setup: /usr/libexec/ipsec/addconn Non-fips mode set in /proc/sys/crypto/fips_enabled
ipsec_setup: /usr/libexec/ipsec/addconn Non-fips mode set in /proc/sys/crypto/fips_enabled


Additional info:
$ cat /etc/ipsec.conf; echo; cat /etc/ipsec.secrets
version	2.0

config setup
	protostack=netkey
	nat_traversal=yes
	#virtual_private=
	oe=off
	nhelpers=0


include /etc/ipsec.d/*.secrets

Comment 2 Paul Wouters 2014-01-16 08:52:12 UTC
This bug still needs all the flags :(

Comment 6 Ludek Smid 2014-06-13 09:56:07 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


Note You need to log in before you can comment on or make changes to this bug.