Landscape scripts have hard coded postgres superuser

Bug #1987689 reported by Marcelo Henrique Neppel
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Landscape Server

Bug Description

Landscape has some script that have hard code the postgres superuser (the default in PostgreSQL installations).

Some examples:

This is fine for most of the PostgreSQL installations, but if the PostgreSQL cluster is bootstrapped with another superuser name, Landscape fails when trying to bootstrap the database on PostgreSQL, because the postgres user does not exist.

One possible solution would be to have a configurable username that would replace those hard coded values in the scripts.

About the use case where we faced this issue: we are using Patroni ( do manage a PostgreSQL deployment in the new PostgreSQL VM charm and we have some alignments to use specific superusers inside the database, like one named operator, and remove other users. For now, we are keeping the postgres superuser because, otherwise, the charm will not work with Landscape Server charm or Landscape Scalable bundle.

information type: Proprietary → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.