action #39809

[functional][u][s390x] ssh connection check shows red border misleading that something is wrong when there is not -> should be no red border

Added by okurz over 1 year ago. Updated 10 months ago.

Status:ResolvedStart date:13/03/2018
Priority:LowDue date:
Assignee:dheidler% Done:

0%

Category:Enhancement to existing tests
Target version:QA - future
Difficulty:easy
Duration:

Description

Observation

https://openqa.suse.de/tests/1946861#step/boot_to_desktop/16 shows https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5319 in action with a red border around the first connection check when the SUT is not yet reachable.

Acceptance criteria

  • AC1 No red border when afterwards everything works fine
  • AC2 Still obvious notice in case the connection can never be established

Suggestions

The ideal case would be to use a grey color which is neutral.
A workaround would be to use the blue color, but not using the wording "soft-fail".

Use same approach as mgriessmeier used in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5319#issuecomment-409203353 to show a blue border seems to be a good choice

Further details

Always latest result in this scenario: latest


Related issues

Copied from openQA Tests - action #33202: [sle][functional][s390x][zkvm][u][hard] test fails in boo... Resolved 13/03/2018 14/08/2018
Copied to openQA Tests - action #39815: [functional][y] logs_from_installation_system always show... Resolved 13/03/2018 12/03/2019

History

#1 Updated by okurz over 1 year ago

  • Copied from action #33202: [sle][functional][s390x][zkvm][u][hard] test fails in boot_to_desktop - still insufficient error reporting, black screen with mouse cursor - we all hate it (was: I hate it) added

#2 Updated by okurz over 1 year ago

  • Estimated time deleted (13.00)

#3 Updated by okurz over 1 year ago

  • Copied to action #39815: [functional][y] logs_from_installation_system always shows a red border but we do not track it as a bug added

#4 Updated by SLindoMansilla over 1 year ago

  • Description updated (diff)

#5 Updated by SLindoMansilla over 1 year ago

  • Description updated (diff)
  • Assignee set to okurz
  • Priority changed from Normal to Low

#6 Updated by okurz over 1 year ago

  • Subject changed from [functional][s390x][u] ssh connection check shows red border misleading that something is wrong when there is not -> should be no red border to [functional][s390x] ssh connection check shows red border misleading that something is wrong when there is not -> should be no red border
  • Due date deleted (11/09/2018)
  • Target version set to future

As discussed with the team, QSF is not convinced in doing that. I am fine with that so let's work on it as a side-project, e.g. outside work hours :)

#7 Updated by okurz over 1 year ago

  • Subject changed from [functional][s390x] ssh connection check shows red border misleading that something is wrong when there is not -> should be no red border to [s390x] ssh connection check shows red border misleading that something is wrong when there is not -> should be no red border

#8 Updated by okurz 12 months ago

  • Status changed from New to Blocked

-> #39815

#9 Updated by okurz 12 months ago

  • Subject changed from [s390x] ssh connection check shows red border misleading that something is wrong when there is not -> should be no red border to [functional][u][s390x] ssh connection check shows red border misleading that something is wrong when there is not -> should be no red border
  • Status changed from Blocked to Workable
  • Assignee deleted (okurz)

We can look into this again, #39815 resolved

#10 Updated by dheidler 10 months ago

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

This seems to be already fixed as of https://openqa.suse.de/tests/2314767

Also available in: Atom PDF