Good Morning Greg, That is not the problem as our client's requirement are to scrub every server hostname and IP address out before submitting every log file to a vendor case. Thanks in advance, Johnny J. Ayissi
Good afternoon Team, I posted a reply back to RH Case #02063452 a few days ago. Client's security policy will prohibit exposing sensitive information in logs, so the records of hostname and IP must be scrubbed before given to a vendor. Is there any update on this BZ/Case? Is there anything I can provide to help push this along? Thanks in advance, Johnny J. Ayissi
Reviewing this issue more the issue is that the `migrate` method is exposed directly on the VmOrTemplate model (the base model) and was originally written when Infra providers existed and has not been updated. The basic logic is Infra specific and only two providers are fully supported today: VMware and RHV Brad - We can look to address this issue but I am wondering if you are aware of any work-arounds that may existing? Do you know of any automate solutions to go directly against the provider?
Openstack provider has a supports_not :migrate which should prevent the UI from issuing a migrate operations, https://github.com/ManageIQ/manageiq-providers-openstack/blob/master/app/models/manageiq/providers/openstack/cloud_manager/vm/operations/relocation.rb#L9 If this is being called from automate and the script isn't checking for supported features that sounds like the issue.
The current workaround for this is using a Rails Runner Command: cmd = "/var/www/miq/vmdb/bin/rails r 'ManageIQ::Providers::Openstack::CloudManager::Vm.live_migrate(#{vm.id}, {:hostname=> \"#{new_host}\"})'"