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

Fix attaching encrypted volume on controller nodes #407

Merged

Commits on Jun 28, 2024

  1. Fix attaching encrypted volume on controller nodes

    Just like with iscsiadm and other command tools there is a need to run
    the command on the host's namespace.
    
    If we don't run it like that the command will get stuck in:
    
      cryptsetup luksOpen --key-file=- /dev/dm-8 crypt-os-brick+dev+dm-8
    
    And if we manually run the command with debug option (`--debug
    --verbose`) we'll see that it gets stuck in:
    
      # Udev cookie 0xd4d73ad (semid 3) waiting for zero
    
    And is unable to continue with the rest:
    
      # Udev cookie 0xd4d3938 (semid 3) destroyed
      # Releasing crypt device /dev/mapper/3600140584b9fc02da024f9c8130ce253 context.
      # Releasing device-mapper backend.
      # Closing read only fd for /dev/mapper/3600140584b9fc02da024f9c8130ce253.
      Command successful.
    
    This patch ensure we use `nsenter` to run `cryptsetup`.
    Akrog committed Jun 28, 2024
    Configuration menu
    Copy the full SHA
    99be1db View commit details
    Browse the repository at this point in the history