** Description changed: [Impact] sosreport doesn't exercise the MAAS plugin if it is installed as a SNAP. Only work if installed as a DEB package. [Test Case] * snap install maas - * sosreport -a + * sosreport -a * Looking the sosreport archive content and validate that MAAS information haven't been collected (e.g. /path_to_sosreport/sos_commands/maas) [Regression Potential] No regression expected. If a regression happens it will only be isolated to the plugin itself. It won't affect/impact other plugin nor sosreport core functionalities. Worst case scenario, the MAAS plugin won't be exercised as expected, and - one would need to request the data manually. + one would need to request MAAS informations manually. [Other Info] [Original Description] Upstream commit: https://github.com/sosreport/sos/commit/1417827a Installing maas via snap on a focal machine (in my case lxd container) following: sudo snap install maas-test-db sudo snap install maas sudo maas init region --database-uri maas-test-db:/// Then running sosreport, sosreport does not correctly enable the maas plugin. I tested with version 3.9.1-1ubuntu0.20.04.1 of sosreport and also the upstream package from source. Here are the results: root@testing:/sos# dpkg -l | grep sosreport ii sosreport 3.9.1-1ubuntu0.20.04.1 amd64 Set of tools to gather troubleshooting data from a system root@testing:/sos# sosreport -l | grep maas maas inactive Ubuntu Metal-As-A-Service root@testing:/sos# ./bin/sosreport -l | grep maas maas Ubuntu Metal-As-A-Service maas.profile-name The name with which you will later refer to this remote maas.url The URL of the remote API maas.credentials The credentials, also known as the API key As you can see the version of sosreport from the package lists the maas plugin as inactive but from source it is enabled.
** Description changed: [Impact] sosreport doesn't exercise the MAAS plugin if it is installed as a SNAP. Only work if installed as a DEB package. [Test Case] * snap install maas * sosreport -a * Looking the sosreport archive content and validate that MAAS information haven't been collected (e.g. /path_to_sosreport/sos_commands/maas) [Regression Potential] No regression expected. If a regression happens it will only be isolated to the plugin itself. It won't affect/impact other plugin nor sosreport core functionalities. Worst case scenario, the MAAS plugin won't be exercised as expected, and one would need to request MAAS informations manually. [Other Info] - [Original Description] - Upstream commit: https://github.com/sosreport/sos/commit/1417827a + + [Original Description] Installing maas via snap on a focal machine (in my case lxd container) following: sudo snap install maas-test-db sudo snap install maas sudo maas init region --database-uri maas-test-db:/// Then running sosreport, sosreport does not correctly enable the maas plugin. I tested with version 3.9.1-1ubuntu0.20.04.1 of sosreport and also the upstream package from source. Here are the results: root@testing:/sos# dpkg -l | grep sosreport ii sosreport 3.9.1-1ubuntu0.20.04.1 amd64 Set of tools to gather troubleshooting data from a system root@testing:/sos# sosreport -l | grep maas maas inactive Ubuntu Metal-As-A-Service root@testing:/sos# ./bin/sosreport -l | grep maas maas Ubuntu Metal-As-A-Service maas.profile-name The name with which you will later refer to this remote maas.url The URL of the remote API maas.credentials The credentials, also known as the API key As you can see the version of sosreport from the package lists the maas plugin as inactive but from source it is enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886494 Title: sosreport does not correctly enable the maas plugin for a snap install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1886494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
