Fixing the lexical error Hello-world test

[ramdrvcs]

it has been already pushed on the main branch
and the reference PR #2509

While I was running the E2E tests, I had the follwing error for hello-world module.

fatal: [west]: FAILED! => {"attempts": 30, "changed": true, "msg": "Task failed: Action failed: Unknown error.", "rc": 1, "return_code": 1, 
"stderr": "cannot parse the data: `lexical error: invalid character inside string.\n
{\"user\":{\"uid\":0,\"gid\":0,\"addi\n                     (right here) ------^\n`\n",
"stderr_lines": ["cannot parse the data: `lexical error: invalid character inside string.", " 
{\"user\":{\"uid\":0,\"gid\":0,\"addi", "                     (right here) ------^", "`"], 
"stdout": "", "stdout_lines": []}

Description

Fixes a critical runtime failure in the run_curl role where the task fails with an Unknown error (lexical error: invalid character inside string).

The failure occurs because ansible task definition contain end of line character in sh location. As of now it has been noticed in s390x.

Changes

Key Changes

• Single Network Call (curl -s -w "\n%{http_code}" "{{ run_curl_address }}"): Reduces traffic by making exactly one request to the backend. The API response text is captured alongside the 3-digit HTTP status code, which is appended to a brand-new line at the very bottom.
• Local Code Extraction (tail -n 1): Pipes the combined response string and isolates only the final line to extract the HTTP status code.
• Local Body Preservation (sed "$ d"): Trims the appended status code line from the stream, safely preserving the original API message body (including any native trailing text or newlines).
• Defensive String Evaluation ([ "$code" = "200" ]): Switches the conditional check to a robust string comparison. This protects the shell executor from crashing if network drops cause the status code to return empty.
• Clean YAML Syntax: Formatted using the folded block scalar (>) to preserve intended script indentation and readability without breaking the Kubernetes command processor array.

Testing Triaged

• Verified that payloads containing nested JSON quotes no longer trigger a lexical error.
• Confirmed that the loop correctly runs exactly one HTTP request per retry iteration.
• Confirmed the task successfully completed.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 24e711ac-32dd-4101-bd0b-909cc29d3063

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[hash-d]

lgtm