Skip to content

Commit 64dab1a

Browse files
committed
(DOCSP-33242) concision
1 parent 9e0634f commit 64dab1a

File tree

1 file changed

+5
-9
lines changed

1 file changed

+5
-9
lines changed

source/release-notes/changelogs/ops-manager/changelog-onprem-v6.0.rst

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -351,15 +351,11 @@
351351

352352
.. note::
353353

354-
``network.target`` in a ``systemd`` unit file indicates that the network management stack
355-
has been started. Ordering after ``network.target`` has little meaning
356-
during start-up, because ``after=network.target`` doesn't define whether any network interfaces have
357-
already been configured when ``network.target`` is reached. Therefore, when waiting on ``network.target``,
358-
it is possible that the :manual:`mongod </reference/program/mongod/#mongodb-binary-bin.mongod>` fails to start
359-
after a system reboot. Most Linux host-oriented distributions with ``systemd`` support ``network-online.target``
360-
which indicates that your network connectivity has been established. Its primary purpose is to actively delay the
361-
activation of services until the network is up. To improve user experience, |onprem| server 6.0.13 updates the |onprem|
362-
systemd unit file from ``after=network.target`` to ``after=network-online.target``.
354+
To improve user experience, |onprem| server 6.0.13 updates the |onprem| systemd unit file from
355+
``after=network.target`` to ``after=network-online.target``. This prevents reboot failures caused
356+
by attempting to start :manual:`mongod </reference/program/mongod/#mongodb-binary-bin.mongod>` after
357+
the network management stack has started, but before verifying that the network connectivity has
358+
been established.
363359

364360
- Updates the {+mdbagent+} to :ref:`12.0.21.7698
365361
<mongodb-12.0.21.7698>`.

0 commit comments

Comments
 (0)