You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current instructions for preparing ubuntu 22.04 results in errors. From a customer on AWS with Ubuntu 22.04 AMI:
--Begin customer note-----------------------------------------------------
1. When we run “sudo systemctl enable --now multipath-tools.service”, this error is thrown:
sm-user@ip-192-168-49-253:/var/snap/amazon-ssm-agent/7993$ sudo systemctl enable --now multipath-tools.serviceFailed to enable unit: Refusing to operate on alias name or linked unit file: multipath-tools.service
--
TheNetApp docsstate“For Ubuntu 18.04, you must discover target ports with iscsiadm before starting open-iscsi for the iSCSI daemon to start. You can alternatively modify the iscsi service to start iscsid automatically.”but since we’re running 22.04, we don’t know if this is applicable.
1. When we run “sudo systemctl enable --now multipath-tools.service”, this error is thrown:
Condition: start condition failed at Fri 2024-07-26 12:01:36 UTC; 2h 38min ago
├─ ConditionDirectoryNotEmpty=|/etc/iscsi/nodes was not met
└─ ConditionDirectoryNotEmpty=|/sys/class/iscsi_session was not met
Docs: man:iscsiadm(8)
man:iscsid(8)
Jul 25 19:12:16 ip-192-168-49-253 systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped.
Jul 25 19:13:52 ip-192-168-49-253 systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped.
Jul 26 11:56:41 ip-192-168-49-253 systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped.
Jul 26 12:01:17 ip-192-168-49-253 systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped.
Jul 26 12:01:22 ip-192-168-49-253 systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped.
Jul 26 12:01:36 ip-192-168-49-253 systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped.
The NetApp docs state “For Ubuntu 18.04, you must discover target ports with iscsiadm before starting open-iscsi for the iSCSI daemon to start. You can alternatively modify the iscsi service to start iscsid automatically.” but since we’re running 22.04, we don’t know if this is applicable.
-----End customer note------------------------------------------------------------------------------------------------------------------------------
I was able to reproduce these problems on a clean install of ubuntu AMI. Problem with iscsi is resolved by running sudo iscsiadm -m discovery -t st -p
so the note about 18.04 should read 18.04 and up. But since we don't really support the older versions of ubuntu anyway, we ought to just rewrite the instructions with the port discovery in mind.
Also, for checking the status of multipath drivers, this can be accomplished without errors using:
Page URL
https://docs.netapp.com/us-en/trident/trident-use/worker-node-prep.html
Page title
Prepare the worker node
Summary
The current instructions for preparing ubuntu 22.04 results in errors. From a customer on AWS with Ubuntu 22.04 AMI:
--Begin customer note-----------------------------------------------------
1. When we run “sudo systemctl enable --now multipath-tools.service”, this error is thrown:
sm-user@ip-192-168-49-253:/var/snap/amazon-ssm-agent/7993$ sudo systemctl enable --now multipath-tools.serviceFailed to enable unit: Refusing to operate on alias name or linked unit file: multipath-tools.service --The NetApp docs state “For Ubuntu 18.04, you must discover target ports with iscsiadm before starting open-iscsi for the iSCSI daemon to start. You can alternatively modify the iscsi service to start iscsid automatically.” but since we’re running 22.04, we don’t know if this is applicable.
1. When we run “sudo systemctl enable --now multipath-tools.service”, this error is thrown:sm-user@ip-192-168-49-253:/var/snap/amazon-ssm-agent/7993$ sudo systemctl enable --now multipath-tools.service
Failed to enable unit: Refusing to operate on alias name or linked unit file: multipath-tools.service
ssm-user@ip-192-168-49-253:/var/snap/amazon-ssm-agent/7993$ sudo systemctl status open-iscsi
○ open-iscsi.service - Login to default iSCSI targets
Condition: start condition failed at Fri 2024-07-26 12:01:36 UTC; 2h 38min ago
Jul 25 19:12:16 ip-192-168-49-253 systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped.
Jul 25 19:13:52 ip-192-168-49-253 systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped.
Jul 26 11:56:41 ip-192-168-49-253 systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped.
Jul 26 12:01:17 ip-192-168-49-253 systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped.
Jul 26 12:01:22 ip-192-168-49-253 systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped.
Jul 26 12:01:36 ip-192-168-49-253 systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped.
The NetApp docs state “For Ubuntu 18.04, you must discover target ports with iscsiadm before starting open-iscsi for the iSCSI daemon to start. You can alternatively modify the iscsi service to start iscsid automatically.” but since we’re running 22.04, we don’t know if this is applicable.
-----End customer note------------------------------------------------------------------------------------------------------------------------------
I was able to reproduce these problems on a clean install of ubuntu AMI. Problem with iscsi is resolved by running sudo iscsiadm -m discovery -t st -p
so the note about 18.04 should read 18.04 and up. But since we don't really support the older versions of ubuntu anyway, we ought to just rewrite the instructions with the port discovery in mind.
Also, for checking the status of multipath drivers, this can be accomplished without errors using:
systemctl list-unit-files | grep multipath
bwagoner@netapp.com
Public issues must not contain sensitive information
The text was updated successfully, but these errors were encountered: