improve the name of var partition

[pengshanyu]

Resolve: #722

Summary by Sourcery

Tests:

• Improve the logic to detect the /var partition in the test script.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request improves the check_var_partition function in tests/ffi/disk/test.sh by introducing a variable for the partition name, adding a condition for CentOS, and moving debugging commands to improve the detection of the /var partition.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Improved the logic to detect the /var partition by introducing a variable for the partition name and adding a condition for CentOS.	Introduced the var_partition_name variable to store the partition name. Modified the conditional logic to use var_partition_name instead of qm_var_partition. Added a condition to set var_partition_name specifically for CentOS based on the OS release ID.	tests/ffi/disk/test.sh
Moved lsblk and df -kh commands before the conditional check for the /var partition.	Moved lsblk and df -kh commands to execute before the conditional check to aid in debugging.	tests/ffi/disk/test.sh

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @pengshanyu - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider using more descriptive variable names than var_partition_name to improve readability.
• The lsblk and df -kh commands are helpful for debugging, but should be removed before merging.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[pengshanyu]

I'm not sure why there are failures of SRPM build failed/copying system image from manifest list: parsing image configuration: fetching blob: received unexpected HTTP status: 502 Bad Gateway INFO: Pulling image: registry.fedoraproject.org/fedora:41
Hi @Yarboa @dougsland , could you help to take a look, thanks.

[Yarboa]

Please refer that, I assume it will be online soon
b'Trying to pull registry.fedoraproject.org/fedora:41...\nError: copying system image from manifest list: parsing image configuration: fetching blob: received unexpected HTTP status: 502 Bad Gateway\n'
INFO: Pulling image: registry.fedoraproject.org/fedora:41

[Yarboa]

@pengshanyu So if this solves #722
I see this part
https://github.com/containers/qm/blob/main/tests/ffi/common/prepare.sh#L75-L79
still exist, I assume it should be replaced by that #727 isnt it?