[
https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907463#comment-15907463
]
Will Stevens commented on CLOUDSTACK-9811:
------------------------------------------
I really doubt my change in https://github.com/apache/cloudstack/pull/1741 is
causing this. The change to `cs_ip.py` in that PR fixes a bug that cause the
IP addresses to be reordered on reboot. If there are secondary IPs on that
nic, then the source nat IP will no longer be the primary IP on that nic and
instead one of the other secondary IPs will be the primary IP after reboot.
The change I made results in the same network config after a reboot by
recording the index and modifying that index rather than removing it and
re-adding it at the end.
I know Murali made a LOT of VR changes that got merged into 4.10 as well. I
have not reviewed all of them, but he made a lot of changes.
I will review the logs and see if anything pops up. [~boriss], let me know if
reverting that change to cs_ip.py makes any difference.
> 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)
