Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jobscheduler does not start in staging #382

Closed
niraymak opened this issue Feb 26, 2021 · 1 comment · Fixed by #384
Closed

Jobscheduler does not start in staging #382

niraymak opened this issue Feb 26, 2021 · 1 comment · Fixed by #384
Assignees
Labels
bug Something isn't working

Comments

@niraymak
Copy link
Member

Describe the bug
Jobscheduler does not start on staging environment

Expected behavior
JobScheduler needs to start up properly on staging environment

@niraymak niraymak added the bug Something isn't working label Feb 26, 2021
@niraymak niraymak added this to To do in Sprint 9 - Backend via automation Feb 26, 2021
@niraymak niraymak self-assigned this Feb 26, 2021
@niraymak
Copy link
Member Author

The worker service called: JobScheduler was merged to develop earlier. Unfortunately there were some problems starting. The problems regarding starting were because of mistakes in the docker-compose-staging (and production) files. There was a typo and the JobScheduler was not in the same network as the Identity server and API server.

Another issue found was the JobScheduler not working in a local Docker container due to certificate problems. A new issue was created to find out how we can solve this. For now it is possible to test the JobScheduler locally non Docker.

While testing I encountered a problem where the UserTask layer did not retrieve users so I created a new method for retrieving user tasks including users.

Because there are no unit tests yet for the JobScheduler I created a new issue for it. #381

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant