Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Update2() allows to block autoconnect but it does not allow to block changes to connection.metered or connection.zone. Please consider adding a flag that will allow to only update the on-disk configuration without any immediate changes to the active connection.
Additional info:
This is based from a suggestion from Thomas for the system roles:
https://github.com/linux-system-roles/network/issues/35
> Per the Jul 22nd blocker and exception review meeting, it is requested that a justfication as to why this missed feature freeze is required.
Current review says this is not approved for exception
Comment 6> Is there an impact to Ansible?
Yes. This extension to the API is requested for the ansible network role to implement https://github.com/linux-system-roles/network/issues/35
Nmstate assumes now that nothing is changed when editing the profile (commit/update2) and the actual changes are applied on reapply/activation.
It seems that this assumption is wrong (based on this BZ), therefore we will find this options useful.
If possible, please consider exposing it to `commit_changes_async` as well.
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/RHBA-2019:3623