Project

General

Profile

Actions
Copy link

action #41207

closed

[qe-core][functional][ipmi] test fails in reboot_gnome - seems we call some code which we are not allowed to do, need to "reset_consoles" or something? nearly there to a complete run again :)

Added by okurz over 6 years ago. Updated 7 months ago.

Status:
Rejected
Priority:
Low
Assignee:
szarate
Category:
Bugs in existing tests
Target version:
QA (public) - future
Start date:
2018-09-18
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:
qecore-cleanup

Description

Observation

Installation on an IPMI machine doesn't work for SLE15+.

Reproducible

Fails since SLE15.

Expected result

The test never worked for SLE15

Suggestions

  • Create a separate test suite for only text editors that runs after create_hdd_gnome (For text editors that should_be installed on sles, in this case, just vim for now)
  • Remove text editor tests from default scenarios (vim in this particular case)
  • Schedule reboot test module at the end of the scenario

Acceptance criteria

  • AC1: Test suite default is able to complete installation and post installation test modules for SLE12-SP5+ and SLE15-SP1+ over IPMI
  • AC2: Test suite gnome is able to complete installation and post installation test modules for SLE12-SP5+ and SLE15-SP1+ over IPMI
  • AC3: test module vim runs on it's own separate test suite
  • AC4: Changes are documented in this ticket.

Further details

Always latest result in this scenario:

Related issues 2 (0 open — 2 closed)

Blocked by openQA Tests (public) - coordination #23650: [sle][functional][ipmi][epic][u] Fix test suite gnome to work on ipmi 12-SP3 and 15 (WAS: test fails in boot_from_pxe - connection refused trying to ipmi host over ssh?)ResolvedSLindoMansilla2017-10-20

Actions
Blocked by openQA Tests (public) - action #38423: [sle][functional][u][hard] Refactor first_boot to unify duplicated behavior for remote backendRejectedzluo2018-07-16

Actions
Actions
Copy link
 #1

Updated by okurz about 6 years ago

  • Priority changed from Normal to High
Actions
Copy link
 #2

Updated by szarate about 6 years ago

Still happening, connection to gonzo seems to timeout according to the logs of this test)DIE Error connecting to host : IO::Socket::INET: connect: Connection timed out

Actions
Copy link
 #3

Updated by szarate about 6 years ago

perhaps disconnect from it (the console), and wait until ssh comes back after 1 minute or a bit more?

Actions
Copy link
 #4

Updated by okurz about 6 years ago

except for the "waste time by just blindly waiting"-part, yes :)

Actions
Copy link
 #5

Updated by okurz about 6 years ago

shouldn't there be other tickets about ipmi and that we were never complete? Need to reference

Actions
Copy link
 #6

Updated by okurz about 6 years ago

  • Blocked by coordination #23650: [sle][functional][ipmi][epic][u] Fix test suite gnome to work on ipmi 12-SP3 and 15 (WAS: test fails in boot_from_pxe - connection refused trying to ipmi host over ssh?) added
Actions
Copy link
 #7

Updated by okurz about 6 years ago

  • Status changed from New to Blocked
  • Assignee set to okurz
  • Target version changed from Milestone 20 to Milestone 25+
Actions
Copy link
 #8

Updated by SLindoMansilla over 5 years ago

  • Description updated (diff)

This ticket should follow #23650

Actions
Copy link
 #9

Updated by SLindoMansilla over 5 years ago

  • Description updated (diff)
Actions
Copy link
 #10

Updated by mgriessmeier over 5 years ago

  • Target version changed from Milestone 25+ to Milestone 25

moving to M25 then

Actions
Copy link
 #11

Updated by okurz over 5 years ago

  • Assignee changed from okurz to mgriessmeier

Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.

Actions
Copy link
 #12

Updated by mgriessmeier over 5 years ago

  • Target version changed from Milestone 25 to Milestone 26
Actions
Copy link
 #13

Updated by mgriessmeier over 5 years ago

  • Status changed from Blocked to New
  • Assignee deleted (mgriessmeier)
  • Target version changed from Milestone 26 to Milestone 28

check with 15SP2

Actions
Copy link
 #14

Updated by SLindoMansilla over 5 years ago

  • Blocked by action #38423: [sle][functional][u][hard] Refactor first_boot to unify duplicated behavior for remote backend added
Actions
Copy link
 #15

Updated by SLindoMansilla over 5 years ago

  • Status changed from New to Blocked
Actions
Copy link
 #16

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 28 to Milestone 32
Actions
Copy link
 #17

Updated by tjyrinki_suse about 4 years ago

  • Subject changed from [functional][u][ipmi] test fails in reboot_gnome - seems we call some code which we are not allowed to do, need to "reset_consoles" or something? nearly there to a complete run again :) to [qe-core][functional][ipmi] test fails in reboot_gnome - seems we call some code which we are not allowed to do, need to "reset_consoles" or something? nearly there to a complete run again :)
Actions
Copy link
 #18

Updated by okurz about 4 years ago

  • Status changed from Blocked to Workable

was blocked by #38423 which is "Resolved" by now

Actions
Copy link
 #19

Updated by szarate almost 4 years ago

Are we seriously testing vim in every scenario? https://openqa.suse.de/tests/5443832#step/vim/6

Actions
Copy link
 #20

Updated by okurz almost 4 years ago

Well, it's fast and easy and a simple check of a real application. Don't just see it as a test for "just vim" but "just any console application, with colors! :)"

Actions
Copy link
 #21

Updated by szarate almost 4 years ago

  • Description updated (diff)
Actions
Copy link
 #22

Updated by szarate almost 4 years ago

okurz wrote:

Well, it's fast and easy and a simple check of a real application. Don't just see it as a test for "just vim" but "just any console application, with colors! :)"

it's just a test for vim. If I want to check for color support, https://openqa.suse.de/tests/5476680#step/aplay/15 is a better candidate.

Actions
Copy link
 #23

Updated by maritawerner over 3 years ago

So what is the plan here? Fix it or leave it as is? Or skip it?

Actions
Copy link
 #24

Updated by szarate over 3 years ago

  • Priority changed from High to Normal
Actions
Copy link
 #25

Updated by livdywan over 2 years ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link
 #26

Updated by slo-gin 9 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link
 #27

Updated by mgrifalconi 8 months ago

  • Tags set to qecore-cleanup
  • Status changed from Workable to Rejected
Actions
Copy link
 #28

Updated by okurz 8 months ago

  • Status changed from Rejected to Workable
  • Priority changed from Normal to Low
  • Target version changed from Milestone 32 to future

I think this is still a valid request although granted not high priority. Why did you reject it?

Actions
Copy link
 #30

Updated by szarate 7 months ago

  • Assignee set to szarate

This ticket isn't really needed anymore.

Actions
Copy link
 #31

Updated by szarate 7 months ago

  • Status changed from Workable to Rejected
Actions
Copy link

Also available in: Atom PDF