Bug 1806652

Summary: When a node is unassigned from an application in the edit flow, the change is not applied
Product: OpenShift Container Platform Reporter: Jaivardhan Kumar <jakumar>
Component: Dev ConsoleAssignee: cvogt
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, dsantra, nmukherj, rgarg, spathak, viraj
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1803867 Environment:
Last Closed: 2020-05-04 11:39:25 UTC Type: ---
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: 1803867    
Bug Blocks:    
Attachments:
Description Flags
When a node is unassigned from an application in the edit flow, the change is applied none

Description Jaivardhan Kumar 2020-02-24 17:08:42 UTC
+++ This bug was initially created as a clone of Bug #1803867 +++

Description of problem:
In the edit flow when the node is unassigned from an application group, the change is not applied and the node continues to remain in the application group.

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

How reproducible:
Always

Steps to Reproduce:
1. Right-click on a topology node, which is in an application group, to edit
2. In the General Section of the Import form, change the application to `Unassigned`
3. Click on Submit

Actual results:
The workload continues to remain in the application group

Expected results:
The workload should be removed from the application group

Additional info:

Comment 3 spathak@redhat.com 2020-02-28 16:47:31 UTC
Created attachment 1666444 [details]
When a node is unassigned from an application in the edit flow, the change is applied

Comment 4 spathak@redhat.com 2020-02-28 20:56:56 UTC
Verified on build : 4.4.0-0.ci-2020-02-26-215902
Chrome browser: 76.0.3809.132

Comment 6 errata-xmlrpc 2020-05-04 11:39:25 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, 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-2020:0581