Description of problem:
When running a hammer command to provision a discovered host while providing additional information (i.e. --interface "list=of,many=values,...") on how to configure bonded networking, foreman will ignore the networking information and will provision the discovered host without applying any of the bonding options.

Version-Release number of selected component (if applicable):
Satellite 6.8.3
tfm-rubygem-hammer_cli_foreman-2.1.2.1-1.el7sat.noarch
tfm-rubygem-smart_proxy_discovery-1.0.5-5.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_discovery-1.0.2-1.el7sat.noarch
tfm-rubygem-hammer_cli_katello-0.22.2.3-1.el7sat.noarch
tfm-rubygem-hammer_cli-2.1.2-1.el7sat.noarch
foreman-discovery-image-3.6.7-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_admin-0.0.9-1.el7sat.noarch
tfm-rubygem-foreman_discovery-16.1.2-1.el7sat.noarch

How reproducible:
100% of attempts.

Steps to Reproduce:
1. PXE-discover a new host that has 2 NICs: em1 and em2.
2. Run the hammer command below to provision said discovered host:

hammer -d discovery provision \
--name mac000102030405 \
--new-name mynewhost \
--organization MyOrg \
--hostgroup-title myhg/childhg \
--location MyLocation \
--domain-id 1 \
--build false \
--enabled true \
--managed true \
--owner-id 12 \
--interface="identifier=em1, \
mac=00:01:02:03:04:05, \
managed=true, \
type=Nic::Managed, \
domain_id=1, \
subnet_id=15" \
--interface="identifier=em2, \
mac=00:11:12:13:14:15, \
managed=true, \
type=Nic::Managed, \
domain_id=1, \
subnet_id=15" \
--interface="identifier=bond0, \
ip=10.11.12.13, \
type=Nic::Bond, \
mode=active-backup, \
attached_devices='[em1,em2]', \
managed=true, \
domain_id=1, \
subnet_id=15"
~~~

Actual results:
The host will kexec and install the appropriate RHEL version but it will configure only em1 as the single NIC with an IP address and all and won't even create bond0 or configure em2.

Expected results:
The host kexecs and installs the appropriate RHEL version, configuring bond0 as its main interface while configuring em1 and em2 as simply attached to bond0 i.e. em1 and em2 won't have IP addresses or anything.

Additional info:
If using the web UI to modify the discovered host before provisioning it, the intended result is achieved i.e. bond0 is created and the host provisions through it and comes out of provisioning with bond0 correctly configured.

One more note: using JSON-formatted parameters to the "hammer discovery provision --interface" command showed no difference in results: the host was provisioned with em1 as the sole NIC just like when using comma-separated options for hammer.