[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
This bug was fixed in the package sosreport - 3.6-1ubuntu0.16.04.4 --- sosreport (3.6-1ubuntu0.16.04.4) xenial; urgency=medium * d/p/juju-shouldnt-restart-juju-db-service.patch (LP: #1828467) sosreport shouldn't restart a service. It can only collect it's status to notify user in case the service is stopped. -- Eric Desrochers Mon, 11 Nov 2019 16:06:09 + -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
This bug was fixed in the package sosreport - 3.6-1ubuntu0.18.04.4 --- sosreport (3.6-1ubuntu0.18.04.4) bionic; urgency=medium * d/p/juju-shouldnt-restart-juju-db-service.patch (LP: #1828467) sosreport shouldn't restart a service. It can only collect it's status to notify user in case the service is stopped. -- Eric Desrochers Mon, 11 Nov 2019 16:13:35 + ** Changed in: sosreport (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: sosreport (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
This bug was fixed in the package sosreport - 3.6-1ubuntu2.2 --- sosreport (3.6-1ubuntu2.2) disco; urgency=medium * d/p/juju-shouldnt-restart-juju-db-service.patch (LP: #1828467) sosreport shouldn't restart a service. It can only collect it's status to notify user in case the service is stopped. -- Eric Desrochers Mon, 11 Nov 2019 15:51:56 + ** Changed in: sosreport (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
For the future, please be sure to record the version tested during verification. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
This bug was fixed in the package sosreport - 3.6-1ubuntu3.1 --- sosreport (3.6-1ubuntu3.1) eoan; urgency=medium * d/p/juju-shouldnt-restart-juju-db-service.patch (LP: #1828467) sosreport shouldn't restart a service. It can only collect it's status to notify user in case the service is stopped. -- Eric Desrochers Mon, 11 Nov 2019 15:32:21 + ** Changed in: sosreport (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
[VERIFICATION DISCO] + [VERIFICATION EOAN] Same exact verification as #9 has been made on D/E, and no more mongod restart observed when juju plugin is exercised in a Juju controller. - Eric ** Tags removed: verification-needed-disco verification-needed-eoan verification-needed-xenial ** Tags added: verification-done-disco verification-done-eoan verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
[VERIFICATION XENIAL] + [VERIFICATION DISCO] + [VERIFICATION EOAN] Same exact verification as #9 has been made on D/E, and no more mongod restart observed when juju plugin is exercised in a Juju controller. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
[VERIFICATION BIONIC] # pidof mongod 975 # service juju-db status Active: active (running) since Thu 2019-11-14 16:59:56 UTC; 9min ago Main PID: 975 (mongod) # sosreport -o juju # pidof mongod 975 # service juju-db status Active: active (running) since Thu 2019-11-14 16:59:56 UTC; 9min ago Main PID: 975 (mongod) No more mongod restart observed when juju plugin is exercised in a Juju controller. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
[VERIFICATION BIONIC] # pidof mongod 975 # sosreport -o juju # pidof mongod 975 No mongod restart observed, all good. - Eric ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
Hello Dan, or anyone else affected, Accepted sosreport into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sosreport/3.6-1ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: sosreport (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan ** Changed in: sosreport (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
** Description changed: [Impact] The juju plugin will stop and start the juju-db service during data collection. sosreport should not impact running services, or attempt to recover them. This has been reported upstream[0] and will be fixed by the juju 2.x refactor[1] This is a stop-gap tracking the removal of the juju-db service restart code in existing sosreport releases. [0] - https://github.com/sosreport/sos/issues/1653 [1] - https://github.com/sosreport/sos/pull/1670 [Test Case] * Make sure you are in the juju controller. * Install sosreport (if not present already) $ sudo apt-get install sosreport -y * Look mongod PID before $ pidof mongod * Run sosreport, ensuring that the juju plugin is exercised $ sosreport -a # Should detect it if /usr/bin/juju' or '/usr/bin/juju-run' are found and/or $ sosreport -o juju # In a snap package env, it's possible sosreport doesn't detect it and the plugin would need to be enforce. * Confirm the juju-db service was not restarted, and mongoexport data captured by looking mongod PID after $ pidof mongod Check for errors while running, or in /tmp/sosreport-*/sos_logs/ The offending function ensure_service_is_running() in theory doesn't create any harm unless juju plugin is exercised during a sosreport run from a juju controller where mongod and/or juju-db resides. [Regression Potential] * Risk is low. * Change is limited in scope to the juju plugin. * Worst-case scenario is that the mongoexport command will fail to collect any data, which won't affect core functionality of sosreport itself nor impact other sosreport plugins. If any regression, it will be way less worse than current situation, - where daemon are susceptible to be restarted. + where daemon are susceptible to be restarted. It's not sosreport + responsability to take action on daemons, it should only monitor it and + report back to users via its respective plugin. [Other information] We will temporary divert from the juju plugin found upstream and debian, while the refactoring is completed to avoid any situation where sosreport is run on a controller since it may have production impact on Ubuntu juju environment. Once the refactoring of the juju plugin is completed upstream, we will make sure to update debian and put the juju plugin align with what found upstream and debian. Actually, sosreport 3.8 micro-release is blocked waiting for this refactoring to be completed (LP: #1825010). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
** Changed in: sosreport (Ubuntu Trusty) Assignee: Dan Hill (hillpd) => (unassigned) ** Description changed: [Impact] The juju plugin will stop and start the juju-db service during data collection. sosreport should not impact running services, or attempt to recover them. This has been reported upstream[0] and will be fixed by the juju 2.x refactor[1] This is a stop-gap tracking the removal of the juju-db service restart code in existing sosreport releases. [0] - https://github.com/sosreport/sos/issues/1653 [1] - https://github.com/sosreport/sos/pull/1670 [Test Case] * Make sure you are in the juju controller. - * Install sosreport + * Install sosreport (if not present already) + $ sudo apt-get install sosreport -y + * Look mongod PID before - ** $ pidof mongod + $ pidof mongod + * Run sosreport, ensuring that the juju plugin is exercised - * Confirm the juju-db service was not restarted, and mongoexport data captured. - * Look mongod PID after - ** $ pidof mongod + $ sosreport -a + and/or + $ sosreport -o juju + + * Confirm the juju-db service was not restarted, and mongoexport data captured by looking mongod PID after + $ pidof mongod Check for errors while running, or in /tmp/sosreport-*/sos_logs/ The offending function ensure_service_is_running() in theory doesn't create any harm unless juju plugin is exercised during a sosreport run from a juju controller where mongod and/or juju-db resides. [Regression Potential] * Risk is low. * Change is limited in scope to the juju plugin. * Worst-case scenario is that the mongoexport command will fail to collect any data, which won't affect core functionality of sosreport itself nor impact other sosreport plugins. If any regression, it will be way less worse than current situation, where daemon are susceptible to be restarted. [Other information] We will temporary divert from the juju plugin found upstream and debian, while the refactoring is completed to avoid any situation where sosreport is run on a controller since it may have production impact on Ubuntu juju environment. Once the refactoring of the juju plugin is completed upstream, we will make sure to update debian and put the juju plugin align with what found upstream and debian. Actually, sosreport 3.8 micro-release is blocked waiting for this refactoring to be completed (LP: #1825010). ** Description changed: [Impact] The juju plugin will stop and start the juju-db service during data collection. sosreport should not impact running services, or attempt to recover them. This has been reported upstream[0] and will be fixed by the juju 2.x refactor[1] This is a stop-gap tracking the removal of the juju-db service restart code in existing sosreport releases. [0] - https://github.com/sosreport/sos/issues/1653 [1] - https://github.com/sosreport/sos/pull/1670 [Test Case] * Make sure you are in the juju controller. * Install sosreport (if not present already) - $ sudo apt-get install sosreport -y + $ sudo apt-get install sosreport -y * Look mongod PID before $ pidof mongod * Run sosreport, ensuring that the juju plugin is exercised - $ sosreport -a - and/or - $ sosreport -o juju + $ sosreport -a # Should detect it if /usr/bin/juju' or '/usr/bin/juju-run' are found + and/or + $ sosreport -o juju # In a snap package env, it's possible sosreport doesn't detect it and the plugin would need to be enforce. * Confirm the juju-db service was not restarted, and mongoexport data captured by looking mongod PID after $ pidof mongod Check for errors while running, or in /tmp/sosreport-*/sos_logs/ The offending function ensure_service_is_running() in theory doesn't create any harm unless juju plugin is exercised during a sosreport run from a juju controller where mongod and/or juju-db resides. [Regression Potential] * Risk is low. * Change is limited in scope to the juju plugin. * Worst-case scenario is that the mongoexport command will fail to collect any data, which won't affect core functionality of sosreport itself nor impact other sosreport plugins. If any regression, it will be way less worse than current situation, where daemon are susceptible to be restarted. [Other information] We will temporary divert from the juju plugin found upstream and debian, while the refactoring is completed to avoid any situation where sosreport is run on a controller since it may have production impact on Ubuntu juju environment. Once the refactoring of the juju plugin is completed upstream, we will make sure to update debian and put the juju plugin align with what found upstream and debian. Actually, sosreport 3.8 micro-release is blocked waiting for this refactoring to be completed (LP:
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
Uploaded in E/D/B/X. - Eric ** Changed in: sosreport (Ubuntu Xenial) Importance: Low => Medium ** Changed in: sosreport (Ubuntu Bionic) Importance: Low => Medium ** Changed in: sosreport (Ubuntu Disco) Importance: Low => Medium ** Changed in: sosreport (Ubuntu Eoan) Importance: Low => Medium ** Description changed: [Impact] The juju plugin will stop and start the juju-db service during data collection. sosreport should not impact running services, or attempt to recover them. This has been reported upstream[0] and will be fixed by the juju 2.x refactor[1] This is a stop-gap tracking the removal of the juju-db service restart code in existing sosreport releases. [0] - https://github.com/sosreport/sos/issues/1653 [1] - https://github.com/sosreport/sos/pull/1670 [Test Case] * Make sure you are in the juju controller. * Install sosreport * Look mongod PID before ** $ pidof mongod * Run sosreport, ensuring that the juju plugin is exercised * Confirm the juju-db service was not restarted, and mongoexport data captured. * Look mongod PID after ** $ pidof mongod Check for errors while running, or in /tmp/sosreport-*/sos_logs/ The offending function ensure_service_is_running() in theory doesn't create any harm unless juju plugin is exercised during a sosreport run from a juju controller where mongod and/or juju-db resides. [Regression Potential] * Risk is low. * Change is limited in scope to the juju plugin. * Worst-case scenario is that the mongoexport command will fail to collect any data, which won't affect core functionality of sosreport itself nor impact other sosreport plugins. + If any regression, it will be way less worse than current situation, + where daemon are susceptible to be restarted. + [Other information] We will temporary divert from the juju plugin found upstream and debian, while the refactoring is completed to avoid any situation where sosreport is run on a controller since it may have production impact on Ubuntu juju environment. Once the refactoring of the juju plugin is completed upstream, we will make sure to update debian and put the juju plugin align with what found upstream and debian. Actually, sosreport 3.7 micro-release is blocked waiting for this refactoring to be completed (LP: #1825010). ** Description changed: [Impact] The juju plugin will stop and start the juju-db service during data collection. sosreport should not impact running services, or attempt to recover them. This has been reported upstream[0] and will be fixed by the juju 2.x refactor[1] This is a stop-gap tracking the removal of the juju-db service restart code in existing sosreport releases. [0] - https://github.com/sosreport/sos/issues/1653 [1] - https://github.com/sosreport/sos/pull/1670 [Test Case] * Make sure you are in the juju controller. * Install sosreport * Look mongod PID before ** $ pidof mongod * Run sosreport, ensuring that the juju plugin is exercised * Confirm the juju-db service was not restarted, and mongoexport data captured. * Look mongod PID after ** $ pidof mongod Check for errors while running, or in /tmp/sosreport-*/sos_logs/ The offending function ensure_service_is_running() in theory doesn't create any harm unless juju plugin is exercised during a sosreport run from a juju controller where mongod and/or juju-db resides. [Regression Potential] * Risk is low. * Change is limited in scope to the juju plugin. * Worst-case scenario is that the mongoexport command will fail to collect any data, which won't affect core functionality of sosreport itself nor impact other sosreport plugins. If any regression, it will be way less worse than current situation, where daemon are susceptible to be restarted. [Other information] We will temporary divert from the juju plugin found upstream and debian, while the refactoring is completed to avoid any situation where sosreport is run on a controller since it may have production impact on Ubuntu juju environment. Once the refactoring of the juju plugin is completed upstream, we will make sure to update debian and put the juju plugin align with what found upstream and debian. - Actually, sosreport 3.7 micro-release is blocked waiting for this + Actually, sosreport 3.8 micro-release is blocked waiting for this refactoring to be completed (LP: #1825010). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
** Changed in: sosreport (Ubuntu) Assignee: Dan Hill (hillpd) => Eric Desrochers (slashd) ** Changed in: sosreport (Ubuntu) Status: In Progress => Fix Released ** Changed in: sosreport (Ubuntu Cosmic) Status: New => Won't Fix ** Changed in: sosreport (Ubuntu Eoan) Assignee: Dan Hill (hillpd) => Eric Desrochers (slashd) ** Changed in: sosreport (Ubuntu Disco) Assignee: Dan Hill (hillpd) => Eric Desrochers (slashd) ** Changed in: sosreport (Ubuntu Cosmic) Assignee: Dan Hill (hillpd) => (unassigned) ** Changed in: sosreport (Ubuntu Bionic) Assignee: Dan Hill (hillpd) => Eric Desrochers (slashd) ** Changed in: sosreport (Ubuntu Xenial) Assignee: Dan Hill (hillpd) => Eric Desrochers (slashd) ** Changed in: sosreport (Ubuntu Disco) Status: New => In Progress ** Changed in: sosreport (Ubuntu Bionic) Status: New => In Progress ** Changed in: sosreport (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
I marked Trusty as 'Won't Fix' as it reached EOL. ** Description changed: [Impact] The juju plugin will stop and start the juju-db service during data collection. sosreport should not impact running services, or attempt to recover them. This has been reported upstream[0] and will be fixed by the juju 2.x refactor[1] This is a stop-gap tracking the removal of the juju-db service restart code in existing sosreport releases. [0] - https://github.com/sosreport/sos/issues/1653 [1] - https://github.com/sosreport/sos/pull/1670 [Test Case] - * Make sure you are in the juju controller. + * Make sure you are in the juju controller. * Install sosreport * Look mongod PID before ** $ pidof mongod * Run sosreport, ensuring that the juju plugin is exercised * Confirm the juju-db service was not restarted, and mongoexport data captured. * Look mongod PID after ** $ pidof mongod - Check for errors while running, or in /tmp/sosreport-*/sos_logs/ The offending function ensure_service_is_running() in theory doesn't create any harm unless juju plugin is exercised during a sosreport run from a juju controller where mongod and/or juju-db resides. [Regression Potential] * Risk is low. * Change is limited in scope to the juju plugin. * Worst-case scenario is that the mongoexport command will fail to collect any data, which won't affect core functionality of sosreport itself nor impact other sosreport plugins. + + [Other information] + + We will temporary divert from the juju plugin found upstream and debian, + while the refactoring is completed to avoid any situation where + sosreport is run on a controller since it may have production impact on + Ubuntu juju environment. + + Once the refactoring of the juju plugin is completed upstream, we will + make sure to update debian and put the juju plugin align with what found + upstream and debian. + + Actually, sosreport 3.7 micro-release is waiting on this via LP: + #1825010. ** Description changed: [Impact] The juju plugin will stop and start the juju-db service during data collection. sosreport should not impact running services, or attempt to recover them. This has been reported upstream[0] and will be fixed by the juju 2.x refactor[1] This is a stop-gap tracking the removal of the juju-db service restart code in existing sosreport releases. [0] - https://github.com/sosreport/sos/issues/1653 [1] - https://github.com/sosreport/sos/pull/1670 [Test Case] * Make sure you are in the juju controller. * Install sosreport * Look mongod PID before ** $ pidof mongod * Run sosreport, ensuring that the juju plugin is exercised * Confirm the juju-db service was not restarted, and mongoexport data captured. * Look mongod PID after ** $ pidof mongod Check for errors while running, or in /tmp/sosreport-*/sos_logs/ The offending function ensure_service_is_running() in theory doesn't create any harm unless juju plugin is exercised during a sosreport run from a juju controller where mongod and/or juju-db resides. [Regression Potential] * Risk is low. * Change is limited in scope to the juju plugin. * Worst-case scenario is that the mongoexport command will fail to collect any data, which won't affect core functionality of sosreport itself nor impact other sosreport plugins. [Other information] We will temporary divert from the juju plugin found upstream and debian, while the refactoring is completed to avoid any situation where sosreport is run on a controller since it may have production impact on Ubuntu juju environment. Once the refactoring of the juju plugin is completed upstream, we will make sure to update debian and put the juju plugin align with what found upstream and debian. - Actually, sosreport 3.7 micro-release is waiting on this via LP: - #1825010. + Actually, sosreport 3.7 micro-release is blocked waiting for this + refactoring to be completed (LP: #1825010). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
I marked Trusty as 'Won't Fix' in it reached EOL. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
** Changed in: sosreport (Ubuntu Trusty) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
** Description changed: [Impact] The juju plugin will stop and start the juju-db service during data collection. sosreport should not impact running services, or attempt to recover them. This has been reported upstream[0] and will be fixed by the juju 2.x refactor[1] This is a stop-gap tracking the removal of the juju-db service restart code in existing sosreport releases. [0] - https://github.com/sosreport/sos/issues/1653 [1] - https://github.com/sosreport/sos/pull/1670 [Test Case] + * Make sure you are in the juju controller. * Install sosreport - * Look mongod PID before -** pidof mongod + * Look mongod PID before + ** $ pidof mongod * Run sosreport, ensuring that the juju plugin is exercised * Confirm the juju-db service was not restarted, and mongoexport data captured. * Look mongod PID after -** pidof mongod + ** $ pidof mongod + Check for errors while running, or in /tmp/sosreport-*/sos_logs/ - The offending function ensure_service_is_running() in theory doesn't create any harm unless juju plugin is exercised during a sosreport run from a juju controller where mongod and juju-db reside. - + The offending function ensure_service_is_running() in theory doesn't + create any harm unless juju plugin is exercised during a sosreport run + from a juju controller where mongod and/or juju-db resides. [Regression Potential] * Risk is low. * Change is limited in scope to the juju plugin. - * Worst-case scenario is that the mongoexport command will fail to collect - any data. + * Worst-case scenario is that the mongoexport command will fail to collect any data, which won't affect core functionality of sosreport itself nor impact other sosreport plugins. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
** Description changed: [Impact] The juju plugin will stop and start the juju-db service during data collection. sosreport should not impact running services, or attempt to recover them. - This has been reported upstream and will be fixed by the juju 2.x refactor: - https://github.com/sosreport/sos/issues/1653 + This has been reported upstream[0] and will be fixed by the juju 2.x + refactor[1] - This is a stop-gap tracking the removal of the juju-db service restart code in - existing sosreport releases. - + This is a stop-gap tracking the removal of the juju-db service restart + code in existing sosreport releases. + + [0] - https://github.com/sosreport/sos/issues/1653 + [1] - https://github.com/sosreport/sos/pull/1670 + [Test Case] - * Install sosreport - * Run sosreport, ensuring that the juju plugin is exercised. - * Confirm the juju-db service was not restarted, and mongoexport data captured. + * Install sosreport + * Look mongod PID before +** pidof mongod + * Run sosreport, ensuring that the juju plugin is exercised + * Confirm the juju-db service was not restarted, and mongoexport data captured. + * Look mongod PID after +** pidof mongod Check for errors while running, or in /tmp/sosreport-*/sos_logs/ + The offending function ensure_service_is_running() in theory doesn't create any harm unless juju plugin is exercised during a sosreport run from a juju controller where mongod and juju-db reside. + + [Regression Potential] - * Risk is low. - * Change is limited in scope to the juju plugin. - * Worst-case scenario is that the mongoexport command will fail to collect -any data. + * Risk is low. + * Change is limited in scope to the juju plugin. + * Worst-case scenario is that the mongoexport command will fail to collect + any data. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
** Changed in: sosreport (Ubuntu Eoan) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
** Also affects: sosreport (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: sosreport (Ubuntu Xenial) Assignee: (unassigned) => Dan Hill (hillpd) ** Changed in: sosreport (Ubuntu Bionic) Assignee: (unassigned) => Dan Hill (hillpd) ** Changed in: sosreport (Ubuntu Cosmic) Assignee: (unassigned) => Dan Hill (hillpd) ** Changed in: sosreport (Ubuntu Disco) Assignee: (unassigned) => Dan Hill (hillpd) ** Changed in: sosreport (Ubuntu Eoan) Assignee: (unassigned) => Dan Hill (hillpd) ** Changed in: sosreport (Ubuntu Trusty) Assignee: (unassigned) => Dan Hill (hillpd) ** Changed in: sosreport (Ubuntu Trusty) Importance: Undecided => Low ** Changed in: sosreport (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: sosreport (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: sosreport (Ubuntu Cosmic) Importance: Undecided => Low ** Changed in: sosreport (Ubuntu Disco) Importance: Undecided => Low ** Changed in: sosreport (Ubuntu Eoan) Importance: Undecided => Low ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
