action #69754
closed
[y][u] tests fail in bootloader_start for ppc64le - PowerVM workers not available
Added by syrianidou_sofia almost 4 years ago.
Updated over 3 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - SLE 15 SP3
- 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.
- Related to action #69406: [y][timeboxed:12h] Fix console switching on PowerVM during installation added
- Related to action #68980: [y] Enable sles+sdk+proxy_SCC_via_YaST on powerVM added
- Related to action #68977: [y] Enable btrfs+warnings on powerVM added
- 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
- Has duplicate action #70474: Machine ppc64le-hmc-single-disk is down added
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
So hmc workers are up and running, but provisioning doesn't work. We need to investigate what goes wrong.
So I guess it isn't blocked anymore? I am at least not aware of any issues that we would need to wait for
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:
-
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 |
`--------------'
- Status changed from Blocked to Resolved
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Also available in: Atom
PDF