Description of problem: If the name of the datacenter that is chosen for a VMware Compute Resource is changed in the vCenter, Satellite gives error messages when trying to access e.g. the Virtual Machines tab on the Compute Resource or trying to edit a host that is provisioned with that Compute Resource. Version-Release number of selected component (if applicable): Fresh install of Satellite 6.2.8 How reproducible: Every time Steps to Reproduce: 1. Create a new Compute Resource 2. Choose Provider: VMware 3. Add server address, username and password 4. Click on Load Datacenter and choose a datacenter you want to use 5. Save 6. Open the Compute Resource in the Satellite GUI and click the Virtual Machines tab to make sure that you can list the vms in that datacenter 7. Go to vCenter and change name of the datacenter you chose in step 4 8. Go back to Satellite and try to list all Virtual Machines again (this will generate the error message) 9. If you have a host in Satellite that is created on that Compute Resource, open it in the GUI and click Edit (this will also generate error message) Actual results: The Compute Resource won't function until you change back to the old datacenter name. Expected results: It should be possible to change the name of the datacenter without breaking Satellite usage. Additional info: Unfortunately I don't have the error messages or logs available at this point, but it should be simple to reproduce.
A simple workaround should vmbe visiting compute resource edit form, reloading datacenters and saving it with the new name.
Tested & still a problem in 1.18 (nightly). cloning to upstream
Created redmine issue http://projects.theforeman.org/issues/22723 from this bug
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Rich Jerrido or Bryan Kearney or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
This bugzilla applies not only to the name of the compute resource but to the datacenter path as well. The current solution to this problem, re-associating the new correct vcenter compute resource information to the compute profiles referencing that resource, is to re-submit the configuration of each compute profile. (Infrastructure > Compute Profiles > select profile name > select resource name > press submit on this edit page) In one particular case this meant going through ~140 compute profiles and resubmitting their configurations. Even though no real change is needed for the profile to pick up the new resource attributes, having to select *all* of the profiles for some customers is not convenient or sustainable.
We have no other identifier for datacenter, so it would be hard to trace the datacenter after the name change. Setting the new name in Compute Resource seems like quite satisfyable workaround. Paul the path seems like a bit different issue, can we have a new BZ for that?
@oezr Thanks, bug 1946120 submitted regarding the compute profile issues related to changing the datacenter name.
I believe that with bug 1946120 we can close this, as changing the name will not get fixed, the autocorrection of path in compute profile should.