cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Stevens (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
Date Mon, 13 Mar 2017 14:14:41 GMT

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

Will Stevens commented on CLOUDSTACK-9811:
------------------------------------------

I will admit that I am a bit confused that the  IP was matched by looping through the databag
and an index was found, but then when it tries to set the IP, it is not found.  Is `eth3`
supposed to exist?  Can you post the ips.json and ip_associations.json databags so we understand
what the config is there?

We can easily 'get rid' of the error by changing this line of code: https://github.com/apache/cloudstack/blob/master/systemvm/patches/debian/config/opt/cloud/bin/cs_ip.py#L48

from:
if index != -1:

to:
if index != -1 and ip['device'] in dbag and index in dbag[ip['device']]:

I am curious if the `nic_dev_id` variable is correct.  It was introduced here (it looks to
be relatively consistent with the functionality before): https://github.com/apache/cloudstack/commit/6749785caba78a9379e94bf3aaf0c1fbc44c5445#diff-a7d6f7150cca74029f23c19b72ad0622R24

Looking at the logs, I am unclear how the `nic_dev_id` is getting set to `3`.

Let me know if the code change I suggested in this comment works to fix your issue.  If it
does, I will create a PR with that change for you.

Cheers...

> VR will not start, looking to configure eth3 while no such device exists on the VR. On
KVM-CentOS6.8 physical host
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9811
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Virtual Router
>    Affects Versions: 4.10.0.0
>            Reporter: Boris Stoyanov
>            Priority: Blocker
>         Attachments: agent.log, cloud.log, management.log
>
>
> This issue appears only on 4.10. When you add an instance with a new network the VR starts
and fails at the configuration point. Looks like it is looking to configure eth3 adapter while
no such device should be available on the VR. 
> The VR does not start and aborts the deployment of the VM. 
> Pease note that this issue was reproduced on physical KVM hosts in our lab.
> Hardware Hosts details:
> - 4x Dell C6100
> - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant)
> OS:
> CentOS 6.8. 
> Management: 
> VM, running CentOS 6.8
> ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67
> In a nested virtualization environment it was working fine with CentOS6.8. 
> Attached are the management log and the cloud.log form the VR. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message