Skip to content

Commit

Permalink
docs(changelog): version 1.15.2 [citest skip]
Browse files Browse the repository at this point in the history
Update changelog and .README.html for version 1.15.2

Signed-off-by: Sergei Petrosian <spetrosi@redhat.com>
  • Loading branch information
spetrosi committed Apr 4, 2024
1 parent b4174b8 commit 00d78dd
Show file tree
Hide file tree
Showing 2 changed files with 37 additions and 4 deletions.
13 changes: 9 additions & 4 deletions .README.html
Original file line number Diff line number Diff line change
Expand Up @@ -315,12 +315,17 @@ <h1 id="variables">Variables</h1>
<li><code>network_connections</code> - The connection profiles are
configured as <code>network_connections</code>, which is a list of
dictionaries that include specific options.</li>
<li><code>network_allow_restart</code> - Certain configurations require
the role to restart network services. For example, if a wireless
<li><code>network_allow_restart</code> - It defaults to
<code>false</code>. To load NetworkManager plugins after installation,
NetworkManager requires to be restarted. For example, if a wireless
connection is configured and NetworkManager-wifi is not installed,
NetworkManager must be restarted prior to the connection being
configured. Setting this to <code>false</code> will prevent the role
from restarting network service.</li>
configured. The restart can result in connectivity loss and therefore
the role does not allow it without explicit consent. The user can
consent to it by setting <code>network_allow_restart</code> to
<code>true</code>. Setting <code>network_allow_restart</code> to
<code>false</code> will prevent the role from restarting
NetworkManager.</li>
<li><code>network_state</code> - The network state settings can be
configured in the managed host, and the format and the syntax of the
configuration should be consistent with the <a
Expand Down
28 changes: 28 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,34 @@
Changelog
=========

[1.15.2] - 2024-04-04
--------------------

### Bug Fixes

- fix: Allow network to restart when wireless or team connection is specified (#675)

Enhancement: Ask user's consent to restart NM due to wireless or team interfaces when the updates for network packages are available.

Reason: When wireless or team connections are specified and the updates for network packages are available, NetworkManager must be restarted, the role requires user's consent to restart NetworkManager. Otherwise, there
might be property conflicts between NetworkManager daemon and plugin, or
NetworkManager plugin is not taking effect.

Result: When wireless or team connections are specified and the updates for network packages are available, NetworkManager must be restarted, the role will ask user's explicit consent to restart NetworkManager.

Issue Tracker Tickets (Jira or BZ if any):

Resolves: https://issues.redhat.com/browse/NMT-1039

### Other Changes

- test: improve bond test failure debugging (#676)
- ci: Bump ansible/ansible-lint from 6 to 24 (#677)
- docs: Add MAC VTAP example (#679)
- tests: Team interface is indeed supported on Fedora (#680)
- test: improve name text for skipped ostree tests (#684)
- ci: Bump mathieudutour/github-tag-action from 6.1 to 6.2 (#687)

[1.15.1] - 2024-02-14
--------------------

Expand Down

0 comments on commit 00d78dd

Please sign in to comment.