ci: update longhorn-e2e-test pipeline for new HAL environment

[chriscchien]

Which issue(s) this PR fixes:

What this PR does / why we need it:

Update longhorn-e2e-test pipeline for running new HAL environment

Special notes for your reviewer:

Running Test Volume Basic(both v1 and v2 volume) passed on my local after connected to infraVPN

Additional documentation or context

N/A

Summary by CodeRabbit

• Bug Fixes

  • Corrected a typographical error in a build output message for clearer logging.

• Chores

  • Updated configuration settings for machine resources, reflecting revised image and network parameters to ensure accurate resource allocation.

[coderabbitai]

Walkthrough

This pull request makes two changes. First, it corrects a typographical error in the echo statement within the build stage of the Jenkinsfile. Second, it updates the Terraform configuration for SLES machine resources by modifying the imageName and networkName fields in the disk and network information sections. No changes were made to the control flow or exported entities.

Changes

File(s)	Change Summary
pipelines/e2e/Jenkinsfile	Fixed typo in the echo statement during the build stage by changing "Using registration coce: $REGISTRATION_CODE_ID" to "Using registration code: $REGISTRATION_CODE_ID".
test_framework/terraform/…/sles/main.tf	Updated imageName from "longhorn-qa/image-qn4cg" to "longhorn-qa/image-pqjk7" and networkName from "longhorn-qa/vlan104" to "longhorn-qa/vlan-2011" for both machine configurations.

Possibly related PRs

• ci: support sles for hal cluster #2149: Addresses similar adjustments in the handling of the registration code variable for SLES, specifically related to variable declarations.

Suggested reviewers

• khushboo-rancher
• roger-ryao

Poem

I'm a rabbit hopping with cheer,
Fixing typos so the message is clear.
Configs updated with a swift little nudge,
Tracking the code without any grudge.
Hooray for changes, carrots in sight,
May our code always shine bright! 🥕

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0f442b5 and 0bfea1e.

📒 Files selected for processing (2)

• pipelines/e2e/Jenkinsfile (1 hunks)
• test_framework/terraform/harvester/sles/main.tf (4 hunks)

✅ Files skipped from review due to trivial changes (1)

• pipelines/e2e/Jenkinsfile

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Build images
• GitHub Check: Summary

🔇 Additional comments (4)

test_framework/terraform/harvester/sles/main.tf (4)

48-56: Confirm Updated Disk Image for Controlplane Resource
The imageName field in the disk configuration was updated to "longhorn-qa/image-pqjk7". Please verify that this new image identifier is correct and available in the new HAL environment.

---

58-64: Validate Network Name for Controlplane Resource
The networkName field has been modified from the old value (presumably "longhorn-qa/vlan104") to "longhorn-qa/vlan-2011". Ensure that this new network name matches the correct network setup in the updated HAL environment.

---

95-108: Confirm Updated Disk Image for Worker Resource
Within the worker machine configuration, the imageName has been updated to "longhorn-qa/image-pqjk7". As with the controlplane resource, please verify that this new image identifier is correctly configured and available.

---

110-116: Validate Network Name for Worker Resource
The networkName for the worker configuration has been changed to "longhorn-qa/vlan-2011". Make sure that this conforms to the expected network configuration in the HAL environment and is correctly provisioned for worker nodes.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.