ASF GitHub Bot commented on CLOUDSTACK-10261:

rhtyd commented on issue #2441: CLOUDSTACK-10261: Libvirt metadata: only create 
one nuage-extension tag
URL: https://github.com/apache/cloudstack/pull/2441#issuecomment-364891629
   LGTM, merging based on review and test results (ignoring intermittent 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Nuage: Multinic: Libvirt nuage-extenstion metadata contains only one 
> interface.
> -------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-10261
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10261
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: cloudstack-agent
>    Affects Versions:
>         Environment: Nuage VSP plugin on RHEL 7.4
>            Reporter: Frank Maximus
>            Assignee: Frank Maximus
>            Priority: Critical
>             Fix For:
> When installed ACS 4.11 on top of Rhel7.4 baseimage with libvirt-3.2.0 ,there 
> is an issue with the metadata of the created VM in cloudstack. 
> It leads to password reset failure as the nuage vrs is not allowing passage 
> to DomainRouter.
> After debugging , it was found that the nuage-extension in metadata was 
> missing.
> When cloudstack-agent is preparing xml to be sent to openvswitch it contains 
> metadata with nuage-extension block as follows
> <metadata>
> <nuage-extension>
> <interface mac='02:00:6c:fb:00:03' vsp-vr-ip=''></interface>
> </nuage-extension>
> </metadata>
> In /var/log/openvswitch/vm-monitor.log , the received XML of VM is without 
> nuage-extension block in metadata as follows:
> Jan 15 18:17:17 ovs-1 vm-monitor.log: <metadata/>
> So the metadata block is now empty. It seems libvirt 3.2.0 requires an url in 
> its metada, so the libvirt namespace needs to be adapted.

This message was sent by Atlassian JIRA

Reply via email to