Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: MountVolume.SetUp failed for volume - Add multipath config for Longhorn #1383

Closed
Danielss89 opened this issue May 10, 2024 · 1 comment · Fixed by #1386
Closed

Bug: MountVolume.SetUp failed for volume - Add multipath config for Longhorn #1383

Danielss89 opened this issue May 10, 2024 · 1 comment · Fixed by #1386
Labels
bug Something isn't working groomed Task that everybody agrees to pass the gatekeeper

Comments

@Danielss89
Copy link
Contributor

I was getting the following error for a pvc:

2024-05-10 13:18:58+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.2.3+maria~ubu2204 started.
2024-05-10 13:18:58+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
2024-05-10 13:18:58+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-05-10 13:18:58+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.2.3+maria~ubu2204 started.
2024-05-10 13:18:59+00:00 [Note] [Entrypoint]: Initializing database files
2024-05-10 13:18:59 0 [ERROR] InnoDB: innodb_page_size=16384 requires innodb_buffer_pool_size >= 5MiB current 2MiB
2024-05-10 13:18:59 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2024-05-10 13:18:59 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2024-05-10 13:18:59 0 [ERROR] Aborting

A fix for this is to update a config on the nodes where volumes are stored.

Basicly the file /etc/multipath.conf must be updated to include:

blacklist {
    devnode "^sd[a-z0-9]+"
}

And then restart: systemctl restart multipathd.service

I think Claudie should do this for all the nodes when bootstrapping them.

Read more about it here: https://longhorn.io/kb/troubleshooting-volume-with-multipath/

@Danielss89 Danielss89 added the bug Something isn't working label May 10, 2024
@Danielss89
Copy link
Contributor Author

✨✨ Here's an AI-assisted sketch of how you might approach this issue saved by @Danielss89 using Copilot Workspace v0.17

Topic

Does the /etc/multipath.conf file include the specified blacklist configuration to prevent MountVolume.SetUp errors? 🛠️

Before
  • No, the /etc/multipath.conf file does not include the specified blacklist configuration to prevent MountVolume.SetUp errors. 🛠️
  • The repository does not contain a file named /etc/multipath.conf or any ansible playbook that modifies this file. 📁
  • The ansible playbook services/ansibler/server/ansible-playbooks/longhorn-req.yml is used for installing Longhorn dependencies but does not modify /etc/multipath.conf. 🐂
After
  • Yes, the /etc/multipath.conf file now includes the specified blacklist configuration to prevent MountVolume.SetUp errors. 🛠️
  • The ansible playbook services/ansibler/server/ansible-playbooks/longhorn-req.yml is modified to include tasks for updating /etc/multipath.conf with the required blacklist configuration and restarting the multipathd.service. 🔄
  • The modification ensures that all nodes, upon setup, will have the correct multipath configuration to support Longhorn without encountering MountVolume.SetUp errors. 🖥️
Plan
  • services/ansibler/server/ansible-playbooks/longhorn-req.yml (CHANGE)
    • Add tasks to update /etc/multipath.conf with the specified blacklist configuration
    • Add a task to restart multipathd.service after updating the configuration
    • Ensure the changes are applied before installing Longhorn dependencies
Sketch of implementation

View the changes

Details

Code analyzed at a6836cd

@bernardhalas bernardhalas added the groomed Task that everybody agrees to pass the gatekeeper label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working groomed Task that everybody agrees to pass the gatekeeper
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants