-
Bug
-
Resolution: Done
-
Blocker
-
fuse-7.8-GA
During the test running, we noticed a problem when two Syndesis is installing at the same time. The syndesis-jaeger pod in one namespace is not able to appear and the operator pod has the following error in the log:
E0903 10:49:00.542035 1 reflector.go:178] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:224: Failed to list *v1.PackageManifest: packagemanifests.packages.operators.coreos.com is forbidden: User "system:serviceaccount:syndesis:syndesis-operator" cannot list resource "packagemanifests" in API group "packages.operators.coreos.com" in the namespace "syndesis"
When I have tried to install two syndesis sequentially, everything works.
Probably the issue is caused by `syndesis-operator:install-olm` clusterrolebindings which contains information about one namespace but both syndesis installations are writing to it at the same time.
- apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
labels:
app: syndesis
syndesis.io/app: syndesis
syndesis.io/component: syndesis-operator
syndesis.io/type: operator
name: syndesis-operator:install-olm
subjects:
- kind: ServiceAccount
name: syndesis-operator
namespace: {{ .Namespace }}
Maybe if both installations create their own closterrolebindings (e.g. syndesis-<namespace>-operator:install-olm), the issue will be gone.
- causes
-
-
- Done
-