Description of problem: Not able to copy class(include all instances) to new writeable domain in multi-zone appliance Version-Release number of selected component (if applicable): 5.7 How reproducible: Not always Steps to Reproduce: 1. Should have multiple zone with automate rote enabled on at least one or more appliance 2. Create a new writable domain. Assign top preference to the domain. 3. Try to copy class (tick all instances within the class) to new domain Actual results: Example: ~~~ [----] E, [2017-06-07T00:53:51.382286 #3040:10425e4] ERROR -- : MIQ(miq_ae_class_controller-copy_objects): Error during 'Automate Instance copy': Destination Class already exists /Integration/Customization/VMcustomization ~~~ Please note that `VMcustomization` is never copied Expected results: Should be able to copy class including instances Additional info: Workaround: 1. Copy the class first 2. and they copy it instances (URL to recording(private))
I wasn't able to re-create this problem. The copy worked in a multi zone appliance.
Milan, Any idea why this works for me but fails for the customer?
Hello, we are deploying the same automate model from DEV to 3 single appliance environments (TEST, UAT, DEMO) without any issue. Error appears only for PROD environment that is build by multi appliances deployed to multi zones. Feel free to contact me if you need more details or like to have a call to see environment setting. Vaclav
I will try looking into it and possibly find a reliable reproducer steps. I hope I can do it today as I am off for rest of the week then.
I cannot reproduce it, can anybody chime in with some schema of their deployment?
Hi Sachin, Any update from the customer? Thanks, Tina
@Tina, See comment#6 from customer
We cannot reproduce and have not gotten a response on our request for additional information. If more data or details can be provided please re-open.
Drew - At this point I would suggest adding some debug logging to the miq_ae_class_copy.rb validate method to help identify the root cause.
Customer should restart the server after replacing the file, then reproduce the issue, and send us the evm.log and automation.logs. The debug file is the attachment in comment 18.
Hey Sachin! Is there any update on this issue?
Hi Drew, The case is still waiting on customer.