Andrey Klyachkin

It is a real example, I built it on my mac before posting and deployed the same function on 2 clusters - one on x86 and one on ppc64le. golang-http/Dockerfile:...

ansible-navigator can be installed and works on IBM Power (ppc64le). The problem is usually too old version of oniguruma in some Linux distros. If it is reinstalled, everything works as...

The issue is not about lpp_source name format, but about error reporting. If it doesn't work with the lpp_source provided, it MUST report the error and set the task to...

Sorry, I don't use any flags in any commands. I use IBM's provided ansible module. E.g. as for now I see another error message on another server: ``` "meta": {...

The whole playbook is posted in the first message.

Please provide information what you want to see in the output. There is no NIM command in the verbose output and the only error information I posted above. I can't...

I posted above the whole meta section. I post it again: ``` "meta": { "nimclient": { "messages": [ "Cannot get oslevel from lpp source name: 7200-05-03_current" ] }, "messages": []...

The localhost is NIM server where the playbook is. There is no inventory, because I don't need it for the example and we don't have many NIM servers, where NIM...

> the lpp_source name does not follow the required format based on the current design. please change to: xxxx-xx-xx-xxxx-lpp_source > > You would keep hitting the same message without changing...

Here was wrong info from my side. With the lpp_source named according to your undocumented rules, the server is being updated. Still the issue with ignoring errors persist.