** Description changed: - This commit move the collection of unattended-upgrades from 'logs' plugin to 'apt' plugin: + [Impact] + + Having u-u logs collection inside the apt plugin make more sense + (instead of logs plugin) as it is using apt functionalities and python + modules such as apt, apt_inst, apt_pkg. + + u-u is a mechanism to automatically install security upgrades on + Debian/Ubuntu. It is enabled by default at installation. + + 'sos' philosophy is that each plugin should be taken care of its own + logs. + + [Test case] + + * Deploy Ubuntu (A container will do) + * Run sosreport and make sure the systemd plugin is executed + ** sosreport -o apt + * Look the content of the generated tarball under 'path_to_sosreport/var/log/unattended-upgrades/' + + and under 'path_to_sosreport/sos_logs/sos.log' for the execution log of the 'apt' plugin: + sos.log:2021-02-06 11:23:55,257 INFO: [plugin:apt] collecting path '/var/log/unattended-upgrades/..... + + + [Where problem could occur] + + If a problem have to occur, it will only be impacting the apt plugin + itself, not the core functionalities of 'sos' nor its other plugins. + + A third party vendor might have to break the habit to assume that the + 'logs' plugin will take care of the 'u-u' logs, and that 'apt' is the + way to move forward now. + + [Other information] https://github.com/sosreport/sos/commit/9f057fb43a949cabb496d06506a59e411ef17812
** Description changed: [Impact] Having u-u logs collection inside the apt plugin make more sense (instead of logs plugin) as it is using apt functionalities and python modules such as apt, apt_inst, apt_pkg. u-u is a mechanism to automatically install security upgrades on Debian/Ubuntu. It is enabled by default at installation. 'sos' philosophy is that each plugin should be taken care of its own logs. [Test case] * Deploy Ubuntu (A container will do) * Run sosreport and make sure the systemd plugin is executed - ** sosreport -o apt + ** sosreport -o apt * Look the content of the generated tarball under 'path_to_sosreport/var/log/unattended-upgrades/' - and under 'path_to_sosreport/sos_logs/sos.log' for the execution log of the 'apt' plugin: - sos.log:2021-02-06 11:23:55,257 INFO: [plugin:apt] collecting path '/var/log/unattended-upgrades/..... + * And under 'path_to_sosreport/sos_logs/sos.log' for the execution log + of the 'apt' plugin: + sos.log:2021-02-06 11:23:55,257 INFO: [plugin:apt] collecting path + '/var/log/unattended-upgrades/..... [Where problem could occur] If a problem have to occur, it will only be impacting the apt plugin itself, not the core functionalities of 'sos' nor its other plugins. A third party vendor might have to break the habit to assume that the 'logs' plugin will take care of the 'u-u' logs, and that 'apt' is the way to move forward now. [Other information] https://github.com/sosreport/sos/commit/9f057fb43a949cabb496d06506a59e411ef17812 ** Changed in: sosreport (Ubuntu Groovy) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: sosreport (Ubuntu Groovy) Status: New => In Progress ** Changed in: sosreport (Ubuntu Focal) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: sosreport (Ubuntu Focal) Status: New => In Progress ** Changed in: sosreport (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: sosreport (Ubuntu Bionic) Status: New => In Progress ** Changed in: sosreport (Ubuntu Bionic) Assignee: (unassigned) => Eric Desrochers (slashd) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906302 Title: [plugin][apt] Move unattended-upgrades log collection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1906302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
