action #95221
Updated by okurz almost 3 years ago
## Motivation There were multiple people trying to understand why some jobs were scheduled or not scheduled by qa-maintenance/openQABot, e.g. asmorodskyi on 2021-07-08 "I see that there was trigger for Public Cloud job groups 28 minutes whom I can ask for the reasons ? and was it in our "prod" instance or it was someone "personal initiative" ?" https://chat.suse.de/channel/testing?msg=NPuXTpKknF99dhY22 and then there was a discussion what could be done, e.g. it was suggested to use botmaster to run the "bot" which is basically a schedule based script, not a continous service https://chat.suse.de/channel/testing?msg=K4LixBDAMGp248Zzr ## Acceptance Criteria * **AC1:** Users can see the logs of qa-maintenance/openQABot without special accounts * *DONE* ~~**AC2:** **AC2:** Provide tools team members access to this logs~~ -> #9576 logs ## Suggestions * Run services in a way that users can see the logs, e.g. gitlab CI pipeline, botmaster.suse.de, etc. * Maybe https://github.com/openSUSE/openSUSE-release-tools/blob/master/gocd/daily-cleanup.gocd.yaml#L20 can be used as example * We could just deploy user accounts and ssh keys same as for the OSD infrastructure using https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/sshd/users.sls . Likely salt+ansible don't conflict here