Josh, I think you link to the wrong dependent bug. It looks like it's missing a digit.
I've tested this with the latest 54z (5.4.0.0.19.20150410165622_ad23806). Testing Steps: 1. Set up two new appliances, A1 and A99. (A1 in Region 1, A99 in Region 99) 2. Configure A1's replication worker to replicate to A99. 3. Enable Database Synchronization role on A1. 4. Add vSphere provider to A1. 5. Submit Provision VM request from A1. 6. On A99, view provisioned VM's information page under Infrastructure>Virtual Machines. Viewing the VM's information on A1 shows that the "Owner" and "Group" information is shown in the Lifecyle table. The owner and group displayed is for the user account that corresponds to the email and name that is entered into the provisioning VM request form, NOT the user account that is logged in when submitting the request. If no user account matches the email address provided, the "Owner" and "Group" information is not displayed. Regarding miq_groups being excluded from replication: I tested this my removing "miq_groups" from the replication exclusion list under Configuration>Advanced. After removing this line from the main configuration file for both A1 and A99, I enabled the replication worker and provisioned a VM from A1. The owner and group are displayed on A1, but the group is still not displayed on A99.
Blair, we also spoke about a second replicated child appliance, any update there?
So I have tested this on 5.7.0.17 following comment 3 instructions and it seems the owner and group fields are populated correctly on both r0 and r99 appliances.
Closing this as I believe its fixed with the central admin feature in CloudForms 4.2