On a maas with 3 networks, identical charms can be deployed, one for amd64, arm64, and armhf. The amd64 agents call home and the service is deployed and starts. But the arm* agents are stuck in pending.
The machine logs for arm* contain this
2014-10-02 14:05:04 INFO juju.state.api apiclient.go:242 dialing "wss://tytjp.maas:17070/"
2014-10-02 14:05:04 INFO juju.state.api apiclient.go:250 error dialing "wss://tytjp.maas:17070/": websocket.Dial wss://tytjp.maas:17070/: x509: certificate has expired or is not yet valid
An examination of the working and faled machines revealed that ca-cert.pem was placed in the working virtual node but not on armhf and arm64 bit machines.
Note that there were issue getting this env to see the tools. The proxies are configured to provide access to streams.canonical.com, but tools were not found. sync-tools was run to put all the 1.20.9 tools into the env
cloud output log.