| *** digitalsimboja has joined #openstack-kuryr | 04:26 | |
| *** digitalsimboja has quit IRC | 04:38 | |
| *** digitalsimboja has joined #openstack-kuryr | 04:38 | |
| *** digitalsimboja has quit IRC | 05:50 | |
| *** digitalsimboja has joined #openstack-kuryr | 06:02 | |
| *** ltomasbo has joined #openstack-kuryr | 06:13 | |
| *** digitalsimboja has quit IRC | 06:49 | |
| *** digitalsimboja has joined #openstack-kuryr | 06:49 | |
| maysams | digitalsimboja: Hello, good morning | 07:49 |
|---|---|---|
| maysams | digitalsimboja: are you still seeing the issues? if yes, please share you local.conf | 07:50 |
| digitalsimboja | one moment | 07:52 |
| digitalsimboja | http://paste.openstack.org/show/806359/ | 07:52 |
| maysams | digitalsimboja: so, you're trying again with recommendations from the Neutron team in place, right? | 07:54 |
| digitalsimboja | yes | 07:54 |
| maysams | awesome | 07:54 |
| maysams | digitalsimboja: can you check with Neutron team if there is a launchpad bug for this issue and if not, create one? | 07:55 |
| maysams | digitalsimboja: It can help out some other people in the future | 07:55 |
| digitalsimboja | right away! | 08:02 |
| *** digitalsimboja has quit IRC | 08:23 | |
| *** digitalsimboja has joined #openstack-kuryr | 08:28 | |
| *** digitalsimboja has joined #openstack-kuryr | 08:29 | |
| *** digitalsimboja has quit IRC | 08:29 | |
| *** digitalsimboja has joined #openstack-kuryr | 08:30 | |
| *** digitalsimboja has quit IRC | 08:43 | |
| *** digitalsimboja has joined #openstack-kuryr | 08:43 | |
| *** digitalsimboja has quit IRC | 08:52 | |
| *** digitalsimboja has joined #openstack-kuryr | 09:14 | |
| maysams | digitalsimboja: is devstack working fine with neutron's tweak? | 09:15 |
| digitalsimboja | still setting up | 09:15 |
| maysams | digitalsimboja: regarding the neutron bug https://bugs.launchpad.net/neutron/+bug/1930858 you might want to share your local.conf(without mentioning the IPs) | 09:16 |
| opendevmeet | Launchpad bug 1930858 in neutron "OVN central service does not start properly" [Undecided,New] | 09:16 |
| maysams | and describe how you hit it (e.g. when re-stacking the env?) | 09:17 |
| maysams | digitalsimboja: and if the workaround works it might be good to also mention on the launchpad bug | 09:19 |
| digitalsimboja | Sure | 09:21 |
| *** opendevreview has joined #openstack-kuryr | 09:38 | |
| opendevreview | Roman Dobosz proposed openstack/kuryr-kubernetes master: Fixes for latest changes on Neutron devstack. https://review.opendev.org/c/openstack/kuryr-kubernetes/+/794200 | 09:38 |
| *** digitalsimboja has quit IRC | 10:00 | |
| *** digitalsimboja has joined #openstack-kuryr | 10:13 | |
| *** digitalsimboja has quit IRC | 10:20 | |
| *** digitalsimboja has joined #openstack-kuryr | 10:35 | |
| maysams | digitalsimboja: any news about the env? | 10:39 |
| digitalsimboja | cloning | 10:40 |
| digitalsimboja | + functions-common:git_timed:625 : timeout -s SIGINT 0 git clone https://opendev.org/openstack/placement.git /opt/stack/placement --branch master | 10:40 |
| digitalsimboja | Cloning into '/opt/stack/placement'... | 10:40 |
| maysams | ok | 10:41 |
| digitalsimboja | I believe it will succeed this time | 10:43 |
| *** digitalsimboja has quit IRC | 10:44 | |
| *** digitalsimboja has joined #openstack-kuryr | 10:45 | |
| ltomasbo | good that you are optimistic! xD | 10:47 |
| digitalsimboja | sure it will | 11:06 |
| digitalsimboja | At the stage of setting up docker now! | 11:06 |
| digitalsimboja | You can check my responses on Trello as I await the stackup to complete | 11:07 |
| digitalsimboja | @maysams | 11:07 |
| *** ltomasbo has quit IRC | 11:11 | |
| *** digitalsimboja has quit IRC | 11:14 | |
| *** digitalsimboja has joined #openstack-kuryr | 11:26 | |
| maysams | digitalsimboja: great, thanks | 11:47 |
| maysams | digitalsimboja: did you spot anything worth improving in the docs? | 11:48 |
| *** ltomasbo has joined #openstack-kuryr | 11:50 | |
| digitalsimboja | Sure yes @maysams: Should I proceed with that maybe over the weekends do some facelifts on the docs? | 11:51 |
| digitalsimboja | before monday? | 11:52 |
| digitalsimboja | By the way I am here right now on the stack up | 11:52 |
| digitalsimboja | Connecting to github-releases.githubusercontent.com (github-releases.githubusercontent.com)|185.199.111.154|:443... connected. | 11:52 |
| digitalsimboja | HTTP request sent, awaiting response... 200 OK | 11:52 |
| digitalsimboja | Length: 16300544 (16M) [application/octet-stream] | 11:52 |
| digitalsimboja | Saving to: ‘/opt/stack/devstack/files/cirros-0.5.2-x86_64-disk.img’ | 11:52 |
| maysams | digitalsimboja: whenever works best for you | 11:52 |
| digitalsimboja | I believe this is almost the last steps? | 11:52 |
| maysams | nop, there are a few more | 11:53 |
| digitalsimboja | Great! | 11:53 |
| digitalsimboja | is there a way of speeding up kubeadm image pull? | 12:19 |
| digitalsimboja | http://paste.openstack.org/show/806371/ | 12:19 |
| *** digitalsimboja has quit IRC | 12:33 | |
| *** digitalsimboja has joined #openstack-kuryr | 12:33 | |
| gryf | digitalsimboja, not really. although seems like you bump on some connectivity issue (see first line error message). | 12:57 |
| digitalsimboja | Yeah I noticed, have passed the stgage now pulling the fs layer from centos | 12:58 |
| gryf | so, it's building kuryr containers. | 12:59 |
| digitalsimboja | Yes | 13:19 |
| *** digitalsimboja has quit IRC | 13:28 | |
| *** digitalsimboja has joined #openstack-kuryr | 13:28 | |
| *** luis5tb has joined #openstack-kuryr | 13:33 | |
| *** luis5tb has quit IRC | 13:33 | |
| digitalsimboja | Yeah! my machine is up and running!!! | 13:44 |
| digitalsimboja | http://paste.openstack.org/show/806378/ | 13:45 |
| *** dulek has joined #openstack-kuryr | 13:47 | |
| gryf | congrats :) | 13:48 |
| ltomasbo | \o/ | 13:49 |
| *** dulek has quit IRC | 13:58 | |
| maysams | yayy!! | 14:11 |
| *** dulek has joined #openstack-kuryr | 14:17 | |
| digitalsimboja | Yeah!!! | 14:20 |
| digitalsimboja | I am so excited! | 14:20 |
| *** dulek has quit IRC | 14:27 | |
| *** ltomasbo has quit IRC | 14:43 | |
| *** ltomasbo has joined #openstack-kuryr | 14:43 | |
| digitalsimboja | any Idead why I am hitting this | 15:25 |
| digitalsimboja | http://paste.openstack.org/show/806385/ | 15:25 |
| digitalsimboja | default namespace | 15:25 |
| digitalsimboja | and this long pending time too | 15:26 |
| digitalsimboja | http://paste.openstack.org/show/806386/ | 15:26 |
| maysams | have you sourced the openstack credentials? | 15:27 |
| ltomasbo | digitalsimboja, most probably kubernetes is not working there (or kuryr) | 15:27 |
| *** digitalsimboja has quit IRC | 15:27 | |
| ltomasbo | there is no klb, as there is no pod running | 15:27 |
| ltomasbo | and kuryr will only create it if there is service endpoints | 15:27 |
| ltomasbo | so, you need "kubectl get endpoints demo" to be there | 15:28 |
| *** digitalsimboja has joined #openstack-kuryr | 15:28 | |
| ltomasbo | digitalsimboja, there is no klb, as there is no pod running | 15:29 |
| ltomasbo | and kuryr will only create it if there is service endpoints | 15:29 |
| ltomasbo | so, you need "kubectl get endpoints demo" to be there | 15:29 |
| ltomasbo | digitalsimboja, so, your initial problem is that the pod does not transition to "containerCreating" status | 15:29 |
| ltomasbo | and you need to figure out why | 15:29 |
| digitalsimboja | the pod creating action has taking more than 70mins, | 15:30 |
| ltomasbo | you can do "kubectl describe pod demo-6cb99dfd4d-4sm7j", to see if there is any error there | 15:30 |
| ltomasbo | and you probably can do "kubectl get pods -A", to see if the k8s scheduler is running | 15:30 |
| digitalsimboja | ok | 15:30 |
| digitalsimboja | http://paste.openstack.org/show/806387/ | 15:32 |
| ltomasbo | digitalsimboja, see... if you do "kubectl get nodes", you will see there is no node in "Ready" status | 15:32 |
| ltomasbo | digitalsimboja, meaning there is no node where the pod can be scheduled | 15:33 |
| digitalsimboja | Kube-schedular is running | 15:33 |
| digitalsimboja | stack@devstack:~$ kubectl get pods -A | 15:33 |
| digitalsimboja | NAMESPACE NAME READY STATUS RESTARTS AGE | 15:33 |
| digitalsimboja | default demo-6cb99dfd4d-4sm7j 0/1 Pending 0 82m | 15:33 |
| digitalsimboja | kube-system kube-apiserver-devstack 1/1 Running 0 170m | 15:33 |
| digitalsimboja | kube-system kube-controller-manager-devstack 1/1 Running 0 170m | 15:33 |
| digitalsimboja | kube-system kube-scheduler-devstack 1/1 Running 0 170m | 15:33 |
| digitalsimboja | sunday demo-6cb99dfd4d-szc42 0/1 Pending 0 72m | 15:33 |
| digitalsimboja | stack@devstack:~$ | 15:33 |
| ltomasbo | what is the node status? | 15:33 |
| digitalsimboja | My machine should serve as a single node i gues? | 15:33 |
| digitalsimboja | stack@devstack:~$ kubectl get nodes | 15:34 |
| digitalsimboja | NAME STATUS ROLES AGE VERSION | 15:34 |
| digitalsimboja | devstack NotReady control-plane,master 173m v1.20.4 | 15:34 |
| digitalsimboja | stack@devstack:~$ | 15:34 |
| digitalsimboja | NotREady | 15:34 |
| ltomasbo | yep... so now you need to figure out why | 15:36 |
| ltomasbo | and, similarly to the pods, you can do "kubectl describe node devstack" | 15:36 |
| ltomasbo | and see why the node is not ready | 15:36 |
| digitalsimboja | lets have a look together | 15:37 |
| digitalsimboja | http://paste.openstack.org/show/806388/ | 15:38 |
| ltomasbo | digitalsimboja, seems kuryr is not running | 15:39 |
| ltomasbo | did you run containerized or non-containerized? | 15:39 |
| digitalsimboja | non-containerized | 15:40 |
| ltomasbo | I see you don't have any kuryr pod... so I assume you run non-containerized | 15:40 |
| ltomasbo | ok, so you need to check the status of the kuryr services | 15:41 |
| ltomasbo | systemctl | grep kuryr | 15:41 |
| ltomasbo | and then "systemctl status THE_KURYR_SERVICE_NAME" | 15:41 |
| digitalsimboja | stack@devstack:~$ systemctl | grep kuryr | 15:42 |
| digitalsimboja | stack@devstack:~$ systemctl | grep kuryr | 15:42 |
| digitalsimboja | stack@devstack:~$ | 15:42 |
| digitalsimboja | returns nothing | 15:42 |
| ltomasbo | can I see your local.conf? | 15:42 |
| ltomasbo | that means you probably run containerized... and the stack failed for some reason... | 15:42 |
| digitalsimboja | http://paste.openstack.org/show/806389/ | 15:43 |
| digitalsimboja | by default? | 15:43 |
| ltomasbo | by default is running containerzied | 15:44 |
| ltomasbo | and you did not disable it | 15:44 |
| ltomasbo | so you were supposed to have couple of extra pods running there | 15:44 |
| ltomasbo | one for the kuryr-controller, and one for the kuryr-cni | 15:44 |
| ltomasbo | basically, you have no kuryr running there | 15:45 |
| digitalsimboja | so to get Kuryr running? | 15:46 |
| ltomasbo | I don't know what it fails... but looks like your stack.sh did not finish | 15:47 |
| ltomasbo | you need to check the logs on the devstack folder... to see on what step it failed | 15:47 |
| digitalsimboja | Okay | 15:47 |
| ltomasbo | and you will need to restack again | 15:48 |
| ltomasbo | digitalsimboja, after the stack.sh finishes, you need to see something similar to this: http://paste.openstack.org/show/806391/ | 15:48 |
| ltomasbo | otherwise something did not work | 15:48 |
| digitalsimboja | that means thats the problem | 15:49 |
| digitalsimboja | I tried creating thos pods while the stack is pulling the image from centos registry | 15:50 |
| digitalsimboja | so until the stack run finishes kuryr wont start? | 15:50 |
| digitalsimboja | Have'nt gotten to the stack finish then, but it will surely succeed in this run | 15:52 |
| digitalsimboja | so I wait it out | 15:52 |
| ltomasbo | digitalsimboja, so you still have the stack running? | 15:52 |
| digitalsimboja | yeah | 15:52 |
| ltomasbo | ahh, ok | 15:52 |
| ltomasbo | so, you need to wait | 15:52 |
| ltomasbo | one thing is having k8s installed... but you are still missing pieces | 15:52 |
| digitalsimboja | it has survived all the stages where it used to exit so it will surely complete | 15:53 |
| ltomasbo | you need octavia to be installed, and the loadbalancer to be created | 15:53 |
| ltomasbo | then kuryr will be installed | 15:53 |
| ltomasbo | and once that is done, your k8s node will transition to Ready | 15:53 |
| digitalsimboja | in that order? | 15:53 |
| ltomasbo | and the Pod will be schedule | 15:53 |
| ltomasbo | and then the service endpoints will be created | 15:53 |
| digitalsimboja | aha! | 15:53 |
| ltomasbo | and kuryr will create the loadbalancer and the klb | 15:53 |
| digitalsimboja | aha! | 15:54 |
| *** digitalsimboja has quit IRC | 16:00 | |
| *** digitalsimboja has joined #openstack-kuryr | 16:02 | |
| *** ltomasbo has quit IRC | 16:38 | |
| *** digitalsimboja has quit IRC | 16:54 | |
| *** digitalsimboja has joined #openstack-kuryr | 16:55 | |
| *** digitalsimboja has quit IRC | 17:02 | |
| *** digitalsimboja has joined #openstack-kuryr | 17:04 | |
| *** digitalsimboja has quit IRC | 17:05 | |
| *** digitalsimboja has joined #openstack-kuryr | 17:06 | |
| *** digitalsimboja has quit IRC | 17:08 | |
| *** digitalsimboja has joined #openstack-kuryr | 17:09 | |
| *** digitalsimboja has quit IRC | 17:25 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!