I work for IBM and trying to prototype netboot (pxe) for ubuntu. This question is used to identify some issue involved in setting up juju end point client provisioning (for jujud).
As part of prototype trying to use juju to deploy to end point. Could occur on a bootstrap or add-machine. This process was using the manual environment. The 4 VMs needed were previously provisioned by maas.
juju bootstrap --show-log --debug -e manual
juju add-machine ssh:firstname.lastname@example.org --show-log --debug
juju end point does NOT setup do to access to https:/streams/cannoical/com
On endpoint check /var/log/cloud-init-output.log
curl: (60) SSL certificate problem: self signed certificate More details here: //curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. tools from //streams.canonical.com/juju/tools/releases/juju-1.24.6-trusty-ppc64el.tgz downloaded: HTTP 000; time 0.006s; size 0 bytes; speed 0.000 bytes/s sha256sum: /var/lib/juju/tools/1.24.6-trusty-ppc64el/tools.tar.gz: No such file or directory