-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Description
Feature request
What did you do?
I upgraded to the latest ansible-operator and ansible-runner versions. I then ran make run
via the Makefile generated by the operator-sdk create api
. The ansible-operator would launch and connect but as soon as the socket became available it would try to launch ansible-runner
and fail. The failure was due to ansible-runner > 2.0.0
changing the order required for parameter input.
What did you expect to see?
I'm guessing compatability with ansible-runner > 2.0.0
just simply has not been implemented yet so let me know if a bug is not the appropriate thing to do here. I expected to see a functional ansible-runner
exec via ansible-operator
.
What did you see instead? Under which circumstances?
The parameters supplied to ansible-runner
via this code block are wrong. All of them need to be moved. They should instead be appended after the run
command (when and only when ansible-runner version > 2.0.0
).
Environment
Operator type:
/language ansible
Kubernetes cluster type:
$ operator-sdk version
operator-sdk version: "v1.9.0", commit: "205e0a0c2df0715d133fbe2741db382c9c75a341", kubernetes version: "1.20.2", go version: "go1.16.5", GOOS: "linux", GOARCH: "amd64"
$ go version
(if language is Go)
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.4", GitCommit:"e87da0bd6e03ec3fea7933c4b5263d151aafd07c", GitTreeState:"clean", BuildDate:"2021-02-18T16:12:00Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.10", GitCommit:"a84e568eeb56c4e3966314fc2d58374febd12ed7", GitTreeState:"clean", BuildDate:"2021-03-09T14:35:22Z", GoVersion:"go1.13.15 BoringCrypto", Compiler:"gc", Platform:"linux/amd64"}
Possible Solution
Described above.