[Sts-sponsors] [Bug 1868215] Re: SRU: [lxd] Drop db collection and introduce lxd.buginfo

2020-03-30 Thread Eric Desrochers
** Tags added: sts-sponsor-volunteer

-- 
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1868215

Title:
  SRU: [lxd] Drop db collection and introduce lxd.buginfo

Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Bionic:
  In Progress
Status in sosreport source package in Eoan:
  In Progress
Status in sosreport source package in Focal:
  Fix Released

Bug description:
  [Impact]

  sosreport doesn't have to collect everything related to lxd which is very 
huge and unhelpful that much.
  This commit make sosreport collect proper info as installation types.

  [Test Case]

  Scenario #1
  * Deploy a machine (Xenial) with lxd installed as a DEB package
  * Install sosreport
  * sudo sosreport -o lxd or/and sudo sosreport -a
  * Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
  The data collection should be the one in the else statement of the plugin.

  Scenario #2
  * Deploy a machine (Bionic and late) with lxd installed as a SNAP.
  * Install sosreport
  * sudo sosreport -o lxd or/and sudo sosreport -a
  * Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
  The data collection should be the one in the if statement of the plugin, only 
executing "lxd.buginfo" command only available in SNAP.

  Scenario #3:
  A quick script to run on a node to verify multiple different options (as a 
sanity check):

  https://raw.githubusercontent.com/sosreport/sos/master/tests/simple.sh

  sudo bash simple.sh /usr/bin/python3 /usr/bin/sosreport

  simple.sh is a quick port of the travis tests to bash, requires root.

  There is some work to incorporate this exact script into the sosreport
  package for autopkg testing, but meanwhile it can be run manually for
  verifications.

  [Regression]

  "lxd.buginfo" has the advantage of not needing updates whenever
  lxd upstream add a new feature or find something new that’s worth capturing 
since LXD is now only offered as a SNAP nowadays.

  The plugin will remain backward compatible with DEB and SNAP, until
  there is no supported lxd DEB package available.

  If a problem occurs it will only impact the lxd plugin, not the other
  plugins nor core functionnalities.

  If for some reasons a command can be executed (not found in versions
  installed or else). sosreport is fault tolerant, and will
  continue/skip the command that doesn't exist, fails, ...

  FWIW, the commit has been +1 by lxd upstream himself stgraber:
  https://github.com/sosreport/sos/pull/1982/

  [Others]

  upstream patch
  - 
https://github.com/sosreport/sos/pull/1982/commits/bdc5ffdf5b8376ab2014ec8fbd9a878cc9d0d264

  LXD upstream reference:
  
https://discuss.linuxcontainers.org/t/what-lxd-information-should-be-collected-by-sosreport

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1868215/+subscriptions

-- 
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help   : https://help.launchpad.net/ListHelp


Re: [Sts-sponsors] easy bugs for seyeongkim to take

2020-03-30 Thread Dan Streetman
Sounds great!  I added the tag to a few bugs :)

On Mon, Mar 30, 2020 at 9:36 AM Mauricio Oliveira
 wrote:
