action #36730
closed[sle][functional][y][medium] no route to the host 10.0.2.1 iscsi_client
Added by riafarov almost 6 years ago. Updated over 5 years ago.
0%
Description
Observation¶
Seems that not all workers support required configuration. Need to investigate and potentially set WORKER_CLASS properly
openQA test in scenario sle-15-Installer-DVD-x86_64-iscsi_client@64bit fails in
iscsi_client
workaround¶
- Retrigger, should work if another worker picks the job
Reproducible¶
Fails since (at least) Build 661.1 (current job)
Expected result¶
Last good: 658.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 6 years ago
- Subject changed from [sle][functional][y] no route to the host 10.0.2.1 iscsi_client to [sle][functional][y][fast] no route to the host 10.0.2.1 iscsi_client
- Due date set to 2018-06-19
- Priority changed from Normal to Urgent
- Target version set to Milestone 17
happening in SLE15 GMC. Should be treated urgently.
Updated by riafarov almost 6 years ago
- Subject changed from [sle][functional][y][fast] no route to the host 10.0.2.1 iscsi_client to [sle][functional][y] no route to the host 10.0.2.1 iscsi_client
- Status changed from New to Workable
Updated by mgriessmeier almost 6 years ago
- Subject changed from [sle][functional][y] no route to the host 10.0.2.1 iscsi_client to [sle][functional][y][medium] no route to the host 10.0.2.1 iscsi_client
- Description updated (diff)
- Priority changed from Urgent to High
downrating to High, since we have a workaround by restarting the test
Updated by okurz almost 6 years ago
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5197 merged. But this only improves and does not fix this ticket, right?
Updated by riafarov almost 6 years ago
@okurz, as described in the ticket, we may start configuring client before server configuration is finished. In 2 failed runs when we close xterm, in the video we can see that iscsi server hasn't returned exit code yet. As for original hypothesis, I was not able to identify any differences in the workers configuration.
Updated by okurz almost 6 years ago
- Target version changed from Milestone 17 to Milestone 17
Updated by riafarov almost 6 years ago
Test runs triggered on osd: https://openqa.suse.de/tests/1765737# and previous
Updated by riafarov almost 6 years ago
- Due date changed from 2018-06-19 to 2018-07-03
Wait for verification runs, then block by https://progress.opensuse.org/issues/31351
Updated by riafarov almost 6 years ago
- Blocked by action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally) added
Updated by riafarov almost 6 years ago
- Status changed from Feedback to Blocked
Issue can be reproduced only on SLE 15 and only on osd. Currently test always fails because of performance issues of the VM, required tab cannot be selected, so set to blocked and wait until it we resolve #31351 first.
Updated by riafarov almost 6 years ago
- Due date changed from 2018-07-03 to 2018-07-31
Updated by okurz almost 6 years ago
- Due date changed from 2018-07-31 to 2018-08-14
- Target version changed from Milestone 17 to Milestone 18
riafarov please document your current findings, it's not urgent to fix now. Let's wait for a 15SP1 build and see if it fails there as it currently does not seem to make problems on SLE12SP4
Updated by riafarov almost 6 years ago
- Blocked by deleted (action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally))
Updated by riafarov almost 6 years ago
- Assignee deleted (
riafarov)
So test rarely fails with no route found to the host (~1 per 20 runs), usually tab is not displayed properly, which was addressed with explicit btrfs balancing calls. For SLE 12 SP4 test works stably and there are no issues at all.
There is no clear pattern with workers either, as job may fail or succeeds on the same instance of the same worker. I was not able to reproduce the issue locally in my setup neither, which got broken. So after all it can be related to firewalld, but there is no proof so far. Steps are pretty well synced and this was partly improved with PR mentioned above. Un-assign myself for now. SLE 15 SP1 build fail on registration ATM.
Updated by riafarov almost 6 years ago
- Due date deleted (
2018-08-14) - Priority changed from High to Normal
- Target version changed from Milestone 18 to Milestone 20
As discussed with okurz, revisiting for SLE 15
Updated by riafarov over 5 years ago
- Status changed from Workable to Rejected
- Assignee set to riafarov
Issue not detected for SLE 15-SP1, but we have other issues, like mkfs.ext4 returning non-zero code, I will create ticket for that.