sap_swpm: New functionality to push SUM through the manual steps

[rob0d]

This will push SUM through the manual steps in order to fully automate the installation of the system when sap_swpm_sum_start is enabled.

If SWPM is in observer mode, it will not do anything as SWPM waits for SUM to complete.

[berndfinger]

@rob0d Thanks for this contribution, this looks really cool and seems to be nice additional functionality without adding too much complexity. Will soon have some time for testing.

[berndfinger]

@rob0d - I'd ran a first test but it timed out in task Checking the status of SUM after 60 retries. Can you please explain which SAP software you used and if and how you prepared the test? I will then try to use the same scenario for my next test.

[rob0d]

Hi @berndfinger, Can you check what was the response from ansible.builtin.uri on line 8 of roles/sap_swpm/tasks/post_install/sum_push_to_finish.yml? It couldn't connect or the response wasn't what it expected (tests on line 20)? If it's still running or if you can restart it try connecting to the SUM URL and check what it says there.

Also did you provide stack file to SUM? For SUM to start correctly and start executing you need to set the following (at least this is what I set: sap_swpm_mp_stack_path: sap_swpm_mp_stack_file_name: . #MPStack{{ sap_system_sid }}.xml sap_swpm_configure_tms: 'true' sap_swpm_sum_prepare: 'true' sap_swpm_sum_start: 'true' sap_swpm_tmsadm_password:

[berndfinger]

Hi @berndfinger, Can you check what was the response from ansible.builtin.uri on line 8 of roles/sap_swpm/tasks/post_install/sum_push_to_finish.yml? It couldn't connect or the response wasn't what it expected (tests on line 20)? If it's still running or if you can restart it try connecting to the SUM URL and check what it says there.

It couldn't connect, and the reply of a wget --no-check-certificate on the URL was:

HTTP request sent, awaiting response... 404 Not Found

But it is probably related to the missing parameters for SUM to start correctly. To prepare for this, I need more time for preparing and testing with a MP stack file. Unfortunately, I also have to work on some other open issues and PRs for this collection so I cannot immediately continue with testing this PR.

But maybe someone else can jump in and test the proposed code?

@rob0d Can you please provide more details about the software you configured in Maintenance Planner (e.g. product name, version, any additional selections)?

[rob0d]

Hi @berndfinger,

It looks like the SUM wasn't started by SWPM due to the missing parameters.

The process with Maintenance Planner is something like this:

• Create maintenance transaction in MP. I am using S/4 HANA 2023 with all current patches.
• Download the XML file.
• Download all the other files (or use Ansible role to do it).
• Set the parameters above and point it at the XML file.
• Run SWPM, it should start SUM.
• SUM will run for a while until it stops for a prompt. This is the point the Ansible SUM script takes over. It keeps checking and waiting until SUM is in the correct phase then does a POST to move it to the next step.
• The next step is the main upgrade which on our systems takes 8 hours (full S/4 HANA SP1 + all patches). Again, Ansible script loops and waits until SUM reaches the end of the process.
• There is a prompt at this stage asking for SPAU processing. As this is a new install, we just tick the box and continue.
• Finally Ansible script waits for SUM to complete the processing and the swpm role finishes.