Trove guest agent has postgres 9.4 configuration template. Ubuntu 16.04 LTS database guests support only postgres 9.5

[bugproxy]

---Problem Description---
checkpoint_segment parameter in Trove configuration template prohibits postgres9.5 from starting. It needs to be removed.

The name of the .pid file changes in postgres9.5 and needs to be changed accordingly in trove code

Trove checks first for upstart to start/stop database service and if exist, doesn't check for systemd files. can not start all postgres services with init . It needs to check first for systemd to start/stop database service.

---uname output---
Linux zhyp169 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:42:36 UTC 2016 s390x s390x s390x GNU/Linux

Machine Type = KVM guest on s390 lpar

---Steps to Reproduce---
1. Create an Ubuntu 16.04 database image for postgresql
2. Add a postgresql datastore to your OpenStack Trove environment
3. Launch a DB instance using this image and this datastore for postgresql

Userspace tool common name: trove guest agent

Userspace package: trove-guestagent

[Doug Shelley (0-doug)]

I believe the fix for this is [1] which was for bug [2]. While the fix is for 9.6, I believe it could be adjusted easily to suit 9.5.

[1] https://review.openstack.org/#/c/409524/
[2] https://bugs.launchpad.net/trove/+bug/1649084

[Dimitri John Ledkov (xnox)]

openstack-ibm severity-critical appears to be inaccurate, as I don't think Trove is covered for this severity level. I do not believe Trove is part of the Canonical distributions of OpenStack and one should simply use juju to deploy HA databases. Trove is an Optional OpenStack Upstream Service and clearly it's broken on xenial, and not supported. I believe experimental trove charm was a 3rd party contributed charm.

This is for the Ubuntu bug report portion.

Upstream bug report portion is valid, and appears to be in-progress by upstream.

(Note launchpad is a multi-project bug tracker)

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-09-06 10:27 EDT-------
IBM Bugzilla Status-> closed. will not be requested anymore !