Bug 1246245 - Cannot change server's zone from 'default'
Summary: Cannot change server's zone from 'default'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.4.2
Assignee: Tim Wade
QA Contact: bmorriso
URL:
Whiteboard:
Depends On: 1237110
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-23 19:12 UTC by Dan Clarizio
Modified: 2019-08-15 04:57 UTC (History)
12 users (show)

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.
Clone Of: 1237110
Environment:
Last Closed: 2015-09-09 12:26:08 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1744 0 normal SHIPPED_LIVE CFME 5.4.2 bug fixes, and enhancement update 2015-09-09 16:25:05 UTC

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
Note You need to log in before you can comment on or make changes to this bug.