>
> Thought?
>
> Yes, that sounds like a great Friday night!
>
> On Mon, Mar 30, 2020 at 10:34 AM Eric Desrochers
>  wrote:
> >
> > I like "sts-sponsor-volunteer"
> >
> > Mauricio, your concern about skill levels make a lot of sense.
> > Note to myself, don't pick tag name on Friday night without thinking too 
> > much about it while watching Star Wars with the kids. ;)
> >
> > Thought ?
> >
> > Eric
> >
> > On Mon, Mar 30, 2020 at 7:08 AM Mauricio Oliveira 
> >  wrote:
> >>
> >> I do like the tag idea too.
> >>
> >> However, I think we should not use wording associated with skill
> >> levels (no matter how great and cool padawan is :-) to avoid the
> >> impression a bug requires less skill from the assignee to handle it
> >> (even though it may be the case, technically.)
> >>
> >> If that makes sense, perhaps tags like "sts-sponsor-volunteer" or
> >> "sts-sponsor-help" indicate a more proactive attitude from the person
> >> willing to take it.
> >>
> >> Then a search link for the tag, with a banner like "We need you for
> >> SRUs!" (lol, just kidding) prompting people to volunteer for
> >> fixes/SRUs to help with their own review/sponsoring practice, would
> >> help! :-)
> >>
> >> cheers,
> >>
> >> On Fri, Mar 27, 2020 at 10:50 PM Eric Desrochers
> >>  wrote:
> >> >
> >> > I like the tag idea. What about "sts-sponsor-padawan" ?
> >> >
> >> > On Fri, Mar 27, 2020 at 5:19 PM Dan Streetman 
> >> >  wrote:
> >> >>
> >> >> going thru my old watched bugs, here are some bugs that should be easy
> >> >> to handle.  Maybe we should figure out a LP bug tag to use for bugs
> >> >> that we find that are good for potential sponsors, like seyeongkim, to
> >> >> take?
> >> >>
> >> >> https://bugs.launchpad.net/ubuntu/bionic/+source/nvme-cli/+bug/1800544
> >> >> -super easy bug
> >> >>
> >> >> https://bugs.launchpad.net/ubuntu/bionic/+source/python-etcd3gw/+bug/1820083
> >> >> -the actual patch is trivial, but this needs fixing in debian as well
> >> >> and setting up a reproducer to verify might be difficult.  This
> >> >> originally came from a case from Bloomberg, so setuid might be able to
> >> >> help with reproducer and/or verification.
> >> >>
> >> >> https://bugs.launchpad.net/ubuntu/xenial/+source/drbd-utils/+bug/1673255
> >> >> -i have not actually looked at this one in a long time, so i'm not
> >> >> sure if it is still needed, but should be easy enough to check if it's
> >> >> still needed, and if so then it should be easy to patch
> >> >>
> >> >> --
> >> >> Mailing list: https://launchpad.net/~sts-sponsors
> >> >> Post to : sts-sponsors@lists.launchpad.net
> >> >> Unsubscribe : https://launchpad.net/~sts-sponsors
> >> >> More help   : https://help.launchpad.net/ListHelp
> >> >
> >> > --
> >> > Mailing list: https://launchpad.net/~sts-sponsors
> >> > Post to : sts-sponsors@lists.launchpad.net
> >> > Unsubscribe : https://launchpad.net/~sts-sponsors
> >> > More help   : https://help.launchpad.net/ListHelp
> >>
> >>
> >>
> >> --
> >> Mauricio Faria de Oliveira
>
>
>
> --
> Mauricio Faria de Oliveira

-- 
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help   : https://help.launchpad.net/ListHelp


Re: [Sts-sponsors] easy bugs for seyeongkim to take

2020-03-30 Thread Mauricio Oliveira
Thought?

Yes, that sounds like a great Friday night!

On Mon, Mar 30, 2020 at 10:34 AM Eric Desrochers
 wrote:
