-
Notifications
You must be signed in to change notification settings - Fork 619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[occm] 'internal-network-name' broken since release 1.18 #1039
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
@gdetal can you set verbose debugging ( "addresses": {
"private": [
{
"OS-EXT-IPS-MAC:mac_addr": "00:0c:29:0d:11:74",
"OS-EXT-IPS:type": "fixed",
"addr": "192.168.1.30",
"version": 4
}
]
},
|
thanks for the fast follow-up. Find below the requested output with
Note here is also the relevant
|
@kayrus ok, thank you ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
I configured
internal-network-name
in thecloud.conf
configuration file. But the InternalIP of my minion nodes always get the wrong IP address.What you expected to happen:
That the InternalIP of my minion nodes corresponds to the one allocated in the network specified by
internal-network-name
.How to reproduce it:
Create a cluster with minion that have more than one network. Specify one of the networks under
internal-network-name
and create minions. Depending on the ordering of the VM's ports the wrong node InternalIP will be patched.Anything else we need to know?:
I've tested releases 1.17, 1.18 and master. Only the latter two are broken. After increasing log verbosity to 5 for occm I can see the following for those releases:
It seems that commit 46cab81 broke #444 as the first loop do not use the
internal-network-name
option.Environment:
The text was updated successfully, but these errors were encountered: