[SRU] apt purge/remove percona-xtradb-cluster-server-5.7 postrm fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| percona-xtradb-cluster-5.7 (Ubuntu) |
High
|
Unassigned | ||
| Bionic |
High
|
Unassigned |
Bug Description
[Impact]
Both of the following commands fail:
apt remove percona-
apt purge percona-
with:
Removing percona-
dpkg: error processing package percona-
installed percona-
Errors were encountered while processing:
percona-
E: Sub-process /usr/bin/dpkg returned an error code (1)
The case statement in the postrm script has a 'purge)' case but no 'remove)' case. Therefore when called with the remove parameter (which occurs for both apt purge and apt remove), no match is found in the case statement, and the '*)' path is taken which calls 'exit 1'.
[Testcase]
apt remove/purge should be successful. See [Impact] section for failure that should no longer be encountered.
[Regression Potential]
Low. This just updates the postrm script to add a no-op 'remove' case.
summary: |
- apt purge/remove of percona-xtradb-cluster-server-5.7 postrm failure + apt purge/remove of percona-xtradb-cluster-server-5.7 postrm fails |
summary: |
- apt purge/remove of percona-xtradb-cluster-server-5.7 postrm fails + [SRU] apt purge/remove of percona-xtradb-cluster-server-5.7 postrm fails |
summary: |
- [SRU] apt purge/remove of percona-xtradb-cluster-server-5.7 postrm fails + [SRU] apt purge/remove percona-xtradb-cluster-server-5.7 postrm fails |
description: | updated |
Launchpad Janitor (janitor) wrote : | #1 |
Changed in percona-xtradb-cluster-5.7 (Ubuntu): | |
status: | New → Confirmed |
Changed in percona-xtradb-cluster-5.7 (Ubuntu): | |
importance: | Undecided → High |
status: | Confirmed → Triaged |
Launchpad Janitor (janitor) wrote : | #2 |
This bug was fixed in the package percona-
---------------
percona-
* d/percona-
to prevent postrm failure when removing or purging package (LP: #1771869).
* d/rules: Update based on previous renaming of d/bundle-boost.s to
d/repack.sh.
-- Corey Bryant <email address hidden> Thu, 17 May 2018 14:46:31 -0400
Changed in percona-xtradb-cluster-5.7 (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in percona-xtradb-cluster-5.7 (Ubuntu Bionic): | |
importance: | Undecided → High |
status: | New → Triaged |
description: | updated |
description: | updated |
description: | updated |
Vincent Gerris (vgerris) wrote : | #3 |
hi, when will the package be available ? I have the same issue :
dpkg: error processing package percona-
installed percona-
Processing triggers for man-db (2.8.3-2) ...
Errors were encountered while processing:
percona-
I work around apt being stuck with:
sudo apt install --reinstall percona-
Corey Bryant (corey.bryant) wrote : | #4 |
Hi Vincent,
It's just waiting on review by the SRU team and it's in queue for that at: https:/
Thanks,
Corey
Hello Corey, or anyone else affected,
Accepted percona-
Please help us by testing this new package. See https:/
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-
Further information regarding the verification process can be found at https:/
Changed in percona-xtradb-cluster-5.7 (Ubuntu Bionic): | |
status: | Triaged → Fix Committed |
tags: | added: verification-needed verification-needed-bionic |
EvgeniyPatlan (evgeniy-patlan) wrote : | #6 |
I wasn't able to enable proposed repo:
=======
Err:5 http://
404 Not Found [IP: 91.189.91.11 80]
Ign:7 http://
Fetched 242 kB in 2s (100 kB/s)
Reading package lists... Done
E: Failed to fetch http://
E: Some index files failed to download. They have been ignored, or old ones used instead.
========
I have manually build package from sources provided on launchpad and tested it. Seems it works ok.
Vincent Gerris (vgerris) wrote : Re: [Bug 1771869] Re: [SRU] apt purge/remove percona-xtradb-cluster-server-5.7 postrm fails | #7 |
hi,
I tested the package by downloading and:
- it upgrades the current version
- is able to be removed : I guess that is the main factor
- can be installed again
- the database starts and is accessible
Seems like it works, thank you and I hope we see it in Release soon.
On Wed, Jun 6, 2018 at 4:39 PM, Robie Basak <email address hidden>
wrote:
> Hello Corey, or anyone else affected,
>
> Accepted percona-
> will build now and be available at https:/
> /percona-
> then in the -proposed repository.
>
> Please help us by testing this new package. See
> https:/
> 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-
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-
> testing will help us make a better decision.
>
> Further information regarding the verification process can be found at
> https:/
> advance!
>
> ** Changed in: percona-
> Status: Triaged => Fix Committed
>
> ** Tags added: verification-needed verification-
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [SRU] apt purge/remove percona-
>
> Status in percona-
> Fix Released
> Status in percona-
> Fix Committed
>
> Bug description:
> [Impact]
>
> Both of the following commands fail:
>
> apt remove percona-
> apt purge percona-
>
> with:
>
> Removing percona-
> dpkg: error processing package percona-
> (--remove):
> installed percona-
> script subprocess returned error exit status 1
> Errors were encountered while processing:
> percona-
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> The case statement in the postrm script has a 'purge)' case but no
> 'remove)' case. Therefore when called with the remove parameter (which
> occurs for both apt purge and apt remove), no match is found in the
> case statement, and the '*)' path is taken which calls 'exit 1'.
>
> [Testcase]
>
> apt remove/purge should be successful. See [Impact] section for
> failure that should no longer be encountered.
>
> [Regression Potential]
> Low. This just updates the postrm script to add a no-op 'remove' case.
>
> To manage notifications about this bug...
Corey Bryant (corey.bryant) wrote : | #8 |
Based on the feedback above, I'm tagging this as verification-
Evgeniy, I don't have a armhf/arm64/
Thanks,
Corey
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
Launchpad Janitor (janitor) wrote : | #9 |
This bug was fixed in the package percona-
---------------
percona-
* d/percona-
to prevent postrm failure when removing or purging package (LP: #1771869).
* d/rules: Update based on previous renaming of d/bundle-boost.s to
d/repack.sh.
-- Corey Bryant <email address hidden> Thu, 17 May 2018 14:46:31 -0400
Changed in percona-xtradb-cluster-5.7 (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
The verification of the Stable Release Update for percona-
Status changed to 'Confirmed' because the bug affects multiple users.