>
> I like "sts-sponsor-volunteer"
>
> Mauricio, your concern about skill levels make a lot of sense.
> Note to myself, don't pick tag name on Friday night without thinking too much 
> about it while watching Star Wars with the kids. ;)
>
> Thought ?
>
> Eric
>
> On Mon, Mar 30, 2020 at 7:08 AM Mauricio Oliveira 
>  wrote:
>>
>> I do like the tag idea too.
>>
>> However, I think we should not use wording associated with skill
>> levels (no matter how great and cool padawan is :-) to avoid the
>> impression a bug requires less skill from the assignee to handle it
>> (even though it may be the case, technically.)
>>
>> If that makes sense, perhaps tags like "sts-sponsor-volunteer" or
>> "sts-sponsor-help" indicate a more proactive attitude from the person
>> willing to take it.
>>
>> Then a search link for the tag, with a banner like "We need you for
>> SRUs!" (lol, just kidding) prompting people to volunteer for
>> fixes/SRUs to help with their own review/sponsoring practice, would
>> help! :-)
>>
>> cheers,
>>
>> On Fri, Mar 27, 2020 at 10:50 PM Eric Desrochers
>>  wrote:
>> >
>> > I like the tag idea. What about "sts-sponsor-padawan" ?
>> >
>> > On Fri, Mar 27, 2020 at 5:19 PM Dan Streetman 
>> >  wrote:
>> >>
>> >> going thru my old watched bugs, here are some bugs that should be easy
>> >> to handle.  Maybe we should figure out a LP bug tag to use for bugs
>> >> that we find that are good for potential sponsors, like seyeongkim, to
>> >> take?
>> >>
>> >> https://bugs.launchpad.net/ubuntu/bionic/+source/nvme-cli/+bug/1800544
>> >> -super easy bug
>> >>
>> >> https://bugs.launchpad.net/ubuntu/bionic/+source/python-etcd3gw/+bug/1820083
>> >> -the actual patch is trivial, but this needs fixing in debian as well
>> >> and setting up a reproducer to verify might be difficult.  This
>> >> originally came from a case from Bloomberg, so setuid might be able to
>> >> help with reproducer and/or verification.
>> >>
>> >> https://bugs.launchpad.net/ubuntu/xenial/+source/drbd-utils/+bug/1673255
>> >> -i have not actually looked at this one in a long time, so i'm not
>> >> sure if it is still needed, but should be easy enough to check if it's
>> >> still needed, and if so then it should be easy to patch
>> >>
>> >> --
>> >> Mailing list: https://launchpad.net/~sts-sponsors
>> >> Post to : sts-sponsors@lists.launchpad.net
>> >> Unsubscribe : https://launchpad.net/~sts-sponsors
>> >> More help   : https://help.launchpad.net/ListHelp
>> >
>> > --
>> > Mailing list: https://launchpad.net/~sts-sponsors
>> > Post to : sts-sponsors@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~sts-sponsors
>> > More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> --
>> Mauricio Faria de Oliveira



-- 
Mauricio Faria de Oliveira

-- 
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help   : https://help.launchpad.net/ListHelp


Re: [Sts-sponsors] easy bugs for seyeongkim to take

2020-03-30 Thread Eric Desrochers
I like "sts-sponsor-volunteer"

Mauricio, your concern about skill levels make a lot of sense.
Note to myself, don't pick tag name on Friday night without thinking too
much about it while watching Star Wars with the kids. ;)

Thought ?

Eric

On Mon, Mar 30, 2020 at 7:08 AM Mauricio Oliveira <
mauricio.olive...@canonical.com> wrote:

