Name of provided root certificate is not applied to the install.sh script
Opened this issue · 2 comments
I followed this guide to install a nested edge hierarchy.
At step 3 of the chapter "Create a hierarchy of IoT Edge devices" is described that I can provide a custom root certificate by editing the iotedge_config.yaml. I adjusted the paths of the root_ca_cert_path and root_ca_cert_key_path accordingly. After executing ./iotedge_config --config <path to config> --output <output path> -f the generated install.sh file contains the (hardcoded here and here) root CA name iotedge_config_cli_root.pem instead of my configured root CA name.
Let me know if you need further information. Thanks in advance for you efforts.
I can reproduce this. Looks like the cert is properly copied over, but install.sh doesn't reference it correctly
Confirming I'm seeing this error message as well. Device certs and hub auth certs are copied correctly and set correctly in final config.toml but the script refers to the hard coded 'iotedge_config_cli_root.pem' which is not part of the {deviceid}.zip file.
Error message after running the script in an Azure VM through az vm run-command invoke --command-id RunShellScript
unable to re-open stdin: \n./install.sh: 11: [[: not found\ncp: cannot stat 'iotedge_config_cli_root.pem': No such file or directory\ncp: cannot stat 'iotedge_config_cli_root.pem': No such file or directory\
All does seem to work, and IoT Edge is working correctly in the end.