Bug 1601228

Summary: Containers Chargeback Compute Rate Assignments doesn't save
Product: Red Hat CloudForms Management Engine Reporter: brahmani
Component: C&U Capacity and UtilizationAssignee: Ari Zellner <azellner>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: cpelland, obarenbo
Target Milestone: GAKeywords: Regression
Target Release: 5.9.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: containers
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-22 08:14:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Container Management Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Compute Rate Assignments none

Description brahmani 2018-07-15 11:26:24 UTC
Created attachment 1458981 [details]
Compute Rate Assignments

Description of problem:

On Chargeback Compute Rate Assignments,
choose Assign To: Labeled Container Images,
Image Labels: com.redhat.component

When pressing the Save button:
1) Changes don't save.
2) There is no flash message about Save process( success\fail).
3) The ability to choose again the Assign To: Labeled Container Images is not available.

Attach zip file with screenshots and production.log.


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

How reproducible:
Always

Steps to Reproduce:
1. Cloud Intel --> Chargeback --> Assignment --> Compute
2. Assignments --> Compute
3. choose Assign To: Labeled Container Images,
Image Labels: com.redhat.component

Actual results:
1) Changes don't save.
2) There is no flash message about Save process( success\fail).
3) The ability to choose again the Assign To: Labeled Container Images is not available.

Expected results:
1) Changes saved.
2) Flash message about Save process( success\fail).

Additional info:

Comment 2 Ari Zellner 2018-07-22 08:14:28 UTC

*** This bug has been marked as a duplicate of bug 1581349 ***