Bug 1246245

Summary: Cannot change server's zone from 'default'
Product: Red Hat CloudForms Management Engine Reporter: Dan Clarizio <dclarizi>
Component: ApplianceAssignee: Tim Wade <twade>
Status: CLOSED ERRATA QA Contact: bmorriso
Severity: medium Docs Contact:
Priority: medium    
Version: 5.4.0CC: abellott, bmorriso, cpelland, dajohnso, gtanzill, jhardy, jocarter, mfeifer, obarenbo, rananda, snansi, twade
Target Milestone: GAKeywords: ZStream
Target Release: 5.4.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.4.2.0 Doc Type: Bug Fix
Doc Text:
In the previous version of CloudForms Management Engine, attempting to change the zone of the first server deployed in the default zone would fail despite the UI indicating that the change was successful. This was because the zone update process wrongly reported success without changing the server's zone. This bug was fixed by ensuring that the server's zone information was saved when changing its basic information. It is now possible to change any server's zone in the new version of CloudForms Management Engine.
 Story Points: ---
Clone Of: 1237110 Environment:
Last Closed: 2015-09-09 12:26:08 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:
Bug Depends On: 1237110    
Bug Blocks:    

Comment 3 bmorriso 2015-08-31 13:54:13 UTC 
Verified fixed in  5.4.2.0.20150820153254_83e434d

Followed verification steps in the description. The DB shows that the appliance is successfully changed to the new zone.


vmdb_production=# select id, name from zones;
 id |  name   
----+---------
  1 | default
  2 | newzone
(2 rows)

vmdb_production=# select id, name, zone_id from miq_servers;
 id | name | zone_id 
----+------+---------
  1 | EVM  |       2
(1 row)
Comment 5 errata-xmlrpc 2015-09-09 12:26:08 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://rhn.redhat.com/errata/RHBA-2015-1744.html