I'm trying to install the whole Open CIT 3.2.1 framework on two physical machines with Open Stack Mitaka, one for the controller and one for the compute node. The wizard manages to install all the components of the framework, but fails to install the Trust Agent on compute node. SSH access is granted, and the deployment wizard logs don't show anything. Also, the Trust Agent logs in /opt/trustagent and /var/log/... are not available, as the installer fails before creating them.
I would like to know what are the exact prerequisites on the compute node in order to launch the deployment wizard. At this point, the base point for installation is as follows:
- TPM enabled and clear ownership
- Intel TXT enabled from BIOS
tboot package installed and rebooted with it
The machine runs Ubuntu 16.04.2 LTS with kernel 4.4.0-83.
Please note that if I run the .bin installer manually, It works as expected...but I am not able to register the compute node with the Attestation Service because of authentication issue (which may be related to missing client API user in Attestation Service, caused by the failure during installation of the Trust Agent).
I'm trying to install the whole Open CIT 3.2.1 framework on two physical machines with Open Stack Mitaka, one for the controller and one for the compute node. The wizard manages to install all the components of the framework, but fails to install the Trust Agent on compute node. SSH access is granted, and the deployment wizard logs don't show anything. Also, the Trust Agent logs in
/opt/trustagentand/var/log/...are not available, as the installer fails before creating them.I would like to know what are the exact prerequisites on the compute node in order to launch the deployment wizard. At this point, the base point for installation is as follows:
tbootpackage installed and rebooted with itThe machine runs Ubuntu 16.04.2 LTS with kernel 4.4.0-83.
Please note that if I run the
.bininstaller manually, It works as expected...but I am not able to register the compute node with the Attestation Service because of authentication issue (which may be related to missing client API user in Attestation Service, caused by the failure during installation of the Trust Agent).