This message was deleted.
# longhorn-storage
a
This message was deleted.
a
Hi, 1. Do you have all requirements #installation-requirements 2. Could you check if
open-iscsi
is installed and
iscsid
is running on all work nodes? Try
systemctl status iscsid.
3. Could you please provide us a support bundle for further investigation? You can generate a support bundle on Longhorn UI.
r
@cuddly-vase-67379 iscid is running on all work nodes. doing a describe of the pod shows me the following traces:
Copy code
Warning  FailedAttachVolume  25m (x33 over 3h45m)    attachdetach-controller  AttachVolume.Attach failed for volume "pvc-xxx" : rpc error: code = Aborted desc = volume pvc-xxxxx is not ready for workloads
  Warning  FailedMount         19m (x20 over 3h29m)    kubelet                  Unable to attach or mount volumes: unmounted volumes=[volv], unattached volumes=[kube-api-access-js429 volv]: timed out waiting for the conditio
a
Could you please provide us a support bundle for further investigation? You can generate a support bundle on Longhorn UI.
r
I have tried but point 5 does not work for me
a
You could find
Generate Support Bundle
link in the Bottom of the UI.
r
Done!
a
Could you attach the support bundle file here?
r
Can I send it to an email address, for security?
a
Yes, please mail to longhorn-support-bundle@suse.com, Thanks.
r
sent the mail @cuddly-vase-67379 please any update I would appreciate you tell me
a
Hi @ripe-queen-73614, I saw
"Failed to init frontend: device pvc-db03aac2-7027-45fe-b86c-e38e85b74ad9: fail to delete target iqn.2019-10.io.longhorn:pvc-db03aac2-7027-45fe-b86c-e38e85b74ad9"
this log in the instance-manager. Could you check that
tgtd
service status and is tgtd busy? BTW I noticed that you built the system on RHEL8.6 , that may have some potential risk because it is not verified yet for Longhorn system.
r
how do i check that tgtd?
@cuddly-vase-67379 how do i check that tgtd?
a
You could use
top
or
atop
to see if there any process is busy, usually
systemctl status tgtd
to check but RHEL8.6 seems use the
target
service instead.
Ref: https://github.com/longhorn/longhorn/issues/923 Maybe you could log into the corresponding engine manager pod, and manually delete the target first.
r
@cuddly-vase-67379 I don't see this process
systemctl status tgtd Unit tgtd.service could not be found.
f
Can you try to scale down the workload that are using Longhorn volumes and delete the instance-manager-e-xxx pods inside
longhorn-system
namespace?
109 Views