> I do like the tag idea too.
>
> However, I think we should not use wording associated with skill
> levels (no matter how great and cool padawan is :-) to avoid the
> impression a bug requires less skill from the assignee to handle it
> (even though it may be the case, technically.)
>
> If that makes sense, perhaps tags like "sts-sponsor-volunteer" or
> "sts-sponsor-help" indicate a more proactive attitude from the person
> willing to take it.
>
> Then a search link for the tag, with a banner like "We need you for
> SRUs!" (lol, just kidding) prompting people to volunteer for
> fixes/SRUs to help with their own review/sponsoring practice, would
> help! :-)
>
> cheers,
>
> On Fri, Mar 27, 2020 at 10:50 PM Eric Desrochers
>  wrote:
> >
> > I like the tag idea. What about "sts-sponsor-padawan" ?
> >
> > On Fri, Mar 27, 2020 at 5:19 PM Dan Streetman <
> dan.street...@canonical.com> wrote:
> >>
> >> going thru my old watched bugs, here are some bugs that should be easy
> >> to handle.  Maybe we should figure out a LP bug tag to use for bugs
> >> that we find that are good for potential sponsors, like seyeongkim, to
> >> take?
> >>
> >> https://bugs.launchpad.net/ubuntu/bionic/+source/nvme-cli/+bug/1800544
> >> -super easy bug
> >>
> >>
> https://bugs.launchpad.net/ubuntu/bionic/+source/python-etcd3gw/+bug/1820083
> >> -the actual patch is trivial, but this needs fixing in debian as well
> >> and setting up a reproducer to verify might be difficult.  This
> >> originally came from a case from Bloomberg, so setuid might be able to
> >> help with reproducer and/or verification.
> >>
> >>
> https://bugs.launchpad.net/ubuntu/xenial/+source/drbd-utils/+bug/1673255
> >> -i have not actually looked at this one in a long time, so i'm not
> >> sure if it is still needed, but should be easy enough to check if it's
> >> still needed, and if so then it should be easy to patch
> >>
> >> --
> >> Mailing list: https://launchpad.net/~sts-sponsors
> >> Post to : sts-sponsors@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~sts-sponsors
> >> More help   : https://help.launchpad.net/ListHelp
> >
> > --
> > Mailing list: https://launchpad.net/~sts-sponsors
> > Post to : sts-sponsors@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~sts-sponsors
> > More help   : https://help.launchpad.net/ListHelp
>
>
>
> --
> Mauricio Faria de Oliveira
>
-- 
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help   : https://help.launchpad.net/ListHelp


Re: [Sts-sponsors] easy bugs for seyeongkim to take

2020-03-30 Thread Mauricio Oliveira
I do like the tag idea too.

However, I think we should not use wording associated with skill
levels (no matter how great and cool padawan is :-) to avoid the
impression a bug requires less skill from the assignee to handle it
(even though it may be the case, technically.)

If that makes sense, perhaps tags like "sts-sponsor-volunteer" or
"sts-sponsor-help" indicate a more proactive attitude from the person
willing to take it.

Then a search link for the tag, with a banner like "We need you for
SRUs!" (lol, just kidding) prompting people to volunteer for
fixes/SRUs to help with their own review/sponsoring practice, would
help! :-)

cheers,

On Fri, Mar 27, 2020 at 10:50 PM Eric Desrochers
 wrote:
>
> I like the tag idea. What about "sts-sponsor-padawan" ?
>
> On Fri, Mar 27, 2020 at 5:19 PM Dan Streetman  
> wrote:
>>
>> going thru my old watched bugs, here are some bugs that should be easy
>> to handle.  Maybe we should figure out a LP bug tag to use for bugs
>> that we find that are good for potential sponsors, like seyeongkim, to
>> take?
>>
>> https://bugs.launchpad.net/ubuntu/bionic/+source/nvme-cli/+bug/1800544
>> -super easy bug
>>
>> https://bugs.launchpad.net/ubuntu/bionic/+source/python-etcd3gw/+bug/1820083
>> -the actual patch is trivial, but this needs fixing in debian as well
>> and setting up a reproducer to verify might be difficult.  This
>> originally came from a case from Bloomberg, so setuid might be able to
>> help with reproducer and/or verification.
>>
>> https://bugs.launchpad.net/ubuntu/xenial/+source/drbd-utils/+bug/1673255
>> -i have not actually looked at this one in a long time, so i'm not
>> sure if it is still needed, but should be easy enough to check if it's
>> still needed, and if so then it should be easy to patch
>>
>> --
>> Mailing list: https://launchpad.net/~sts-sponsors
>> Post to : sts-sponsors@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~sts-sponsors
>> More help   : https://help.launchpad.net/ListHelp
>
> --
> Mailing list: https://launchpad.net/~sts-sponsors
> Post to : sts-sponsors@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~sts-sponsors
> More help   : https://help.launchpad.net/ListHelp



-- 
Mauricio Faria de Oliveira

-- 
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help   : https://help.launchpad.net/ListHelp