** Description changed:
- d/package-hooks/subiquity.py has a typo for the path "CurtinAptConfig"
- which leads to the literal path being included in the report, and not
- the content of the file that path points to.
+ [ Impact ]
+
+ Apport contains the "package hooks" for the ubuntu-desktop-bootstrap and
+ subiquity snap, which are used for information collection during error
+ reporting. There were some typos in the file paths that caused errors
+ during collection.
+
+ [ Test Plan ]
+
+ The test plan is focused on testing the behavior of apport within the
+ live installation environment, where we primarily expect users to submit
+ bug reports from.
+
+
+ ## Desktop
+
+ The test plan for Desktop involves beginning an install and checking
+ that the report properly collects the "ProbeData" portion of the report.
+
+ ### Reproduction Steps
+ 1) Download the latest Desktop ISO for the series being tested [1].
+ 2) You don't have to actually run the installation, just get booted into the
live environment.
+ 3) Open a terminal and run `ubuntu-bug ubuntu-desktop-bootstrap`
+ 4) Confirm the report does not contain the "ProbeData" key.
+
+ ## Confirm the upload fixes the issue
+ 1) Update apport from -proposed and re-run `ubuntu-bug
ubuntu-desktop-bootstrap` and confirm the report contains "ProbeData" with real
data. You can compare the content of this data with that in
"/var/log/installer/block/probe-data.json"
+
+
+ ## Server
+
+ The test plan for Server involves performing an install to completion
+ (without rebooting) and checking that the report properly contains the
+ "CurtinAptConfig" portion of the report.
+
+ ### Reproduction Steps
+ 1) Download the latest (installer) Server ISO for the series being tested [1].
+ 2) Complete a full installation of the system but do not let it reboot. If
the installer offers a refresh, accept it.
+ 3) Open a terminal (Alt+Right_arrow, Help->Enter shell, etc.) and run
`ubuntu-bug subiquity`
+ 4) Confirm the value of the key "CurtinAptConfig" in the report contains the
literal value "var/log/installer/curtin-install/subiquity-curtin-apt.conf".
+
+
+ ### Confirm the upload fixes the issue
+ 1) Update apport from -proposed and re-run `ubuntu-bug subiquity` and confirm
the "CurtinAptConfig" contains real data instead of the file path.
+
+
+ [ Where problems could occur ]
+
+ This update only makes changes to the file:
/usr/share/apport/package-hooks/{subiquity.py,ubuntu-desktop-bootstrap.py}
+ thus I only expect regressions in the form of manual bug reporting failures.
This code in this SRU is only ever automatically executed as part of
ubuntu-desktop-bootstrap's error handling (via whoopsie, which doesn't run on
server) and so should only regress behavior as part of data collection for
ubuntu-desktop-bootstrap bug reporting flow.
+
+ [ Other Info ]
+
+ * The fields starting with "lsusb" may report an error with exit code 1
+ when run on a QEMU VM. This is acceptable.
+
+ * The goal of the SRU is to get the package hook until the next Noble
+ point release (.3). The Oracular SRU is for archive consistency (we
+ don't expect to build now Oracular images).
+
+ [1] https://releases.ubuntu.com/noble/
+
+ --
+
+ [ Original Description ]
+ d/package-hooks/subiquity.py has a typo for the path "CurtinAptConfig" which
leads to the literal path being included in the report, and not the content of
the file that path points to.
d/package-hooks/ubuntu-desktop-bootstrap.py has a typo for the path of
"ProbeData" which results in the content not being added to the report.
(I accidentally a directory when refactoring the code and didn't catch
it)
** Summary changed:
- Typos in installer package hooks
+ [SRU] Typos in installer package hooks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2098423
Title:
[SRU] Typos in installer package hooks
Status in apport package in Ubuntu:
Fix Committed
Status in apport source package in Noble:
New
Status in apport source package in Oracular:
New
Bug description:
[ Impact ]
Apport contains the "package hooks" for the ubuntu-desktop-bootstrap
and subiquity snap, which are used for information collection during
error reporting. There were some typos in the file paths that caused
errors during collection.
[ Test Plan ]
The test plan is focused on testing the behavior of apport within the
live installation environment, where we primarily expect users to
submit bug reports from.
## Desktop
The test plan for Desktop involves beginning an install and checking
that the report properly collects the "ProbeData" portion of the
report.
### Reproduction Steps
1) Download the latest Desktop ISO for the series being tested [1].
2) You don't have to actually run the installation, just get booted into the
live environment.
3) Open a terminal and run `ubuntu-bug ubuntu-desktop-bootstrap`
4) Confirm the report does not contain the "ProbeData" key.
## Confirm the upload fixes the issue
1) Update apport from -proposed and re-run `ubuntu-bug
ubuntu-desktop-bootstrap` and confirm the report contains "ProbeData" with real
data. You can compare the content of this data with that in
"/var/log/installer/block/probe-data.json"
## Server
The test plan for Server involves performing an install to completion
(without rebooting) and checking that the report properly contains the
"CurtinAptConfig" portion of the report.
### Reproduction Steps
1) Download the latest (installer) Server ISO for the series being tested [1].
2) Complete a full installation of the system but do not let it reboot. If
the installer offers a refresh, accept it.
3) Open a terminal (Alt+Right_arrow, Help->Enter shell, etc.) and run
`ubuntu-bug subiquity`
4) Confirm the value of the key "CurtinAptConfig" in the report contains the
literal value "var/log/installer/curtin-install/subiquity-curtin-apt.conf".
### Confirm the upload fixes the issue
1) Update apport from -proposed and re-run `ubuntu-bug subiquity` and confirm
the "CurtinAptConfig" contains real data instead of the file path.
[ Where problems could occur ]
This update only makes changes to the file:
/usr/share/apport/package-hooks/{subiquity.py,ubuntu-desktop-bootstrap.py}
thus I only expect regressions in the form of manual bug reporting failures.
This code in this SRU is only ever automatically executed as part of
ubuntu-desktop-bootstrap's error handling (via whoopsie, which doesn't run on
server) and so should only regress behavior as part of data collection for
ubuntu-desktop-bootstrap bug reporting flow.
[ Other Info ]
* The fields starting with "lsusb" may report an error with exit code
1 when run on a QEMU VM. This is acceptable.
* The goal of the SRU is to get the package hook until the next Noble
point release (.3). The Oracular SRU is for archive consistency (we
don't expect to build now Oracular images).
[1] https://releases.ubuntu.com/noble/
--
[ Original Description ]
d/package-hooks/subiquity.py has a typo for the path "CurtinAptConfig" which
leads to the literal path being included in the report, and not the content of
the file that path points to.
d/package-hooks/ubuntu-desktop-bootstrap.py has a typo for the path of
"ProbeData" which results in the content not being added to the
report. (I accidentally a directory when refactoring the code and
didn't catch it)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2098423/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
