Installation via OLM in specific namespace fails
See original GitHub issueDescribe the bug
Following the steps https://enmasse.io/documentation/master/openshift/#assembly-installing-configuring-olm-messaging to deploy enmasse via OLM in a specific namespace leads into a failed installation of the operator and the error shown is unable to adopt APIService
To Reproduce Follow the steps https://enmasse.io/documentation/master/openshift/#assembly-installing-configuring-olm-messaging
Expected behavior enmasse successfully installed in namespace enmasse-infra via OLM
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Install your operator with OLM | Operator Lifecycle Manager
If the ClusterServiceVersion fails to show up or does not reach the Succeeded phase, please check the troubleshooting documentation to debug your installation....
Read more >Installing Operators in your namespace - User tasks
Choose a specific namespace in which to install the Operator. ... If a volumeMount references a volume that does not exist, OLM fails...
Read more >1831081 – The OLM "where to install operator" dialog does ...
Created attachment 1684880 [details] Screenshot of install error Reproduce 1. Log in as kubeadmin 2. Go to openshift-operators namespace to look at what...
Read more >Installing Operators in your namespace - User tasks | OKD 4.9
Choose a specific namespace in which to install the Operator. ... If a volumeMount references a volume that does not exist, OLM fails...
Read more >Troubleshooting | olm-book - GitHub Pages
The CSV is failing because its install strategy changes some immutable field of an existing Deployment . This usually happens on upgrade, after...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@famartinrh The problem is that the fsGroup was applied to the address-space-controller, which was wrong. It should only be applied to standard-authservice. Another PR is required to ensure that it is applied/not applied to brokers though.
yes