4store related services fails to start on the first boot of the AWS instance thus causing the firstboot script to fail.

ncbo / virtual_appliance

Bioportal Virtual Appliance

5 stars 7 forks source link

4store related services fails to start on the first boot of the AWS instance thus causing the firstboot script to fail. #18

Closed alexskr closed 4 years ago

alexskr commented 4 years ago

in some cases, 4store fails to start during the first boot of the AWS instance which causes firstboot script to fail. Firstboot script resets API keys and sets the initial password for Admin user. Web UI shows "something went wrong" error and Admin user is unable to log into Web UI.

rebooting AWS instance seem to fix this issue.

alexskr commented 4 years ago

in some cases, cloud-init could interfere with firstboot.rb. For instance, cloud-init and firstboot could run at the same time so when cloud-init kicks off yum update it could restart services which firstboot needs.

we need to either fix systemd ordering or integrate firsboot into cloud-init.

alexskr commented 4 years ago

updated systemd unit file for ontoportal-firstboot to ensure it runs after cloud-init run is complete by including After=cloud-final.service

The cloud-init first run can take a considerable amount of time because it runs system package update so user will see an error if they access ontoportal web ui before cloud-init and ontoportal-firstboot runs are fully complete. For this reason we added a splash screen/maintenance page that will be in place until firstboot is complete.

alexskr commented 4 years ago

fixed in v3.0.2