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

problem with multi node multi writer block device attaching ceph csi #13860

Closed
thatsk opened this issue Jul 20, 2022 · 4 comments
Closed

problem with multi node multi writer block device attaching ceph csi #13860

thatsk opened this issue Jul 20, 2022 · 4 comments

Comments

@thatsk
Copy link

thatsk commented Jul 20, 2022

Nomad version

1.3.1

Operating system and Environment details

centos 7

Issue

trying to attach policy multi-node-multi-writer. for csi volume in ceph

Reproduction steps

test-volume.hcl

id = "testmysql[0]"
name = "testmysql[0]"
type = "csi"
plugin_id = "ceph-csi"
capability {
  access_mode     = "multi-node-multi-writer"
  attachment_mode = "block-device"
}
mount_options {}
secrets {
  userID  = "test"
  userKey = "AQC19ddi7WnlKBAALrO9uNWQAe3Ss4yGJr/wAA=="
}

parameters {
  clusterID = "11c21580-0430-11ed-b181-0050568ee646"
  pool = "myPool"
  imageFeatures = "layering"
}

Expected Result

it should mount to MySQL job.

Actual Result

Screenshot from 2022-07-20 18-08-40

Job file (if appropriate)

Nomad mysql job.

job "mysql-server" {
  datacenters = ["test"]
  type        = "service"
  constraint {
    attribute = "${node.unique.name}"
    operator  = "regexp"
    value     = "test"
  }
  group "mysql-server" {
    count = 1
    volume "ceph-mysql" {
      type      = "csi"
      access_mode     = "multi-node-multi-writer"
      attachment_mode = "block-device"
      read_only = false
      source    = "testmysql[0]"
    }
    network {
      port "db" {
        static = 3306
      }
    }
    restart {
      attempts = 10
      interval = "5m"
      delay    = "25s"
      mode     = "delay"
    }
    task "mysql-server" {
      driver = "docker"
      volume_mount {
        volume      = "ceph-mysql"
        destination = "/srv"
        read_only   = false
      }
      env {
        MYSQL_ROOT_PASSWORD = "password"
      }
      config {
        image = "hashicorp/mysql-portworx-demo:latest"
        args  = ["--datadir", "/srv/mysql"]
        ports = ["db"]
      }
      resources {
        cpu    = 100
        memory = 1024
      }
      service {
        name = "mysql-server"
        port = "db"
        check {
          type     = "tcp"
          interval = "10s"
          timeout  = "2s"
        }
      }
    }
  }
}
@thatsk thatsk changed the title problem with multi node multi writer block device attaching csi problem with multi node multi writer block device attaching ceph csi Jul 20, 2022
@Amier3
Copy link
Contributor

Amier3 commented Jul 20, 2022

Hey @thatsk

Thanks for making this bug report, we'll take a look at this shortly. If you haven't seen it already, please read the comment I made on your other bug report

@tgross
Copy link
Member

tgross commented Aug 23, 2022

Hi @thatsk I tried to come up with a reproduction for this and wasn't able to; I'm not much of a Ceph expert and my Ceph isn't letting me create block device volumes.

That being said, it looks like this error is bubbling up from the mount syscall that runc is making, so it's way at the bottom of the stack in how runc is treating the block device. Do you still see this problem if you mount the volume with attachment_mode = "file-system"?

@tgross tgross self-assigned this Aug 23, 2022
@tgross
Copy link
Member

tgross commented Sep 29, 2022

Haven't heard back on this one and there's not enough information for us to reproduce (and it feels like a Ceph config issue?). If you've got more information, we'll be happy to reopen. Thanks!

@tgross tgross closed this as completed Sep 29, 2022
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Development

No branches or pull requests

3 participants