action #95765
closedProvide more people with administrative access to services on qam2.suse.de, adding ssh keys for existing tools team members
0%
Description
Motivation¶
There were multiple people trying to understand why some jobs were scheduled or not scheduled by qa-maintenance/openQABot, some people were in vacation and others could not help because they had no access
Acceptance Criteria¶
- AC1: SUSE QE Tools team members have access to the machine qam2.suse.de and services within
Suggestions¶
- Add ssh keys of each users manually for now
- Think about how ssh keys could be managed, e.g. based on https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/sshd/users.sls using salt like we do for within OSD infrastructure
Updated by okurz almost 3 years ago
- Copied from action #95221: Provide more people with administrative access to services on qam2.suse.de, at least qa-maintenance/openQABot, i.e. increase bus factor size:M added
Updated by okurz almost 3 years ago
As the problem was raised again in a different context vpelcak provided me access and I can add th ssh keys of everyone that is currently within the tools team
Updated by okurz almost 3 years ago
- Status changed from In Progress to Feedback
I added the SSH keys from https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/sshd/users.sls to both qam.suse.de:/root/.ssh/authorized_keys as well as qam2.suse.de:/root/.ssh/authorized_keys for all current team members excluding sriedel and osukup and jbaier (keys already present) as well as vanastasiadis (no key present in https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/sshd/users.sls)
please everyone from SUSE QE Tools try to login once as root to each machine.
Updated by okurz almost 3 years ago
- Status changed from Feedback to Resolved
was verified to be working for at least two additional members. Added as onboarding step on our team's wiki as well.