RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1464808 - modify discoveryDB
Summary: modify discoveryDB
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: iscsi-initiator-utils
Version: 6.10
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Chris Leech
QA Contact: Martin Hoyer
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-25 23:59 UTC by loloevian
Modified: 2017-07-20 07:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-20 07:01:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description loloevian 2017-06-25 23:59:53 UTC 
Hello everyone, 
Situation : 

- iscsiadm -m session -o show
tcp: [1] 192.168.120.230:3260,1 iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)
tcp: [2] 10.16.0.11:3260,1 iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)
tcp: [3] 10.16.0.10:3260,1 iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)

But when I performed : iscsiadm -m discoverydb
I have only : 192.168.120.230:3260 via sendtargets

So If I cut the connection to this IP : 192.168.120.230 , I lost the connection to my iscsi platform.

What the process to add on the discoverydb the IP :
10.16.0.11 and 10.16.0.10 and don't use 192.168.120.230.

Bestregards
Laurent NEBOUT
Comment 2 loloevian 2017-06-29 23:58:14 UTC 
Hello,
let me try  to provide more  focused information.

- iscsiadm -m session -o show
tcp: [1] 192.168.120.230:3260,1 iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)
tcp: [2] 10.16.0.11:3260,1 iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)
tcp: [3] 10.16.0.10:3260,1 iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)

If I perform a logout for 
tcp: [1] 192.168.120.230:3260,1 iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)

and  do : - iscsiadm -m session -o show
tcp: [2] 10.16.0.11:3260,1 iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)
tcp: [3] 10.16.0.10:3260,1 iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)

But my access to the data is : Read Only

how do you do to use 10.16.0.11 and 10.16.0.10 with a R/W access ?

Best regards
LAurent
Comment 3 loloevian 2017-06-30 00:50:10 UTC 
(In reply to loloevian from comment #2)
> Hello,
> let me try  to provide more  focused information.
> 
> - iscsiadm -m session -o show
> tcp: [1] 192.168.120.230:3260,1
> iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)
> tcp: [2] 10.16.0.11:3260,1
> iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)
> tcp: [3] 10.16.0.10:3260,1
> iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)
> 
> If I perform a logout for 
> tcp: [1] 192.168.120.230:3260,1
> iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)
> 
> and  do : - iscsiadm -m session -o show
> tcp: [2] 10.16.0.11:3260,1
> iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)
> tcp: [3] 10.16.0.10:3260,1
> iqn.2004-04.com.qnap:ts-453a:iscsi.vmstore1.18eb4c (non-flash)
>
>[root@SC-KVM2 images]# iscsiadm -m discoverydb
>10.16.0.10:3260 via sendtargets
>10.16.0.11:3260 via sendtargets
> But my access to the data is : Read Only
> 
> how do you do to use 10.16.0.11 and 10.16.0.10 with a R/W access ?
> 
> Best regards
> LAurent
Comment 4 Martin Hoyer 2017-06-30 13:33:04 UTC 
Hello LAurent,
can You paste the output of 'iscsiadm -m session -P3'?
Comment 5 loloevian 2017-07-06 00:59:56 UTC 
(In reply to Martin Hoyer from comment #4)
> Hello LAurent,
> can You paste the output of 'iscsiadm -m session -P3'?

Hi Martin 
Sorry for the delay between my last post.
I had a business trip and I was busy.

Concerning the problem , I try one more time to implement multipath and now that's ok.
I don't know why the first time, I had trouble.

Have a nice day.

Laurent
Comment 6 Martin Hoyer 2017-07-07 07:37:23 UTC 
(In reply to loloevian from comment #5)
Hi Laurent,
thank you for the update. Is it ok to close this bz?
Comment 7 loloevian 2017-07-20 00:37:31 UTC 
(In reply to Martin Hoyer from comment #6)
> (In reply to loloevian from comment #5)
> Hi Laurent,
> thank you for the update. Is it ok to close this bz?

Sorry for the delay Martin
Yes that's ok to close the ticket

Have a nice day 
Laurent
Comment 8 Martin Hoyer 2017-07-20 07:01:16 UTC 
(In reply to loloevian from comment #7)
Thank you Laurent.
Have a nice day,
Martin
Note You need to log in before you can comment on or make changes to this bug.