Project

General

Profile

Actions
Copy link

action #124391

closed

test fails in bootloader_start - The command server of powerhmc1 cannot be connected size:M

Added by tinawang123 about 1 year ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
nicksinger
Category:
-
Target version:
openQA Project - Ready
Start date:
2023-02-13
Due date:
% Done:

0%

Estimated time:
Tags:
infra

Description

Motivation

This ticket is to track https://sd.suse.com/servicedesk/customer/portal/1/SD-112262
and share information about the failure:

Failed case: https://openqa.suse.de/tests/10481719#step/bootloader_start/7
Try by manually:
hscroot@powerhmc1:~> lslic -m redcurrant -t syspower
connect: Connection refused
A connection to the Command Server failed.

Try by webpage:
https://powerhmc1.arch.suse.de
Console not Ready
You cannot log on at this time. The console is still initializing and is not yet ready for users to login. Allow the console to finish initializing and then try to login again.

Related issues 1 (0 open — 1 closed)

Related to openQA Infrastructure - action #124685: [qe-tools] Make sure Power8 and Power9 machines can be used with *any* usable HMC (was: move to new powerhmc3.arch.suse.de) size:MResolvednicksinger2023-02-16

Actions
Actions
Copy link
 #2

Updated by JERiveraMoya about 1 year ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by maritawerner about 1 year ago

  • Project changed from openQA Tests to openQA Infrastructure
  • Category deleted (Bugs in existing tests)

I guess this is an infrastructure ticket? It you want to track it in the yam team please move it to your space.

Actions
Copy link
 #5

Updated by okurz about 1 year ago

  • Project changed from openQA Infrastructure to qe-yam

Please track in the yam project. I can't see the SD ticket

Actions
Copy link
 #6

Updated by JERiveraMoya about 1 year ago

  • Project changed from qe-yam to openQA Infrastructure
Actions
Copy link
 #7

Updated by JERiveraMoya about 1 year ago

Under discussion with @Antonio Eisner about reinstalling powerhmc1 on newer VM, as moving to powerhmc3 might require code changes.

Actions
Copy link
 #8

Updated by JERiveraMoya about 1 year ago

shared sd ticket with @okurz in case they need to perform this change.

Actions
Copy link
 #9

Updated by okurz about 1 year ago

  • Tags set to infra
  • Project changed from openQA Infrastructure to qe-yam

still, we can't see the SD ticket. You can share with the user "OSD Admins" in Jira SD, the black+white figure icon.

Actions
Copy link
 #10

Updated by okurz about 1 year ago

  • Related to action #124685: [qe-tools] Make sure Power8 and Power9 machines can be used with *any* usable HMC (was: move to new powerhmc3.arch.suse.de) size:M added
Actions
Copy link
 #11

Updated by okurz about 1 year ago

According to https://sd.suse.com/servicedesk/customer/portal/1/SD-112262 the reboot of powerhmc1 helped. https://sd.suse.com/servicedesk/customer/portal/1/SD-112280 I can't see yet. Now zluo created #124685 . Please tell me if we should try to move to powerhmc3 right now or if for the time being powerhmc1 is usable.

Actions
Copy link
 #12

Updated by JERiveraMoya about 1 year ago

okurz wrote:

According to https://sd.suse.com/servicedesk/customer/portal/1/SD-112262 the reboot of powerhmc1 helped. https://sd.suse.com/servicedesk/customer/portal/1/SD-112280 I can't see yet. Now zluo created #124685 . Please tell me if we should try to move to powerhmc3 right now or if for the time being powerhmc1 is usable.

we cannot connect to hmc: https://powerhmc1.arch.suse.de/

Actions
Copy link
 #13

Updated by tjyrinki_suse about 1 year ago

This seems broken again, maybe a daily reboot could help if nothing else...

Actions
Copy link
 #14

Updated by livdywan about 1 year ago

Regarding powerhmc1.arch.suse.de being unavailable, please note the discussions in Slack

Actions
Copy link
 #15

Updated by JERiveraMoya about 1 year ago

  • Project changed from qe-yam to openQA Infrastructure

Setting correct project, but from the point of view of hmc1 reachability this ticket can be solved as now it is reachable, which one the original issue.
we just need to follow what happen in hmc3 or the changes for hmc1 in #124685

Actions
Copy link
 #16

Updated by okurz about 1 year ago

  • Status changed from New to Blocked
  • Assignee set to nicksinger
  • Target version set to Ready

@tinawang123 please update the ticket according to https://progress.opensuse.org/projects/openqav3/wiki/#Defects

@nicksinger assigning to you to track as you are working on #124685

Actions
Copy link
 #17

Updated by openqa_review about 1 year ago

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

This bug is still referenced in a failing openQA test: default@ppc64le-hmc
https://openqa.suse.de/tests/10718895#step/bootloader/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 28 days if nothing changes in this ticket.

Actions
Copy link
 #18

Updated by nicksinger about 1 year ago

  • Status changed from Blocked to Resolved

powerhmc1 has been recovered, redcurrant was connected, needles where adjusted and tests work again: https://openqa.suse.de/tests/10753893

Actions
Copy link
 #19

Updated by openqa_review about 1 year ago

  • Status changed from Resolved to Feedback

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

This bug is still referenced in a failing openQA test: default@ppc64le-hmc
https://openqa.suse.de/tests/10847618#step/bootloader/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 28 days if nothing changes in this ticket.

Actions
Copy link
 #20

Updated by livdywan about 1 year ago

  • Subject changed from test fails in bootloader_start - The command server of powerhmc1 cannot be connected to test fails in bootloader_start - The command server of powerhmc1 cannot be connected size:M
Actions
Copy link
 #21

Updated by nicksinger about 1 year ago

  • Status changed from Feedback to Resolved

openqa_review wrote:

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

This bug is still referenced in a failing openQA test: default@ppc64le-hmc
https://openqa.suse.de/tests/10847618#step/bootloader/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 28 days if nothing changes in this ticket.

Wrong reference and not related to the topic here. I updated the test and added a proper reference to #126821

Actions
Copy link
 #22

Updated by openqa_review 11 months ago

  • Status changed from Resolved to Feedback

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

This bug is still referenced in a failing openQA test: SAPHanaSR_ScaleUp_PerfOpt_node01@ppc64le-hmc-sap
https://openqa.suse.de/tests/11117776#step/bootloader_start/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 28 days if nothing changes in this ticket.

Actions
Copy link
 #23

Updated by nicksinger 11 months ago

  • Status changed from Feedback to Resolved

Last reference found by host=openqa.suse.de ./openqa-query-for-job-label poo#124391 deleted as it was not related to this ticket here.

Actions
Copy link

Also available in: Atom PDF