Project

General

Profile

Actions

action #64403

closed

[functional][y][Timebox: 24h] test fails in iscsi_client - Fix service on demand and checks of sockets and service

Added by JERiveraMoya about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 32
Start date:
2020-03-11
Due date:
2020-03-24
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP2-Online-x86_64-iscsi_client_normal_auth_backstore_fileio@64bit fails in
iscsi_client

Test suite description

iSCSI multimachine test suite with manually configure the static network between SUTs.
Authentication: 2way normal authentication, discovery authentication is not configured
Backstore: fileIO
Test data are included in enclosed yaml file.

We need to ensure in the client we start the service on demand and check that the following service should be active and not the current one failing:
systemctl("is-active iscsid.socket");
systemctl("is-active iscsiuio.socket");
systemctl("is-active iscsi.service");

New fix is provided according https://bugzilla.suse.com/show_bug.cgi?id=1160606#c16

Reproducible

Fails since (at least) Build 122.1

Expected result

Last good: 105.4 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by JERiveraMoya about 4 years ago

  • Subject changed from [functional][y] test fails in iscsi_client - Fix service on demand and checks of sockets and service to [functional][y][Timebox: 24h] test fails in iscsi_client - Fix service on demand and checks of sockets and service
Actions #2

Updated by JERiveraMoya about 4 years ago

  • Status changed from New to Workable
Actions #3

Updated by ybonatakis about 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to ybonatakis
Actions #4

Updated by ybonatakis about 4 years ago

So we make it work. the services and the sockets seems just fine. the only thing i changed is set the initiator to (automatic)[[http://aquarius.suse.cz/tests/2039#step/iscsi_client/63]]. After writing configuration we are doing a restart and connection is down. With "manual" startup there is no session available. Side-note from teclator is "if for example after restart you open the client and mark it "keep current state" and connect the target then, after writing the config, the session should be still alive even if set as manual." But i think this would not be necessary as it doesnt seem to be anything wrong and automatic startup makes more sense.

So tomorrow i can commit necessary changes and resolve this.

test for investigation http://aquarius.suse.cz/tests/2039

Actions #5

Updated by ybonatakis about 4 years ago

So we make it work. the services and the sockets seems just fine. the only thing i changed is set the initiator to (automatic)[[http://aquarius.suse.cz/tests/2039#step/iscsi_client/63]]. After writing configuration we are doing a restart and connection is down. With "manual" startup there is no session available. Side-note from teclator is "if for example after restart you open the client and mark it "keep current state" and connect the target then, after writing the config, the session should be still alive even if set as manual.

So tomorrow i can commit necessary changes and resolve this.

test for investigation http://aquarius.suse.cz/tests/2039

Actions #7

Updated by ybonatakis about 4 years ago

  • Status changed from In Progress to Feedback
Actions #8

Updated by ybonatakis about 4 years ago

merged

Actions #9

Updated by riafarov about 4 years ago

  • Target version set to Milestone 32
Actions #10

Updated by JERiveraMoya about 4 years ago

  • Status changed from Feedback to Resolved

We did our part to update the test scenario, now there are still some issues that YaST team needs to tackle regarding recent changes in yast: https://bugzilla.suse.com/show_bug.cgi?id=1166707#c5

Actions

Also available in: Atom PDF