Tuesday, 2024-09-24

*** mhen_ is now known as mhen01:17
*** zilti_ is now known as zilti08:15
sylvrGood morning ! I'm studying Cloud Operation and I'm trying to deploy an OpenStack using Kayobe. However I'm encountering issue when I try to create an instance, it seems like neutron can't bind port to my instances causing them to timeout during build this is the error I get in /var/log/kolla/neutron/neutron-server.log :09:39
sylvr2024-09-24 08:37:40.295 22 ERROR neutron.plugins.ml2.managers [req-c21a9ea8-1ecf-4a10-a3c0-c7b266fa8021 req-80f12b11-1123-4b19-8b49-5dcc389ce8ad 607a43b606a54e11bdf89c46577db5f2 53a3ffb6389641e1934e0ac97a9be36e - - default default] Failed to bind port 0d12f559-2fa2-485b-ae31-3b75ad9a2a72 on host compute2 for vnic_type normal using segments [{'id': '97ee4fe9-cf1f-47d4-9736-128f4982abc9', 'network_type': 'flat', 'physical_network':09:39
sylvr'physnet1', 'segmentation_id': None,'network_id': 'd933b37d-9e74-44ef-aa82-cbc3ba67a7b1'}]09:39
sylvrI'm thinking I may have misconfigured something, could you help me troubleshoot this ? thanks 😁09:39
DHEservers running virtual machines need a neutron agent running and configured on them. other hosts (controller, or dedicated neutron hosts) run more services like layer 3 services, but compute nodes still need a layer 2 agent10:11
sylvrDHE : my computes nodes are running neutron-openvswitch-agent, and I don't see any error in the logs of the various neutron components running on the node...11:27
sylvrDHE : but no neutron-L3-agent are running on the computes nodes...12:20
jrosserthe "failed to bind port" error can sometimes mean that you have a mapping for physnet1 to some physical port name that does not exist on that host12:22
sylvrjrosser: ooh12:26
sylvrjrosser : I think I may have found the error I made : try to create instance directly on the external network...12:28
jrosserright - and if that interface is not present, you'll get an error very much like that12:28
sylvryeah, so I totally misunderstood the use case of floating IP...12:31
DHEas I understand it, floating IPs are "attached" to a virtual machine by essentially attaching them to a NAT router, and putting in rewrite rules to make it look like that server owns that IP address directly.12:32
sylvryeah that make so much more sense now, I though that would be the case also if you created a machine directly on the network...12:34
jrosserif you want to have instances on the external netwkr, that is up to you12:34
jrosserbut that network must go to all the computes in a way that is consistent with what you told neutron about physnet112:35
sylvryeah I was trying to get to 0 error with rally/tempest and I had instance creation error, so I was trying to investigate on the bug/issue12:35
sylvrworst part is that wasn't truly my issue with instance creation (cinder/volume acting up)12:36
sylvrwell thanks for your help ! :)12:36
elinux_Hi all13:24
elinux_anyone here who does or know someone who does part time projects in openstack like installing, setups, troubleshooting etc ? I want to take up such tasks in my free time for upskill13:25
mocallinsHello everybody15:05
mocallinsis there a known solution for 500 Internal Server Error, 15:06
mocallinsI've double checked all the steps from install, but nothing seems to fix it15:07
mocallinsI installed from  the Deban package15:07
fricklermocallins: it would help to know from which service you are seeing the error, usually then check the logs for that service15:15
mocallinsI'm new to Openstack, so i think its the Horizon service ? does that sound right ?15:20
fricklermocallins: that sounds at least possible. Horizon is the dashboard for OpenStack, which installation guide did you follow? likely you'll first want to check if the remainder of your openstack installation is working by using some CLI tools15:33
mocallinshttps://docs.openstack.org/horizon/latest/install/install-debian.html15:42
fricklermocallins: so you only installed horizon and nothing else? openstack consists of a lot of other components, too, I suggest you take a look at https://docs.openstack.org/install-guide/15:59
mocallinsYep, just folowed that guide to start with.16:00
fricklermocallins: ok, so you did install keystone and the verification worked? cf. https://docs.openstack.org/keystone/2024.1/install/keystone-verify-ubuntu.html16:21
mocallinsNo i did not.  Looks like i need to do a full devstack install16:23
fricklermocallins: well devstack is doing something different than a distro based installation. but if this is just for testing, that may be a valid option, too. you'll want to start again from a freshly installed server though in that case16:27
jrossermocallins: if you could describe what you are trying to achieve it would help, like "a completely manual installation as an excercise" / "i want to do a POC for a real deployment" / "i want to work on the openstack code" .....16:28
mocallinsWellllll, lol16:33
mocallinsAs a former network contractor, i had the pleasure of scripting / testing in an Openstack environment (for a couple diffent NFV solutions), and i just wanted to see a lot of the nuts a bolts of what Openstack actually was, and i thought installing for myself in my own environment, i could play around with it , for a bit.16:36
mocallinsI'm no longer a working contractor, so i guess it could be classified as "test"16:37
mocallinsThanks for the guidance. Is starting to look more involved and not sure what i want to do.  Thanks again17:27
mocallinsquit17:27
mocallinsexit17:27

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!