This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

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:

Clone of https://issues.redhat.com/browse/RFE-4210

New OCP node is installed with basic network configuration (network interface has an IP assigned for installation purposes)
NodeNetworkConfigurationPolicy (NNSP) is applied to configure netwok on the node.
NNSP is removed by the administrator.
Request:

The configuration of the node should be reverted to the state before NNSP has been applied when an NNSP is removed.
 

Without preparing for the situation and having an NNSP with the original state it is currently impossible to revert to the original state.
According to the customer this is not 'Kubernetes like' behavior.
 

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


How reproducible: Always


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Thank you for the report. Could you please clarify how to reproduce this with Nmstate and write down the current and the expected behavior to clarify what the request is about. Thanks.

Hi Till,

After follow up reporter, they are expecting nmstate to provider a way to generate reverse network state YAML file on specified desired state.
By storing the reverse state in `openshift-nmstate` operator, the operator could revert the network when customer is uninstalling the `openshift-nmstate` operator.

For implementation, nmstatectl will provide API and CLI like:

nmstatectl gen-revert desire_state.yml -c optional_current_state.yml