-
Notifications
You must be signed in to change notification settings - Fork 18
Components page is temporarily unavailable #75
Comments
Thanks for reporting this issue. We have the same problem and are unable to install/use SW360. |
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? |
@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 |
@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. |
needs retest |
should be retested after this is solved: https://github.com/sw360/sw360chores/issues/new |
We experienced a similar issue with several components (including "Components") shown as being "temporarily unavailable". We used the docker compose from the v2 directory. |
Followed procedure: https://gist.github.com/roycyt/b6ddd241caf734732d1780d5de27a6ec
using latest stable release: sw360-8.1.0-M1
In the fresh install of sw360 via docker chores
We have the sw360-8.1.0-M1
I have imported users as well
and tried to login with different users as well (admin, user etc)
Error log:
Components_ErrorLog.txt
Highlights of error
Also refer https://sw360chat.slack.com/archives/C68C2RYS3/p1586447237060000
The text was updated successfully, but these errors were encountered: