Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1616014 - split the state setting of the network role into state and persistent_state
split the state setting of the network role into state and persistent_state
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rhel-system-roles (Show other bugs)
7.6
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Pavel Cahyna
Leos Pol
: Extras
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-08-14 13:49 EDT by Pavel Cahyna
Modified: 2018-08-21 05:33 EDT (History)
6 users (show)

See Also:
Fixed In Version: rhel-system-roles-1.0-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-08-21 05:32:58 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github linux-system-roles/network/pull/77 None None None 2018-08-14 13:49 EDT
Red Hat Product Errata RHEA-2018:2531 None None None 2018-08-21 05:33 EDT

  None (edit)
Description Pavel Cahyna 2018-08-14 13:49:39 EDT
The state setting of network connections confuses two concepts: persistent (on disk) state of the profile and operational state of the interface. It should be split into two orthogonal settings: state with values up and down and persistent_state with present and absent. To some extent persistent_state is analogous to the "enabled" parameter of the service module: https://docs.ansible.com/ansible/latest/modules/service_module.html#service-module
Comment 2 Leos Pol 2018-08-20 03:48:24 EDT
rhel-system-roles-1.0-4.el7:
upstream testsuite manually executed with ansible-2.5.7-1.el7ae and ansible-2.6.2-1.el7ae on x86_64.
Comment 4 errata-xmlrpc 2018-08-21 05:32:58 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:2531

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