Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1541316

Summary: [ipsec] Some IPsec tunnels do not start after machines reboot
Product: Red Hat Enterprise Linux 7 Reporter: Otto Sabart <osabart>
Component: redhat-releaseAssignee: Release Engineering Bug Triage <releng-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: aokuliar, atomasov, jhladky, lkocman, osabart, systemd-maint-list
Target Milestone: rcKeywords: TestBlocker
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-12 10:21:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 16 Lukáš Nykrýn 2018-02-08 09:23:31 UTC
Can you please reboot, add debug to kernel cmdline, reporduce the issue and post here output of journalctl -b?

Comment 18 Lukáš Nykrýn 2018-02-12 08:27:32 UTC
I think this is your problem:
NetworkManager-wait-online.service            disabled

This should be enabled by default on rhel7, so either you have disabled that manually or there is an issue with preset policy (redhat-release package).

Comment 19 Otto Sabart 2018-02-12 10:21:44 UTC
You are correct, the problem was in *preset* policy of NetworkManager-wait-online.service (compose RHEL-7.5-20180208.1).

$ systemctl status NetworkManager-wait-online.service
...
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; disabled; vendor preset: disabled)
...

This is fixed in redhat-release-server-7.5-6.el7 package:
- https://bugzilla.redhat.com/show_bug.cgi?id=1540243
- http://pkgs.devel.redhat.com/cgit/rpms/redhat-release-server/commit/90-default.preset?h=rhel-7.5&id=fef0e2556c5460e068f44e888982e0643b8b27d9

$ systemctl status NetworkManager-wait-online.service
NetworkManager-wait-online.service - Network Manager Wait Online
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled; vendor preset: enabled)

$ grep NetworkManager-wait-online.service /usr/lib/systemd/system-preset/*
/usr/lib/systemd/system-preset/90-default.preset:enable NetworkManager-wait-online.service

$ rpm -qf /usr/lib/systemd/system-preset/90-default.preset
redhat-release-server-7.5-6.el7.x86_64

The IPsec IPv4 and IPv6 tunnels are now started automatically after boot. I
cannot reproduce this problem anymore.

Closing this as a duplicate of BZ1540243.

Thanks!

*** This bug has been marked as a duplicate of bug 1540243 ***