redhat-cop / redhat-cop/gitops-catalog
AAP can't create instance in ArgoCD
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 383
- Forks
- 184
- PR merge metrics
- No merged PRs in 30d
Description
I added instance definition to our systems.
The definition for that is here
Argo is giving error stating this requires more privileges. Peshaps such privileges could be set earlier, or at least documented in README?
system:serviceaccount:openshift-gitops:openshift-gitops-argocd-application-controller" cannot create resource "automationcontrollers" in API group "[automationcontroller.ansible.com](http://automationcontroller.ansible.com/)" in the namespace "ansible-automation-platform"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ocp-configs/gitops/mgmt-eu-arrow-lab/argocd-applications/ansible-automation-platform-instance.yaml and the instance definition under ocp-configs/gitops/mgmt-eu-arrow-lab/ansible-automation-platform/; compare them with the reported ArgoCD authorization error. Done means the application controller can create the automationcontroller resource, with the required privilege setup documented in the README if appropriate.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100