The installer -- probably only for the Xen version -- expects it is going to die and just takes a nap. Unfortunately, when it DOES die, the stack of processes that spawned it see dead children and do error exits themselves.
make -> install.sh -> ssh -> sudo -> edera-install.sh -> docker run -> protect-installer
At the end of a successful run, the protect-installer triggers a reboot then sleeps with a 'sleeping forever' message. So it never gets to display the echo "Edera $TAG installed successfully!" message.
When the machine reboots, the ssh tunnel collapses and returns an error to install.sh. It wants to send Installation complete on $NODE_IP, but this will also never get seen. The set -e causes it to error exit before the echo can happen.
Then, that error-exit get passed up to the makefile that outputs it as a failed run of make.
More history in #32.
The installer -- probably only for the Xen version -- expects it is going to die and just takes a nap. Unfortunately, when it DOES die, the stack of processes that spawned it see dead children and do error exits themselves.
make -> install.sh -> ssh -> sudo -> edera-install.sh -> docker run -> protect-installer
At the end of a successful run, the protect-installer triggers a reboot then sleeps with a 'sleeping forever' message. So it never gets to display the
echo "Edera $TAG installed successfully!"message.When the machine reboots, the ssh tunnel collapses and returns an error to install.sh. It wants to send
Installation complete on $NODE_IP, but this will also never get seen. Theset -ecauses it to error exit before the echo can happen.Then, that error-exit get passed up to the makefile that outputs it as a failed run of make.
More history in #32.