Activity log for bug #2038648

Date Who What changed Old value New value Message
2023-10-06 10:39:47 Branimir Radovic bug added bug
2023-10-18 19:26:24 Athos Ribeiro tags amd64 apport-package ec2-images need-duplicate-check third-party-packages xenial amd64 apport-package ec2-images need-duplicate-check server-triage-discuss third-party-packages xenial
2023-10-18 19:29:29 Athos Ribeiro bug added subscriber Athos Ribeiro
2023-10-25 15:26:59 Robie Basak sosreport (Ubuntu): status New Triaged
2023-10-25 15:27:10 Robie Basak nominated for series Ubuntu Bionic
2023-10-25 15:27:10 Robie Basak bug task added sosreport (Ubuntu Bionic)
2023-10-25 15:27:16 Robie Basak sosreport (Ubuntu Bionic): status New Triaged
2023-10-25 15:47:03 nikhil kshirsagar bug added subscriber nikhil kshirsagar
2023-10-25 16:47:02 Robie Basak sosreport (Ubuntu Bionic): importance Undecided High
2023-10-25 20:53:52 Mauricio Faria de Oliveira attachment added lp2038648-sosreport-bionic.debdiff https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5713265/+files/lp2038648-sosreport-bionic.debdiff
2023-10-25 20:54:08 Mauricio Faria de Oliveira sosreport (Ubuntu Bionic): status Triaged Incomplete
2023-10-26 00:19:45 Ubuntu Foundations Team Bug Bot tags amd64 apport-package ec2-images need-duplicate-check server-triage-discuss third-party-packages xenial amd64 apport-package ec2-images need-duplicate-check patch server-triage-discuss third-party-packages xenial
2023-10-26 13:09:17 Mauricio Faria de Oliveira bug added subscriber Mauricio Faria de Oliveira
2023-10-27 13:30:31 Mauricio Faria de Oliveira sosreport (Ubuntu): status Triaged Invalid
2023-11-01 15:23:54 Bryce Harrington tags amd64 apport-package ec2-images need-duplicate-check patch server-triage-discuss third-party-packages xenial amd64 apport-package ec2-images need-duplicate-check patch third-party-packages xenial
2023-11-16 19:08:39 Mauricio Faria de Oliveira sosreport (Ubuntu Bionic): status Incomplete Triaged
2024-03-13 09:20:58 Arif Ali sosreport (Ubuntu Bionic): status Triaged Fix Committed
2024-03-13 09:21:02 Arif Ali sosreport (Ubuntu Bionic): assignee Arif Ali (arif-ali)
2024-03-14 13:28:15 Mauricio Faria de Oliveira sosreport (Ubuntu Bionic): status Fix Committed In Progress
2024-03-14 16:24:43 Arif Ali attachment added apt.log https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5756025/+files/apt.log
2024-03-14 16:24:56 Arif Ali attachment added apt-term.log https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5756026/+files/apt-term.log
2024-03-14 16:25:07 Arif Ali attachment added history.log https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5756027/+files/history.log
2024-03-14 16:25:16 Arif Ali attachment added main.log https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5756028/+files/main.log
2024-03-20 09:44:12 Arif Ali attachment added bionic-4_4-sosreport.debdiff https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5757522/+files/bionic-4_4-sosreport.debdiff
2024-03-20 09:45:19 Arif Ali tags amd64 apport-package ec2-images need-duplicate-check patch third-party-packages xenial amd64 apport-package ec2-images need-duplicate-check patch sts-sru-needed third-party-packages xenial
2024-03-21 11:42:42 Mauricio Faria de Oliveira sosreport (Ubuntu Bionic): status In Progress Incomplete
2024-03-21 17:11:04 Heitor Alves de Siqueira bug added subscriber Heitor Alves de Siqueira
2024-03-25 14:56:23 Mauricio Faria de Oliveira attachment added diff_apt-term_log.diff https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5759306/+files/diff_apt-term_log.diff
2024-04-26 09:05:55 Arif Ali bug added subscriber Ubuntu Sponsors
2024-04-26 09:23:48 Arif Ali sosreport (Ubuntu Bionic): status Incomplete In Progress
2024-04-26 13:10:13 David Negreira bug added subscriber David Negreira
2024-05-14 17:36:12 Arif Ali description This is what I got when I tried do-release-upgrade from 16.04 to 18.04 Setting up sosreport (4.4-1ubuntu0.18.04.1) ... File "/usr/lib/python3/dist-packages/sos/report/plugins/gcp.py", line 99 f"Failed to communicate with Metadata Server " ^ SyntaxError: invalid syntax dpkg: error processing package sosreport (--configure): installed sosreport package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: sosreport ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sosreport.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sosreport 4.4-1ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.29 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 6 11:34:34 2023 Ec2AMI: ami-1e749f67 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: m3.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: installed sosreport package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.5, Python 3.5.2, python3-minimal, 3.5.1-3 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.4 apt 1.6.17 SourcePackage: sosreport Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2023-10-06 (0 days ago) [impact] This is what I got when I tried do-release-upgrade from 16.04 to 18.04 Setting up sosreport (4.4-1ubuntu0.18.04.1) ... File "/usr/lib/python3/dist-packages/sos/report/plugins/gcp.py", line 99 f"Failed to communicate with Metadata Server " ^ SyntaxError: invalid syntax dpkg: error processing package sosreport (--configure): installed sosreport package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: sosreport ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sosreport.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sosreport 4.4-1ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.29 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 6 11:34:34 2023 Ec2AMI: ami-1e749f67 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: m3.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: installed sosreport package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.5, Python 3.5.2, python3-minimal, 3.5.1-3 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.4 apt 1.6.17 SourcePackage: sosreport Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2023-10-06 (0 days ago) [ Test Plan ] The bug is not easily reproducible, and has been tested by many people within the team. One process that has been a form of testing it so add the bionic repo to a xenial machine, and try upgrading sosreport. When this is done we see the above error. This is the only test scenario we have that are able to test. Then we can enabled -proposed pocket or the PPA with the change, and do the same upgrade, and we should not face the same problem. [ Where problems could occur ] * The package may not install * The package may not have the right dependencies * There could be other factors in play that the above that we may not have seen entirely [ Other Info ] The proposed fix adds "X-Python3-Version: >= 3.6" to the control file, and this is based on the upstream dependency, and that 3.6 and above are supported. This would be reflected in all packages for consistency. As per the discussion in this bug the upstream project is due to move to Python 3.8 later in the year for releases greater than 4.8.0. This line would follow suite in a future SRU when we do a release from upstream SRU.
2024-06-19 17:38:07 Mauricio Faria de Oliveira description [impact] This is what I got when I tried do-release-upgrade from 16.04 to 18.04 Setting up sosreport (4.4-1ubuntu0.18.04.1) ... File "/usr/lib/python3/dist-packages/sos/report/plugins/gcp.py", line 99 f"Failed to communicate with Metadata Server " ^ SyntaxError: invalid syntax dpkg: error processing package sosreport (--configure): installed sosreport package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: sosreport ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sosreport.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sosreport 4.4-1ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.29 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 6 11:34:34 2023 Ec2AMI: ami-1e749f67 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: m3.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: installed sosreport package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.5, Python 3.5.2, python3-minimal, 3.5.1-3 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.4 apt 1.6.17 SourcePackage: sosreport Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2023-10-06 (0 days ago) [ Test Plan ] The bug is not easily reproducible, and has been tested by many people within the team. One process that has been a form of testing it so add the bionic repo to a xenial machine, and try upgrading sosreport. When this is done we see the above error. This is the only test scenario we have that are able to test. Then we can enabled -proposed pocket or the PPA with the change, and do the same upgrade, and we should not face the same problem. [ Where problems could occur ] * The package may not install * The package may not have the right dependencies * There could be other factors in play that the above that we may not have seen entirely [ Other Info ] The proposed fix adds "X-Python3-Version: >= 3.6" to the control file, and this is based on the upstream dependency, and that 3.6 and above are supported. This would be reflected in all packages for consistency. As per the discussion in this bug the upstream project is due to move to Python 3.8 later in the year for releases greater than 4.8.0. This line would follow suite in a future SRU when we do a release from upstream SRU. [ Impact ] On release upgrade from Xenial to Bionic, there seems to be an unknown corner case (difficult to reproduce) that Python 3.5 from Xenial is still in place at the time sosreport from Bionic is installed, which breaks postinst/py3compile as the project has f-strings, which requires Python 3.6. This causes an error on do-release-upgrade for affected users, who may have a need to upgrade in order to get Ubuntu Pro updates. This is the reason this is being uploaded to the Ubuntu Archive for Bionic (now ESM), and not only into the 'Bionic ESM' archive. [ Test Plan ] The bug is not easily reproducible, and has been tested by many people within the team (see comment history). One way to force the issue (although not on release upgrade) is add the bionic repo to a xenial machine, and try upgrading sosreport. In this case, the error happens This is the only test case we have to _reproduce the issue_. Therefore, since the change makes sense and is expected not to cause regressions, the test is to check for (no) regressions. 1) Run do-release-upgrade from Xenial to Bionic without -proposed enabled, which is not expected to hit the issue because things usually work. 2) Run do-release-upgrade from Xenial to Bionic *with* -proposed enabled, which is not expected to hit issue either because of the fix in place. 3) Compare terminal output, apt history, `dpkg -l` between each cases, and check for no differences in package install order, or unexpected things. (see comments 19-31). [ Where problems could occur ] * The package may not install * The package may not have the right dependencies * There could be other factors in play that the above that we may not have seen entirely [ Other Info ] The proposed fix adds "X-Python3-Version: >= 3.6" to the control file, and this is based on the upstream dependency, and that 3.6 and above are supported. This does not have to be reflected in all packages for consistency, as the only potentially affected release/upgrade is Xenial-Bionic, as clarified by Steve L. in uploads for other series with this change (bug 2054395 comment 50): > + - Add 'X-Python3-Version: >= 3.6' to ensure we use the python > + revision that is supported. (LP #2038648) > > Well this is pointless, since python3 is >= 3.6 in all releases after bionic [ Original Description ] This is what I got when I tried do-release-upgrade from 16.04 to 18.04 Setting up sosreport (4.4-1ubuntu0.18.04.1) ...   File "/usr/lib/python3/dist-packages/sos/report/plugins/gcp.py", line 99     f"Failed to communicate with Metadata Server "                                                  ^ SyntaxError: invalid syntax dpkg: error processing package sosreport (--configure):  installed sosreport package post-installation script subprocess returned error exit status 1 Errors were encountered while processing:  sosreport ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sosreport.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sosreport 4.4-1ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.29 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 6 11:34:34 2023 Ec2AMI: ami-1e749f67 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: m3.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: installed sosreport package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.5, Python 3.5.2, python3-minimal, 3.5.1-3 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions:  dpkg 1.19.0.5ubuntu2.4  apt 1.6.17 SourcePackage: sosreport Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2023-10-06 (0 days ago)
2024-06-19 17:40:05 Mauricio Faria de Oliveira description [ Impact ] On release upgrade from Xenial to Bionic, there seems to be an unknown corner case (difficult to reproduce) that Python 3.5 from Xenial is still in place at the time sosreport from Bionic is installed, which breaks postinst/py3compile as the project has f-strings, which requires Python 3.6. This causes an error on do-release-upgrade for affected users, who may have a need to upgrade in order to get Ubuntu Pro updates. This is the reason this is being uploaded to the Ubuntu Archive for Bionic (now ESM), and not only into the 'Bionic ESM' archive. [ Test Plan ] The bug is not easily reproducible, and has been tested by many people within the team (see comment history). One way to force the issue (although not on release upgrade) is add the bionic repo to a xenial machine, and try upgrading sosreport. In this case, the error happens This is the only test case we have to _reproduce the issue_. Therefore, since the change makes sense and is expected not to cause regressions, the test is to check for (no) regressions. 1) Run do-release-upgrade from Xenial to Bionic without -proposed enabled, which is not expected to hit the issue because things usually work. 2) Run do-release-upgrade from Xenial to Bionic *with* -proposed enabled, which is not expected to hit issue either because of the fix in place. 3) Compare terminal output, apt history, `dpkg -l` between each cases, and check for no differences in package install order, or unexpected things. (see comments 19-31). [ Where problems could occur ] * The package may not install * The package may not have the right dependencies * There could be other factors in play that the above that we may not have seen entirely [ Other Info ] The proposed fix adds "X-Python3-Version: >= 3.6" to the control file, and this is based on the upstream dependency, and that 3.6 and above are supported. This does not have to be reflected in all packages for consistency, as the only potentially affected release/upgrade is Xenial-Bionic, as clarified by Steve L. in uploads for other series with this change (bug 2054395 comment 50): > + - Add 'X-Python3-Version: >= 3.6' to ensure we use the python > + revision that is supported. (LP #2038648) > > Well this is pointless, since python3 is >= 3.6 in all releases after bionic [ Original Description ] This is what I got when I tried do-release-upgrade from 16.04 to 18.04 Setting up sosreport (4.4-1ubuntu0.18.04.1) ...   File "/usr/lib/python3/dist-packages/sos/report/plugins/gcp.py", line 99     f"Failed to communicate with Metadata Server "                                                  ^ SyntaxError: invalid syntax dpkg: error processing package sosreport (--configure):  installed sosreport package post-installation script subprocess returned error exit status 1 Errors were encountered while processing:  sosreport ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sosreport.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sosreport 4.4-1ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.29 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 6 11:34:34 2023 Ec2AMI: ami-1e749f67 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: m3.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: installed sosreport package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.5, Python 3.5.2, python3-minimal, 3.5.1-3 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions:  dpkg 1.19.0.5ubuntu2.4  apt 1.6.17 SourcePackage: sosreport Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2023-10-06 (0 days ago) [ Impact ] On release upgrade from Xenial to Bionic, there seems to be an unknown corner case (difficult to reproduce) that Python 3.5 from Xenial is still in place at the time sosreport from Bionic is installed, which breaks postinst/py3compile as the project has f-strings, which requires Python 3.6. This causes an error on do-release-upgrade for affected users, who may have a need to upgrade in order to get Ubuntu Pro updates. This is the reason this is being uploaded to the Ubuntu Archive for Bionic (now ESM), and not only into the 'Bionic ESM' archive. [ Test Plan ] The bug is not easily reproducible, and has been tested by many people within the team (see comment history). One way to force the issue (although not on release upgrade) is add the bionic repo to a xenial machine, and try upgrading sosreport. In this case, the error happens This is the only test case we have to _reproduce the issue_. Therefore, since the change makes sense and is expected not to cause regressions, the test is to check for (no) regressions. 1) Run do-release-upgrade from Xenial to Bionic without -proposed enabled, which is not expected to hit the issue because things usually work. 2) Run do-release-upgrade from Xenial to Bionic *with* -proposed enabled, which is not expected to hit issue either because of the fix in place. 3) Compare terminal output, apt history, `dpkg -l` between each cases, and check for no differences in package install order, or unexpected things. (see comments 19-31). 4) Compare the sosreport package .deb control and contents before/after, to make sure the only diff is the expected Python version in `Depends:`. [ Where problems could occur ] * The package may not install * The package may not have the right dependencies * There could be other factors in play that the above that we may not have seen entirely [ Other Info ] The proposed fix adds "X-Python3-Version: >= 3.6" to the control file, and this is based on the upstream dependency, and that 3.6 and above are supported. This does not have to be reflected in all packages for consistency, as the only potentially affected release/upgrade is Xenial-Bionic, as clarified by Steve L. in uploads for other series with this change (bug 2054395 comment 50): > + - Add 'X-Python3-Version: >= 3.6' to ensure we use the python > + revision that is supported. (LP #2038648) > > Well this is pointless, since python3 is >= 3.6 in all releases after bionic [ Original Description ] This is what I got when I tried do-release-upgrade from 16.04 to 18.04 Setting up sosreport (4.4-1ubuntu0.18.04.1) ...   File "/usr/lib/python3/dist-packages/sos/report/plugins/gcp.py", line 99     f"Failed to communicate with Metadata Server "                                                  ^ SyntaxError: invalid syntax dpkg: error processing package sosreport (--configure):  installed sosreport package post-installation script subprocess returned error exit status 1 Errors were encountered while processing:  sosreport ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sosreport.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sosreport 4.4-1ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.29 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 6 11:34:34 2023 Ec2AMI: ami-1e749f67 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: m3.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: installed sosreport package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.5, Python 3.5.2, python3-minimal, 3.5.1-3 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions:  dpkg 1.19.0.5ubuntu2.4  apt 1.6.17 SourcePackage: sosreport Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2023-10-06 (0 days ago)
2024-06-19 17:46:20 Mauricio Faria de Oliveira sosreport (Ubuntu Bionic): status In Progress Incomplete
2024-06-25 14:20:26 Lukas Märdian removed subscriber Ubuntu Sponsors
2024-06-26 13:30:08 Mauricio Faria de Oliveira sosreport (Ubuntu Bionic): status Incomplete In Progress
2024-07-02 20:22:49 Brian Murray sosreport (Ubuntu Bionic): status In Progress Fix Committed
2024-07-02 20:22:51 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2024-07-02 20:22:55 Brian Murray bug added subscriber SRU Verification
2024-07-02 20:23:05 Brian Murray tags amd64 apport-package ec2-images need-duplicate-check patch sts-sru-needed third-party-packages xenial amd64 apport-package ec2-images need-duplicate-check patch sts-sru-needed third-party-packages verification-needed verification-needed-bionic xenial
2024-07-03 08:40:39 Arif Ali attachment added xenial-bionic-sos-update-test.txt https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5794414/+files/xenial-bionic-sos-update-test.txt
2024-07-03 08:42:02 Arif Ali tags amd64 apport-package ec2-images need-duplicate-check patch sts-sru-needed third-party-packages verification-needed verification-needed-bionic xenial amd64 apport-package ec2-images need-duplicate-check patch sts-sru-needed third-party-packages verification-done-bionic verification-needed xenial
2024-07-03 14:55:21 Mauricio Faria de Oliveira tags amd64 apport-package ec2-images need-duplicate-check patch sts-sru-needed third-party-packages verification-done-bionic verification-needed xenial amd64 apport-package ec2-images need-duplicate-check patch sts-sru-needed third-party-packages verification-needed verification-needed-bionic xenial