#2401 closed defect (fixed)

ETF not deployed due to ETS download not present

Reported by: jenriquesoriano Owned by: osgeolive@…
Priority: blocker Milestone: OSGeoLive15.0
Component: OSGeoLive Keywords: ETF
Cc: osgeolive@…


Dear OSGeoLive team,

thanks for your efforts and congratulations for your excellent work.

We are reporting an issue in the ETF installation due to it is deployed but not loading some information needed.

We have tested the ETF deployment in the RC1. We have noticed that, the ETSs are not in the corresponding folder (/home/user/.etf/projects/inspire-ets-repository/). They should be downloaded and executed in the first deployment. We have checked the installation script and it seems correct, as we have ran it manually on the machine RC1 and the ETSs have been downloaded and the ETF is deployed properly.

Thus, it seems that there can be something in the virtual machine generation that has prevented the installation script from running completely. Probably in one of these lines of the installation scripts (/home/user/gisvm/bin/install_etf.sh):

if [ ! -d "$ETF_FOLDER/projects/inspire-ets-repository/ets-repository-osgeolive-15" ];then
	sudo mkdir "$ETF_FOLDER/projects/inspire-ets-repository/"
	cd "$ETF_FOLDER/projects/inspire-ets-repository/"
	sudo unzip -o "$TMP/ets-repository-osgeolive-15.zip"

Is there any hint that you can provide us with in order to get the installation script properly executed in the VM building process?

Thanks a lot.

Change history (6)

comment:1 by jbarrero, 22 months ago

Dear OSGeoLive Team,

again thanks for your effort.

We contact you again to share with you our current status with regard to this issue in order to know if you have progressed or can provide us with some insight to solve the issue.

From our side, we have been analyzing a different approach, which is not ideal but could solve the issue (our first option would be to solve the issue in the installer).
Please see below our rationale and the alternative approach.

The ETF, in order to work properly, needs to download a .zip file (ets-repository-osgeolive-15.zip) and unzip it at: $ETF_FOLDER/projects/inspire-ets-repository/.
These files are needed to load a set of tests in the ETF.
In the RC1, the unzipped file was not present in the mentioned folder.
We tested the installation script in the beta and it worked.
Thus, we are not sure of what could happen in the VM building process so these files are not present there.

Then, we have been considered a different approach where we download the ets-repository-osgeolive-15.zip in the start process. It is not ideal, but will also solve the issue.

We could make a PR of this potential solution, but, given that it is a kind of workaround, we would like to share it with you in advance.

Thus, our questions are:

1) Did you have the chance to check the issue in the installer so you can provide us with some insights to solve it?
2) Do you think it is appropriate to solve the issue by downloading and unzipping the required file in the start process as an alternative to solve the issue (a PR can be done inmediately from our side).

Thanks a million for your great contribution.


comment:2 by kalxas, 22 months ago

Cc: osgeolive@… added
Priority: normalmajor

comment:3 by kalxas, 22 months ago

Thank you for the feedback, it looks like we will need another RC for the VM version.

The only thing running after the ETF installer was this:


comment:4 by kalxas, 22 months ago

Priority: majorcritical

comment:5 by jenriquesoriano, 20 months ago

Priority: criticalblocker

Dear OSGeoLive Team,

thanks for your continuous support and effort. Please let us update the ETF status regarding to the VM RC2.

The .war file produced for the RC2 contains a set of properties to use credentials when the ETF uses the Team Engine endpoint from OGC. This endpoint will need these credentials at some point before the end of the year (OGC provided that deadline) and the ETF will need to send them to the endpoint accordingly.

The ETF .war file present in RC2 seems to be correct, but the necessary properties have not been updated accordingly.

We think that this is caused because the ETF creates a folder in deployment time where some stuff like the testdrivers or the configuration are present: /home/user/.etf We started from the (wrong) assumption that the installation script would be executed on a clean VM, but it seems that it was executed on top of the previous installation of RC1.

Then, the ETF.war is actually new (containing the properties), but the configuration on /home/user/.etf remains from the previous installation of the RC1 (without the properties).

To prevent this error from happening again we have modified the installation script. This modification consists in removing this /home/user/.etf folder before running the rest of the installation.

rm -rf /home/user/.etf

We have included this line in the install_script in the VM RC2, executed it and worked properly.

We have made a PR accordingly, please see it at: https://github.com/OSGeo/OSGeoLive/pull/355

Thus, in order to fix this issue the install script should be updated and executed in the RC2. This could be done manually, in case it is needed.

We remain attentive to your feedback at this regard.

Thanks a lot for all your support.

comment:6 by jenriquesoriano, 19 months ago

Resolution: fixed
Status: newclosed

Dear all,

thanks a lot for your support. The blocker has been solved in the last update of the RC3 and the ETF works properly. This was caused due to the install scripts execution as root. We will update the install script accordingly for future releases.

Thanks again for your effort.

Best regards,

Note: See TracTickets for help on using tickets.