Components page is temporarily unavailable about sw360chores HOT 7 OPEN

We experienced a similar issue with several components (including "Components") shown as being "temporarily unavailable". We used the docker compose from the v2 directory.
The issue was with the backend container(s) not finding the servelets. The problem is with the create-slim-war-files.sh script and the extraction of .jar files. Removing the execution of the script and copying the "fat" .war files appears to solve the issue.

sw360.patch.txt

from sw360chores.

Thanks for reporting this issue. We have the same problem and are unable to install/use SW360.

from sw360chores.

Hello, I am terribly sorry for not updating the issue. But is that is likely resulting from the fact that the setup uer does not have a group. Is that the case?

from sw360chores.

But is that is likely resulting from the fact that the setup uer does not have a group. Is that the case?

@mcjaeger This issue still persists even after importing sample users and logging into using other ids like admin, user etc

@milindur also stated the same in https://sw360chat.slack.com/archives/C68C2RYS3/p1586447237060000

from sw360chores.

@mcjaeger When using vagrant deployment in VirtualBox, the issue does not exist. In that case I can see that the CouchDB gets populated with the SW360 databases. But when using the docker deployment, the CouchDB remains empty. I do not know if that matters, but maybe it helps to track the issue down.

I also used the example users and logged in using one of these users.

from sw360chores.

needs retest

from sw360chores.

should be retested after this is solved: https://github.com/sw360/sw360chores/issues/new

from sw360chores.