Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

PXC bootstrap service changes incomplete for systemd

Description

First of all, the mysql@bootstrap.service is NOT meant for being enabled, unless in a very specific (odd) case of a single node "cluster" maybe.

Now, there is an issue when this service gets enabled by accident/mistake. Disabling it does not revert all the changes it made during enable command.

It was observed on PXC 8.0.27 without previous other services modifications, but I can consistently reproduce it only when I first manually remove the mysqld symlink, as follows:

 

At this point, the mysql@bootstrap.service cannot be disabled using systemctl command alone, but we have to manually remove the second symlink first:

This happens in both PXC 8.0.27 and 8.0.30. If "enable" creates two symlinks, then "disable" should also remove two symlinks, but it does remove only one.

 

In PXC 5.7.40 the situation is slightly different, but still the issue is there:

 

 

Environment

None

AFFECTED CS IDs

CS0033212

Activity

Show:

Kamil Holubicki February 27, 2023 at 2:16 PM

As explained above, this is systemd problem. Closing.

Kamil Holubicki February 8, 2023 at 12:59 PM
Edited

TL;DR

In my opinion, it is the problem with systemd version on CentOS 7 (v219). CentOS 8 (v239-44) works fine.

 

Details

CentOS 7. I confirm it works exactly the same as in the ticket description

 

According to THESE INSTRUCTIONS, I've update systemd to v231, but the behavior is the same.

 

CentOS 8. Everyting works fine

 

Symlinks mentioned in the description are managed (created and deleted) by systemctl. It looks like it was fixed between v231 and v239-44. I think it may be commit https://github.com/systemd/systemd/commit/9ea3a0e702e741e5a6015093dd02a2374722a62d

 

I'm afraid there is nothing we can do about this.

Not a Bug

Details

Assignee

Reporter

Needs QA

Yes

Affects versions

Priority

Smart Checklist

Created February 3, 2023 at 10:33 AM
Updated March 6, 2024 at 8:46 PM
Resolved February 27, 2023 at 2:16 PM