[Users] Adding a VMNIC via the REST api returns no error, but the NIC isn't added

[Moti Asayag]

----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Moti Asayag" <masayag at redhat.com>
> Cc: users at ovirt.org
> Sent: Sunday, February 9, 2014 11:57:08 PM
> Subject: Re: [Users] Adding a VMNIC via the REST api returns no error, but the NIC isn't added
> 
> On 02/09/2014 10:40 PM, Moti Asayag wrote:
> >
> >
> > ----- Original Message -----
> >> From: "Satya Vempati" <svempati at tintri.com>
> >> To: "Moti Asayag" <masayag at redhat.com>
> >> Cc: users at ovirt.org
> >> Sent: Sunday, February 9, 2014 7:42:07 PM
> >> Subject: Re: [Users] Adding a VMNIC via the REST api returns no error, but
> >> the NIC isn't added
> >>
> >> Thanks for the reply. Should have noted it earlier, I am using
> >> 3.3.0-0.38.rc.el6ev.
> >>
> >> I am chiefly concerned that no error is thrown when a nic isn¹t added, so
> >> when I am doing this programmatically I wouldn¹t be able to discover that
> >> the operation failed.
> >>
> >
> > I just tried the same example and got the following error:
> >
> > <fault>
> > <reason>Operation Failed</reason>
> > <detail>
> > [Cannot add Interface. There is no VM network interface profile for the
> > network the user can use. - Please use a VM network interface profile
> > instead of a network name.]
> > </detail>
> > </fault>
> >
> > Where you using the restapi directly or used the SDK for posting that
> > request ?
> > Please provide the steps to reproduce this issue, since i wasn't able to
> > experience the same behavior.
> 
> Moti - isn't this a regression to the API as this call should have
> worked as-is pre-3.3 vnic profiles?

If there was a network in < 3.3 env which were used for port mirroring, the 
upgrade script to 3.3 would have create a suitable profile for it, therefore
the same code which were run before 3.3 should remain working, for an existing
entities.

However in order to consume new networks configured for port mirroring, there
is a need to define a specific profile for it.

This shares the same concept as introduced by Network permissions: user will be
able to consume a network which was defined before the adding the permissions
feature, but for new networks, it is required to grant a specific permission.
So the equivalent to 'grant a specific permissions' in this case is creating a
matching vnic profile.

> 
> >
> >> On 2/9/14, 7:56 AM, "Moti Asayag" <masayag at redhat.com> wrote:
> >>
> >>> ----- Original Message -----
> >>>> From: "Satya Vempati" <svempati at tintri.com>
> >>>> To: users at ovirt.org
> >>>> Sent: Sunday, February 9, 2014 5:54:15 AM
> >>>> Subject: [Users] Adding a VMNIC via the REST api returns no error, but
> >>>> the NIC isn't added
> >>>>
> >>>> POST <server>/api/vms/670fa876-a18d-436c-b999-1dc7cbbd5bcf/nics
> >>>>
> >>>> <nic>
> >>>> <name>eth0</name>
> >>>> <network>
> >>>> <name>rhevm</name>
> >>>> </network>
> >>>> <interface>virtio</interface>
> >>>> <port_mirroring>
> >>>> <networks>
> >>>> <network>
> >>>> <name>rhevm</name>
> >>>> </network>
> >>>> </networks>
> >>>> </port_mirroring>
> >>>> </nic>
> >>>>
> >>>> Return code is 200, but no VM Nic is added.
> >>>
> >>> Assuming this is ovirt-engine-3.3 and above:
> >>>
> >>> Do you have a vnic profile for rhevm network with port_mirroring enabled
> >>> ?
> >>> Which user are you using for adding this vnic ?
> >>>
> >>> You need to verify such a vnic profile exist and the user which adds the
> >>> vnic has permissions to use that profile.
> >>>
> >>> Alternately, you can provide the vnic_profile_id instead of the network
> >>> name
> >>> and the port mirroring which is the deprecated signature.
> >>>
> >>> http://www.ovirt.org/Features/Vnic_Profiles#REST_API
> >>>
> >>>>
> >>>> _______________________________________________
> >>>> Users mailing list
> >>>> Users at ovirt.org
> >>>> http://lists.ovirt.org/mailman/listinfo/users
> >>>>
> >>
> >>
> > _______________________________________________
> > Users mailing list
> > Users at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
> 
>