adietrich-ussignal opened a new issue, #8794:
URL: https://github.com/apache/cloudstack/issues/8794
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Other
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Agent
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.19.0.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Advanced Networking Setup
cloudbr0 - Guest/Private VXLAN Bridge
cloudbr1 - Public Network (VLAN)
cloudbr2 - Management Network (VLAN)
Three KVM hosts in a single cluster on the same top-of-rack.
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Ubuntu 22.04 LTS
Below is the netplan configuration from one of the KVM hosts.
```
---
network:
version: 2
<Physical and Bond portions omitted for brevity>
bridges:
cloudbr0:
interfaces:
- bond0.2007
addresses:
- 10.255.0.4/24
parameters:
stp: false
forward-delay: 5
mtu: 9000
cloudbr2:
interfaces:
- bond0.2003
addresses:
- 10.120.0.5/24
dhcp4: false
routes:
- to: default
via: 10.120.0.1
nameservers:
addresses:
- 10.10.0.10
- 10.10.0.11
mtu: 1500
cloudbr1:
interfaces:
- bond0
parameters:
stp: false
mtu: 1500
vlans:
bond0.2000:
id: 2000
link: bond0
bond0.2003:
id: 2003
link: bond0
mtu: 1500
bond0.2007:
id: 2007
link: bond0
mtu: 9000
```
##### SUMMARY
<!-- Explain the problem/feature briefly -->
When adding a host to CloudStack, the assigned IP address does not match the
IP addressed used to join the host to the cluster. This causes unpredictable
results for IP Addresses that are assigned to a host. This breaks a variety of
functionality for communications for management and VM traffic.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
1. Create the appropriate Advanced Network Configuration settings with a
VXLAN capable bridge/VLAN interface with a VTEP IP.
2. Add host in CloudStack UI with Management bridge IP address.
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
See the management IP address (10.120.0.x) used to add the host reflected in
the CloudStack UI.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
CloudStack reports the 10.255.0.x IP address of the host instead of the host
management IP (10.120.0.x) used to add the host to CloudStack.
In some cases the IP address is added correctly, but it is not persistent
and is subject to change in reconnects or agent restarts.
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
