#3: NetTestCommandSystemConfig: multiple values for one option -------------------------+---------------------- Reporter: olichtne | Owner: rpazdera Type: defect | Status: assigned Priority: major | Milestone: Component: component1 | Version: Resolution: | Keywords: Blocked By: | Blocking: -------------------------+---------------------- Changes (by rpazdera):
* type: task => defect * status: new => assigned
Comment:
I looked and this problem and it's valid in the following cases:
{{{ <command machine="1" type="system_config"> <options> <option name="/sys/class/net/em1/ifindex" value="5" /> <option name="/sys/class/net/em1/ifindex" value="6" /> <option name="/sys/class/net/em1/ifindex" value="7" /> </options> </command> }}}
When a single option is assigned multiple values at once. I don't think this makes much sense though.
In the current implementation, the first value is used without any warning, which is very misleading as Ondra points out. Better solution would be to use the last one and warn the user, that the previous values were optimized out.
We could be particularly restrictive and disallow this completely. LNST would simply die with error, that setting a single value multiple times at once isn't supported (because they won't be used anyway).