RPM spec doesn't restart Percona on upgrade
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Percona Server | Status tracked in 5.6 | |||||
| | 5.5 |
Critical
|
Stewart Smith | |||
| | 5.6 |
Critical
|
Laurynas Biveinis | |||
| | Percona XtraDB Cluster |
Critical
|
Ignacio Nin | |||
Bug Description
The change at https:/
The conditional should be around the section that creates the test DB but is around a larger section, including the section that sets the SERVER_TO_START variable. Since [ $1 -eq 1 ] will only be true for new installs, the section that sets the varialbe SERVER_TO_START is never run and the variable is never set. When it gets to part of the spec where it would restart Percona based on the SERVER_TO_START variable, it doesn't restart it since the variable was never set.
Related branches
- Ignacio Nin (community): Disapprove on 2013-04-23
- Percona core: Pending requested 2013-04-23
- Diff: 26 lines (+6/-5) 1 file modified
- Stewart Smith (community): Approve on 2013-04-23
- Percona core: Pending requested 2013-04-23
- Diff: 26 lines (+6/-5) 1 file modified
- Raghavendra D Prabhu: Needs Fixing on 2013-06-05
- Diff: 0 lines
- Stewart Smith (community): Approve on 2013-05-31
- Diff: 28652 lines (+8737/-18610) 172 files modified
| tags: | added: pkg |
| Stewart Smith (stewart) wrote : | #1 |
| Changed in percona-server: | |
| status: | New → Fix Committed |
| importance: | Undecided → High |
| assignee: | nobody → Stewart Smith (stewart) |
| Ignacio Nin (ignacio-nin) wrote : | #2 |
Confirmed not to affect 5.1.
Confirmed to affect PXC, added to the bug list
5.6 is not yet affected, but it will become affected as soon as revno 472 from 5.5 is merged.
Rebasing Stewart's fix to revno 472 so it can be merged easily to PXC and in the future to 5.6.
| Changed in percona-xtradb-cluster: | |
| status: | New → Confirmed |
| importance: | Undecided → Critical |
| assignee: | nobody → Ignacio Nin (ignacio-nin) |
| Changed in percona-xtradb-cluster: | |
| status: | Confirmed → Fix Committed |
| milestone: | none → 5.5.30-24.8 |
| Changed in percona-xtradb-cluster: | |
| status: | Fix Committed → Fix Released |
This is pretty serious (especially when combined with automatic updates on a server). We should reissue packages with this fix.
I have not checked if this affects 5.6 - i'm told it doesn't affect 5.1