Multiple issues found on Ubuntu 20.04 against drmgr
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
High
|
Ubuntu on IBM Power Systems Bug Triage | ||
powerpc-utils (Ubuntu) |
Fix Released
|
High
|
Patricia Domingues | ||
Focal |
Fix Released
|
Undecided
|
Patricia Domingues | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Lunar |
Fix Released
|
Undecided
|
Unassigned | ||
Mantic |
Fix Released
|
High
|
Patricia Domingues |
Bug Description
SRU for Focal
[ Impact ]
* Customers using Focal are hitting several issues with drmgr command.
* drmgr command cannot add or remove a vty-server (server vterm device) slot - it fails finding an existent slot.
* Open terminal for a LPAR and hit ctrl+c - closes the terminal
* ctrl+] doesn't kill the terminal as expected.
[ Test Plan ]
* running the script provided by IBM (original bug description at `---Steps to Reproduce---`) - adjusting to your devices
[ Where problems could occur ]
* commit 60d9f54 introduces modifications in drmgr's hotplugging,
hence in case of issues with these modifications, hotplugging could be harmed or even broken.
* commit b0586b5 changes internal structures for parsing new DRC info,
so things could go wrong in case the parsing has issues, or the storage in the data structure is not done properly.
Issues here could in worst case lead to unforeseen problems, but this code is now upstream like several years.
* Package is ppc64el architecture only.
[other]
* The commits are upstream with v1.3.8 (and newer), so we only need to add them on Focal. _______
== Comment: #0 - SANUJIT HOTA <email address hidden> - 2023-05-09 12:40:54 ==
---Problem Description---
1. drmgr command fails as it doesn't find a slot
2. drmgr throws error while removing the slot
3. ctrl+c closes the terminal opened for any vm
4. ctrl+] doesn't close the terminal. But comes out with an extra 'Enter'
Contact Information = <email address hidden>, <email address hidden>
---uname output---
Linux novap9zz 5.4.0-148-generic #165-Ubuntu SMP Tue Apr 18 08:53:04 UTC 2023 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = type_model=
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Issue#1
=======
neo@novap9zz:~$ date;mkvterm --id 24;date
Tue May 9 13:23:40 EDT 2023
+ . gettext.sh
++ test 'X\t' = 'X\t'
++ echo=echo
++ test -z ''
++ case "$0" in
+ hvcsadmin=
+ hvcsdevlimit=1024
+ pvmutil=
+ socat=/
+ rmvterm=
+ openvt=/bin/openvt
+ '[' -f /usr/bin/linuxvnc ']'
+ linuxvnc=
+ flock=/
+ modprobe=
+ slattach=
+ ifconfig=
+ tcpdump=
+ Xvfb=/usr/bin/Xvfb
+ x11vnc=
+ java=/opt/
+ xinit=/
+ bash=/bin/bash
+ xterm=/
+ pgrep=/
+ giveUsage=0
+ lparId=0
+ lparIsIBMi=false
+ vnc=0
+ localVNC=0
+ ttyNumber=-1
+ vncPort=
+ vncPasswd=
+ vncDesktop=
+ lockFile=
+ lockTimeout=15
+ lockFD=3
+ logFile=
+ socatParms=
+ socatParmsVNC=
+ useXterm=false
+ xtermParms='-fa xft:DejaVuSansM
+ xtermSuffix1=' -- /usr/bin/Xvfb'
+ xtermSuffix2=' -screen 0 804x484x8 -nolisten tcp'
+ vncPortFile=
+ ptsLink=
+ socatParms5250=
+ prefixLocal5250
+ prefixRemote525
+ xvfbParms='-screen 0 976x615x8'
+ emulatorLocatio
+ emulatorSetting
+ emulatorSetting
+ emulatorParms=
+ emulatorParmsSu
+ emulatorParmsSu
+ emulatorParmsSu
+ RET_FAIL=1
+ RET_ITEMS_
+ RET_VTERM_
+ RET_OUT_OF_VTERMS=4
+ RET_USAGE=99
+ socatPid=-1
+ slattachPid=-1
+ declare -A lang_code
+ lang_code=([930]=0 [e930]=1 [939]=2 [1399]=3 [e1399]=4)
+ codePage=(930 930 939 1399 1399)
+ codePageKey=
+ fontName=
+ pdfFont=
++ getopt -o h --long id:,help,
+ TEMP=' --id '\''24'\'' --'
+ '[' 0 -ne 0 ']'
+ eval set -- ' --id '\''24'\'' --'
++ set -- --id 24 --
+ true
+ case "$1" in
+ lparId=24
+ shift 2
+ true
+ case "$1" in
+ break
+ [[ 24 -eq 0 ]]
+ [[ 24 =~ ^[0-9]+$ ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ /usr/sbin/pvmutil -o getrmcstatus
+ grep lpar_id=24,
+ grep os400
+ '[' 1 -eq 0 ']'
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ false = true ]]
+ [[ -n '' ]]
+ [[ false = false ]]
+ [[ -e /usr/bin/xinit ]]
+ [[ -e /usr/bin/Xvfb ]]
+ [[ -e /usr/bin/xterm ]]
+ [[ -e /usr/bin/x11vnc ]]
+ useXterm=true
++ expr 1024 - 1
+ '[' '!' -e /dev/hvcs1023 ']'
+ [[ false = true ]]
+ pvmhvcsadmin=
+ '[' -s /tmp/pvmhvcsadmin ']'
+ hvcsadmin=
+ chmod +x /tmp/pvmhvcsadmin
+ grep -F '=~ /.+(3\d+)$/' /tmp/pvmhvcsadmin
+ '[' 1 -eq 0 ']'
++ /usr/sbin/pvmutil -o create_vterm_dev --id 24
+ createDev=
+ '[' 0 -ne 0 ']'
+ exec
+ /usr/bin/flock -x -w 15 3
+ '[' 0 -ne 0 ']'
+ trap '$flock -u $lockFD' SIGHUP SIGINT SIGTERM EXIT
++ /tmp/pvmhvcsadmin -all
+ hvcsCloseAll=
++ /tmp/pvmhvcsadmin -status
++ grep 'partition:24 '
+ hvcsConsoleString=
+ [[ -z '' ]]
+ gettext 'Warning - vterm not found. You likely have run out of vterm devices.'
Warning - vterm not found. You likely have run out of vterm devices.+ echo
+ gettext 'Attempting to clean up unused devices. Please wait...'
Attempting to clean up unused devices. Please wait...+ echo
++ /usr/sbin/pvmutil -o delete_vterm_dev --id 24
+ deleteDev=
+ '[' 0 -ne 0 ']'
+ /usr/sbin/
Error removing the vterm device /dev/hvcs0 for partition 2:
[PVME0105FF05-0187] Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9009.
Validating I/O DLPAR capability...yes.
There are no DR capable slots on this system
U9009.42A.
Error removing the vterm device /dev/hvcs1 for partition 8:
[PVME0105FF05-0187] Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9009.
Validating I/O DLPAR capability...yes.
There are no DR capable slots on this system
U9009.42A.
++ /usr/sbin/pvmutil -o create_vterm_dev --id 24
[PVME0105FF05-0187] Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9009.
Validating I/O DLPAR capability...yes.
There are no DR capable slots on this system
Could not find drc index for U9009.42A.
+ createDev=
+ '[' 1 -ne 0 ']'
+ gettext 'Error creating a vterm device:'
Error creating a vterm device:+ echo
+ echo
+ exit 1
+ /usr/bin/flock -u 3
Tue May 9 13:24:16 EDT 2023
neo@novap9zz:~$
Issue#2
=======
Open terminal for a vm with mkvterm command, try to close it with ctrl+].
$ ^]
+ exitClean
+ lastCmd=0
+ [[ -z '' ]]
+ socatRet=0
+ '[' 0 -ne 0 ']'
+ echo ''
+ gettext 'Cleaning up...'
Cleaning up...+ echo
+ [[ true = true ]]
++ expr 100 + 2
+ pkill --full -SIGKILL '/usr/bin/
+ [[ false = true ]]
+ pkill --full -SIGHUP '.*/dev/hvcs0.*'
+ pkill --full -SIGKILL '.*/dev/hvcs0.*'
++ expr 100 + 2
+ pkill --full -SIGKILL '.*/usr/bin/Xvfb :102 .*'
+ /tmp/pvmhvcsadmin -close /dev/hvcs0
++ /usr/sbin/pvmutil -o delete_vterm_dev --id 2
+ deleteDev=
Validating I/O DLPAR capability...yes.
There are no DR capable slots on this system
U9009.42A.
'
+ '[' 1 -ne 0 ']'
+ gettext 'Error removing the vterm device:'
Error removing the vterm device:+ echo
+ echo '[PVME0105FF05-
[PVME0105FF05-0187] Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9009.
+ exit 1
Tue May 9 13:29:34 EDT 2023
neo@novap9zz:~$
Issue#3
=======
Open terminal for a vm and hit ctrl+c. terminal closes.
Issue#4
=======
ctrl+] doesn't kill the terminal. User needs to hit 'Enter'.
Userspace tool common name: mkvterm
The userspace tool has the following bit modes: 64
Userspace rpm: na
Userspace tool obtained from project website: na
*Additional Instructions for <email address hidden>, <email address hidden>:
-Post a private note with access information to the machine that the bug is occuring on.
-Attach ltrace and strace of userspace application.
== Comment: #1 - Application Cdeadmin <email address hidden> - 2023-05-09 13:05:39 ==
<===This is bridged from RTC description===>
This is the description of the defect added by LTC - RTC bridge automatically,
</===End of RTC description===>
== Comment: #2 - Luciano Chavez <email address hidden> - 2023-05-10 09:54:24 ==
This bug reported looks similar to
Bug 191386 - [Regression] RHEL8.3 zstream - drmgr command failing (DLPAR) (powerpc-utils?)
which was due to older version of drmgr having been bundled in the pvm-core package rather than using the provided 1.3.6 version that came with RHEL.
Here on the Ubuntu 20.04LTS we have the same binary for drmgr...
neo@novap9zz:~$ whereis drmgr
drmgr: /usr/sbin/drmgr /usr/local/
neo@novap9zz:~$ md5sum /usr/sbin/drmgr /usr/local/
c7863c699a27615
c7863c699a27615
yet according to the list of packages installed, is based on a fairly older version of powerpc-
Assigning to Nathan to review and see which changes might be missing in order to resolve this. I'll also attach a sosreport collected from the LPAR...
== Comment: #3 - Luciano Chavez <email address hidden> - 2023-05-10 09:55:44 ==
== Comment: #4 - Nathan Lynch <email address hidden> - 2023-05-10 15:21:34 ==
Assigning to Scott.
== Comment: #5 - Scott Cheloha <email address hidden> - 2023-05-11 09:58:31 ==
(In reply to comment #2)
> This bug reported looks similar to
>
> Bug 191386 - [Regression] RHEL8.3 zstream - drmgr command failing (DLPAR)
> (powerpc-utils?)
>
> which was due to older version of drmgr having been bundled in the pvm-core
> package rather than using the provided 1.3.6 version that came with RHEL.
>
> Here on the Ubuntu 20.04LTS we have the same binary for drmgr...
>
> neo@novap9zz:~$ whereis drmgr
> drmgr: /usr/sbin/drmgr /usr/local/
> neo@novap9zz:~$ md5sum /usr/sbin/drmgr /usr/local/
> c7863c699a27615
> c7863c699a27615
>
> yet according to the list of packages installed, is based on a fairly older
> version of powerpc-
> for 20.04 LTS. Current versions of Ubuntu provide version 1.3.10-2
>
> Assigning to Nathan to review and see which changes might be missing in
> order to resolve this. I'll also attach a sosreport collected from the
> LPAR...
It also resembles this:
https:/
== Comment: #6 - RITU AGARWAL <email address hidden> - 2023-05-16 00:22:34 ==
The issues mentioned here is after using default drmgr provided by OS.
Yes we saw similar issues and fix has been provided for RHEL, which If i am not wrong was with socat as well.
== Comment: #7 - RITU AGARWAL <email address hidden> - 2023-05-18 00:21:22 ==
Any update ?
== Comment: #8 - RITU AGARWAL <email address hidden> - 2023-06-02 04:21:10 ==
Any update? We are seeing this issue in customer env also. Customer is looking for update.
== Comment: #9 - Scott Cheloha <email address hidden> - 2023-06-05 11:58:06 ==
(In reply to comment #8)
> Any update? We are seeing this issue in customer env also. Customer is
> looking for update.
I can't figure out what's wrong with my current permissions.
Is there a root password for that NovaLink partition? That would help me look at what the utilities are doing under the hood.
== Comment: #10 - Scott Cheloha <email address hidden> - 2023-06-05 12:35:32 ==
The version of powerpc-utils installed on this partition is ancient:
neo@novap9zz:~$ apt info powerpc-utils
Package: powerpc-utils
Version: 1.3.4-0ubuntu2
Priority: important
Section: metapackages
Origin: Ubuntu
Maintainer: Ubuntu Developers <email address hidden>
Original-
Bugs: https:/
Installed-Size: 11.3 kB
Depends: powerpc-ibm-utils
Homepage: http://
Task: minimal
Download-Size: 1,784 B
APT-Manual-
APT-Sources: http://
Description: utilities for maintenance of PowerPC platforms (metapackage)
The powerpc-utils metapackage pulls in the appropriate tools for each
Debian PowerPC port.
I see that 22.04 ("Jammy Jellyfish") packages powerpc-utils 1.3.9, but that 20.04 (Focal Fossa) is still packaging 1.3.4.
Is there a protocol for advancing the packaged version in upstream for a given release?
== Comment: #11 - Scott Cheloha <email address hidden> - 2023-06-05 12:41:13 ==
(In reply to comment #10)
> The version of powerpc-utils installed on this partition is ancient:
>
> neo@novap9zz:~$ apt info powerpc-utils
> Package: powerpc-utils
> Version: 1.3.4-0ubuntu2
> Priority: important
> Section: metapackages
> Origin: Ubuntu
> Maintainer: Ubuntu Developers <email address hidden>
> Original-
> Bugs: https:/
> Installed-Size: 11.3 kB
> Depends: powerpc-ibm-utils
> Homepage: http://
> Task: minimal
> Download-Size: 1,784 B
> APT-Manual-
> APT-Sources: http://
> Packages
> Description: utilities for maintenance of PowerPC platforms (metapackage)
> The powerpc-utils metapackage pulls in the appropriate tools for each
> Debian PowerPC port.
To be perfectly clear: powerpc-utils 1.3.4 was tagged Sep 1 2017:
https:/
I suspect many bugs have been fixed in the interim.
== Comment: #12 - RITU AGARWAL <email address hidden> - 2023-06-06 01:50:27 ==
(In reply to comment #9)
> (In reply to comment #8)
> > Any update? We are seeing this issue in customer env also. Customer is
> > looking for update.
>
> I can't figure out what's wrong with my current permissions.
>
> Is there a root password for that NovaLink partition? That would help me
> look at what the utilities are doing under the hood.
You can "sudo su" to be root on novalink.
== Comment: #13 - RITU AGARWAL <email address hidden> - 2023-06-06 01:56:29 ==
(In reply to comment #11)
> (In reply to comment #10)
> > The version of powerpc-utils installed on this partition is ancient:
> >
> > neo@novap9zz:~$ apt info powerpc-utils
> > Package: powerpc-utils
> > Version: 1.3.4-0ubuntu2
> > Priority: important
> > Section: metapackages
> > Origin: Ubuntu
> > Maintainer: Ubuntu Developers <email address hidden>
> > Original-
> > Bugs: https:/
> > Installed-Size: 11.3 kB
> > Depends: powerpc-ibm-utils
> > Homepage: http://
> > Task: minimal
> > Download-Size: 1,784 B
> > APT-Manual-
> > APT-Sources: http://
> > Packages
> > Description: utilities for maintenance of PowerPC platforms (metapackage)
> > The powerpc-utils metapackage pulls in the appropriate tools for each
> > Debian PowerPC port.
>
> To be perfectly clear: powerpc-utils 1.3.4 was tagged Sep 1 2017:
>
> https:/
> 2e26d2996789a1e
>
> I suspect many bugs have been fixed in the interim.
What is the plan to build powerPS util for ubuntu 20.04 with latest code ?
== Comment: #14 - Scott Cheloha <email address hidden> - 2023-06-06 14:34:59 ==
(In reply to comment #13)
> (In reply to comment #11)
> > (In reply to comment #10)
> > > The version of powerpc-utils installed on this partition is ancient:
> > >
> > > neo@novap9zz:~$ apt info powerpc-utils
> > > Package: powerpc-utils
> > > Version: 1.3.4-0ubuntu2
> > > Priority: important
> > > Section: metapackages
> > > Origin: Ubuntu
> > > Maintainer: Ubuntu Developers <email address hidden>
> > > Original-
> > > Bugs: https:/
> > > Installed-Size: 11.3 kB
> > > Depends: powerpc-ibm-utils
> > > Homepage: http://
> > > Task: minimal
> > > Download-Size: 1,784 B
> > > APT-Manual-
> > > APT-Sources: http://
> > > Packages
> > > Description: utilities for maintenance of PowerPC platforms (metapackage)
> > > The powerpc-utils metapackage pulls in the appropriate tools for each
> > > Debian PowerPC port.
> >
> > To be perfectly clear: powerpc-utils 1.3.4 was tagged Sep 1 2017:
> >
> > https:/
> > 2e26d2996789a1e
> >
> > I suspect many bugs have been fixed in the interim.
>
> What is the plan to build powerPS util for ubuntu 20.04 with latest code ?
What do you mean by "plan"?
The problem is that the distribution is packaging an ancient release of powerpc-utils. They need to package a newer release.
Who on the NovaLink team is responsible for coordinating dependencies with Ubuntu packaging? That person needs to reach out to the person on the Ubuntu side responsible for packaging powerpc-utils and ask them to package powerpc-utils 1.3.9, if not 1.3.10, as they do for all later OS releases.
== Comment: #15 - Scott Cheloha <email address hidden> - 2023-06-06 14:50:05 ==
(In reply to comment #14)
> (In reply to comment #13)
> > (In reply to comment #11)
> > > (In reply to comment #10)
> > > > The version of powerpc-utils installed on this partition is ancient:
> > > >
> > > > neo@novap9zz:~$ apt info powerpc-utils
> > > > Package: powerpc-utils
> > > > Version: 1.3.4-0ubuntu2
> > > > Priority: important
> > > > Section: metapackages
> > > > Origin: Ubuntu
> > > > Maintainer: Ubuntu Developers <email address hidden>
> > > > Original-
> > > > Bugs: https:/
> > > > Installed-Size: 11.3 kB
> > > > Depends: powerpc-ibm-utils
> > > > Homepage: http://
> > > > Task: minimal
> > > > Download-Size: 1,784 B
> > > > APT-Manual-
> > > > APT-Sources: http://
> > > > Packages
> > > > Description: utilities for maintenance of PowerPC platforms (metapackage)
> > > > The powerpc-utils metapackage pulls in the appropriate tools for each
> > > > Debian PowerPC port.
> > >
> > > To be perfectly clear: powerpc-utils 1.3.4 was tagged Sep 1 2017:
> > >
> > > https:/
> > > 2e26d2996789a1e
> > >
> > > I suspect many bugs have been fixed in the interim.
> >
> > What is the plan to build powerPS util for ubuntu 20.04 with latest code ?
>
> What do you mean by "plan"?
>
> The problem is that the distribution is packaging an ancient release of
> powerpc-utils. They need to package a newer release.
>
> Who on the NovaLink team is responsible for coordinating dependencies with
> Ubuntu packaging? That person needs to reach out to the person on the
> Ubuntu side responsible for packaging powerpc-utils and ask them to package
> powerpc-utils 1.3.9, if not 1.3.10, as they do for all later OS releases.
Alternatively, you could upgrade the release to 22.04.2, which packages a newer release of powerpc-utils.
== Comment: #16 - Scott Cheloha <email address hidden> - 2023-06-06 15:27:19 ==
I built powerpc-utils 1.3.11 on the partition in:
/home/neo/
The installed drmgr cannot add a vty-server slot:
# drmgr -c slot -s 'U9009.
Validating I/O DLPAR capability...yes.
There are no DR capable slots on this system
Could not find drc index for U9009.42A.
# tail -n 10 /var/log/drmgr
########## Jun 06 16:17:50 2023 ##########
drmgr: -c slot -s U9009.42A.
Validating I/O DLPAR capability...yes.
Getting node types 0x00000003
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
There are no DR capable slots on this system
Could not find DRC property group in path: /proc/device-tree.
Could not find drc index for U9009.42A.
########## Jun 06 16:17:50 2023 ##########
The drmgr I built can do it:
# /home/neo/
Validating I/O DLPAR capability...yes.
# tail -n 31 /var/log/drmgr
########## Jun 06 16:19:29 2023 ##########
drmgr: -c slot -s U9009.42A.
Validating I/O DLPAR capability...yes.
Getting node types 0x00000003
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
Acquiring drc index 0x30000005
get-sensor for 30000005: 0, 2
Setting allocation state to 'alloc usable'
Setting indicator state to 'unisolate'
Configuring connector for drc index 30000005
Adding device-tree node /proc/device-
ofdt update: add_node /vdevice/
Getting node types 0x00000003
Could not find DRC property group in path: /proc/device-
performing kernel op for U9009.42A.
########## Jun 06 16:19:29 2023 ##########
--
The drmgr binary I built can also remove vty-server slots:
# /home/neo/
Validating I/O DLPAR capability...yes.
# tail -n 17 /var/log/drmgr
########## Jun 06 16:22:01 2023 ##########
drmgr: -c slot -s U9009.42A.
Validating I/O DLPAR capability...yes.
Getting node types 0x00000003
Could not find DRC property group in path: /proc/device-
get-sensor for 30000005: 0, 1
The sensor-state of drc_index 0x30000005 is 1
performing kernel op for U9009.42A.
Releasing drc index 0x30000005
get-sensor for 30000005: 0, 1
Setting isolation state to 'isolate'
Setting allocation state to 'alloc unusable'
get-sensor for 30000005: 0, 2
drc_index 30000005 sensor-state: 2
Resource is not available to the partition.
Removing device-tree node /proc/device-
########## Jun 06 16:22:01 2023 ##########
The installed drmgr chokes when trying to remove the same slot:
# drmgr -c slot -s 'U9009.
Validating I/O DLPAR capability...yes.
There are no DR capable slots on this system
U9009.42A.
# tail -n 9 /var/log/drmgr
########## Jun 06 16:23:20 2023 ##########
drmgr: -c slot -s U9009.42A.
Validating I/O DLPAR capability...yes.
Getting node types 0x00000003
Could not find DRC property group in path: /proc/device-
Could not find DRC property group in path: /proc/device-
There are no DR capable slots on this system
U9009.42A.
########## Jun 06 16:23:20 2023 ##########
So, I think the newer powerpc-utils release may help to resolve the problem here.
== Comment: #18 - Scott Cheloha <email address hidden> - 2023-06-07 13:39:33 ==
Mirroring to Launchpad to bring the package maintainers into the loop.
Changed in ubuntu-power-systems: | |
assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
Changed in powerpc-utils (Ubuntu): | |
importance: | Undecided → Medium |
importance: | Medium → High |
Changed in ubuntu-power-systems: | |
importance: | Undecided → High |
Changed in powerpc-utils (Ubuntu): | |
status: | New → In Progress |
assignee: | Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) → Patricia Domingues (patriciasd) |
Changed in ubuntu-power-systems: | |
status: | New → In Progress |
no longer affects: | powerpc-utils (Ubuntu Jammy) |
no longer affects: | powerpc-utils (Ubuntu Lunar) |
description: | updated |
Changed in powerpc-utils (Ubuntu Focal): | |
status: | New → In Progress |
assignee: | nobody → Patricia Domingues (patriciasd) |
description: | updated |
Changed in ubuntu-power-systems: | |
status: | Fix Committed → Fix Released |
Default Comment by Bridge