Project

General

Profile

action #33337

[tools][functional][medium][pvm][u] Implement proper handling of reconnects

Added by nicksinger about 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Feature requests
Target version:
SUSE QA tests - Milestone 18
Start date:
2018-04-01
Due date:
2018-07-31
% Done:

0%

Estimated time:
Difficulty:
Duration: 87

Description

Motivation

The current implementation of the spvm backend cannot handle reconnects after the installation.
This is most likely caused by "install_and_reboot.pm" not using the right console to switch back to the installer. So
use_ssh_serial_console and/or select_console 'installation' are potential suspects to look into.

Acceptance criteria

AC1: The module install_and_reboot.pm is able to switch back to the installer to continue the reboot timer

Tasks

  • git clone os-autoinst to be ready to adapt the backend
  • TODO nicksinger how to conduct a test?

Related issues

Blocks openQA Project - action #21838: [functional][u][saga] PowerVM backendResolved2017-08-082018-07-31

History

#1 Updated by nicksinger about 2 years ago

  • Copied from action #21838: [functional][u][saga] PowerVM backend added

#2 Updated by nicksinger about 2 years ago

  • Copied from deleted (action #21838: [functional][u][saga] PowerVM backend)

#3 Updated by nicksinger about 2 years ago

  • Blocks action #21838: [functional][u][saga] PowerVM backend added

#4 Updated by nicksinger about 2 years ago

  • Due date set to 2017-04-10
  • Target version changed from Milestone 18 to Milestone 15
  • Start date changed from 2017-08-08 to 2017-04-01

#5 Updated by nicksinger about 2 years ago

  • Due date changed from 2017-04-10 to 2018-04-10
  • Start date changed from 2017-04-01 to 2018-04-01

#6 Updated by okurz about 2 years ago

  • Subject changed from [tools][functional][medium][pvm] Implement proper handling of reconnects to [tools][functional][medium][pvm][u] Implement proper handling of reconnects
  • Description updated (diff)
  • Status changed from New to Workable

#7 Updated by mgriessmeier about 2 years ago

  • Due date changed from 2018-04-10 to 2018-04-24

#8 Updated by okurz about 2 years ago

  • Due date deleted (2018-04-24)
  • Assignee deleted (nicksinger)
  • Target version changed from Milestone 15 to Milestone 17

nsinger: given that you are enthusiastic about setting up servers and writing documentation I doubt we will deliver https://progress.opensuse.org/issues/33337 in S15, can we delay it?

#9 Updated by okurz almost 2 years ago

  • Due date set to 2018-07-17

#10 Updated by okurz almost 2 years ago

  • Target version changed from Milestone 17 to Milestone 17

#11 Updated by okurz almost 2 years ago

  • Target version changed from Milestone 17 to Milestone 18

#12 Updated by okurz almost 2 years ago

  • Due date changed from 2018-07-17 to 2018-07-31
  • Priority changed from Normal to High

#13 Updated by dheidler almost 2 years ago

Is this already resolved with https://progress.opensuse.org/issues/38513 ?

We do have a testrun that goes beyond reboot_after_installation: https://openqa.suse.de/tests/1846505

This is done by calling power_action in reboot_after_installation which calls prepare_system_shutdown from lib/utils.pm.
This function will do:

console('root-ssh')->kill_ssh if check_var('BACKEND', 'ipmi') || check_var('BACKEND', 'spvm');

This seems to properly close the ssh-serial-console connection.

The switch back to the yast screen with its reboot timer is done with this code from reboot_after_installation:

if (check_var('BACKEND', 'spvm')) {
    # this will only work for serial install
    select_console 'novalink-ssh', await_console => 0;
    assert_screen 'rebootnow';
} 

#14 Updated by okurz almost 2 years ago

  • Status changed from Workable to Resolved
  • Assignee set to dheidler

Well, then you solved it, congratulations :)

Also available in: Atom PDF