You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did you expect to see?
Successful run of local Ansible Operator for both Ambrosia and AcmeAgent resources.
What did you see instead? Under which circumstances?
INFO[0000] Running the operator locally.
INFO[0000] Go Version: go1.10.3
INFO[0000] Go OS/Arch: linux/amd64
INFO[0000] Version of operator-sdk: v0.4.0
INFO[0000] Watching myproject namespace.
{"level":"info","ts":1548067633.9967425,"logger":"leader","msg":"Trying to become the leader."}
{"level":"info","ts":1548067633.997802,"logger":"leader","msg":"Skipping leader election; not running in a cluster."}
{"level":"info","ts":1548067634.005074,"logger":"proxy","msg":"Starting to serve","Address":"127.0.0.1:8888"}
{"level":"info","ts":1548067634.050625,"logger":"ansible-controller","msg":"Watching resource","Options.Group":"analytics.acmecorp.com","Options.Version":"v1alpha1","Options.Kind":"Ambrosia"}
{"level":"info","ts":1548067634.054066,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"ambrosia-controller","source":"kind source: analytics.acmecorp.com/v1alpha1, Kind=Ambrosia"}
{"level":"info","ts":1548067634.0556498,"logger":"ansible-controller","msg":"Watching resource","Options.Group":"analytics.acmecorp.com","Options.Version":"v1alpha1","Options.Kind":"AcmeAgent"}
{"level":"info","ts":1548067634.056412,"logger":"ansible-controller","msg":"Version already registered... skipping"}
FATA[0000] failed to add controller
Environment
operator-sdk version:
0.4.0
Kubernetes cluster kind:
Ambrosia and AcmeAgent
Are you writing your operator in ansible, helm, or go?
Ansible
Additional context
In Operator SDK 0.3.0 this was working as expected:
Bug Report
What did you do?
Run Operator SDK with next command:
with next content in
watches.yaml
:What did you expect to see?
Successful run of local Ansible Operator for both
Ambrosia
andAcmeAgent
resources.What did you see instead? Under which circumstances?
Environment
operator-sdk version:
0.4.0
Kubernetes cluster kind:
Ambrosia
andAcmeAgent
Are you writing your operator in ansible, helm, or go?
Ansible
Additional context
In Operator SDK 0.3.0 this was working as expected:
Also when I remove one of the watched resources in
watches.yaml
everything works as expected again.Seems like Operator SDK 0.4.0 doesn't like multiple watched resources for Ansible.
The text was updated successfully, but these errors were encountered: