Project

General

Profile

action #102224

[qe-core] test fails in network_hostname - incorrect hostname + test runs in full blown installation

Added by szarate 9 months ago. Updated 2 months ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Spike/Research
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP4-Online-x86_64-network_configuration@64bit fails in
network_hostname

Test suite description

Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainer: jrivera@suse.com Verify that DHCLIENT_SET_HOSTNAME preloaded from control file does not overwrite the customer selection and check the hostname in the installed system

Reproducible

Fails since (at least) Build 43.1

Further details

Always latest result in this scenario: latest

notes

As a plus, this test can be moved to an extratest at the end, with the corresponding soft failure.

Also see: https://bugzilla.suse.com/show_bug.cgi?id=1162987

Acceptance Criteria

AC1: Move network_hostname to when booting from already installed HDD.


Related issues

Related to openQA Tests - coordination #95935: [epic][qe-core] Limit installation tests by depending more on the create_hdd_* jobs.New

History

#1 Updated by szarate 9 months ago

  • Related to coordination #95935: [epic][qe-core] Limit installation tests by depending more on the create_hdd_* jobs. added

#2 Updated by szarate 9 months ago

  • Subject changed from [qe-core] test fails in network_hostname - incorrect hostname to [qe-core] test fails in network_hostname - incorrect hostname + test runs in full blown installation

#3 Updated by openqa_review 9 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: network_configuration
https://openqa.suse.de/tests/7716745

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#4 Updated by tjyrinki_suse 9 months ago

  • Status changed from New to Workable
  • Start date deleted (2021-11-10)

#5 Updated by tjyrinki_suse 9 months ago

  • Status changed from Workable to New

Probably needs refining together.

#6 Updated by openqa_review 8 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: network_configuration
https://openqa.suse.de/tests/7805904

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#7 Updated by openqa_review 8 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: network_configuration
https://openqa.suse.de/tests/7887830

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#8 Updated by openqa_review 7 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: network_configuration
https://openqa.suse.de/tests/7924210

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#9 Updated by openqa_review 7 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: network_configuration
https://openqa.suse.de/tests/7977286

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#10 Updated by openqa_review 7 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: network_configuration
https://openqa.suse.de/tests/8089615

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#11 Updated by tjyrinki_suse 6 months ago

  • Category changed from Bugs in existing tests to Spike/Research
  • Status changed from New to Workable

#12 Updated by tjyrinki_suse 6 months ago

Needs investigation whether we are able to debug this problem.

#13 Updated by tjyrinki_suse 6 months ago

  • Description updated (diff)
  • Target version deleted (QE-Core: Ready)

#14 Updated by tjyrinki_suse 6 months ago

  • Status changed from Workable to New

#15 Updated by tjyrinki_suse 6 months ago

Needs refinement in the description to be workable.

#16 Updated by tjyrinki_suse 6 months ago

  • Parent task set to #107323

#17 Updated by apappas 6 months ago

  • Status changed from New to Workable

Refinement:

  1. Why should we run this test?

#18 Updated by openqa_review 5 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: network_configuration
https://openqa.suse.de/tests/8292431

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

#19 Updated by tjyrinki_suse 5 months ago

Discussed with Joaquin, there are changes needed for newer product and notes will be also at:

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14565

#20 Updated by openqa_review 4 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: network_configuration
https://openqa.suse.de/tests/8558425#step/network_hostname/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 52 days if nothing changes in this ticket.

#21 Updated by openqa_review 2 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: network_configuration
https://openqa.suse.de/tests/8752538#step/network_hostname/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 104 days if nothing changes in this ticket.

Also available in: Atom PDF