** Description changed:
[Impact]
sosreport does collect postgresql data.
The auto-package detection doesn't seems to work when postgresql is involve.
The postgresql configuration files should be collected by sosreport on
instances that run postgresql databases (Useful in a support context for
Landscape On-Premises, etc ...)
[Test case]
# Synchronize the package index files from system sources.
apt-get update
# Install sosreport
# Make sure postgresql is installed on the system.
# Run sosreport
sosreport -a
# Look at the generated "sosreport*.tar.xz" file under /tmp for
postgresql specfic content.
** Using 'sosreport -o postgresql' works well because the plugin is
specifically mention, and not expecting to auto-detect postgresql. **
[Regression Potential]
- * No regression expected, this will only affect the auto package
- detection as of when the postgresql need to run or not.
-
- This change only add an additional package name to the existing
- postgresql package detection list to better detect when postgresql is
- install for various type of postgresql installations on Debian/Ubuntu.
-
- - packages = ('postgresql',)
- + packages = ('postgresql', 'postgresql-common')
+ * TBD
[Other Info]
Upstream don't have a release planned until April 2018:
https://github.com/sosreport/sos/milestones
but April will be a crucial period for us releasing 18.04/LTS and we
will have already be reaching the freeze period for Bionic in April.
It might be good to accept this change in Bionic before its release and
then SRU it via the existing v3.5 sosreport backport effort currently in
progress via LP: #1734983.
* Upstream Github issue:
https://github.com/sosreport/sos/issues/1103
* PR :
https://github.com/sosreport/sos/pull/1117
-
- * Commit:
-
https://github.com/BryanQuigley/sos/commit/dfa07724a9e11d2ab19f61e496f2f1396d0caea0
** Description changed:
[Impact]
sosreport does collect postgresql data.
The auto-package detection doesn't seems to work when postgresql is involve.
The postgresql configuration files should be collected by sosreport on
instances that run postgresql databases (Useful in a support context for
Landscape On-Premises, etc ...)
[Test case]
# Synchronize the package index files from system sources.
apt-get update
# Install sosreport
# Make sure postgresql is installed on the system.
# Run sosreport
sosreport -a
# Look at the generated "sosreport*.tar.xz" file under /tmp for
postgresql specfic content.
** Using 'sosreport -o postgresql' works well because the plugin is
specifically mention, and not expecting to auto-detect postgresql. **
[Regression Potential]
* TBD
[Other Info]
- Upstream don't have a release planned until April 2018:
- https://github.com/sosreport/sos/milestones
-
- but April will be a crucial period for us releasing 18.04/LTS and we
- will have already be reaching the freeze period for Bionic in April.
-
- It might be good to accept this change in Bionic before its release and
- then SRU it via the existing v3.5 sosreport backport effort currently in
- progress via LP: #1734983.
-
* Upstream Github issue:
https://github.com/sosreport/sos/issues/1103
* PR :
https://github.com/sosreport/sos/pull/1117
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737569
Title:
sosreport does not collect /etc/postgresql contents
To manage notifications about this bug go to:
https://bugs.launchpad.net/sosreport/+bug/1737569/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
