Bugzilla – Bug 1220740
Recreate testing environment for SUSE#1220066 & SUSE#1220711
Last modified: 2024-04-10 15:32:14 UTC
Hello IBM, Daniel would like to work on: Bug 1207781 - SLES15SP5: Not able to inject the Error on Redfish adapter in nvmf mode on ZZ gen4 server (lpfc/Redfish/nvme_core/P9) This bug corresponds to LTC bug: https://bugzilla.linux.ibm.com/show_bug.cgi?id=201000 Could you please do the arrangements in Yellow Zone for Daniel to work on this issue? Thanks for your support.
(In reply to Héctor Orón Martínez from comment #0) > Hello IBM, > > Daniel would like to work on: > > Bug 1207781 - SLES15SP5: Not able to inject the Error on Redfish adapter > in nvmf mode on ZZ gen4 server (lpfc/Redfish/nvme_core/P9) > > This bug corresponds to LTC bug: > https://bugzilla.linux.ibm.com/show_bug.cgi?id=201000 > > Could you please do the arrangements in Yellow Zone for Daniel to work on > this issue? > > Thanks for your support. Hello SUSE, The IBM LTC Bug 201000 (mirror of the SUSE-Bug 1207781) has been closed. Do you wish IBM to reopen it? Thank you for your support.
Hello IBM, SUSE developers still think having a test environment for checking bugs like https://bugzilla.suse.com/show_bug.cgi?id=1220066 would be great to have at YZ.
Note, SUSE1220066 is equivalent to LTC bug: - https://bugzilla.linux.ibm.com/show_bug.cgi?id=205063
Creating this environment should also help resolving LTC bug: - https://bugzilla.linux.ibm.com/show_bug.cgi?id=205755 - SUSE https://bugzilla.suse.com/show_bug.cgi?id=1220711
Hello IBM, I am raising priority here and severity since this is blocking investigating a fix for bug 1220711, which release managers want to see fixed ASAP. Please share any update when possible. Thanks very much for your support.
(In reply to Héctor Orón Martínez from comment #5) > Hello IBM, > > I am raising priority here and severity since this is blocking > investigating a fix for bug 1220711, which release managers want to see > fixed ASAP. > > Please share any update when possible. Thanks very much for your support. Hello Hector, Can we close this Yellow Zone Bug? As per the Comment 21 of the SUSE Bug 1220711 (mirror is Comment 28 by Kyle Mahlkuch of the LTC Bug 205755), the environment has been set up to recreate the bug. Thank you for your support.
(In reply to Géry Schneider from comment #6) > Can we close this Yellow Zone Bug? Allow me to convey to the team. > As per the Comment 21 of the SUSE Bug 1220711 (mirror is Comment 28 by Kyle > Mahlkuch of the LTC Bug 205755), the environment has been set up to recreate > the bug. Great news! Could you share which LPAR needs to be used for testing? Thanks for your support.
------- Comment From Piyush.Sachdeva@ibm.com 2024-03-28 04:10 EDT------- (In reply to comment #16) > (In reply to G?ry Schneider from comment #6) > > > Can we close this Yellow Zone Bug? > > Allow me to convey to the team. > > > As per the Comment 21 of the SUSE Bug 1220711 (mirror is Comment 28 by Kyle > > Mahlkuch of the LTC Bug 205755), the environment has been set up to recreate > > the bug. > > Great news! Could you share which LPAR needs to be used for testing? > > Thanks for your support. Hello SUSE, The YZ lpar environment has been created and is ready to be used. suyz-rain001-lp12 - root/abc123 Please, do let me know in case something doesn't work.
------- Comment From gery.schneider@fr.ibm.com 2024-03-29 07:48 EDT------- (In reply to comment #17) > (In reply to comment #16) > > (In reply to G?ry Schneider from comment #6) > > > > > Can we close this Yellow Zone Bug? > > > > Allow me to convey to the team. > > > > > As per the Comment 21 of the SUSE Bug 1220711 (mirror is Comment 28 by Kyle > > > Mahlkuch of the LTC Bug 205755), the environment has been set up to recreate > > > the bug. > > > > Great news! Could you share which LPAR needs to be used for testing? > > > > Thanks for your support. > > Hello SUSE, > The YZ lpar environment has been created and is ready to be used. > suyz-rain001-lp12 - root/abc123 > > Please, do let me know in case something doesn't work. Hello Hector, I am closing this bug as per the comment above. Please reopen it if needed. Thank you all for your support.
I've tried to replicate the bug in https://bugzilla.suse.com/show_bug.cgi?id=1220711 while I was able to login and the lpar and hmc, it seems I unable to perform the device removal: > hscroot@suseyz-hmc2:~> chhwres -r io --rsubtype slot -m suyz-rain001 -o r --id 7 -l 21010030 > HSCL2957 Either there is currently no RMC connection between the > management console and the partition 7 or the partition does not > support dynamic partitioning operations. Verify the network setup > on the management console and the partition and ensure that any > firewall authentication between the management console and the > partition has occurred. Run the management console diagrmc > command to identify problems that might be causing no RMC connection.
(In reply to Daniel Wagner from comment #10) > I've tried to replicate the bug in > > https://bugzilla.suse.com/show_bug.cgi?id=1220711 > > while I was able to login and the lpar and hmc, it seems I unable > to perform the device removal: > > > hscroot@suseyz-hmc2:~> chhwres -r io --rsubtype slot -m suyz-rain001 -o r --id 7 -l 21010030 > > HSCL2957 Either there is currently no RMC connection between the > > management console and the partition 7 or the partition does not > > support dynamic partitioning operations. Verify the network setup > > on the management console and the partition and ensure that any > > firewall authentication between the management console and the > > partition has occurred. Run the management console diagrmc > > command to identify problems that might be causing no RMC connection. This is probably related to the fact we have no access to IBM Power tools repository from within YZ. We are looking into it via private email. I'll update here if there is any progress, for now, packages might need to be synced manually by copying them to the YZ machines from local host.
IBM power tools repo is also discussed in https://bugzilla.suse.com/show_bug.cgi?id=1192114
In my case it is not a missing package, I can't change the lpar configuration, which is essential for testing the EEH fallouts.
(In reply to Daniel Wagner from comment #13) > In my case it is not a missing package, I can't change the lpar > configuration, which is essential for testing the EEH fallouts. Discussing with Piyush (IBM) in a call, he mentioned packages should be installed, but after first removal, RMC connection goes down, they are investigating it.
------- Comment From gery.schneider@fr.ibm.com 2024-04-10 11:28 EDT------- (In reply to comment #23) > (In reply to Daniel Wagner from comment #13) > > In my case it is not a missing package, I can't change the lpar > > configuration, which is essential for testing the EEH fallouts. > > Discussing with Piyush (IBM) in a call, he mentioned packages should be > installed, but after first removal, RMC connection goes down, they are > investigating it. Hello SUSE, As agreed upon in the SUSE-IBM POWER meeting today, I am reopening this bug with a lower Prio/Sev (P3/Normal): IBM power tools repo still needed to recreate the environment (for Bug 205755, etc.) but there is a workaround. Thank you for your support.