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

Ubuntu instructions result in errors #467

Open
1 task done
Wagz123 opened this issue Jul 31, 2024 · 1 comment
Open
1 task done

Ubuntu instructions result in errors #467

Wagz123 opened this issue Jul 31, 2024 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@Wagz123
Copy link

Wagz123 commented Jul 31, 2024

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

  1. “sudo systemctl status open-iscsi” throws this error:

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

 Loaded: loaded (/lib/systemd/system/open-iscsi.service; enabled; vendor preset: enabled)

 Active: inactive (dead)

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:

systemctl list-unit-files | grep multipath

bwagoner@netapp.com

Public issues must not contain sensitive information

  • This issue contains no sensitive information.
@netapp-aruldeepa
Copy link
Contributor

Hi @Wagz123,

Thanks for sharing the details!
I'll work with the team and update the instructions.

Regards,
Deepa

@netapp-aruldeepa netapp-aruldeepa self-assigned this Aug 1, 2024
@netapp-aruldeepa netapp-aruldeepa added the documentation Improvements or additions to documentation label Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants