[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363791#comment-16363791
 ] 

ASF subversion and git services commented on CLOUDSTACK-10261:
--------------------------------------------------------------

Commit dee5bb527e7aca4e72e2249b348cca6d688fbe5f in cloudstack's branch 
refs/heads/master from [~fmaximus]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=dee5bb5 ]

CLOUDSTACK-10261: Libvirt metadata create only one nuage-extension xml tag 
(#2441)



> 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: 4.11.0.0
>         Environment: Nuage VSP plugin on RHEL 7.4
>            Reporter: Frank Maximus
>            Assignee: Frank Maximus
>            Priority: Critical
>             Fix For: 4.11.0.0
>
>
> 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='10.1.0.2'></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
(v7.6.3#76005)

Reply via email to