| 2020-07-06 14:45:13 |
Nick Niehoff |
bug |
|
|
added bug |
| 2020-07-06 14:52:54 |
Eric Desrochers |
tags |
|
seg sts |
|
| 2020-07-06 14:55:00 |
Eric Desrochers |
nominated for series |
|
Ubuntu Groovy |
|
| 2020-07-06 14:55:00 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Groovy) |
|
| 2020-07-06 14:55:00 |
Eric Desrochers |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-07-06 14:55:00 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Bionic) |
|
| 2020-07-06 14:55:00 |
Eric Desrochers |
nominated for series |
|
Ubuntu Focal |
|
| 2020-07-06 14:55:00 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Focal) |
|
| 2020-07-06 14:55:10 |
Eric Desrochers |
sosreport (Ubuntu Groovy): assignee |
|
Eric Desrochers (slashd) |
|
| 2020-07-06 14:55:14 |
Eric Desrochers |
sosreport (Ubuntu Groovy): status |
New |
In Progress |
|
| 2020-07-06 15:34:36 |
Launchpad Janitor |
sosreport (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2020-07-06 15:34:36 |
Launchpad Janitor |
sosreport (Ubuntu Focal): status |
New |
Confirmed |
|
| 2020-07-06 16:31:16 |
Eric Desrochers |
sosreport (Ubuntu Groovy): importance |
Undecided |
Medium |
|
| 2020-07-06 16:31:19 |
Eric Desrochers |
sosreport (Ubuntu Focal): status |
Confirmed |
In Progress |
|
| 2020-07-06 16:31:21 |
Eric Desrochers |
sosreport (Ubuntu Bionic): status |
Confirmed |
In Progress |
|
| 2020-07-06 16:31:24 |
Eric Desrochers |
sosreport (Ubuntu Focal): assignee |
|
Eric Desrochers (slashd) |
|
| 2020-07-06 16:31:27 |
Eric Desrochers |
sosreport (Ubuntu Bionic): assignee |
|
Eric Desrochers (slashd) |
|
| 2020-07-06 16:31:40 |
Eric Desrochers |
bug |
|
|
added subscriber Eric Desrochers |
| 2020-07-06 16:33:36 |
Eric Desrochers |
sosreport (Ubuntu Groovy): status |
In Progress |
Fix Committed |
|
| 2020-07-06 17:03:13 |
Eric Desrochers |
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. |
[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 the data 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. |
|
| 2020-07-06 17:30:03 |
Eric Desrochers |
description |
[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 the data 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. |
[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
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. |
|
| 2020-07-06 17:30:25 |
Eric Desrochers |
description |
[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
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. |
[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]
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. |
|
| 2020-07-06 20:50:33 |
Eric Desrochers |
description |
[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]
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. |
[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 information manually.
https://wiki.ubuntu.com/SosreportUpdates
[Other Info]
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. |
|
| 2020-07-06 20:51:57 |
Eric Desrochers |
description |
[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 information manually.
https://wiki.ubuntu.com/SosreportUpdates
[Other Info]
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. |
[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 information manually.
https://wiki.ubuntu.com/SosreportUpdates
[Other Info]
Upstream commit:
- [maas] Add snap support to maas plugin
- 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. |
|
| 2020-07-06 20:55:08 |
Eric Desrochers |
sosreport (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2020-07-06 20:55:10 |
Eric Desrochers |
sosreport (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2020-07-06 22:15:30 |
Launchpad Janitor |
sosreport (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
| 2020-07-09 13:41:36 |
Łukasz Zemczak |
sosreport (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-07-09 13:41:38 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-07-09 13:41:39 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2020-07-09 13:41:42 |
Łukasz Zemczak |
tags |
seg sts |
seg sts verification-needed verification-needed-focal |
|
| 2020-07-09 13:50:10 |
Łukasz Zemczak |
sosreport (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-07-09 13:50:14 |
Łukasz Zemczak |
tags |
seg sts verification-needed verification-needed-focal |
seg sts verification-needed verification-needed-bionic verification-needed-focal |
|
| 2020-07-09 15:19:51 |
Eric Desrochers |
tags |
seg sts verification-needed verification-needed-bionic verification-needed-focal |
seg sts verification-done verification-done-bionic verification-done-focal |
|
| 2020-07-15 13:08:38 |
Eric Desrochers |
nominated for series |
|
Ubuntu Xenial |
|
| 2020-07-15 13:08:38 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Xenial) |
|
| 2020-07-15 13:08:46 |
Eric Desrochers |
sosreport (Ubuntu Xenial): importance |
Undecided |
Low |
|
| 2020-07-15 13:08:48 |
Eric Desrochers |
sosreport (Ubuntu Xenial): assignee |
|
Eric Desrochers (slashd) |
|
| 2020-07-15 13:08:54 |
Eric Desrochers |
sosreport (Ubuntu Xenial): status |
New |
In Progress |
|
| 2020-07-16 08:28:00 |
Launchpad Janitor |
sosreport (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-07-16 08:28:04 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-07-16 11:28:47 |
Launchpad Janitor |
sosreport (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-07-16 13:50:01 |
Łukasz Zemczak |
sosreport (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2020-07-16 13:50:04 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-07-16 13:50:07 |
Łukasz Zemczak |
tags |
seg sts verification-done verification-done-bionic verification-done-focal |
seg sts verification-done-bionic verification-done-focal verification-needed verification-needed-xenial |
|
| 2020-07-16 15:28:54 |
Eric Desrochers |
tags |
seg sts verification-done-bionic verification-done-focal verification-needed verification-needed-xenial |
seg sts verification-done verification-done-bionic verification-done-focal verification-done-xenial |
|
| 2020-07-23 17:06:20 |
Launchpad Janitor |
sosreport (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2020-08-04 16:15:10 |
Adam Collard |
bug |
|
|
added subscriber Adam Collard |
