Closed stobias123 closed 4 years ago
@stobias123 - Strange; can you provide more details about the cluster environment? E.g. is it OpenShift, local Minikube, or something else?
The local directory should be inside the ansible container, and that seems like it shouldn't even have the possibility of failing since it's not on a shared filesystem or PV or anything like that.
vanilla k8s. running on rancher.
This was resolved when I rolled back tower operator image from 0.2.2 to 0.2.1 - haven't tried with more recent images.
Interesting, there weren't any substantial changes in the 0.2 release series, except for the actual Tower version being updated (to I think 3.6.1 or 3.6.2?), so maybe it's an upstream issue with that version of Tower / AWX?
Could be. Feel free to close this issue. I don't see it any longer. Maybe it was some other funky thing I had going on.
On Fri, Feb 28, 2020 at 7:24 AM Jeff Geerling notifications@github.com wrote:
Interesting, there weren't any substantial changes in the 0.2 release series, except for the actual Tower version being updated (to I think 3.6.1 or 3.6.2?), so maybe it's an upstream issue with that version of Tower / AWX?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/geerlingguy/tower-operator/issues/22?email_source=notifications&email_token=AAEQGVN4MYWWYMMTGMQ4KH3RFEUD3A5CNFSM4KXNZ4V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENI4LNY#issuecomment-592561591, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEQGVIMK2GFK7TT3FELU3LRFEUD3ANCNFSM4KXNZ4VQ .
Sounds good. Please re-open if you find it happening again!
Operator container shows the below.