question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

iscsi install failure on nodes

See original GitHub issue

I am attempting to get everything installed on my nodes so that I can connect it, but I am running into some issues.

when I run sudo systemctl enable multipath-tools.service I get

Synchronizing state of multipath-tools.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable multipath-tools
Failed to enable unit: Refusing to operate on linked unit file multipath-tools.service

tho sudo systemctl status multipath-tools shows it as active

and when I check sudo systemctl status open-iscsi I get

● open-iscsi.service - Login to default iSCSI targets
   Loaded: loaded (/lib/systemd/system/open-iscsi.service; enabled; vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Thu 2021-05-13 03:52:17 UTC; 17ms ago
           ├─ ConditionDirectoryNotEmpty=|/etc/iscsi/nodes was not met
           └─ ConditionDirectoryNotEmpty=|/sys/class/iscsi_session was not met
     Docs: man:iscsiadm(8)
           man:iscsid(8)

Im on Ubuntu 18.04, and this is /lib/systemd/system/open-iscsi.service

[Unit]
Description=Login to default iSCSI targets
Documentation=man:iscsiadm(8) man:iscsid(8)
Wants=network-online.target remote-fs-pre.target
After=network-online.target iscsid.service
Before=remote-fs-pre.target
DefaultDependencies=no
Conflicts=shutdown.target
Before=shutdown.target
# Must have some pre-defined targets to login to
ConditionDirectoryNotEmpty=|/etc/iscsi/nodes
# or have a session to use via iscsid
ConditionDirectoryNotEmpty=|/sys/class/iscsi_session

[Service]
Type=oneshot
RemainAfterExit=true
# iscsiadm --login will return 21 if no nodes are configured,
# and 15 if a session is alread logged in (which we do not
# consider an error)
SuccessExitStatus=15 21
# Note: iscsid will be socket activated by iscsiadm
ExecStart=/sbin/iscsiadm -m node --loginall=automatic
ExecStart=/lib/open-iscsi/activate-storage.sh
ExecStop=/lib/open-iscsi/umountiscsi.sh
ExecStop=/bin/sync
ExecStop=/lib/open-iscsi/logout-all.sh

[Install]
WantedBy=sysinit.target
Alias=iscsi.service

from what I can tell, its implied here that those two directories cant be empty, but I though that all the connection stuff would be handled by this container?

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:11 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
travisghansencommented, May 15, 2021

Oh yeah that’s a great howto. I’ll add it to the doc! One note about deleting the pvc, it’s less scary if you suggest the user set the reclaim policy to Retain on the PV beforehand…that will prevent a provisioner from deleting the PV.

1reaction
deefdragoncommented, May 15, 2021

I also threw together a quick thing on how to migrate data over if you find it worth adding. I found the other two guides on creating and migrating very useful, but nothing went over migrating any data that I already had. And not much on that anywhere else on the internet for that matter. I had someone else give it a read-through already, but if you have anything else to add or change let me know.

https://gist.github.com/deefdragon/d58a4210622ff64088bd62a5d8a4e8cc

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting iSCSI Configuration Problems
Cause: The initiator's iSCSI version is not supported by the storage device. iscsi connection( OID ) login failed - No more connections can...
Read more >
iSCSI Initiator - Connection Failed - TechNet - Microsoft
I am having a problem with one of our cluster nodes and it's connection the SAN where all the VMs are stored. I...
Read more >
Resolve iSCSI error messages on the storage system
ISCSI: Authentication failed for initiator nodename. CHAP is not configured correctly for the specified initiator.
Read more >
ANS3140E: iSCSI mount connection to iSCSI targets failed - IBM
Symptom. The mount of the backup from the Virtual Machine is failing on the Linux Mount Proxy Node while the iSCSI initiator is...
Read more >
trying to install iscsi utils in tanzu photon based worker nodes ...
i was tring to deploy pod created from iscsi lun and was getting failed since iscsi utils is not present in the worker...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found