Skip to content

test(robot): add io error test cases#3328

Open
chriscchien wants to merge 1 commit into
longhorn:masterfrom
chriscchien:io_error
Open

test(robot): add io error test cases#3328
chriscchien wants to merge 1 commit into
longhorn:masterfrom
chriscchien:io_error

Conversation

@chriscchien

Copy link
Copy Markdown
Contributor

Which issue(s) this PR fixes:

Add test cases

  • Replica Fails When Filesystem Disk Has I/O Errors
  • Replica Fails When V2 Volume Replica Has I/O Errors

test result:

Issue longhorn/longhorn#12288

What this PR does / why we need it:

Special notes for your reviewer:

Additional documentation or context

@chriscchien chriscchien self-assigned this Apr 24, 2026
@chriscchien chriscchien requested a review from a team as a code owner April 24, 2026 07:32
Comment thread e2e/libs/keywords/io_keywords.py Outdated
Comment thread e2e/libs/keywords/io_keywords.py Outdated
Comment thread e2e/libs/keywords/io_keywords.py Outdated
Comment thread e2e/libs/keywords/io_keywords.py Outdated
Comment thread e2e/libs/keywords/io_keywords.py Outdated
Comment thread e2e/tests/negative/io_error.robot
Comment thread e2e/tests/negative/io_error.robot
Comment thread e2e/tests/negative/io_error.robot
Comment thread e2e/tests/negative/io_error.robot
@yangchiu

Copy link
Copy Markdown
Member

Revisit this after the release.

@yangchiu

yangchiu commented May 7, 2026

Copy link
Copy Markdown
Member

Revisit this after v1.12.0 release.

@mergify

mergify Bot commented May 27, 2026

Copy link
Copy Markdown

This pull request is now in conflict. Could you fix it @chriscchien? 🙏

@yangchiu

yangchiu commented Jun 9, 2026

Copy link
Copy Markdown
Member

More investigation is needed. I'll need some time to clarify the questions raised in the discussion.

@chriscchien chriscchien marked this pull request as draft June 18, 2026 08:56
- Replica Fails When Filesystem Disk Has I/O Errors

longhorn/longhorn#12288

Signed-off-by: Chris Chien <chris.chien@suse.com>
@chriscchien chriscchien marked this pull request as ready for review June 18, 2026 09:23
@chriscchien

Copy link
Copy Markdown
Contributor Author

For v1 volume, the device map path is like below in the test code(in the QA meeting, the device mapper is mount directly from /dev/xvdh, however below method sould also equivalent for this test because since test not guarantee the extra block disk is always exist, using a v1 volume as the backing disk source is a workaround)

/dev/mapper/${dm_device_name}
  -> linear
  -> /dev/longhorn/${disk_name}  (v1 Longhorn base volume)
  -> ext4
  -> mounted at ${mount_path}
  -> added to Longhorn as filesystem disk ${disk_name}
image

For v2 volume, the path should be like below, however there is an issue longhorn/longhorn#13354 need to clarify first

/dev/mapper/${dm_device_name}
  -> linear
  -> /dev/xvdh   (actual disk)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants