------- Comment From [email protected] 2018-08-13 11:18 EDT------- I'm afraid the information in this bug is not concise or properly scoped. One internal comment states/clarifies:
"[...] Prudhvi is not able to create network portal with default port which is 3260. [...] But he is able to create network portal with non- default port i.e 3261." I was wondering if this is simply a case of a target having been already created (by the system?) with the default port, and thus a conflict which prevents creating a new target with the same port. Not sure if there is something else the tool should be doing in this case, even if just a better error message. I have seen (older) discussions on the web of similar issues, which talk about manually deleting the default target before creating a new one. But I'm not familiar with this tool or the facilities. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785770 Title: [Ubuntu 18.04]Unable to create NetworkPortal in configFS using Targetcli tool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1785770/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
