You need to look at all the checks we performed in the clustering code from f5_onboarding.
If you try to cluster two brand new VE, it doesn't check to see that device names are not the same.
Text: u'{"code":400,"message":"script did not successfully complete: (Could not add ca-device (error from devmgmtd): Cannot add a device with the same name as the self device.\n while executing\n\"tmsh::modify cm trust-domain Root ca-devices add \{ 172.23.1.30 \} name bigip1 username admin password openstack\" line:1)","errorStack":[]}'
We always reset the trust renaming the devices to the hostname (DNS FQDN) to avoid just this issue.
You need to look at all the checks we performed in the clustering code from f5_onboarding.
If you try to cluster two brand new VE, it doesn't check to see that device names are not the same.
Text: u'{"code":400,"message":"script did not successfully complete: (Could not add ca-device (error from devmgmtd): Cannot add a device with the same name as the self device.\n while executing\n\"tmsh::modify cm trust-domain Root ca-devices add \{ 172.23.1.30 \} name bigip1 username admin password openstack\" line:1)","errorStack":[]}'
We always reset the trust renaming the devices to the hostname (DNS FQDN) to avoid just this issue.