Project

General

Profile

Actions
Copy link

action #69754

closed

[y][u] tests fail in bootloader_start for ppc64le - PowerVM workers not available

Added by syrianidou_sofia over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
szarate
Category:
Bugs in existing tests
Target version:
SUSE QA (private) - SLE 15 SP3
Start date:
2020-08-10
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

For the time being, some machines are turned off, see: https://mailman.suse.de/mlarch/SuSE/maxtorhof/2020/maxtorhof.2020.08/msg00005.html

All openqa ppc64le-hmc-single-disk or ppc64le-hmc-4disk test suites fail in bootloader_start or bootloader with the following error message
bootloader_start

Reproducible

Fails since 9th of August (https://openqa.suse.de/tests/4541148)

Expected result

Last good 6th of August (https://openqa.suse.de/tests/4528757)

Related issues 4 (0 open — 4 closed)

Related to qe-yam - action #69406: [y][timeboxed:12h] Fix console switching on PowerVM during installationClosedriafarov2020-07-28

Actions
Related to qe-yam - action #68980: [y] Enable sles+sdk+proxy_SCC_via_YaST on powerVMClosedriafarov2020-07-142020-10-20

Actions
Related to qe-yam - action #68977: [y] Enable btrfs+warnings on powerVMResolvedriafarov2020-07-142020-10-06

Actions
Has duplicate openQA Infrastructure (public) - action #70474: Machine ppc64le-hmc-single-disk is downRejectedriafarov2020-08-25

Actions
Actions
Copy link
 #1

Updated by riafarov over 4 years ago

  • Target version set to SLE 15 SP3

We have issues with powerVM workers due to overheating in the server room. No actions from our side required. I will reject this ticket once machines are back to normal.

Actions
Copy link
 #2

Updated by riafarov over 4 years ago

  • Assignee set to riafarov
Actions
Copy link
 #3

Updated by riafarov over 4 years ago

  • Related to action #69406: [y][timeboxed:12h] Fix console switching on PowerVM during installation added
Actions
Copy link
 #4

Updated by riafarov over 4 years ago

  • Related to action #68980: [y] Enable sles+sdk+proxy_SCC_via_YaST on powerVM added
Actions
Copy link
 #5

Updated by riafarov over 4 years ago

  • Related to action #68977: [y] Enable btrfs+warnings on powerVM added
Actions
Copy link
 #6

Updated by szarate over 4 years ago

  • Subject changed from [y] tests fail in bootloader_start for ppc64le to [y][u] tests fail in bootloader_start for ppc64le - PowerVM workers not available
  • Description updated (diff)
  • Status changed from New to Blocked
  • Assignee changed from riafarov to szarate
Actions
Copy link
 #7

Updated by riafarov over 4 years ago

  • Has duplicate action #70474: Machine ppc64le-hmc-single-disk is down added
Actions
Copy link
 #8

Updated by okurz over 4 years 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/4635805

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"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #9

Updated by okurz over 4 years 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/4635805

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"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #10

Updated by riafarov over 4 years ago

So hmc workers are up and running, but provisioning doesn't work. We need to investigate what goes wrong.

Actions
Copy link
 #11

Updated by okurz over 4 years ago

So I guess it isn't blocked anymore? I am at least not aware of any issues that we would need to wait for

Actions
Copy link
 #12

Updated by tinawang123 over 4 years ago

Still cannot work,
network has some problem:
powerVM machine still has some problems. The network cannot work
Please refer: https://openqa.suse.de/tests/4709665#step/bootloader/16
redcurrant-2 and redcurrant-7 network cannot work.

Actions
Copy link
 #13

Updated by rfan1 over 4 years ago

Add some my findings here:

I booked another setup "huckleberry-1.arch.suse.de" and no issue seen with netboot, and I can find some clue that the network is not accessible on lpar "redcurrant-2"
PowerPC Firmware
Version FW910.11 (VL910_115)

SMS (c) Copyright IBM Corp. 2000,2017 All rights reserved.

Ping Test
Interpartition Logical LAN: U9008.22L.788201A-V4-C2-T1
Speed, Duplex: auto,auto
Client IP Address: 10.162.8.2
Server IP Address: 10.162.0.1
Gateway IP Address: 10.162.63.254
Subnet Mask: 255.255.192.0
Protocol: Standard
Spanning Tree Enabled: 1
Connector Type:
VLAN Priority: 0
VLAN ID: 0
VLAN Tag:

  1. Execute Ping Test

    Navigation keys:
    M = return to Main Menu

    ESC key = return to previous screen X = eXit System Management Services

    Type menu item number and press Enter or select Navigation key:1

                        .---------------------.
                    |  Attempting Ping... |
                    `---------------------'
                     .--------------.
                        |  Ping Failed |
                        `--------------'
Actions
Copy link
 #14

Updated by riafarov about 4 years ago

  • Status changed from Blocked to Resolved

Can be finally resolved, VIOS server is up and running https://openqa.suse.de/tests/4710086#live

Actions
Copy link
 #15

Updated by okurz about 4 years ago

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

This bug is still referenced in a failing openQA test: RAID10@ppc64le-hmc-4disk
https://openqa.suse.de/tests/5032840

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"
  3. The label in the openQA scenario is removed
Actions
Copy link

Also available in: Atom PDF