You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
jgruber
changed the title
Clustering should be setting the host name of the device before attempting to cluster
Clustering should be setting the device name of the device before attempting to cluster
Jul 11, 2016
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.
The text was updated successfully, but these errors were encountered: