Bug 1384754

Summary: After applying 5.6.2.1 errata service dialogues are missing
Product: Red Hat CloudForms Management Engine Reporter: tachoi
Component: AutomateAssignee: eclarizi
Status: CLOSED DUPLICATE QA Contact: Milan Falešník <mfalesni>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 5.6.0CC: gmccullo, jhardy, jocarter, mfalesni, mkanoor, obarenbo, tachoi, tfitzger
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-14 13:14:21 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:

Description tachoi 2016-10-14 04:52:15 UTC
Description of problem:
After applying 5.6.2.1  errata service dialogues are missing which was working in 5.6.1.2

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


How reproducible:
Still waiting for customer input

Steps to Reproduce:
1.
2.
3.

Actual results:
In the deployment mode selection it is supposed to default to incremental and it is defaulting to "complete".  Even when you go in and edit it and save it with the correct setting, it will not stay and will again go to "complete" even though incremental is saying "default" on the drop down it will not work for it. 

Expected results:
In the deployment mode selection it is supposed to default to incremental and it is defaulting to "complete".  Even when you go in and edit it and save it with the correct setting, it will not stay and will again go to "complete" even though incremental is saying "default" on the drop down it will not work for it


Additional info:
Unum customer in US
Log has been attached to SFDC case

Comment 2 Greg McCullough 2016-10-14 09:12:58 UTC
This should be duplicate of bug 1376603.  (There have been several bugs opened on this issue.)

There is a hotfix available for testing on bug 1383774.

Comment 3 Josh Carter 2016-10-14 13:14:21 UTC

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