IBM / ibm-block-csi-driver

The IBM block storage CSI driver enables container orchestrators, such as Kubernetes and Openshift, to manage the life-cycle of persistent storage
Apache License 2.0
33 stars 25 forks source link

ibm-block-csi-node fails to read initiatorname.iscsi #456

Closed walbers closed 2 years ago

walbers commented 2 years ago

The ibm-block-csi-node pods fail to come up because they get the error GRPC error: rpc error: code = Internal desc = Cannot find valid nvme nqn, fc wwns or iscsi iqn. The pods also say

 WARNING        [77] [-] (node.go:757) - Error while trying to get iscsi port from string: ## DO NOT EDIT OR REMOVE THIS FILE!
## If you remove this file, the iSCSI daemon will not start.
## If you change the InitiatorName, existing access control lists
## may reject this initiator.  The InitiatorName must be unique
## for each iSCSI initiator.  Do NOT duplicate iSCSI InitiatorNames.
InitiatorName=iqn.1993-08.org.debian:01:f64a9ce8f27.

I am guessing the error is because of the comments above InitiatorName in the /etc/iscsi/initiatorname.iscsi file. This really shouldn't happen because this is the default file on Ubuntu. I went ahead and deleted the comments from the file and restarted iscsi and then deleted and reapplied the ibm-block-csi-driver. This error was still happening. I went ahead and restarted my machine and checked the initiatorname.iscsi file and it currently looks like:

root@smexxact:/etc/iscsi# cat initiatorname.iscsi
InitiatorName=iqn.1993-08.org.debian:01:219b5d4f819a

I then deleted and reapplied the ibm-block-csi-driver and it still throwing the same error. What is going on here? How do I fix this?

I included one pods full log dump:

$ kubectl logs ibm-block-csi-node-27x7b -c ibm-block-csi-node
2022-02-19 18:13:42,2196 DEBUG  [1] [-] (main.go:37) - Starting CSI node...
2022-02-19 18:13:42,2196 DEBUG  [1] [-] (driver.go:137) - Config file environment variable DRIVER_CONFIG_YML=./config.yaml
2022-02-19 18:13:42,2196 INFO   [1] [-] (driver.go:138) - trace
2022-02-19 18:13:42,2196 INFO   [1] [-] (main.go:33) - Node version info: {
  "driverVersion": "1.8.0",
  "gitCommit": "312a4aafe9f95d3cebabeb6a72e2d283c925a503",
  "buildDate": "2021-12-13T08:41:08Z",
  "goVersion": "go1.13.15",
  "compiler": "gc",
  "platform": "linux/amd64"
}
2022-02-19 18:13:42,2196 DEBUG  [1] [-] (driver.go:137) - Config file environment variable DRIVER_CONFIG_YML=./config.yaml
2022-02-19 18:13:42,2196 INFO   [1] [-] (driver.go:138) - trace
2022-02-19 18:13:42,2196 INFO   [1] [-] (driver.go:49) - Driver: block.csi.ibm.com Version: 1.8.0
2022-02-19 18:13:42,2196 INFO   [1] [-] (driver.go:97) - Listening for connections on address: &net.UnixAddr{Name:"/csi/csi.sock", Net:"unix"}
2022-02-19 18:13:42,2196 DEBUG  [6] [-] (identity.go:26) - GetPluginInfo: called with args {XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}
2022-02-19 18:13:43,2196 DEBUG  [28] [-] (identity.go:26) - GetPluginInfo: called with args {XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}
2022-02-19 18:13:44,2196 DEBUG  [30] [-] (node.go:723) - >>>> NodeGetInfo: called with args {XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}
2022-02-19 18:13:44,2196 DEBUG  [30] [-] (node.go:735) - discovered topology labels : map[]
2022-02-19 18:13:44,2196 WARNING    [30] [-] (node.go:757) - Error while trying to get iscsi port from string: ## DO NOT EDIT OR REMOVE THIS FILE!
## If you remove this file, the iSCSI daemon will not start.
## If you change the InitiatorName, existing access control lists
## may reject this initiator.  The InitiatorName must be unique
## for each iSCSI initiator.  Do NOT duplicate iSCSI InitiatorNames.
InitiatorName=iqn.1993-08.org.debian:01:f64a9ce8f27.
2022-02-19 18:13:44,2196 DEBUG  [30] [-] (node.go:763) - <<<< NodeGetInfo
2022-02-19 18:13:44,2196 ERROR  [30] [-] (driver.go:85) - GRPC error: rpc error: code = Internal desc = Cannot find valid nvme nqn, fc wwns or iscsi iqn
2022-02-19 18:13:45,2196 DEBUG  [35] [-] (identity.go:26) - GetPluginInfo: called with args {XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}
2022-02-19 18:13:46,2196 DEBUG  [40] [-] (node.go:723) - >>>> NodeGetInfo: called with args {XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}
2022-02-19 18:13:46,2196 DEBUG  [40] [-] (node.go:735) - discovered topology labels : map[]
2022-02-19 18:13:46,2196 WARNING    [40] [-] (node.go:757) - Error while trying to get iscsi port from string: ## DO NOT EDIT OR REMOVE THIS FILE!
## If you remove this file, the iSCSI daemon will not start.
## If you change the InitiatorName, existing access control lists
## may reject this initiator.  The InitiatorName must be unique
## for each iSCSI initiator.  Do NOT duplicate iSCSI InitiatorNames.
InitiatorName=iqn.1993-08.org.debian:01:f64a9ce8f27.
2022-02-19 18:13:46,2196 DEBUG  [40] [-] (node.go:763) - <<<< NodeGetInfo
2022-02-19 18:13:46,2196 ERROR  [40] [-] (driver.go:85) - GRPC error: rpc error: code = Internal desc = Cannot find valid nvme nqn, fc wwns or iscsi iqn
2022-02-19 18:14:00,2196 DEBUG  [55] [-] (identity.go:26) - GetPluginInfo: called with args {XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}
2022-02-19 18:14:01,2196 DEBUG  [47] [-] (node.go:723) - >>>> NodeGetInfo: called with args {XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}
2022-02-19 18:14:01,2196 DEBUG  [47] [-] (node.go:735) - discovered topology labels : map[]
2022-02-19 18:14:01,2196 WARNING    [47] [-] (node.go:757) - Error while trying to get iscsi port from string: ## DO NOT EDIT OR REMOVE THIS FILE!
## If you remove this file, the iSCSI daemon will not start.
## If you change the InitiatorName, existing access control lists
## may reject this initiator.  The InitiatorName must be unique
## for each iSCSI initiator.  Do NOT duplicate iSCSI InitiatorNames.
InitiatorName=iqn.1993-08.org.debian:01:f64a9ce8f27.

I do have IBM support for my FlashSystem 5030 as well. Let me know if that will get me a better response.

roysahar commented 2 years ago

@walbers , Are you running your nodes on ubuntu OS?

walbers commented 2 years ago

@roysahar Yes Ubuntu 18.04

roysahar commented 2 years ago

@walbers Currently IBM block csi driver is not supported with Ubuntu linux distribution. See https://www.ibm.com/docs/en/stg-block-csi-driver/1.8.0?topic=requirements-supported-operating-systems for the supported linux distribution.

walbers commented 2 years ago

@roysahar Is there any other way besides the IBM block csi driver for my Kubernetes pods running on Ubuntu to use the IBM FlashSystem 5030 as storage?

roysahar commented 2 years ago

@walbers , We are planning a support for Ubuntu on our next release of csi driver - 1.10.0

walbers commented 2 years ago

That be great! Please let me know when that happens