{"action":"opened","issue":{"url":"https://api.github.com/repos/spdk/spdk/issues/525","repository_url":"https://api.github.com/repos/spdk/spdk","labels_url":"https://api.github.com/repos/spdk/spdk/issues/525/labels{/name}","comments_url":"https://api.github.com/repos/spdk/spdk/issues/525/comments","events_url":"https://api.github.com/repos/spdk/spdk/issues/525/events","html_url":"https://github.com/spdk/spdk/issues/525","id":385804105,"node_id":"MDU6SXNzdWUzODU4MDQxMDU=","number":525,"title":"NVMe-oF target provides bad info to kernel discovery service","user":{"login":"Seth5141","id":20448512,"node_id":"MDQ6VXNlcjIwNDQ4NTEy","avatar_url":"https://avatars2.githubusercontent.com/u/20448512?v=4","gravatar_id":"","url":"https://api.github.com/users/Seth5141","html_url":"https://github.com/Seth5141","followers_url":"https://api.github.com/users/Seth5141/followers","following_url":"https://api.github.com/users/Seth5141/following{/other_user}","gists_url":"https://api.github.com/users/Seth5141/gists{/gist_id}","starred_url":"https://api.github.com/users/Seth5141/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Seth5141/subscriptions","organizations_url":"https://api.github.com/users/Seth5141/orgs","repos_url":"https://api.github.com/users/Seth5141/repos","events_url":"https://api.github.com/users/Seth5141/events{/privacy}","received_events_url":"https://api.github.com/users/Seth5141/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-29T15:57:47Z","updated_at":"2018-11-29T15:57:47Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Please use the issue tracker only for reporting suspected issues.\r\n\r\nSee [The SPDK Community Page](http://www.spdk.io/community/) for other SPDK communications channels.\r\n\r\n\r\n## Expected Behavior\r\nOur target properly describes the controllers to the discovery service.\r\n\r\n## Current Behavior\r\nAt least for configurations with large numbers of controllers, the target appears to give only a partial response.\r\n\r\nFrom a log reported by @jrgruher:\r\n~~~~\r\ndon@donsl202:~/install/spdk/scripts$ sudo nvme discover -t rdma -a 10.5.0.202\r\n\r\nDiscovery Log Number of Records 12, Generation counter 25\r\n=====Discovery Log Entry 0======\r\ntrtype:  rdma\r\nadrfam:  ipv4\r\nsubtype: nvme subsystem\r\ntreq:    not specified\r\nportid:  0\r\ntrsvcid: 4420\r\nsubnqn:  nqn.2018-11.io.spdk:nqn1\r\ntraddr:  10.5.0.202\r\nrdma_prtype: not specified\r\nrdma_qptype: connected\r\nrdma_cms:    rdma-cm\r\nrdma_pkey: 0x0000\r\n=====Discovery Log Entry 1======\r\ntrtype:  rdma\r\nadrfam:  ipv4\r\nsubtype: nvme subsystem\r\ntreq:    not specified\r\nportid:  1\r\ntrsvcid: 4420\r\nsubnqn:  nqn.2018-11.io.spdk:nqn2\r\ntraddr:  10.5.0.202\r\nrdma_prtype: not specified\r\nrdma_qptype: connected\r\nrdma_cms:    rdma-cm\r\nrdma_pkey: 0x0000\r\n=====Discovery Log Entry 2======\r\ntrtype:  rdma\r\nadrfam:  ipv4\r\nsubtype: nvme subsystem\r\ntreq:    not specified\r\nportid:  2\r\ntrsvcid: 4420\r\nsubnqn:  nqn.2018-11.io.spdk:nqn3\r\ntraddr:  10.5.0.202\r\nrdma_prtype: not specified\r\nrdma_qptype: connected\r\nrdma_cms:    rdma-cm\r\nrdma_pkey: 0x0000\r\n=====Discovery Log Entry 3======\r\ntrtype:  rdma\r\nadrfam:  ipv4\r\nsubtype: nvme subsystem\r\ntreq:    not specified\r\nportid:  3\r\ntrsvcid: 4420\r\nsubnqn:  nqn.2018-11.io.spdk:nqn4\r\ntraddr:  10.5.0.202\r\nrdma_prtype: not specified\r\nrdma_qptype: connected\r\nrdma_cms:    rdma-cm\r\nrdma_pkey: 0x0000\r\n=====Discovery Log Entry 4======\r\ntrtype:  rdma\r\nadrfam:  ipv4\r\nsubtype: nvme subsystem\r\ntreq:    not specified\r\nportid:  4\r\ntrsvcid: 4420\r\nsubnqn:  nqn.2018-11.io.spdk:nqn5\r\ntraddr:  10.5.0.202\r\nrdma_prtype: not specified\r\nrdma_qptype: connected\r\nrdma_cms:    rdma-cm\r\nrdma_pkey: 0x0000\r\n=====Discovery Log Entry 5======\r\ntrtype:  rdma\r\nadrfam:  ipv4\r\nsubtype: nvme subsystem\r\ntreq:    not specified\r\nportid:  5\r\ntrsvcid: 4420\r\nsubnqn:  nqn.2018-11.io.spdk:nqn6\r\ntraddr:  10.5.0.202\r\nrdma_prtype: not specified\r\nrdma_qptype: connected\r\nrdma_cms:    rdma-cm\r\nrdma_pkey: 0x0000\r\n=====Discovery Log Entry 6======\r\ntrtype:  rdma\r\nadrfam:  ipv4\r\nsubtype: nvme subsystem\r\ntreq:    not specified\r\nportid:  6\r\ntrsvcid: 4420\r\nsubnqn:  nqn.2018-11.io.spdk:nqn7\r\ntraddr:  10.5.0.202\r\nrdma_prtype: not specified\r\nrdma_qptype: connected\r\nrdma_cms:    rdma-cm\r\nrdma_pkey: 0x0000\r\n=====Discovery Log Entry 7======\r\ntrtype:  unrecognized\r\nadrfam:  pci\r\nsubtype: unrecognized\r\ntreq:    not specified\r\nportid:  0\r\ntrsvcid:\r\nsubnqn:\r\ntraddr:\r\n=====Discovery Log Entry 8======\r\ntrtype:  unrecognized\r\nadrfam:  pci\r\nsubtype: unrecognized\r\ntreq:    not specified\r\nportid:  0\r\ntrsvcid:\r\nsubnqn:\r\ntraddr:\r\n=====Discovery Log Entry 9======\r\ntrtype:  unrecognized\r\nadrfam:  pci\r\nsubtype: unrecognized\r\ntreq:    not specified\r\nportid:  0\r\ntrsvcid:\r\nsubnqn:\r\ntraddr:\r\n=====Discovery Log Entry 10======\r\ntrtype:  unrecognized\r\nadrfam:  pci\r\nsubtype: unrecognized\r\ntreq:    not specified\r\nportid:  0\r\ntrsvcid:\r\nsubnqn:\r\ntraddr:\r\n=====Discovery Log Entry 11======\r\ntrtype:  unrecognized\r\nadrfam:  pci\r\nsubtype: unrecognized\r\ntreq:    not specified\r\nportid:  0\r\ntrsvcid:\r\nsubnqn:\r\ntraddr:\r\n~~~~\r\n## Possible Solution\r\nThis was broken by commit 1d9be84 which changed the default buffer size used for RDMA transaactions on the target side. This is where I will start looking for the regression.\r\n\r\n## Steps to Reproduce\r\nTBD\r\n\r\n## Context (Environment including OS version, SPDK version, etc.)\r\nTBD\r\n"}}
{"actor":{"display_login":"Seth5141"}}