-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sap_swpm: incorrect label in loop in swpm.yml #681
Comments
Did you check previous step in execution log that it registered that variable? It is possible it did not find any files, therefore item was not defined. I have been running it in current state and I never had this issue with .item.
|
@rnozaki I had the same error when testing an S/4HANA Foundation 2022 installation last week but I could not finish my investigation. Trying to reproduce it again now and also testing the solution you proposed. |
As I mentioned, I tested the new code with the exact same conditions it was working before. Have you executed this code in your environment? |
That is why I was mentioning previous step. It would be good to know what was actual content of your "{{ swpm_output_sapcontrol_files }}" variable and if it contains array with items. I have run this role 20+ times over last 2 weeks (ASCS/ERS, S4H, NW) and it never failed with this error, even if SWPM was successful or failed. |
Have you run it in the last 3 days? Because this is when the PR 665 was merged. |
Sorry @rnozaki , it seems @berndfinger moved his PR and it changed items as you said. I have not tested it with his PR. You can disregard my comments. |
@rnozaki @marcelmamula In #665, I overlooked the fact that the loop variable from the task |
Solved in #682. |
FYI - Test playbook for those who want to reproduce the problem:
|
I noticed that 2 tasks above there was a recent change adding the loop_var under loop_control.
So I updated the code:
a. From: label: "{{ file_output.item }}"
b. To: label: "{{ file_output.line_item }}"
With this update, the playbook was re-executed without error.
The text was updated successfully, but these errors were encountered: