Bug 2072385
| Summary: | [RFE] [network] Support managing the network through nmstate schema | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Gris Ge <fge> | |
| Component: | rhel-system-roles | Assignee: | Rich Megginson <rmeggins> | |
| Status: | CLOSED ERRATA | QA Contact: | Jon Trossbach <jtrossba> | |
| Severity: | medium | Docs Contact: | Jaroslav Klech <jklech> | |
| Priority: | unspecified | |||
| Version: | 9.1 | CC: | gfialova, jklech, nhosoi, rmeggins, spetrosi, till, wenliang | |
| Target Milestone: | rc | Keywords: | FutureFeature, Triaged | |
| Target Release: | 9.1 | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | role:network | |||
| 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.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2100979 (view as bug list) | Environment: | ||
| Last Closed: | 2022-11-15 10:23:22 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2100979 | |||
|
Description
Gris Ge
2022-04-06 08:19:19 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 (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. 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) 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 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 |