V-magine uses my gateway as the dashboard IP and not the IP of the controller so when i browse to 10.0.1.1 i get the dashboard :/ posted the settings i used in the image anyone know why this happens?
This issue has been solved by setting in:
resources/install.rdo.sh
the following line:
openstack-config --set $ANSWER_FILE general CONFIG_PROVISION_OVS_BRIDGE n
If not set, in some circumstances RDO assign the IP of the gateway to br-ex interface, causing a conflict of IPs on the network.
The fix has been committed and released in the v-magine installer available for download.
Asked: 2017-02-20 21:06:30 +0300
Seen: 424 times
Last updated: Feb 22 '17
© 2014-2023 Cloudbase Solutions Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
Hi, can you please upload a link to the v-magine.log file? E.g. on dropbox, pastebin, etc
Additionally, can you please post the network controller's configuration in: /etc/sysconfig/network-scripts/ifcfg-mgmt-ext ?
i canceled the install last night but i wil rerun it now with the same settings and post it when i am done
Thanks. Based on settings I expect to see your controller's management interface set to 10.0.1.149.
http://pastebin.com/jLVrhxsD https://i.imgur.com/gcaCpw9.pnghttps://i.imgur.com/vxueGQ3.png it happend again the dashboard is on 10.0.1.1 again and my whole network becomes unresponsive because both my router and the controller are competing for a single ip.
Network configuration looks good, can you please send the output of "ip addr" in the controller?
Note: you can disconnect the controller VM from the vSwitch while investigating the issue. This way you can avoid issues with the network traffic.
yes thats what i did i just gave it a vlan ID that was not in use, currently not at my pc ill report in later. Thanks a lot for helping tho!
i was just retrying the install and now it gets stuck on this: https://i.imgur.com/fDXaw59.png is there any way i can fully delete it and retry, like does it store things in temp folders?
When you redeploy it, it wipes out the controller VM and starts from scratch, there are no "leftovers" from previous runs
ah ok it worked a few times but now it keeps hanging there, might reinstall server 2016 just to be sure.
thanks again for helping, ill try again when the bug is fixed. :P
What we have so far: apparently the nova.conf configured by RDO is corrupted, causing the following issues. Investigating the cause on the RDO IRC channel.
More details, in case others have the same issue: lots of CentOS packages got updated on Feb 20th, causing the regression. Working on narrowing down the issue: http://mirror.centos.org/centos/7/cloud/x86_64/openstack-newton/?C=M;O=D
Found the issue: the python2-ryu package is broken. As I was suspecting we're not the only ones complaining: https://ask.openstack.org/en/question/103016/packstack-requirement-for-python-tinyrpc-breaks-installation/
Workaround: in install-rdo.sh, before running packstack --answer-file, add: exec_with_retry 5 0 /usr/bin/rpm -Uvh --nodeps https://buildlogs.centos.org/centos/7/cloud/x86_64/openstack-newton/common/python2-tinyrpc-0.5-2.el7.noarch.rpm
Thanks for the status updates! ill retry the install after the issue is fixed, I am not in a rush.