[
https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927006#comment-15927006
]
ASF GitHub Bot commented on CLOUDSTACK-9811:
--------------------------------------------
Github user swill commented on the issue:
https://github.com/apache/cloudstack/pull/2003
Does anyone know what `first_i_p` represents in the `ips.json` dbag? I am
assuming it is the Source NAT IP, but I can't find it represented anywhere in
the code (other than in a test). If it does represent the Source NAT, then we
can use it to maintain the order and keep the Source NAT IP as the primary IP
on the Nic. That was the bug I was trying to fix in my #1741 PR.
Example with: 1) source nat 2) port forwarding 3) static nat 4) load
balancer
```
"eth2": [
{
"add": true,
"broadcast": "192.168.80.255",
"cidr": "192.168.80.8/24",
"device": "eth2",
"first_i_p": true,
"gateway": "192.168.80.5",
"netmask": "255.255.255.0",
"network": "192.168.80.0/24",
"new_nic": false,
"nic_dev_id": 2,
"nw_type": "public",
"one_to_one_nat": false,
"public_ip": "192.168.80.8",
"size": "24",
"source_nat": true,
"vif_mac_address": "06:00:44:00:00:23"
},
{
"add": true,
"broadcast": "192.168.80.255",
"cidr": "192.168.80.9/24",
"device": "eth2",
"first_i_p": false,
"gateway": "192.168.80.5",
"netmask": "255.255.255.0",
"network": "192.168.80.0/24",
"new_nic": false,
"nic_dev_id": 2,
"nw_type": "public",
"one_to_one_nat": false,
"public_ip": "192.168.80.9",
"size": "24",
"source_nat": false,
"vif_mac_address": "06:34:d1:00:00:23"
},
{
"add": true,
"broadcast": "192.168.80.255",
"cidr": "192.168.80.10/24",
"device": "eth2",
"first_i_p": false,
"gateway": "192.168.80.5",
"netmask": "255.255.255.0",
"network": "192.168.80.0/24",
"new_nic": false,
"nic_dev_id": 2,
"nw_type": "public",
"one_to_one_nat": true,
"public_ip": "192.168.80.10",
"size": "24",
"source_nat": false,
"vif_mac_address": "06:34:d1:00:00:23"
},
{
"add": true,
"broadcast": "192.168.80.255",
"cidr": "192.168.80.11/24",
"device": "eth2",
"first_i_p": false,
"gateway": "192.168.80.5",
"netmask": "255.255.255.0",
"network": "192.168.80.0/24",
"new_nic": false,
"nic_dev_id": 2,
"nw_type": "public",
"one_to_one_nat": false,
"public_ip": "192.168.80.11",
"size": "24",
"source_nat": false,
"vif_mac_address": "06:34:d1:00:00:23"
}
],
```
@ustcweizhou @murali-reddy @remibergsma
> 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)
