Girder does not find hpccloud and pvwproxy plugins when main VM (development) is restarted

[felixveysseyre]

Hi,

I am working on a new type of HPCCloud simulation and to test it, I would like HPCCloud-deploy to use my own HPCCloud directory.

To do that, I followed the instructions provided at the bottom of this file and built my main VM using: DEVELOPMENT=1 vagrant up

At the end of the building, my VM is running correctly and the HPCCloud directory used is the mine. Everything is working correctly.

Restarting the VM with the following command, I got several issues in the web console: vagrant halt && DEVELOPMENT=1 vagrant up

The issue is:

GET http://localhost:8888/api/v1/projects 404 (Not Found)

Looking a Girder logs, it seems that hpccloud and pvwproxy plugins can not be loaded:

vagrant@vagrant-ubuntu-trusty-64:~$ cat /home/hpccloud/.girder/logs/error.log [2017-12-08 13:04:14,139] ERROR: Required plugin pvwproxy does not exist. [2017-12-08 13:04:14,139] ERROR: Required plugin hpccloud does not exist.

Weirdly, these two plugins seem available in the Girder plugin directory:

vagrant@vagrant-ubuntu-trusty-64:~$ ls -alsh /opt/hpccloud/girder/plugins/ 0 lrwxrwxrwx 1 hpccloud hpccloud 38 Dec 8 10:15 hpccloud -> /opt/hpccloud/hpccloud/server/hpccloud 0 lrwxrwxrwx 1 hpccloud hpccloud 38 Dec 8 10:15 pvwproxy -> /opt/hpccloud/hpccloud/server/pvwproxy ...

These two symbolic links seem correct:

vagrant@vagrant-ubuntu-trusty-64:~$ ls -alsh /opt/hpccloud/hpccloud/server/ total 0 0 drwxr-xr-x 1 hpccloud 1003 204 Nov 22 13:51 hpccloud 0 drwxr-xr-x 1 hpccloud 1003 204 Nov 22 13:51 pvwproxy 0 drwxr-xr-x 1 hpccloud 1003 204 Dec 7 16:56 taskflows

Thanks for your help !

[felixveysseyre]

@jourdain Do you have any intuition concerning this issue ?

@cjh1 took a look yesterday but without success :(

[cjh1]

Hi @felixveysseyre, I now understand what you where trying todo. DEVELOPMENT=1 has to be used when the VM is created ( its not enough to halt the VM and then bring it back up ). So try the following vagrant destroy && DEVELOPMENT=1 vagrant up.

[felixveysseyre]

Well, some time I just want to restart the VM without rebuilding it. For example when I restart my computer.

Did I missed something ?

[cjh1]

@felixveysseyre Try #113, this should resolve your issue. When the VM is restart the services don't get restarted, this adds two provisioners to ensure this is done. If this resolves the problem please review the PR and then we can merge it.

[felixveysseyre]

@cjh1 I tried your pull request and the issue seems to be fixed !

Thanks !

[cjh1]

I think this is now resolved