Wednesday, 2021-07-28

digitalsimboja@maysams, @ltomasbo: please assist to resolve06:53
digitalsimbojahttps://paste.opendev.org/show/807743/06:54
ltomasbodigitalsimboja, what did you execute there?06:54
digitalsimbojaGood morning 06:54
digitalsimbojathis06:54
digitalsimbojastack@outreachy:~/tempest$ tempest run -r 'kuryr-tempest-plugin.*'06:54
ltomasbolooks like you run out of disk space06:56
gryfltomasbo, I also suspect that.06:56
digitalsimbojaoops!06:57
gryfdigitalsimboja, df -h06:57
digitalsimbojaokay06:57
digitalsimbojahttps://paste.opendev.org/show/807744/06:58
ltomasboyep: /dev/vda1        39G   39G     0 100% /06:58
ltomasbodigitalsimboja, probably just removing some of the log files would help there06:59
digitalsimbojamoment..06:59
ltomasboyep, /var/log is taking up to 28G06:59
ltomasbohttps://paste.opendev.org/show/807746/07:00
ltomasboyou can probably just remove the syslog.1 file and get things recovered07:01
digitalsimbojachecking..07:01
digitalsimbojaokay I removed the syslog files07:03
digitalsimbojado I need to remove /dev/vdal files too?07:03
gryfno!07:06
ltomasboand probably you should have not removed the syslog but set its size to 0, lets see if it gets regenerated07:07
digitalsimbojanow I am getting this^07:09
digitalsimbojahttps://paste.opendev.org/show/807747/07:09
digitalsimbojaI ran stestr init 07:10
digitalsimbojayet07:10
ltomasbodigitalsimboja, this is the same as yesterday, right? where do you have to run that? what directory?07:10
ltomasboalso, I quickly check... you have a lot of leftovers from previous tempest run... it is possible that some new runs fails due to lack of quota07:11
digitalsimbojatempest07:11
digitalsimbojahow do I clear previous runs?07:11
digitalsimbojaI wanted to do that in the night but couldn't07:12
ltomasbono magic I'm aware of... you will to manually remove the vms/networks/subnets...07:12
ltomasbowell.. no VMs in your case07:12
ltomasbobut namespaces named "kuryr-namespace-xxx" or pods on the defult namespace named "kuryr-pod-Xxx"07:13
ltomasboprobably some services named "kuryr-service-xxx"07:14
gryfdigitalsimboja, you need to run stestr from tempest directory.07:18
digitalsimbojaohh!07:19
digitalsimbojaI am just taking a look. Thanks 07:19
digitalsimbojahttps://paste.opendev.org/show/807748/07:25
digitalsimbojaseems connection issues I guess?07:25
digitalsimbojahttps://paste.opendev.org/show/807749/07:29
digitalsimbojaI am having connection timeouts07:29
ltomasbodigitalsimboja, did you cleaned up the env?07:32
ltomasbootherwise the extra amount of resources may be affecting you07:32
gryfdigitalsimboja, probably some devstack services has failed, due to no space left on device. maybe you need to start those again, although I suspect, that you'll need to unstack/stack again.07:34
ltomasboyeah, unstack and stack may be simpler07:35
digitalsimbojacool07:39
digitalsimbojahttps://paste.opendev.org/show/807750/07:52
digitalsimbojastacking hitting a block07:52
digitalsimbojahttps://paste.opendev.org/show/807751/08:04
ltomasboyou need to check that is the problem (journalctl)08:10
opendevreviewRoman Dobosz proposed openstack/kuryr-kubernetes master: [WIP] Fix multinode gate, separate variations for OVN and OVS.  https://review.opendev.org/c/openstack/kuryr-kubernetes/+/80161809:43
opendevreviewRoman Dobosz proposed openstack/kuryr-kubernetes master: [WIP] Fix multinode gate, separate variations for OVN and OVS.  https://review.opendev.org/c/openstack/kuryr-kubernetes/+/80161811:08
digitalsimboja@maysams, @ltomasbo: Just a quick one on the kuryr-tempest-plugin12:41
digitalsimbojaI understand I need to add the test on the config.py?12:42
digitalsimbojaThe question is where do I define the test function?12:43
digitalsimbojaWith regards to :12:44
digitalsimbojahttps://paste.opendev.org/show/807762/12:44
digitalsimbojaSay on this line : if not CONF.kuryr_kubernetes.test_sctp_services:12:45
digitalsimboja            raise cls.skipException("Service SCTP tests are not enabled")12:45
digitalsimbojaI want to find where test_sctp_services is defined?12:46
ltomasbothose are flags for some test that should not run in all the configurations13:01
ltomasbofor yours, probably you don't need to add any config function13:01
digitalsimbojaperfect13:04
ltomasbomaybe just reuse some of the existing configs (such a service_tests_enabled)13:06
digitalsimbojagot it! but not defining a specific one per my test?13:14
ltomasbothat can be decided later, I think (at least for now) it is not needed13:15
digitalsimbojagot it. Thanks13:15
digitalsimboja@ltomasbo, @maysams: Just to clarify14:40
digitalsimbojaThis is the approach I am taking:14:41
digitalsimboja1. Create as ervice14:41
digitalsimboja1. Create a service14:41
digitalsimboja2. Delete the associated loadbalancers on the service14:41
digitalsimboja3. Wait for the reconciliation timeout14:41
digitalsimbojaNow my question is on number 214:41
digitalsimbojaI guess that means I need to set the status to {}?14:42
digitalsimbojaIs that correct?14:42
gryfstatus of what?14:42
digitalsimbojathe CRD14:42
gryfwell, no.14:43
ltomasbodigitalsimboja, you need to  remove the loadbalancer from openstack side14:43
digitalsimbojahttps://paste.opendev.org/show/807769/14:43
gryfthink of tempest tests as "real life", so it might happened that loadbalancer could be removed by mistake.14:43
ltomasboand ensure your reconciliation removes the status, to trigger the recreation of the loadbalancer14:43
gryfso that you need to actually remove LB from octavia.14:44
gryfas ltomasbo already said.14:44
ltomasbo:)14:44
digitalsimbojaSo I am removing LB from Octavia right on the tempest right and not setting the status of the CRD to 'empty'?14:44
gryfyes.14:45
ltomasbothe status of the CRD should be handle by the patch you already merged on kuryr-kubernetes14:45
ltomasbotempest side is to test that what you merged actually works14:45
digitalsimbojaThat means my above implementation is wrong14:45
digitalsimboja:)14:46
ltomasboso, as gryf mention, think of tempest as the same tests you were manually doing for testing your kuryr-kubernetes reconciliation patch14:46
gryfimagine you want to test if your code works - you'll just remove the lb and wait, to see if it works, right?14:46
digitalsimbojasure @gryf14:46
gryfso the tempest test is just "you" doing this as a code.14:46
ltomasbowhat you were doing to ensure your patch was working was removing the loadbalancer and wait for your code to detect it, and recreate it. So that is what tempest test need to do14:46
digitalsimbojaunderstood14:46
digitalsimbojaunderstood14:47
ltomasbogryf, seems we are aligned in our thinking! xD14:47
gryfltomasbo, ;)14:47
digitalsimbojaYeah! You both are very much aligned14:47
digitalsimbojaLet me reconfirm: I still need to get the openstackSDK client similarly same way as per my patch on tempest? Correct?14:48
ltomasbodigitalsimboja, check other tests on kuryr-tempest-plugin to see how those are done14:50
digitalsimbojaGot it!14:50
ltomasbothey are both creating/checking OpenStack and Kubernetes resources14:51
simboja@ltomasbo: seems  i missed few messages you sent regarding this?^16:09
simboja they are both creating/checking OpenStack and Kubernetes resources16:09
ltomasbothat was the last one16:17
simbojacool Thanks16:37
digitalsimboja@dulek, @gryf, @maysams: I am yet to fiend a way of calling octavia to delete the loadbalancers on tempest18:14
digitalsimbojamy research took me here18:14
digitalsimbojahttps://docs.openstack.org/api-ref/network/v2/index.html?expanded=confirm-a-tag-detail#list-service-providers18:14
maysamsdigitalsimboja: have you checked the tempest repository?18:14
gryfbtw, on irc you can skip the '@' before nickname as it here does nothing ;)18:14
digitalsimbojaohh18:15
digitalsimbojatempest repo on github?18:15
digitalsimbojachecking the repo18:20
digitalsimbojai tried  pr = cls.os_admin.service_providers_client.list_service_providers()18:23
*** pmannidi|AFK is now known as pmannidi23:08

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