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 2072385 - [RFE] [network] Support managing the network through nmstate schema
Summary: [RFE] [network] Support managing the network through nmstate schema
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rhel-system-roles
Version: 9.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 9.1
Assignee: Rich Megginson
QA Contact: Jon Trossbach
Jaroslav Klech
URL:
Whiteboard: role:network
Depends On:
Blocks: 2100979
TreeView+ depends on / blocked
 
Reported: 2022-04-06 08:19 UTC by Gris Ge
Modified: 2023-09-11 12:52 UTC (History)
7 users (show)

Fixed In Version: rhel-system-roles-1.19.3-1.el9
Doc Type: Enhancement
Doc Text:
.The `network` RHEL System Role supports network configuration using the `nmstate` API The `network` RHEL System Role now supports network configuration through the `nmstate` API. You can now directly apply the configuration of the required network state to a network interface instead of creating connection profiles. This update results in the following enhancements: * Decreased network configuration complexity. * Reliable way to apply the network state changes. * No need to track the entire network configuration. * Partial configuration of a network.
Clone Of:
: 2100979 (view as bug list)
Environment:
Last Closed: 2022-11-15 10:23:22 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles network pull 504 0 None open [Draft] Support the nmstate network state configuration 2022-06-01 16:20:58 UTC
Red Hat Issue Tracker RHELPLAN-118010 0 None None None 2022-04-06 08:37:54 UTC
Red Hat Product Errata RHEA-2022:8117 0 None None None 2022-11-15 10:23:39 UTC

Description Gris Ge 2022-04-06 08:19:19 UTC 
Description of problem:

The nmstate is providing decorative way of managing the network, unlike the current `connection` based schema.

Please introduce a new way allowing `nmstate` schema been used in network role.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 7 Jon Trossbach 2022-07-29 15:00:57 UTC 
With the recent change to 2.13 we have to decide are we just dropping <RHEL6.qcow> from testing now?
https://issues.redhat.com/browse/RHELPLAN-125014
Comment 8 Rich Megginson 2022-07-29 15:11:19 UTC 
(In reply to Jon Trossbach from comment #7)
> With the recent change to 2.13 we have to decide are we just dropping
> <RHEL6.qcow> from testing now?
> https://issues.redhat.com/browse/RHELPLAN-125014

Yes.  ansible-core 2.13 does not support RHEL6 managed hosts, and there is no workaround.
Comment 9 Jon Trossbach 2022-08-02 03:29:23 UTC 
This one appears good.

# dnf install http://download.eng.bos.redhat.com/brewroot/vol/rhel-9/packages/rhel-system-roles/1.19.3/1.el9/n\
oarch/rhel-system-roles-1.19.3-1.el9.noarch.rpm

# ansible --version
ansible [core 2.13.2]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.9/site-packages/ansible
  ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/bin/ansible
  python version = 3.9.13 (main, Jul 25 2022, 00:00:00) [GCC 11.3.1 20220421 (Red Hat 11.3.1-2)]
  jinja version = 3.1.2
  libyaml = True

# export SYSTEM_ROLES_ONLY_TESTS=network/network_tests_network_state_nm.yml

:: [ 22:47:12 ] :: [   PASS   ] :: Test network with ANSIBLE- against RHEL_7_9_GA (Expected 0, got 0)
:: [ 22:56:48 ] :: [   PASS   ] :: Test network with ANSIBLE- against RHEL_8_6_0_GA (Expected 0, got 0)
:: [ 23:02:45 ] :: [   PASS   ] :: Test network with ANSIBLE- against RHEL_8_7_TESTING (Expected 0, got 0)
:: [ 23:13:14 ] :: [   PASS   ] :: Test network with ANSIBLE- against RHEL_9_0_0_GA (Expected 0, got 0)
:: [ 23:17:38 ] :: [   PASS   ] :: Test network with ANSIBLE- against RHEL_9_1_TESTING (Expected 0, got 0)
Comment 10 Jon Trossbach 2022-08-02 13:13:05 UTC 
Just realized these weren't added to the above comment. Adding for future reference.

# uname -r
5.14.0-138.el9.x86_64
# rpm -q rhel-system-roles
rhel-system-roles-1.19.3-1.el9.noarch
Comment 17 errata-xmlrpc 2022-11-15 10:23:22 UTC 
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 (rhel-system-roles bug fix and enhancement update), 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-2022:8117
Note You need to log in before you can comment on or make changes to this bug.