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: Longhorn volumes not corretly mounted #1595

Open
Despire opened this issue Dec 3, 2024 · 1 comment
Open

Bug: Longhorn volumes not corretly mounted #1595

Despire opened this issue Dec 3, 2024 · 1 comment
Labels
bug Something isn't working groomed Task that everybody agrees to pass the gatekeeper

Comments

@Despire
Copy link
Contributor

Despire commented Dec 3, 2024

Current Behaviour

For AWS the volumes that are attached while spawning the infrastructure in terraformer are not properly mounted under /opt/claudie/data which is the path used for longhorn.

One can verify this by spawning an cluster with AWS working nodes and SSHing into a node executing
mount | grep claudie.
which returns nothing as there is no mount for the /opt/claudie/data/ directory.

Also there are missing settings under /etc/fstab

Expected Behaviour

Volumes should be mounted correctly

Steps To Reproduce

  1. Spawn a cluster with AWS nodes
  2. verify missing mounts for /opt/claudie/data/ with mount | grep "claudie" or cat /proc/mount | grep "claudie" or cat /etc/fstab

Anything else to note

Check other cloudproviders as well

@Despire Despire added bug Something isn't working groomed Task that everybody agrees to pass the gatekeeper labels Dec 3, 2024
@bernardhalas
Copy link
Member

Pending GenesisCloud IPV4 public address cross-connectivity fix.

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

No branches or pull requests

2 participants