| 2023-03-28 13:34:04 |
Keha |
bug |
|
|
added bug |
| 2023-03-28 13:37:13 |
Launchpad Janitor |
resource-agents (Ubuntu): status |
New |
Confirmed |
|
| 2023-03-29 14:57:12 |
Athos Ribeiro |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-03-29 14:57:12 |
Athos Ribeiro |
bug task added |
|
resource-agents (Ubuntu Jammy) |
|
| 2023-03-29 14:57:19 |
Athos Ribeiro |
resource-agents (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2023-03-29 14:59:34 |
Athos Ribeiro |
resource-agents (Ubuntu Jammy): status |
New |
Triaged |
|
| 2023-03-29 14:59:44 |
Athos Ribeiro |
bug |
|
|
added subscriber Ubuntu Server |
| 2023-03-29 15:13:57 |
Athos Ribeiro |
tags |
ha postgresql |
bitesize ha postgresql |
|
| 2023-03-29 15:15:52 |
Athos Ribeiro |
summary |
deprecated package |
pgsql heartbeat does not support current postgreSQL version |
|
| 2023-05-03 10:25:42 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~michal-maloszewski99/ubuntu/+source/resource-agents/+git/resource-agents/+merge/442253 |
|
| 2023-05-22 13:50:37 |
Michał Małoszewski |
description |
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case the bug reporter will be responsible for testing the package.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
|
| 2023-05-23 16:27:38 |
Michał Małoszewski |
description |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case the bug reporter will be responsible for testing the package.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case the bug reporter will be responsible for testing the package.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
The monitor function is triggered and the wal receiver process is named "wal receiver process".
Expected result:
.
The monitor function is triggered and the wal receiver process is named "walreceiver".
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
|
| 2023-05-23 16:27:52 |
Michał Małoszewski |
description |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case the bug reporter will be responsible for testing the package.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
The monitor function is triggered and the wal receiver process is named "wal receiver process".
Expected result:
.
The monitor function is triggered and the wal receiver process is named "walreceiver".
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case the bug reporter will be responsible for testing the package.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
The monitor function is triggered and the wal receiver process is named "wal receiver process".
Expected result:
The monitor function is triggered and the wal receiver process is named "walreceiver".
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
|
| 2023-05-24 06:26:05 |
Michał Małoszewski |
resource-agents (Ubuntu Jammy): assignee |
|
Michał Małoszewski (michal-maloszewski99) |
|
| 2023-05-24 06:26:09 |
Michał Małoszewski |
resource-agents (Ubuntu Jammy): status |
Triaged |
In Progress |
|
| 2023-05-24 07:05:04 |
Michał Małoszewski |
description |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case the bug reporter will be responsible for testing the package.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
The monitor function is triggered and the wal receiver process is named "wal receiver process".
Expected result:
The monitor function is triggered and the wal receiver process is named "walreceiver".
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case the bug reporter will be responsible for testing the package.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
After typing in: "ps -ef" the wal receiver process should be named "wal receiver process".
Expected result:
If the monitor function is triggered, then after typing in: "ps -ef" the wal receiver process should be named "walreceiver".
(In my system, there are some issues which prevents me from testing that. I got some errors related to calling that function which were unpredictable and after resolving one problem, another occurred.)
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
|
| 2023-05-24 16:20:35 |
Michał Małoszewski |
description |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case the bug reporter will be responsible for testing the package.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
After typing in: "ps -ef" the wal receiver process should be named "wal receiver process".
Expected result:
If the monitor function is triggered, then after typing in: "ps -ef" the wal receiver process should be named "walreceiver".
(In my system, there are some issues which prevents me from testing that. I got some errors related to calling that function which were unpredictable and after resolving one problem, another occurred.)
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case the bug reporter will be responsible for testing the package.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
Pgsql monitor function does not monitor the process correctly.
Expected result:
Pgsql monitor function does monitor the process correctly and the result of that operation is visible.
((In my system, there are some issues which prevents me from testing that. I got some errors related to calling that function which were unpredictable and after resolving one problem, another occurred.)
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
|
| 2023-05-31 15:13:52 |
Michał Małoszewski |
tags |
bitesize ha postgresql |
bitesize ha postgresql server-todo |
|
| 2023-06-01 16:05:50 |
Ubuntu Archive Robot |
bug |
|
|
added subscriber Athos Ribeiro |
| 2023-06-01 21:08:39 |
Andreas Hasenack |
resource-agents (Ubuntu Jammy): status |
In Progress |
Incomplete |
|
| 2023-06-02 11:36:22 |
Michał Małoszewski |
tags |
bitesize ha postgresql server-todo |
ha postgresql server-todo |
|
| 2023-06-22 09:29:05 |
Michał Małoszewski |
description |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case the bug reporter will be responsible for testing the package.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
Pgsql monitor function does not monitor the process correctly.
Expected result:
Pgsql monitor function does monitor the process correctly and the result of that operation is visible.
((In my system, there are some issues which prevents me from testing that. I got some errors related to calling that function which were unpredictable and after resolving one problem, another occurred.)
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case, the bug reporter will be responsible for testing the package. Keha confirmed that he would test the package.
I tried myself to create a setup manually and using Juju; either way, I couldn't cope with the problem that I bumped into and that I described in comment #15 in the comment section below.
Due to that, plus the fact that I do not know what kind of output or result I should expect and Keha is willing to test the package, my Test Plan is quite vague.
Additionally, I cannot outline my specific steps that did not work out in the Test Plan to not mislead anyone who will be in charge of testing - in that case - Keha.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
Pgsql monitor function does not monitor the process correctly.
Expected result:
Pgsql monitor function does monitor the process correctly and the result of that operation is visible.
((In my system, there are some issues which prevents me from testing that. I got some errors related to calling that function which were unpredictable and after resolving one problem, another occurred.)
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
|
| 2023-06-22 09:30:40 |
Michał Małoszewski |
description |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case, the bug reporter will be responsible for testing the package. Keha confirmed that he would test the package.
I tried myself to create a setup manually and using Juju; either way, I couldn't cope with the problem that I bumped into and that I described in comment #15 in the comment section below.
Due to that, plus the fact that I do not know what kind of output or result I should expect and Keha is willing to test the package, my Test Plan is quite vague.
Additionally, I cannot outline my specific steps that did not work out in the Test Plan to not mislead anyone who will be in charge of testing - in that case - Keha.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
Pgsql monitor function does not monitor the process correctly.
Expected result:
Pgsql monitor function does monitor the process correctly and the result of that operation is visible.
((In my system, there are some issues which prevents me from testing that. I got some errors related to calling that function which were unpredictable and after resolving one problem, another occurred.)
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case, the bug reporter will be responsible for testing the package. Keha confirmed that he would test the package.
I tried myself to create a setup manually and using Juju; either way, I couldn't cope with the problem that I bumped into and that I described in comment #15 in the comment section below.
Due to that, plus the fact that I do not know what kind of output or result I should expect and Keha is willing to test the package, my Test Plan is quite vague.
Additionally, I cannot outline my specific steps that did not work out in the Test Plan to not mislead anyone who will be in charge of testing - in this case - Keha.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
Pgsql monitor function does not monitor the process correctly.
Expected result:
Pgsql monitor function does monitor the process correctly and the result of that operation is visible.
((In my system, there are some issues which prevents me from testing that. I got some errors related to calling that function which were unpredictable and after resolving one problem, another occurred.)
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
|
| 2023-06-22 09:32:24 |
Michał Małoszewski |
description |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case, the bug reporter will be responsible for testing the package. Keha confirmed that he would test the package.
I tried myself to create a setup manually and using Juju; either way, I couldn't cope with the problem that I bumped into and that I described in comment #15 in the comment section below.
Due to that, plus the fact that I do not know what kind of output or result I should expect and Keha is willing to test the package, my Test Plan is quite vague.
Additionally, I cannot outline my specific steps that did not work out in the Test Plan to not mislead anyone who will be in charge of testing - in this case - Keha.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
Pgsql monitor function does not monitor the process correctly.
Expected result:
Pgsql monitor function does monitor the process correctly and the result of that operation is visible.
((In my system, there are some issues which prevents me from testing that. I got some errors related to calling that function which were unpredictable and after resolving one problem, another occurred.)
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case, the bug reporter will be responsible for testing the package. Keha confirmed that he would test the package.
I tried myself to create a setup manually and using Juju; either way, I couldn't cope with the problem that I bumped into and that I described in comment #15 in the comment section below.
Due to that, plus the fact that I do not know what kind of output or result I should expect and Keha is willing to test the package, my Test Plan is quite vague.
Additionally, I cannot outline my specific steps that did not work out in the Test Plan to not mislead anyone who will be in charge of testing - in this case - Keha.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
Pgsql monitor function does not monitor the process correctly.
Expected result:
Pgsql monitor function does monitor the process correctly and the result of that operation is visible.
(In my system, there are some issues which prevents me from testing that. I got some errors related to calling that function which were unpredictable and after resolving one problem, another occurred.)
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
|
| 2023-07-04 21:37:16 |
Andreas Hasenack |
bug |
|
|
added subscriber Andreas Hasenack |
| 2023-07-05 15:10:25 |
Michał Małoszewski |
description |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
In this specific case, the bug reporter will be responsible for testing the package. Keha confirmed that he would test the package.
I tried myself to create a setup manually and using Juju; either way, I couldn't cope with the problem that I bumped into and that I described in comment #15 in the comment section below.
Due to that, plus the fact that I do not know what kind of output or result I should expect and Keha is willing to test the package, my Test Plan is quite vague.
Additionally, I cannot outline my specific steps that did not work out in the Test Plan to not mislead anyone who will be in charge of testing - in this case - Keha.
First, there is a need to create a PostgreSQL streaming replication setup.
Then, after the setup will work correctly, there is a need to trigger a function from the heartbeat/pgsql file which will trigger the wal receiver by resource-agents and check processes.
Actual result:
Pgsql monitor function does not monitor the process correctly.
Expected result:
Pgsql monitor function does monitor the process correctly and the result of that operation is visible.
(In my system, there are some issues which prevents me from testing that. I got some errors related to calling that function which were unpredictable and after resolving one problem, another occurred.)
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
[Impact]
* resource-agents version 4.7.0 does not correctly work with PostgreSQL 11 and above.
* The issue appears on 22.04 and the resource-agents package is affected.
* This issue is caused by the receiver_parent_pids variable, which assigns the wrong name of the wal receiver process.
* The fix is to assign the correct name of the wal receiver process to search for that process and make the wal receiver check compatible with PostgreSQL >= 11.
[Test Plan]
Create a lxd container for the primary postgresql:
$ lxc launch ubuntu:jammy j1
Connect and install packages:
$ lxc shell j1
# apt update && apt install postgresql resource-agents-extra pacemaker-cli-utils -y
Configure postgresql.conf and pg_hba.conf:
# pg_conftool 14 main set listen_addresses '*'
# pg_conftool 14 main set wal_level replica
# echo "host replication replicator all scram-sha-256" >> /etc/postgresql/14/main/pg_hba.conf
Create replication user (choose a password, and remember it, it will be needed again later):
# sudo -u postgres createuser --replication -P -e replicator
restart the primary postgresql:
# systemctl restart postgresql
Back on the host, create lxd container for the secondary postgresql:
$ lxc launch ubuntu:jammy j2
Connect and install packages:
$ lxc shell j2
# apt update && apt install postgresql resource-agents-extra pacemaker-cli-utils -y
Stop postgresql:
# systemctl stop postgresql
Configure postgresql.conf:
# pg_conftool 14 main set listen_addresses '*'
# pg_conftool 14 main set hot_standby on
Cleanup data dir:
# rm -rf /var/lib/postgresql/*/main/*
Perform initial replication as "postgres" user. The pg_basebackup command will prompt for the "replicator" password created earlier on the primary:
# sudo -u postgres -i
$ pg_basebackup -h <IP-of-primary> -D /var/lib/postgresql/14/main -U replicator -P -v -R
$ exit
Start the secondary:
# systemctl start postgresql
Verify replication: list of databases on the secondary does not have a "test" database:
# sudo -u postgres psql -l 2>/dev/null | grep test
#
On the primary, create a test database:
$ lxc shell j1
# sudo -u postgres createdb test
could not change directory to "/root": Permission denied
# sudo -u postgres psql -l 2>/dev/null | grep test
test | postgres | UTF8 | C.UTF-8 | C.UTF-8 |
On the secondary, verify that the test database now exists:
$ lxc shell j2
# sudo -u postgres psql -l 2>/dev/null | grep test
test | postgres | UTF8 | C.UTF-8 | C.UTF-8 |
Check that the secondary does have a "walreceiver" process running:
$ lxc shell j2
# ps axw|grep -E "postgres:.*wal" | grep -v grep
6001 ? Ss 0:06 postgres: 14/main: walreceiver streaming 0/7000780
Now run this long command, one line, on the secondary.
Actual result:
With the bug present, the command will complain that the walreceiver process is NOT running:
# OCF_RESKEY_check_wal_receiver=true OCF_RESKEY_socketdir=/run/postgresql OCF_RESKEY_config=/etc/postgresql/14/main/postgresql.conf OCF_RESKEY_pgctl=/usr/lib/postgresql/14/bin/pg_ctl OCF_RESKEY_pgdata=/var/lib/postgresql/14/main OCF_ROOT=/usr/lib/ocf /usr/lib/ocf/resource.d/heartbeat/pgsql monitor
INFO: Don't check /var/lib/postgresql/14/main during probe
WARNING: wal receiver process is not running
Expected result:
The warning is not present in the output.
[Where problems could occur]
* The patch itself modifies only the heartbeat/pgsql code, so regressions should be limited to the behavior of pgsql.
* Since the code changes affect the pgsql_wal_receiver_status() function, there might be a problem related to the status of the wal receiver and the status of the running processes.
----------------------------original bug report---------------------------
Hello!
Ubuntu 22.04.2 include packages resource-agents version 4.7.0 (release 2020). This version non-correct work with PostgreSQL 11 and above.
resource-agents get fix 'WAL receiver process' in 4.8.0 rc1 (release 2021)
See links
https://github.com/ClusterLabs/resource-agents/blob/baddb06c9720c8df3dadea42ad863d5948a6345f/ChangeLog
Current version resource-agents 4.12.0 |
|
| 2023-07-07 21:26:37 |
Steve Langasek |
resource-agents (Ubuntu Jammy): status |
Incomplete |
In Progress |
|
| 2023-07-14 22:35:06 |
Steve Langasek |
resource-agents (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2023-07-14 22:35:07 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-07-14 22:35:15 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2023-07-14 22:35:20 |
Steve Langasek |
tags |
ha postgresql server-todo |
ha postgresql server-todo verification-needed verification-needed-jammy |
|
| 2023-07-19 14:24:57 |
Michał Małoszewski |
tags |
ha postgresql server-todo verification-needed verification-needed-jammy |
ha postgresql server-todo verification-done verification-done-jammy |
|
| 2023-07-26 13:54:50 |
Robie Basak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-07-26 13:55:09 |
Launchpad Janitor |
resource-agents (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
