** Description changed: [ Impact ] * Ubuntu Insights is not a user-facing application, so direct impact on - the user is minimized. However, the bugs fixed here are important for - the developer side. + the user is minimized. However, the bug fixed here is important for the + developer side. - * There are two critical but unrelated bugs fixed in this SRU. Firstly, improper localization standardization resulting in bad collection of reports. Second, broken internet connectivity in the upload systemd unit. - - The localization standardization is not properly applied to commands executed by Ubuntu Insights when it generates its collection reports. In certain environments, particularly localization environments that use comma decimal delimiters, this results in error messages in logs and incorrect report generation. This means misleading reports being potentially generated. - - The upload systemd unit is presently nonfunctional due to a too restrictive sandboxing configuration, preventing Ubuntu Insights when run through this unit, from accessing the internet. This means that the reports are not properly being uploaded, even though the unit is periodically attempting uploads and the server listening for requests is functioning properly. Beyond the reports not being properly uploaded, this issue results in a periodic useless usage of system resources as the unit tries and fails to upload reports, though it is very minimal. + * The localization standardization is not properly applied to commands + executed by Ubuntu Insights when it generates its collection reports. In + certain environments, particularly localization environments that use + comma decimal delimiters, this results in error messages in logs and + incorrect report generation. This means misleading reports being + potentially generated. [ Test Plan ] - * Collection Issue 1. Ensure consent is set to true via `ubuntu-insights consent linux -s=true`. 2. With a localization that uses comma separators for decimals, for instance FR, generate a report via `ubuntu-insights collect -f`. - 3. Check that there are no unexpected errors related for formatting and check that the printed output makes sense, particularly for disk and memory size. + 3. Check that there are no unexpected errors related to formatting, and check that the printed output makes sense, particularly for disk and memory size. 4. Check that a generated report is present in `~/.cache/ubuntu-insights/linux/local/` and that its contents make sense, particularly for disk and memory size. - - * Upload Issue - 1. Ensure consent is set, either via `ubuntu-insights consent -s=true` or ubuntu-insights consent -s=false`. - 2. Generate a valid Ubuntu Insights report. For example, use `ubuntu-insights collect -f`. - 3. Validate that the report was generated and is present in `~/.cache/ubuntu-insights/linux/local/`. - 4. Rename the report generated to a Unix timestamp at least a full week earlier. - - For example, `1665919002.json -> 1565919002.json` - 5. With a working internet connection, upload the report using the upload systemd unit. Either wait for the weekly timer to trigger it or trigger it manually. - - `systemctl --user start ubuntu-insights-upload.service` - 6. Check the status and logs of the user systemd unit `ubuntu-insights-upload.service` to ensure that the unit ran successfully - 7. Check that the report generated and renamed is no longer present in `~/.cache/ubuntu-insights/linux/local/`, and is instead present in `~/.cache/ubuntu-insights/linux/uploaded/` in some form. [ Where problems could occur ] * Collection localization standardization is not properly solved, and the reports are either still improperly generated in certain localization environments, or no reports are generated at all. - * The upload unit's sandboxing is relaxed too much, to the point where - it poses an undue risk. - - * The upload unit's sandboxing is not relaxed enough, resulting in the - upload issue to persist. - [ Other Info ] * As mentioned earlier, Ubuntu Insights is not a user-facing - application. However, these issues break core functionality that the + application. However, this issue breaks core functionality that the development team relies on for the collection of anonymized, consent- based telemetry on Ubuntu Desktop. Thus, though Questing is an interim release, an SRU is justified. * Related upload for Resolute (26.04): https://bugs.launchpad.net/ubuntu/+source/ubuntu-insights/+bug/2135266 * GitHub repository: https://github.com/ubuntu/ubuntu-insights
** Summary changed: - [SRU]: Broken collection in certain localization environments and broken upload unit + [SRU]: Broken collection in certain localization environments -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2137483 Title: [SRU]: Broken collection in certain localization environments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-insights/+bug/2137483/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
