Closed qrkourier closed 4 years ago
The problem was that ziti-tunnel
had not yet been run for the first time following enrollment.
❯ ziti edge list identities --output-json 'name="kenneth_bingham-laptop"' | jq '.data[]|{sdkInfo:.sdkInfo,envInfo:.envInfo}'
{
"sdkInfo": {
"branch": "master",
"revision": "b01ae733cb76",
"type": "ziti-sdk-golang",
"version": "v0.13.20"
},
"envInfo": {
"arch": "amd64",
"os": "linux",
"osRelease": "5.4.0-7634-generic\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000",
"osVersion": "#38~1592497129~20.04~9a1ea2e-Ubuntu SMP Fri Jun 19 22:43:37 UTC \u0000"
}
}
I enrolled
ziti-tunnel
0.15.1 on Linux/x86 withziti-controller
0.14.9 and the identity metadatasdkInfo
andenvironmentInfo
are still empty. The same objects are populated with expected values in another identity that was enrolled with Android Tunneler.