System test-suite CI should handle scc configuration for service accounts [DBZ-3928]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-3928](https://issues.redhat.com/browse/DBZ-3928)
{code:java}
oc project ${OCP_PROJECT_SQLSERVER}
oc adm policy add-scc-to-user anyuid system:serviceaccount:${OCP_PROJECT_SQLSERVER}:default
oc project ${OCP_PROJECT_MONGO}
oc adm policy add-scc-to-user anyuid system:serviceaccount:${OCP_PROJECT_MONGO}:default
oc project ${OCP_PROJECT_DB2}
oc adm policy add-scc-to-user anyuid system:serviceaccount:${OCP_PROJECT_DB2}:default
oc adm policy add-scc-to-user privileged system:serviceaccount:${OCP_PROJECT_DB2}:default{code}
Contributor guide
Research direction
Start by locating the system test-suite CI configuration and search for OCP_PROJECT_SQLSERVER, OCP_PROJECT_MONGO, or OCP_PROJECT_DB2. Compare the existing service-account setup with the listed SCC commands, then verify that the CI configuration applies the required permissions for each project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100