Project

General

Profile

action #15740

hostname.pm: Network setup won't persist on Xen

Added by michalnowak almost 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
michalnowak
Category:
Bugs in existing tests
Target version:
-
Start date:
2017-01-02
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

https://openqa.suse.de/tests/692200#step/yast2_lan/12

On qemu backend as well as KVM via svirt backend hostname and domain name are set to 'susetest' and '', respectively. However, on Xen HVM via svirt backend it's '1c137' and 'qa.suse.de', respectively.

The difference between qemu/KVM and Xen via svirt is that the former use user-mode networking and the latter bridged.

tests/console/hostname.pm:

    script_run "systemctl status network.service";
    save_screenshot;
    assert_script_run "if systemctl -q is-active network.service; then systemctl reload-or-restart network.service; fi";

After the systemctl reload-or-restart network.service the hostmane/domain name is re-set on Xen.

History

#1 Updated by michalnowak almost 5 years ago

  • Status changed from New to Feedback

#2 Updated by michalnowak almost 5 years ago

  • Status changed from Feedback to In Progress

Taking different approach.

#3 Updated by michalnowak almost 5 years ago

  • Status changed from In Progress to Feedback

#4 Updated by michalnowak almost 5 years ago

Strangely once redefine_svirt_domain.pm is not used, network behaves as we are used to. Reverting those code changes and needle:

https://gitlab.suse.de/openqa/os-autoinst-needles-sles/merge_requests/288
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2328

#5 Updated by michalnowak almost 5 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF