Friday, 2017-05-19

*** rwellum has quit IRC00:00
*** stefan_bo has joined #openstack-kolla00:07
*** fguillot has joined #openstack-kolla00:07
*** schwicht has joined #openstack-kolla00:08
*** sindhu has quit IRC00:09
*** manheim_ has quit IRC00:11
*** stefan_bo has quit IRC00:11
*** eaguilar has joined #openstack-kolla00:13
*** tonanhngo has quit IRC00:17
*** kbaegis1 has joined #openstack-kolla00:23
*** schwicht has quit IRC00:23
openstackgerritsean mooney proposed openstack/kolla master: enable the kolla build system to use out of tree docker files  https://review.openstack.org/46613200:25
*** tonanhngo has joined #openstack-kolla00:26
*** ducttape_ has joined #openstack-kolla00:26
*** kbaegis has quit IRC00:27
sean-k-mooneyinc0: what do you think of https://review.openstack.org/466132 its a very small change but its all that is need to support builing external docker files with kolla build00:28
sean-k-mooneyinc0: instead of a direct replacement i could also model it as an addtional serch path for images so you could build the standard images and external at the same time but i dont know if that is overkill00:30
*** mattmceuen has quit IRC00:30
*** tonanhngo has quit IRC00:30
*** ducttape_ has quit IRC00:31
sean-k-mooneyinc0: personally i would be fine with running kolla build twice once for openstack + once for external images not related to openstack.00:31
*** salv-orlando has joined #openstack-kolla00:33
*** salv-orlando has quit IRC00:34
*** salv-orlando has joined #openstack-kolla00:34
*** hongbin has quit IRC00:46
*** cuongnv has joined #openstack-kolla00:57
*** salv-orlando has quit IRC00:59
*** tovin07_ has joined #openstack-kolla01:02
*** Slower has quit IRC01:04
*** dmellado has quit IRC01:04
*** dave-mccowan has quit IRC01:06
*** sgrasley has quit IRC01:06
*** sgrasley has joined #openstack-kolla01:08
*** srwilkers has quit IRC01:09
*** rhallisey has quit IRC01:10
kfox1111sbezverk: I know why its failing I think.01:14
kfox1111theres a nova placement database now.01:14
kfox1111with that fixed I think the v4 centos gate might be ready.01:14
*** Slower has joined #openstack-kolla01:16
openstackgerritDai Dang Van proposed openstack/kolla-ansible master: Mixing binary and source images (1)  https://review.openstack.org/46043601:18
spsuryamorning all01:19
*** qiliang28 has joined #openstack-kolla01:20
*** qiliang27 has quit IRC01:21
*** qiliang28 is now known as qiliang2701:21
*** dmellado has joined #openstack-kolla01:22
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: WIP: v4 gates.  https://review.openstack.org/45484101:22
sdakekfox1111 sbezverk can you fellas review this and tell me what is wrong with the log capture: https://review.openstack.org/#/c/464031/01:25
sdakealso why is helm-repo PV not present?01:25
sdakesup spsurya01:25
*** gfidente has quit IRC01:26
*** daidv has joined #openstack-kolla01:27
inc0nice Sean01:28
inc0sean-k-mooney:01:28
inc0Jeffrey4l: around?01:28
kfox1111sdake: the whole script is run with -x so I think sbezverk was mistaken. it should gather logs on failure.01:28
sdakekfox1111 i think it doesn't gather the PV/helm/etc objects01:29
sdakekfox1111 which I parsed his comment to mean he wanted to see01:29
sdakekfox1111 however there is no file in the logs dir01:29
kfox1111oh. to see if those are left over?01:29
sdakeif somehthing is left over, its helpful to know what :)01:30
kfox1111yeah. I don't think we currently gather that.01:30
sdakekfox1111 https://review.openstack.org/#/c/464031/16/tests/bin/destroy_tests.sh01:30
kfox1111would be good to add that to tests/bin/gate_capture_logs.sh01:30
*** yee379 has quit IRC01:31
*** zul has joined #openstack-kolla01:31
*** yee379 has joined #openstack-kolla01:31
sdakeany idea why the job times out?01:32
sdake(ironic is the job)01:32
*** hrw has quit IRC01:32
kfox1111once in a blue moon we see that.01:32
kfox1111does it happen again on recheck?01:33
*** hrw has joined #openstack-kolla01:34
sdakeunclear01:34
sdakei'll try again01:34
sdakehelm-repo is the pv name?01:34
sdakeit seems to not be found01:34
kfox1111I think so.01:35
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Add a destroy workflow for kolla-kubernetes  https://review.openstack.org/46403101:35
sdakekfox1111 ubuntu jobs broken atm?01:36
kfox1111not sure.01:36
kfox1111I know sbezverk put in a fix for the 1.6.3 thing, but not sure if it fixed just centos or both.01:37
Jeffrey4linc0, yep.01:37
kfox1111I was rather medicated at the time and havent checked back up on it yet.01:37
openstackgerritshaofeng cheng proposed openstack/kolla-ansible master: Add VMware DataStore support to glance  https://review.openstack.org/45217601:37
kfox11111.6.4 is immenent though.01:37
inc0Jeffrey4l: so when we pip install Kolla it installs 4.0.001:38
inc0shouldn't we be in 5.0.0 now?01:38
sdakeinc0 pip is a pile of garb?01:38
sdakeinc0 pip pips up the git tag01:38
Jeffrey4linc0, we missed 5.0.0b1. it will be still 4.0.0 until 5.0.0b2 is tagged.01:38
sdakethere is no 5.0.0 tag as pike is unreleased01:38
inc0yeah that's what I was thinking01:39
inc0too much chaos01:39
openstackgerritpangliye proposed openstack/kolla master: Install docker_client and groupadd  https://review.openstack.org/46588001:40
inc0I'm thinking whether or not we should maually set up default tags instead of autogenerating from pbr01:41
*** zhubingbing has joined #openstack-kolla01:41
inc0as in, now default tag of images would be pike01:41
Jeffrey4linc0, use pike as default?01:43
Jeffrey4lthe issue is when tagged, we need change the "pike" to pbr value.01:43
Jeffrey4land there is no way to ensure this.01:43
Jeffrey4lif we forget to change it when tagged, big issue will happen.01:44
*** fguillot has quit IRC01:44
inc0on the other hand, if we actually push stuff to dockerhub, people won't be able to use images easily01:45
inc0as default will never point to them01:45
inc0in fact, today if they just use master code they'll pull ocata01:45
sdakeJeffrey4l is this ansible syntax correct:01:45
sdake- name: Delete Kolla PVs01:45
sdake  command: kubectl delete {{ item }}01:45
sdake  with_items:01:45
sdake    - "mariadb"01:45
sdake    - "glance"01:45
sdake    - "rabbitmq"01:45
sdake    - "helm-repo"01:45
inc0and if we'd tag in time, they wouldn't be able to pull anything01:45
inc0sdake: looks good01:45
Jeffrey4labout pike, it is master image stuff. we do not push/support master image right now.01:45
Jeffrey4lsdake, looks good.01:46
inc0right now no, but I want to if TC agrees01:46
sdakedoes [{ item }} need to be in "?01:46
inc0sdake: it does01:46
inc0all of it should01:46
inc0as in "kubectl delete {{item}}"01:46
sdakegroan01:46
Jeffrey4lsdake, right. need. other with, ansible will complain something.01:46
sdakeso all command operations need to be in full quotes?01:46
Jeffrey4lyes.01:47
inc0sdake: most of stuff should be in quotes01:47
*** stefan_bo has joined #openstack-kolla01:47
inc0most of arguments that is01:47
Jeffrey4linc0, re tag name, if we push master image to docker hub, we should re-consider the tag name.01:48
Jeffrey4lfix it to pike is not good too.01:49
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Add a destroy workflow for kolla-kubernetes  https://review.openstack.org/46403101:49
inc0Jeffrey4l: why?01:49
Jeffrey4lcause issue when tagging.01:49
Jeffrey4lunless you are think use the same tag ( pike ) for all tags ( 5.0.1, 5.0.2)01:49
inc0well, with pushes after tagging01:49
inc0we can manually retag on pushing01:50
inc0as in, default will never point to tagged image, but it's there01:50
Jeffrey4lwe can assign the tag name when building for dockerhub or retag.01:50
inc0also, depends if TC agrees to even pushing images01:50
inc0Jeffrey4l: but it won't ever default01:50
inc0reason I want these tags is01:50
*** unicell has quit IRC01:50
inc0when you do pip install kolla-ansible01:50
inc0you'll get set of images immediatly01:51
inc0no matter if you want master or ocata or what01:51
Jeffrey4lthen what will happen i run "pip install kolla-ansible==4.0.1"?01:51
inc0kolla-ansible will be in version 4.0.1 but default images will be ocata01:51
inc0well, that will change in pike01:52
inc0thing is01:52
Jeffrey4lkolla-ansible 4.0.0 may not work with kolla image 4.0.1, there is no way to ensure this.01:52
inc0I don't think it's good to have images frozen at 4.0.1 for example01:52
inc0but having 4.0.1 image means you'll not get security updates on anything01:53
inc0so at this ponit I think we shouldn't even push tags at all01:53
Jeffrey4lthen we have to add a NOTE that: "please update the kolla-ansible into latest version"01:53
Jeffrey4lThis is not *immediatly* either.01:54
inc0well, do you follow all of CVEs of all packages in all containers?01:54
inc0because I don't01:54
Jeffrey4lkolla can not ensure include all CVEs. unless you built it again.01:55
sdakespeaking of 4.0.1 is anyone planning to push these to dockerhub01:55
inc0so dhellman has point on this one, tagged fixed images are bad idea from security standpoint01:55
Jeffrey4lsdake, good point01:55
Jeffrey4lwe can build 4.0.1 4.0.2 by using kolla 4.0.1 and 4.0.2 daily to ensure it include all CVEs.01:56
Jeffrey4lbut only build ocata branch / latest tag image may not good.01:56
Jeffrey4linc0, how about this " build 4.0.1 4.0.2 by using kolla 4.0.1 and 4.0.2 daily"01:59
kfox1111we've used the same objects in kolla-kubernetes to deply 2.x through 4.x.02:00
kfox1111is it really that hard guys?02:00
Jeffrey4lkfox1111, the point is: no body and no way to ensure that it works.02:01
kfox1111with kolla-kubernetes we can.02:01
inc0Jeffrey4l: it won't break within stable that often02:01
kfox1111not sure why its hard in kolla-ansible, but don't know it very well.02:01
inc0and then we can say "upgrade your kolla-ansible"02:01
Jeffrey4linc0, yes.02:01
inc0since all published images will have to pass deploy gates02:01
kfox1111inc0: yeah.02:02
inc0and deploy gates will use latest stable deploy code02:02
kfox1111trunk is an enitirely different animal. if you are on the bleading edge, you should expect to bleed from time to time.02:02
*** sgrasley has quit IRC02:02
kfox1111if using stable, it should be stable.02:02
Jeffrey4linc0, the gate just test image 4.0.1 with kolla-ansible 4.0.1 , no gate to test image 4.0.0 with kolla-ansible 4.0.102:02
inc0so what you'll do is pip install -U kolla-ansible and that's it02:02
inc0we'll build set of gates dedicated for this pushes02:02
*** sgrasley has joined #openstack-kolla02:03
Jeffrey4lpip install -U kolla-ansible, no. this will install latest version. at least, please use "pip install -U kolla-ansible < 5"02:03
inc0well, you know what I mean02:03
Jeffrey4l;)02:03
inc0but bottom line, whatever we propose02:03
inc0we'll gate test it before publishing02:03
kfox1111+102:03
inc0in exactly the way we're proposing it02:03
inc0so unless you skip the step, it's all going to work02:03
inc0if new images fails the gate, they're not going to be pushed02:04
inc0until we fix it02:04
Jeffrey4lare u meaning: \only push latest image ( i.e  image:ocata) by using branch? which is tested in gate.02:04
inc0so my idea goes like that02:06
inc0we build special set of gates that will be run once a day02:06
inc0only these gates will publish to tarballs.o.o02:06
inc0these gates will have to pass (voting) all deploy gates02:07
Jeffrey4lbranch tag is not that stable.  for example no one use nova/stable/ocata direct in prod env.02:07
inc0binary will be voting too02:07
inc0so only if set of containers passes build gates and deploy gates for both ansible and k9s02:07
inc0gets pushed to tarballs02:07
inc0Jeffrey4l: lots of people do02:08
inc0those who don't usually don't because it's hard to orchiestrate02:08
sdakeJeffrey4l tend to disagree slews of people use our images02:08
sdakewhether that is a good idea or not, we leave to them :)02:08
inc0so I'd make it easy to locally build stable tags02:09
inc0but not host them due to security updates being missed02:09
inc0and only host freshest of the fresh builds02:09
inc0I think we need to reverse our approach to dockerhub publishing02:09
inc0becaue on that I agree with dhellman, we can't ensure safety of tagged images02:10
inc0and I'd rather have failed deploys that can be fixed by pip install -U than missed critical security update in one of packages02:10
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600702:12
sdakein other news, kolla-kubernetes requires 3.7gb of ram :)02:12
Jeffrey4ltbh, i never used dockerhub. and for any prod env, use self-build image is recommended. imo, dockerhub should be only used for newbies.02:12
inc0Jeffrey4l: frankly? more I think about it more I disagree with you02:13
sdakeJeffrey4l you dont use dockerhub becausez your in china and dockerhub is slow as mud there02:13
Jeffrey4linc0, aha, that the key point between us.02:13
inc0Jeffrey4l: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116906.html02:14
inc0that's why:P)02:14
inc0I mean I used to think that self-built is good02:14
inc0but now I don't really02:14
sdakeself built is the way to go02:14
*** goldyfruit has joined #openstack-kolla02:14
inc0kfox1111 swayed me otherwise;)02:14
Jeffrey4lsdake, slow it one reason. and personally, i will not use it even if it is fast.02:14
sdakehowever, some nerds in kolla wanted images on dockerhub, so now we are stuck with em :)02:14
inc0that's the thing, if we do good CI and automatic builds, self-building is quite literally worse02:15
inc0simply because, if we do this with CI I envision02:15
inc0containers we build will be deployed before publishing, so we have guarantee that it's deployable02:15
inc0if you build yourself, that's not the case02:15
Jeffrey4linc0, immutable is one issue.  tag:ocata is change for time to time. it may cause different nova version on my whole openstack env.02:16
inc0Jeffrey4l: we'll upload ocata and ocata-4402:16
*** zul has quit IRC02:16
inc0where 44 is autoincremental02:16
inc0so if you force todays 44 it won't upgrade on it's own any more02:17
Jeffrey4lok..02:17
inc0until you bump incremental02:17
inc0you won't be able to download 44 again as we won't store it, but you'll have it locally and it won't get overriden02:17
inc0archiving of images is up to you02:17
inc0dims: btw ^02:18
inc0good discussion about our ideas how that might work in secure manner02:18
inc0also that's argument why we shouldn't follow release team policy on that strictly:) actually if we follow releases, that's where security becomes bad02:19
sdakeinc0 what it really comes down to is nobody wants to take responsibility for the release of the images except the kolla team02:21
sdakeinc0 and the release team is the "gatekeeper" of releasing artifacts02:21
Jeffrey4lwhat i expecting is: 1. build kolla image 4.0.1 and push it into docker hub daily   2. build kolla image 4.0.2 and push it to docker hub daily.02:21
inc0Jeffrey4l: that's gonna be hell to maintain02:21
sdakeinc0 therefore I believe its the release team's position they own the greenlight on any activity you ahve proposed02:21
inc0because if 4.0.1 breaks due to bug02:21
inc0it won't ever be fixed, 4.0.1 is not updated, security is compromised02:22
Jeffrey4lwe can also to add :<branch> tag to point to latest tag ( i.e 4.0.2 )02:22
Jeffrey4lnova 15.0.1 is never be updated. tag is never be changed.02:22
kfox1111that but with release numbers.02:22
kfox111115.0.1 wont ever be updated. but deps might, ensuring 15.0.1-202:23
Jeffrey4lin my way: kolla image 4.0.1 is mutable for ( nova version / neutron version and all it's running env )02:23
kfox1111that doesnt work well with k8s.02:24
Jeffrey4lhrm, all this talk is talk is based on source type. binary is hard..02:24
kfox1111I really want to see atomic upgrades.02:24
kfox1111binary's the easy one I think. it won't change frequently.02:24
kfox1111fingerprint current version. build new one. fingerprint it. only if different, increment release number and push.02:25
Jeffrey4lis that OK to use diffferent  openstack ( nova / neutron ) y/z stream on you env?02:25
kfox1111to some extent, yeah.02:25
kfox1111live upgrades need that sort of thing.02:25
kfox1111not that openstack supports too much of that yet.02:25
kfox1111but it is actively being worked on.02:26
Jeffrey4li prefer to save all images for the future extend usage.02:26
kfox1111I don't disagree. but thats being a harder sale then the current only most recent.02:26
kfox1111and thats a hard sale. :/02:26
Jeffrey4lanyway, this is still my opinion: and for any prod env, use self-build image is recommended. dockerhub should be only used for newbies.02:27
kfox1111+102:28
kfox1111alwasys best to self-build for production.02:28
inc0Jeffrey4l: but nova doesn't ship with all the deps02:28
kfox1111for proof of concept/dev/testing though, should be a much lower bar.02:28
inc0we ship containers witl all the deps02:28
inc0ok, that's different conversation, but we all agree that there is benefit from having :ocata02:29
inc0that is not horribly hole'y, fresh and updated02:29
Jeffrey4lkfox1111, yes. include these purpose.02:29
inc0and easy to download02:29
kfox1111inc0: yeah.02:29
Jeffrey4lon the other hand, it is very hard to download image from docker hub from China ;(02:30
inc0although I'll be adamant that imho dockerhub the way we will do it will be better than self built:)02:30
inc0Jeffrey4l: does China has equivalent?02:30
Jeffrey4land we ( company ) provide this   https://hub.trystack.cn/   lol02:30
inc0we can push there too02:30
kfox1111Jeffrey4l: yeah. but china's great firewall is not reason enough to not do it.02:30
Jeffrey4linc0, no right now. not large/free equivalent at least.02:30
inc0Jeffrey4l: maybe 99cloud would want to host it for kolla?;)02:31
inc0then we'll just document that for China, use this address02:31
*** goldyfruit has quit IRC02:31
Jeffrey4lkfox1111, seem docker hub's image is on CDN. and the CDN provider is blocked.02:31
*** eanylin has quit IRC02:31
Jeffrey4linc0, good idea.02:31
kfox1111even still. being able to download some prebuild container images should be much easier on the great firewall,02:31
kfox1111then building from source which pulls from all over the place. :/02:31
inc0then for China it will be even better02:32
inc0since building containers behind great firewall is painful too02:32
kfox1111right.02:32
Jeffrey4lwe(99cloud) also provide a ISO to install kolla right now too. http://openstack.99cloud.com.cn/02:33
inc0there you go, registry.99cloud.com.cn:)02:33
kfox1111that would work. :)02:33
inc0and a page in docs where are mirrors are02:33
kfox1111I've always said we hsould push to multiple repo's.02:33
Jeffrey4lhttps://hub.trystack.cn/ should be OK.02:33
inc0dockerhub, quay.co, 99cloud02:33
kfox1111+102:34
inc0maybe docker.openstack.org one day02:34
Jeffrey4linc0, ++102:34
inc0anyway, we still need to wait for TC resolution02:34
kfox1111inc0: we must wait for the TC resolution to get the cronjob in place.02:35
kfox1111all the rest we can develop anyway.02:35
inc0that's what I'm doing02:35
kfox1111all the rest is still needed.02:35
kfox1111yeah. me too.02:35
inc0I started with simple tool02:35
inc0and now I'm working on gates02:35
inc0since as we said, we don't want to take chances with these images02:36
kfox1111inc0: maybe we shoudl come up with a final workflow diagram of all the pieces.02:36
kfox1111that may make folks feel better.02:36
inc0probably02:36
inc0gliffy or something02:36
kfox1111I gotta head out now. have a good evening.02:37
inc0you too02:37
kfox1111yeah. maybe we can talk more about that tomorrow.02:37
inc0btw Jeffrey4l take a look at that https://review.openstack.org/#/c/466007/1502:37
inc0I want to refactor our gates quite a bit02:37
Jeffrey4lgot.02:38
inc0for example drop setup_node02:38
inc0and use kolla-ansible bootstrap-servers instead02:38
inc0I already have piece that will prep ansible,inventory02:38
inc0and I'm close with basic globals.yml02:38
inc0after that we'll be able to add scenerios super easily, just add different globals.yml template02:39
Jeffrey4lthats cool.02:39
inc0we'll also be able to effectively remove aio gates02:39
inc0as aio will be same as multinode02:39
inc0just with less nodes02:39
inc0:)02:40
inc0so if we add for example ceph02:40
inc0it will automatically be tested aio and multinode02:40
inc0all within project_config02:40
inc0much like kolla-k8s has today, I like this approach02:40
Jeffrey4lthat will be better.02:41
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600702:44
*** zhubingbing has quit IRC02:46
*** eanylin has joined #openstack-kolla02:46
openstackgerritLi Yingjun proposed openstack/kolla-ansible master: Removing ovs bridge before destroying container  https://review.openstack.org/46499802:46
*** qiliang28 has joined #openstack-kolla02:48
*** xinliang has quit IRC02:49
openstackgerritMerged openstack/kolla stable/newton: Bump OpenStack service  https://review.openstack.org/46584902:50
*** qiliang27 has quit IRC02:51
*** qiliang28 is now known as qiliang2702:51
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600702:53
*** xinliang has joined #openstack-kolla03:01
*** zhubingbing has joined #openstack-kolla03:03
sdakekfox1111 i've sorted out what causes http://logs.openstack.org/31/464031/18/check/gate-kolla-kubernetes-deploy-centos-source-4-ironic-nv/f3b113c/console.html#_2017-05-19_02_37_58_15078903:05
sdakekfox1111 the cloud is destroyed - hence libvirt is no longer present03:05
sdakesuggestions?03:05
openstackgerritzhuangzejian proposed openstack/kolla-ansible master: Delete unnecessary code and insert a blank lines.  https://review.openstack.org/46591903:08
sdakesbezverk ^603:11
*** cosy294 has joined #openstack-kolla03:11
cosy294hello03:13
sbezverksdake: what are you truing to do with libvirt?03:14
sdakecpature_logs does a virsh dump03:14
sdakecapture logs seems to run after desetroy03:15
sdakesbezverk as you know capture logs does a whoe lbunch of stuff, it all happens after destroy it appears03:16
cosy294I install kolla-kubernetes with AIO environments.03:16
cosy294now, i want to install multi node03:16
cosy294help me03:16
sbezverksdake: I think there is a check for ironic gate job.. Only ironic gate job has bits to communicate with virsh..03:16
sdakesbezverk even if i don't run destroy ony in the ironic job (which is where it is run presently) capture_logs still runs after destroy03:17
sbezverkright right, libvirt runs in the container and you kill it03:17
sbezverkso virsh command stop working..03:17
sdakehence capture_logs wont capture any state, as it has been erased03:18
sbezverkbut log capure should be run only if there is a failure03:18
sbezverkyou do not call it unless something gets broken03:18
sdakeright - so we can't have jobs timign out at 1.05 hours just because capture_logs is ordered incorrectly03:19
sbezverkwe can move virsh command in log capture to be the last ones03:19
sbezverkand make is || true03:19
sdakethat would be great if the gate didn't block03:19
sbezverkbut regardless if your script worked then capture log should not be called03:20
sdakedo you know why the gate blocks??03:20
sdakesbezverk i hear you saying my code is broken and I agree03:20
sbezverkit hapens on rare ocasions03:20
sdakesbezverk it should not cause a trap, however ,it does, and we don't want flakey gates when something goes wrong03:20
sdakeits 100% with my patchset ;)03:21
sdakegood chance to debug the problem :)03:21
sbezverksdake: why you always start blaming something else, before makeing sure that you do right thing??03:21
sdakesbezverk its pretty straightforward, I could make my code work correctly03:21
sdakesbezverk and then capture logs wouldn't run03:21
sdakeand then the day somethign breaks and capture logs runs, the gate craters03:21
sdakeand everyone goes "oh thats a random failure"03:21
sdakeno failures are random03:21
sbezverksdake: perfect, you are on the right track to nail it then!!03:22
sdakesadly I don't know shell well enoug hto debug this problem03:22
sbezverkI mean to prove your point, right??03:22
sdakei think back to back traps are occuring03:22
sdakewhich creates a trap loop03:22
sdakei could use your help to debug03:23
sbezverkcan you run in ansible commands and use its output as an input to next action?03:23
sdakeyup03:24
sbezverkexample the issue here is with PVs03:24
sdakei understand there is a problem with the pvs :)03:24
sbezverkwhat then you want to debug?03:24
sdakethe gate lockup03:24
sdakethat happens outside of my code03:24
sdakethat happens in capture logs03:25
sbezverkit get stuck trying to communicate with non-existing libvirt03:25
sbezverkI mean it is not our bits03:25
sbezverkwe cannot change that03:25
*** zhubingbing has quit IRC03:25
sbezverkall we can do is work around it03:25
sdakehere is my theory - destroy raises trap, triggers capture logs03:26
sdakelibvirt raises trap - bash implodes03:26
sbezverkjust move virsh commands to the end of log capturing script03:26
sbezverkand add || true to each of them03:27
sbezverkin this case even if it fails it will not prevent further processing..03:27
sdakesbezverk they are at the end already03:27
sdakethere must surely be a way to ignore traps inside a script?03:27
sdakehttps://github.com/openstack/kolla-kubernetes/blob/master/tools/setup_gate.sh#L1003:28
sdakethat needs to be disabled here: https://github.com/openstack/kolla-kubernetes/blob/master/tests/bin/gate_capture_logs.sh#L303:30
sdakethis scenario happens all the time in signal handling in the c language03:31
*** stefan_bo has quit IRC03:32
sdakei guess i'll try this trap - signal03:33
sbezverksdake: I think last part which is ironic specific just needs to be wrapped into if03:33
sdakethe problem exists independent of my work :)03:33
sdakethis is why you see it from time to time in the gate jobs03:33
sbezverkso it is not executed if failure happen in your destroy script03:33
sbezverksdake: if you can consistently reproduce it, then we can debug, other than that I see failure becuase we try to access already non-existing services..03:35
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Add a destroy workflow for kolla-kubernetes  https://review.openstack.org/46403103:35
sdakesbezverk its reproducible03:35
sdake100% with this code03:35
sdakeanyway I just tested my theory if the internet is correct here: https://bash.cyberciti.biz/guide/How_to_clear_trap03:35
sbezverksdake: hm, is it 100% reproducable why we have green gate all the time ???03:36
sdakesbezverk 100% with my code (which raises a trap in gate_setup.sh)03:36
sbezverkand why do you raise trap?03:37
sdakebecause ansible raises a signal03:37
sdakeand that causes bash to receive a signal03:37
sdakeand trpa catches that signal03:37
sdakeand triggers signal handling03:37
sdakesignal handling in bash = evil :)03:37
sbezverkwe had gate log capture script gets called on every failure03:38
sbezverkno evil, everything was working fine until you declaried it to be evil.. that does not compute will03:38
sdakeright and when the second failure happens, the gate deadlocks03:38
sdakewe will see if the gate lbocks this time. :)03:39
sdakesbezverk if you raise a signal in a signal handler in unix, bad bad things happen (TM)03:39
sdakeits not like || true magically ignores signals :)03:39
sbezverkit is not a C it is a script called from another script, it is done many time03:40
sdakesbezverk i'll be you 1 american dollar03:40
sdakethat if you cause some kind of error in capture_gate_logs, th gat ewill lock up03:40
sdakebe/bet :)03:40
sbezverkthere is OS signal generated like sigterm or sigabort03:40
sbezverkit looks up because virsh cannot get in touch with libvirt03:41
sdakethat is a second possible theory althoug hthe gate logs don't indicate that03:41
sbezverkwe have bunch of commands inluding ipmi commands trying and then re-trying to communicate with libvirt03:41
sdakewell we will know in approximately 30 minutes :)03:42
sbezverkit clearly indicates that: sdake03:42
sbezverkhttp://logs.openstack.org/31/464031/18/check/gate-kolla-kubernetes-deploy-centos-source-4-ironic-nv/f3b113c/console.html#_2017-05-19_02_37_58_15581803:42
sbezverkit is damn last message in the log03:43
sdakesbezverk look at the gate delta in times03:43
sdake20 minutes03:43
sdakebetween that and the gate timeout03:43
sdakethat operation completely locks up03:43
sdakewhereas the job exited and returned...03:43
sdakerather command03:43
sbezverkbecause there are multiple commands and we do not know how virtual bmc reacts on this connection03:44
sbezverkI meant on this condition..03:44
sdake30 minutes03:44
sdakegate will either block or not03:44
sdakeif it doesn't block, my theory is correct :)03:45
sbezverkok, have fun, I am off..03:45
sdakelater03:45
sdakeshame you didn't take me up on my bet :)03:45
openstackgerritzhuangzejian proposed openstack/kolla-ansible master: Test: insert a blank  https://review.openstack.org/46616903:50
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Demonstrate trap failure  https://review.openstack.org/46617003:51
*** unicell has joined #openstack-kolla03:51
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Demonstrate trap failure  https://review.openstack.org/46617003:52
sdakesbezverk that review should fail in about 1-2 minutes :)03:52
sdakesbezverk or alternately block for 1.05 hours03:52
*** zhubingbing has joined #openstack-kolla03:56
sdakeJeffrey4l how does one make ansible ignore errors03:59
*** stefan_bo has joined #openstack-kolla04:05
*** iniazi has joined #openstack-kolla04:07
*** imcsk8 has quit IRC04:12
*** vhosakot has joined #openstack-kolla04:12
openstackgerritAnthony Lin proposed openstack/kolla-kubernetes master: Script to Deploy Kolla Kubernetes AIO  https://review.openstack.org/46431204:24
Seyonghello sdake, just greeting04:24
*** eaguilar has quit IRC04:29
inc0sdake: add ignore_errors: true04:30
inc0to task04:30
*** stefan_bo has quit IRC04:32
*** yuanying has quit IRC04:32
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600704:35
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600704:43
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600704:44
*** yuanying has joined #openstack-kolla04:48
*** skramaja has joined #openstack-kolla04:48
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600704:50
*** salv-orlando has joined #openstack-kolla04:50
*** cosy294 has quit IRC04:54
inc0Jeffrey4l: any ideas why docker failed to install? http://logs.openstack.org/07/466007/21/experimental/gate-kolla-ansible-dsvm-deploy-multinode-ubuntu-source-ubuntu-xenial-2-node-nv/aca66de/console.html04:55
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600705:06
*** salv-orlando has quit IRC05:07
*** cuongnv has quit IRC05:15
*** stefan_bo has joined #openstack-kolla05:15
*** vhosakot has quit IRC05:15
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600705:16
*** cuongnv has joined #openstack-kolla05:19
Jeffrey4lsdake, what's kinda error?05:24
Jeffrey4linc0, not sure, environments may be. try to use  "rpm -ql docker-engine" to list all file?05:26
*** caowei has joined #openstack-kolla05:33
*** unicell has joined #openstack-kolla05:39
*** jaosorior_away has quit IRC05:44
*** stefan_bo has quit IRC05:44
*** mkoderer has quit IRC05:47
*** janki has joined #openstack-kolla05:51
*** jbadiapa has quit IRC05:53
*** caowei has quit IRC05:53
*** stefan_bo has joined #openstack-kolla05:59
*** aagate has quit IRC06:00
*** yuanying has quit IRC06:06
*** jbadiapa has joined #openstack-kolla06:08
*** yuanying has joined #openstack-kolla06:08
*** salv-orlando has joined #openstack-kolla06:08
openstackgerritzhuangzejian proposed openstack/kolla-ansible master: Insert a blank line.  https://review.openstack.org/46619506:10
*** salv-orlando has quit IRC06:13
openstackgerritSurya Prakash (spsurya) proposed openstack/kolla master: Fixing the running of keystone  https://review.openstack.org/46495306:16
openstackgerritzhuangzejian proposed openstack/kolla-ansible master: Delete useless code  https://review.openstack.org/46619906:21
*** sgrasley1 has joined #openstack-kolla06:27
*** sgrasley has quit IRC06:27
*** Serlex has joined #openstack-kolla06:32
*** chas has joined #openstack-kolla06:38
*** pcaruana has joined #openstack-kolla06:39
*** korzen has joined #openstack-kolla06:42
*** athomas has joined #openstack-kolla06:42
*** pcaruana is now known as pcaruana|tve|06:44
*** pcaruana|tve| is now known as pcaruana|rtve|06:44
openstackgerritserlex proposed openstack/kolla-ansible master: Add index pattern to kibana once  https://review.openstack.org/46610106:46
*** matrohon has joined #openstack-kolla06:58
openstackgerritzhuangzejian proposed openstack/kolla-ansible master: Delete useless code  https://review.openstack.org/46619907:03
*** Serlex has quit IRC07:04
*** salv-orlando has joined #openstack-kolla07:09
openstackgerritMathieu Rohon proposed openstack/kolla master: Add skydive service  https://review.openstack.org/45999507:11
*** salv-orlando has quit IRC07:13
*** shardy has quit IRC07:16
*** shardy has joined #openstack-kolla07:17
*** jmccarthy has joined #openstack-kolla07:21
*** unicell has quit IRC07:22
*** unicell has joined #openstack-kolla07:24
openstackgerritJeffrey Zhang proposed openstack/kolla stable/ocata: Catch exception during calling os.chmod in set_configs.py  https://review.openstack.org/46621507:29
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible stable/ocata: Remove verbose log in memcached container  https://review.openstack.org/46621607:30
*** chas has quit IRC07:31
*** egonzalez has joined #openstack-kolla07:32
*** gfidente has joined #openstack-kolla07:38
*** gfidente has quit IRC07:38
*** gfidente has joined #openstack-kolla07:38
*** chas has joined #openstack-kolla07:41
*** blallau has joined #openstack-kolla07:43
*** chas has quit IRC07:45
*** chas has joined #openstack-kolla07:47
*** Serlex has joined #openstack-kolla07:49
*** manheim_ has joined #openstack-kolla07:51
*** manheim_ has quit IRC07:51
*** manheim_ has joined #openstack-kolla07:52
*** chas has quit IRC08:00
*** chas has joined #openstack-kolla08:00
openstackgerritDan Ardelean proposed openstack/kolla-ansible master: Add Hyper-V role  https://review.openstack.org/45568408:04
*** salv-orlando has joined #openstack-kolla08:10
*** salv-orlando has quit IRC08:16
*** mgoddard__ has joined #openstack-kolla08:20
*** chas has quit IRC08:23
*** chas has joined #openstack-kolla08:23
*** powerd has joined #openstack-kolla08:27
*** jaosorior has joined #openstack-kolla08:29
*** lpetrut has joined #openstack-kolla08:39
*** stefan_bo has quit IRC08:49
*** salv-orlando has joined #openstack-kolla09:00
*** xinliang has quit IRC09:00
*** caowei has joined #openstack-kolla09:01
*** c06 has joined #openstack-kolla09:05
*** awebber has joined #openstack-kolla09:05
*** c06 has left #openstack-kolla09:05
*** c06 has joined #openstack-kolla09:05
*** c06 has left #openstack-kolla09:05
*** salv-orlando has quit IRC09:06
*** ArminderSingh- has joined #openstack-kolla09:06
*** chas has quit IRC09:09
*** xinliang has joined #openstack-kolla09:11
*** caowei has quit IRC09:14
openstackgerritEduardo Gonzalez proposed openstack/kolla master: Implement blazar Docker images  https://review.openstack.org/45474509:16
*** kolla-slack1 has joined #openstack-kolla09:17
*** kolla-slack has quit IRC09:17
openstackgerritEduardo Gonzalez proposed openstack/kolla master: Implement blazar Docker images  https://review.openstack.org/45474509:20
*** caowei has joined #openstack-kolla09:23
openstackgerritEduardo Gonzalez proposed openstack/kolla master: Allow nova plugins install, add blazar plugin  https://review.openstack.org/45474309:23
kolla-slack1<archifleks> hi09:25
*** jascott1 has joined #openstack-kolla09:26
hrwmorning09:30
Serlextop of the morning09:34
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla-ansible master: Kibana post_config checks only need to run locally  https://review.openstack.org/46379809:39
*** sambetts|afk is now known as sambetts09:46
*** jascott1 has quit IRC09:48
pbourkeSerlex: did anyone say that in boston?09:50
*** stefan_bo has joined #openstack-kolla09:51
*** openstack has joined #openstack-kolla10:00
*** salv-orlando has joined #openstack-kolla10:02
SerlexUnfortunately no pbourke, I clearly didn't hit the rights part of the city :)10:02
*** salv-orlando has quit IRC10:06
pbourkewell that's the thing, im not sure anyone actually says it :p10:16
*** stefan_bo has quit IRC10:20
*** caowei has quit IRC10:28
*** zul has joined #openstack-kolla10:31
*** mkoderer has joined #openstack-kolla10:31
*** skramaja has quit IRC10:35
*** shardy has quit IRC10:36
*** cuongnv has quit IRC10:37
*** shardy has joined #openstack-kolla10:38
*** daidv has quit IRC10:47
*** blallau has quit IRC11:01
*** YuYangWang has joined #openstack-kolla11:02
*** salv-orlando has joined #openstack-kolla11:02
*** tovin07_ has quit IRC11:03
*** imcsk8 has joined #openstack-kolla11:05
manheim_guys, do you know any good guide for k8s networking? i've failed to find a good one, i have hard time comprehending k8s networking11:06
*** salv-orlando has quit IRC11:07
*** chas has joined #openstack-kolla11:09
*** feisky has quit IRC11:10
*** rhallisey has joined #openstack-kolla11:12
*** shardy has quit IRC11:12
*** chas has quit IRC11:13
*** chas has joined #openstack-kolla11:15
*** zul has quit IRC11:19
*** shardy has joined #openstack-kolla11:19
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: WIP: Implement blazar ansible role  https://review.openstack.org/45475211:19
*** Serlex has quit IRC11:22
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Implement blazar ansible role  https://review.openstack.org/45475211:24
*** blallau has joined #openstack-kolla11:27
*** schwicht has joined #openstack-kolla11:29
*** Serlex has joined #openstack-kolla11:30
*** schwicht has quit IRC11:35
*** schwicht has joined #openstack-kolla11:38
*** YuYangWang has quit IRC11:42
*** zul has joined #openstack-kolla11:54
*** zhubingbing has quit IRC11:55
*** zhubingbing has joined #openstack-kolla11:55
*** srwilkers has joined #openstack-kolla11:59
*** Serlex has quit IRC12:00
*** salv-orlando has joined #openstack-kolla12:03
*** schwicht has quit IRC12:05
*** janki has quit IRC12:06
*** janki has joined #openstack-kolla12:06
*** tloeb has joined #openstack-kolla12:08
*** salv-orlando has quit IRC12:08
*** tloeb has quit IRC12:10
*** egonzalez has quit IRC12:10
openstackgerritJuan Antonio Osorio Robles proposed openstack/kolla master: Add images for novajoin services  https://review.openstack.org/46626812:13
*** schwicht has joined #openstack-kolla12:16
*** jistr is now known as jistr|mtg12:16
*** sean-k-mooney has quit IRC12:18
*** jrist has joined #openstack-kolla12:23
*** dave-mccowan has joined #openstack-kolla12:26
*** shardy has quit IRC12:27
*** shardy has joined #openstack-kolla12:27
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: Add a destroy workflow for kolla-kubernetes  https://review.openstack.org/46403112:27
*** eanylin has quit IRC12:30
*** egonzalez has joined #openstack-kolla12:31
*** rwellum has joined #openstack-kolla12:34
*** fguillot has joined #openstack-kolla12:36
*** jchhatbar has joined #openstack-kolla12:42
*** eaguilar has joined #openstack-kolla12:43
*** janki has quit IRC12:45
openstackgerritBernard Maltais proposed openstack/kolla-kubernetes master: Script to Deploy Kolla Kubernetes AIO  https://review.openstack.org/46431212:45
*** jchhatbar has quit IRC12:48
*** eaguilar has quit IRC12:49
*** goldyfruit has joined #openstack-kolla12:52
*** zhubingbing has quit IRC12:52
*** janki has joined #openstack-kolla12:56
*** eaguilar has joined #openstack-kolla12:57
*** salv-orlando has joined #openstack-kolla12:59
*** jistr|mtg is now known as jistr12:59
*** schwicht has quit IRC13:03
*** janki has quit IRC13:04
*** goldyfruit has quit IRC13:05
*** zhubingbing_ has joined #openstack-kolla13:07
*** schwicht has joined #openstack-kolla13:08
*** shardy has quit IRC13:12
*** shardy has joined #openstack-kolla13:13
*** salv-orlando has quit IRC13:16
*** salv-orlando has joined #openstack-kolla13:16
*** schwicht has quit IRC13:19
*** salv-orlando has quit IRC13:21
*** zul has quit IRC13:27
*** schwicht has joined #openstack-kolla13:30
*** krtaylor has joined #openstack-kolla13:31
*** mattmceuen has joined #openstack-kolla13:37
*** duonghq has joined #openstack-kolla13:46
*** salv-orlando has joined #openstack-kolla13:54
*** Serlex has joined #openstack-kolla13:54
*** blallau has quit IRC13:54
*** srwilkers has quit IRC13:55
*** aagate has joined #openstack-kolla13:55
*** goldyfruit has joined #openstack-kolla13:58
*** eanylin has joined #openstack-kolla13:59
*** iniazi has quit IRC14:01
*** amurali has joined #openstack-kolla14:05
amuraliI'm trying to build neutron-server image from master branch with networking-6wind plugin...but, I ended up with error   "Could not find a version that satisfies the requirement nova (from networking-6wind==0.0.1.dev49) (from versions: )"14:06
amuraliAnybody has any idea about this ?14:06
*** shardy has quit IRC14:08
*** shardy has joined #openstack-kolla14:08
*** zhubingbing_ has quit IRC14:08
*** schwicht has quit IRC14:09
*** duonghq has quit IRC14:09
*** korzen has quit IRC14:10
egonzalezamurali cannot  find a pip  package with that name14:12
*** zhubingbing has joined #openstack-kolla14:16
egonzalezyou  will need to  install from github  or tarball, follow this guide https://github.com/openstack/kolla/blob/master/doc/image-building.rst#plugin-functionality14:17
*** ducttape_ has joined #openstack-kolla14:27
*** srwilkers has joined #openstack-kolla14:34
*** eaguilar has quit IRC14:34
*** ducttape_ has quit IRC14:35
*** iniazi has joined #openstack-kolla14:36
*** lpetrut has quit IRC14:36
*** ducttape_ has joined #openstack-kolla14:36
*** schwicht has joined #openstack-kolla14:38
*** manheim_ has quit IRC14:39
openstackgerritBernard Maltais proposed openstack/kolla-kubernetes master: Script to Deploy Kolla Kubernetes AIO  https://review.openstack.org/46431214:39
sdakemorning folks14:42
*** sgrasley has joined #openstack-kolla14:44
bmaltaisMorning14:44
*** emccormick has joined #openstack-kolla14:44
bmaltaiseanylin: The script is failing when running with sudo14:45
*** sgrasley1 has quit IRC14:45
bmaltaiseanylin: Slowly fixing it but I am stuck at the step "Generate the Kubernetes secrets and register them with Kubernetes"14:46
bmaltaiseanylin: The strange thing is that it work when run by hand... but not via the script.14:46
bmaltaiseanylin: Also, since this script will eventually be run from within a git clone kolla-kubernetes... a lot of the content will need to change14:47
bmaltaiseanylin: If a used download it to another location vs /opt the script should handle that... right now it would just download another copy in /opt14:48
*** schwicht has quit IRC15:00
*** zhubingbing has quit IRC15:00
*** manheim_ has joined #openstack-kolla15:01
*** hongbin has joined #openstack-kolla15:01
*** zhubingbing has joined #openstack-kolla15:02
inc0good morning15:03
*** gmann has quit IRC15:05
*** gmann has joined #openstack-kolla15:05
*** zhubingbing has quit IRC15:06
*** srwilkers has quit IRC15:06
manheim_hello15:07
*** salv-orlando has quit IRC15:09
*** salv-orlando has joined #openstack-kolla15:10
*** srwilkers has joined #openstack-kolla15:12
*** jaosorior has quit IRC15:13
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600715:13
*** salv-orlando has quit IRC15:14
*** schwicht has joined #openstack-kolla15:18
bmaltaiseanylin: Found the issue... but it is now failing with another error. I think it is due to the fact that there is now an all.yml file15:20
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600715:26
openstackgerritMartin André proposed openstack/kolla master: Install ODL driver from package where appropriate  https://review.openstack.org/46632515:30
*** vhosakot has joined #openstack-kolla15:32
*** eaguilar has joined #openstack-kolla15:34
*** manheim_ has quit IRC15:35
*** manheim_ has joined #openstack-kolla15:36
*** salv-orlando has joined #openstack-kolla15:36
*** awebber has quit IRC15:39
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600715:39
*** powerd has quit IRC15:41
*** salv-orlando has quit IRC15:41
*** sgrasley1 has joined #openstack-kolla15:42
*** sgrasley has quit IRC15:42
*** powerd has joined #openstack-kolla15:44
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600715:47
*** matrohon has quit IRC15:50
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600715:50
*** k_mouza has joined #openstack-kolla15:51
k_mouzahello all!. Quick one please. I want to make some changes in the /etc/neutron/plugins/ml2/ml2_conf.ini file on all the neutron-openvswitch-agent nodes15:53
rwellumbmaltais: running a script as sudo and using sudo per command is much different right? Basically you're running as root the first way. Second way you're running certain commands as root - but home directory is still your user etc,15:53
k_mouzawhat file should I put my changes in, on the deployment node?15:53
k_mouzait should be something like /etc/kolla/config/neutron/openvswitch-agent/...15:54
openstackgerritEduardo Gonzalez proposed openstack/kolla master: ODL installed for source images  https://review.openstack.org/46633615:55
k_mouzaI've done a similar configuration for the nova.conf file, but this is a slightly different directory structure15:55
*** eaguilar has quit IRC15:59
egonzalezk_mouza custom  config  for ml2 file is only supported for  all services(neutron-server,  ovs-agent or linuxbridge-agent) or pointing  to  a  host15:59
openstackgerritMartin André proposed openstack/kolla master: Install ODL driver from package for binary distros  https://review.openstack.org/46632515:59
*** janki has joined #openstack-kolla16:00
egonzalezconfig/neutron/ml2_conf.ini or  config/neutron/<inventory_hostname>/ml2_conf.ini16:00
egonzalezk_mouza ^^16:00
k_mouzathanks a lot @egonzalez ! I'll try that now16:02
egonzalezk_mouza for other  service, you  can look at config.yml  of each role and  see what  merge_config support, ex  of  ml2 https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/neutron/tasks/config.yml#L11716:03
openstackgerritStephanie Miller proposed openstack/kolla-ansible master: Fix vagrant dev env build  https://review.openstack.org/46633716:03
egonzalezmost services share the same pattern but in the case of  neutron with  a ton of different config files  is harder16:03
openstackgerritStephanie Miller proposed openstack/kolla master: Fix vagrant dev env  https://review.openstack.org/46633916:04
bmaltaisrwellum: So perhaps I have made changes that were not needed in the script... I tought the idea was that it would be run as a regular user and that each elevated prix functions would be called via sudo in the script...16:04
*** sgrasley1 has quit IRC16:05
rwellumbmaltais: haven't had a chance to look at the script - but I think what you're describing is the correct way imo.16:05
bmaltaisrwellum: Are you saying the the script should be run like: sudo ./setup_AIO.sh vs ./setup_AIO.sh16:05
rwellumNo - before it was the former, I think it should be the latter16:06
*** manheim_ has quit IRC16:06
*** sgrasley has joined #openstack-kolla16:06
bmaltaisrwellum: OK then. This is what I have been working on to fix it so it work that way based on what was started.16:07
rwellumGreat - that in the latest ps?16:07
bmaltaisrwellum: Now I am running on another issue not related to sudo due to a change in how the script will no longer use globals.yml for some of the things.16:07
rwellumAh the all.yml? Yeah I was curious how that would work.16:08
bmaltaisrwellum: I am not sure either. I will let eanylin: look into it as he started with the changes. At least most of the sudo issues are cleared now...16:08
rwellumOk16:09
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Implement blazar ansible role  https://review.openstack.org/45475216:10
rwellumbmaltais: there's one issue with running as individual sudo commands I've discovered. If the script take a long time, then sudo will time out - and mid-way through the script you'll have to enter sudo creds again.16:11
*** eaguilar has joined #openstack-kolla16:15
*** stefan_bo has joined #openstack-kolla16:17
vhosakotk_mouza: I did it recently.  Just place your new OVS config in https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/neutron/tasks/config.yml#L118-L119 and run "kolla-ansible reconfigure".   node_custom_config defaults to /etc/kolla/config in https://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml#L10.16:19
*** stefan_bo has quit IRC16:22
*** jmccarthy has left #openstack-kolla16:23
*** unicell has quit IRC16:23
*** eaguilar has quit IRC16:26
*** manheim_ has joined #openstack-kolla16:26
*** manheim_ has quit IRC16:27
vhosakotamurali: don't think kolla has containerized 6wind yet.  Does neutron+networking-6wind work outside the container? :)16:30
vhosakotinc0: another candidate for the new kolla-sdn repo that does fast data - https://github.com/openstack/networking-6wind16:31
amuraliActually, i'm installing it inside 'neutron-server' container as a plugin16:31
inc0dpdk is cool;)16:32
vhosakotamurali: I have not deployed it, but I've heard it it similar to vpp that I've deployed with neutron, right, as an ml2 plugin for neutron that does fast data in user-space.16:32
*** pbourke has quit IRC16:33
vhosakotamurali: "installing it inside", I think ml2 plugin is a separate process that does fast L2, I think it must be in a separate container like how kolla deploys OTB l2 services like OVS and linux bridge is separate containers.16:35
vhosakots/ml2 plugin/ml2 plugin for 6wind16:35
sdakemorning16:37
vhosakotmorning sdake16:38
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600716:39
sdakepayday16:41
*** pcaruana|rtve| has quit IRC16:42
*** imcsk8 has quit IRC16:42
*** k_mouza has quit IRC16:42
*** imcsk8 has joined #openstack-kolla16:42
egonzalezamurali last commit into the networking-6wind repo is from oct2016,  not sure how maintained is the plugin, unless they moved  to  other repo, I wouldn't use with ocata16:43
*** AzazeL_ has joined #openstack-kolla16:44
vhosakotsome vendor plugins are not as fast moving as other core OpenStack projects16:44
eanylinbmaltais rwellum: I made changes based on what I understand.  I will let kfox1111 comment on that.  But yeah, with the new proposed change, I believe we need to update all.yml as well for it to work properly.16:46
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600716:46
*** sambetts is now known as sambetts|afk16:47
bmaltaisrwellum: This is why I always use a nopassword sudo user so that timeout is not an issue16:51
rwellumbmaltais: ack.16:52
rwellumbmaltais: other work-arounds too. like 'sudo -v' - or setting timeout=-1 in sudoers16:52
bmaltaisrwellum: Perhaps it should be indicated in the guide at some point.16:52
rwellumbmaltais: yeah16:53
sbezverksdake: I have a suggestion. instead of running ansible clean up, let's run just a regular bash script clean up with the same commands adn see if it fails the same way or not16:54
sbezverkat least we will know if it is general issue or specific to ansible16:55
bmaltaiseanylin: The script will be intended to run, when ready, from the kolla-kubernetes git clone... right?16:55
sdakesbezverk i could try that - although i scrweed up my knee yesterday so struggling to get my day going16:55
bmaltaiseanylin: Right now the script is not build on that basis...16:55
bmaltaiseanylin: It is almost build as if it would be downloaded seperatly and not be bundled as part of the tools folder16:56
sbezverksdake: sorry to hear that.. I might have time later tonight to try it16:56
bmaltaiseanylin: What was your original intention?16:56
sbezverkif you do not do it earlier16:56
sdakesbezverk i'll see if i can dig into it - i jammed my knee right into the corner of a door16:56
sdakeyou wouldn't think that would hurt all tha tmuch16:56
*** mgoddard__ has quit IRC16:57
sbezverksdake: yeah, knee is a tricky thing too many moving and delicate parts there16:57
*** salv-orlando has joined #openstack-kolla16:57
*** unicell has joined #openstack-kolla17:02
eanylinbmaltais: It is not in the folder for sure as its still in review.  This was done in respond to feedback from kfox1111 from patch set $917:02
eanylin#917:03
*** salv-orlando has quit IRC17:03
sdakesbezverk re https://review.openstack.org/#/c/464031/20/ansible/roles/destroy/tasks/main.yml - I tend to agree re not deleting PVs17:03
sdakesbezverk those are generally created by the cluster admin (in a perfect world)17:04
*** srwilkers has quit IRC17:04
sbezverksdake: right, but let's keep then for now as we need consistent error17:04
sdakeyou mean to debug the other gate problem?17:04
sbezverksdake: well I am not sure if it is gate or combination your ansible script and gate17:05
sdakeright thats what i mean17:05
sdakehow about i split the review into two17:06
sdakeso we can merge one and I can suffer a sense of accomplishment :)17:06
*** chas has quit IRC17:06
sbezverksdake: if by eleminating ansible it starts working, then ansible experts will nee dto look into it17:06
*** chas has joined #openstack-kolla17:07
sdakegenconfig has the same issue17:07
sdakei actually have a way to fix er, I think17:07
sdakeif traps return to bash17:07
*** chas has quit IRC17:11
rwellumeanylin: in the latest script, you have as an input the subnet size of management network - will that ever be anything other than 24?17:11
*** sgrasley has quit IRC17:11
eanylinrwellum: Not too sure too but it will be /24 in most cases I believe17:12
rwellumDid you test with other ranges?17:12
*** sgrasley has joined #openstack-kolla17:12
eanylinrwellum: I have not, seems like /24 is the default value, so I used /2417:12
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Test of gate deadlock with bash  https://review.openstack.org/46635817:13
rwellumOk. Wasn't sure why we made it an option.17:13
rwellums/you/we17:13
eanylinrwellum: Hmm, cause its an option in the cloud.yml17:13
eanylinrwellum: So I exposed it as well, just in case17:14
rwellumOk. wfm17:15
sdakeegonzalez you about17:18
*** mkoderer has quit IRC17:24
*** salv-orlando has joined #openstack-kolla17:25
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Crater the deploy using genconfig  https://review.openstack.org/46636317:25
sdakerwellum can you confirm the current deployment guide works as is?17:26
*** salv-orlando has quit IRC17:28
rwellumsdake - no I think the cloud.yaml is kaputt17:28
sdakethere is a review in the queue for a canal change17:28
sdakeunless it merged17:28
*** amurali has quit IRC17:28
rwellumUrgh - sorry meant canal17:28
rwellumHmm - interesting - let me look.17:29
*** eaguilar has joined #openstack-kolla17:29
rwellumDon't see it - can you point me to it?17:30
*** mgoddard__ has joined #openstack-kolla17:31
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600717:35
rwellumsdake: https://review.openstack.org/#/c/465754/1/doc/source/deployment-guide.rst17:40
*** fguillot has quit IRC17:40
*** srwilkers has joined #openstack-kolla17:41
rwellumsdake: that looks great - missed that. I have now figured out that: project:openstack/kolla-kubernetes works17:41
sdakerwellum nice ;)17:42
*** ducttape_ has quit IRC17:43
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Add a destroy workflow for kolla-kubernetes  https://review.openstack.org/46403117:48
*** powerd has quit IRC17:48
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600717:48
sdakesbezverk https://review.openstack.org/#/c/466358/1/tools/setup_gate.sh appears to fail also17:49
sbezverksdake:  I do not see gate results for that ps17:51
sdakeya zuul is locked up17:51
sdakeso looks like its timing out17:51
sdakei can't onnect to these machines as I dont' have ipv617:51
sbezverkit will fail because 4th kubectl delete pv does not exist and will fail17:52
sdakeright - althoug htaht shouldn't cause the gate to lock up17:52
sdakethat should cause the gate to fail fast17:52
sbezverksdake: you see it does not lock up17:52
sbezverkit did, 36min instead of 1.5 hour17:52
sdakeyup17:52
sbezverkso it is ansible then17:52
sdakei think it is a relation between ansible and  trap17:57
sdakealthough i had genconfig generate a similar trap and nothing bad happened17:57
*** eaguilar has quit IRC17:58
sdakei think kubectl is not generating signals when it fails outside of ansible17:58
sdakehowever ansible is17:58
sdakehard to tell for certain17:58
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Crater the deploy using genconfig  https://review.openstack.org/46636317:59
sbezverksdake: you are ready to suspect bash, kubectl, but not obvious that it is ansible glitch 99.99%18:00
sdakesbezverk i don't know what precisely the problem is, however, my training says its a trap error18:01
sdakesignal handling is broken18:01
sdakei have spent years of my life debugging signal handling18:01
sdakeand i hae seen this problem hundreds of times in various code18:01
sdakeso forgive me if years of my life wasted debugging points to signal handling and i am biased towards that :)18:02
sdakesbezverk remember the gate fails in this way sans destroy :)18:02
sdake(sans ansible)18:03
vhosakotsdake: I saw a similar issue where a Linux command wasn't generating the right failed signal/trap when it failed and my ansible playbook happily treated it as a successful play.  I debugged it, opened https://bugzilla.redhat.com/show_bug.cgi?id=1288528 with RH, and RH updated their ERRTA now  https://rhn.redhat.com/errata/RHEA-2016-0603.html in OSP8.18:03
openstackbugzilla.redhat.com bug 1288528 in python-oslo-service "services can´t stop due to broken oslo service" [Urgent,Closed: errata] - Assigned to vstinner18:03
sbezverksdake: right, it fails exactly the way it is supposed to fail18:03
sbezverkbecause incorrect operation was performed18:03
sbezverkif you add || true to that kubectl command18:04
sbezverkthen it will not fail18:04
sdakewhich one in particular18:04
sdakethe destroy?18:04
sdakethe gate should never deadlock one a failure18:04
sbezverkno, in your last PS you have line kubectl delete pv helm-repo-wrong18:04
sdakeright, i was expecting the gate to lock up there18:05
sbezverkthis command tries to delete non-existing object18:05
sdakenot for the destroy to work18:05
sdakei get that dude18:05
sdakehow do you think i can reproduce the problem without reproducing the problem?18:05
sbezverkas a result bash catches it and calls another bash script which properly collect data18:05
sdakesbezverk http://logs.openstack.org/63/466363/2/check/gate-kolla-kubernetes-deploy-centos-source-4-ironic-nv/80e5644/console.html#_2017-05-19_18_02_36_61901818:06
sbezverkmaybe the issue is the ansible pass errorness to calling parent bash script?18:06
sbezverkI mean, how18:06
sbezverkinstead of just returning error code it just dies18:07
vhosakotI hit this too where ethtool was returning the wrong signal to ansible and had to open https://bugzilla.redhat.com/show_bug.cgi?id=1434236.  RH hasn't fixed it yet.18:07
openstackbugzilla.redhat.com bug 1434236 in ethtool "ethtool returns incorrect exit code for error (stderr)" [Medium,New] - Assigned to ivecera18:07
sbezverkin a non graceful way18:07
sdakesbezverk ansible doesn't die18:07
sdakecapture logs dies18:07
sdakeor its parent thereof18:07
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600718:08
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600718:09
sbezverksdake: we know this works: bash (parent) hit error, call child bash to collect logs, do you agree?18:10
sdakewe know that a bash parent hit error, this calls bash child to collect logs, that child suffers a virsh error, and then exits immidately: http://logs.openstack.org/63/466363/2/check/gate-kolla-kubernetes-deploy-centos-source-4-ironic-nv/80e5644/console.html#_2017-05-19_18_02_36_61901818:12
sdakewe know that a bash parent hits an error (running ansible), this calls bash child to collect logs, that child suffers a virsh error, and then exits18:12
*** harlowja has joined #openstack-kolla18:13
sbezverksdake: what does not work: bash script (parent) calls ansible script where we hit error and bash script log collector gets stuck.18:13
*** salv-orlando has joined #openstack-kolla18:13
sdakei think the blame of what gets stuck is an open quesiton18:13
sdake+ is returned - indcating the parent shell is back in action18:13
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600718:14
*** Jeffrey4l has quit IRC18:14
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Crater the deploy using genconfig  https://review.openstack.org/46636318:15
sbezverksdake: why, clearly you can see from your PS that the reaction is exactly as expected18:15
sdakewe also know that this review here will test if genconfig fails in same way18:16
*** ddyer has quit IRC18:16
sbezverkwe hit an issue during the execution, and then call log caputre, it hit another issue but it does not get stuck18:16
sdakebefore debating me to deat hon the root cause, why not let me debug it a bit ;)18:16
sbezverkjob does not get hanging for another 40 minutes to be killed18:16
sbezverksure, I was just highlighting the log your PS was generating and that behavior makes perfect sense18:17
sdakeagreed that particular bash log maeks perfect sense18:18
sdakewhat doesn't make sense is the ansible log18:18
sdakeand that is what we are after solving iiuc :)18:18
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600718:18
sdakethe fact that this fails quickly provides extra information: https://review.openstack.org/#/c/466363/18:20
*** Jeffrey4l has joined #openstack-kolla18:20
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600718:24
rwellumsbezverk: I am trying to get a loopback LVM for Cinder running - as per the gate. But nova is complaining that: " 4: no space left on device". df -h shows plenty of space.18:24
* inc0 working up patchset stats18:24
* rwellum daily question for sbezverk 18:25
sbezverksdake: in this case you run a different ansible script, so it means whatever you do you destroy script is causing the issue and not just ansible in general18:26
sdakethat is a possibility18:26
sbezverkrwellum: vgs cinder-volumes18:26
sbezverkrwellum: lvs18:26
rwellumNothing returned sbezverk18:27
sbezverkrwellum: well I guess that is the answer18:28
rwellumSorry..18:28
rwellumlvs nothing18:28
rwellumvgs: https://www.irccloud.com/pastebin/Fd4EfU2S/18:28
openstackgerritNuman Siddique proposed openstack/kolla master: Support openvswitch-ovn docker images  https://review.openstack.org/45917918:28
rwellumlvs: https://www.irccloud.com/pastebin/81zqv9LD/18:29
rwellumI read your commands wrong.18:29
*** JoseMello has joined #openstack-kolla18:29
sbezverkrwellum: how much space you are requesting?18:29
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600718:29
sbezverkcinder service-list18:30
rwellumWhat is my '--os-username'?18:32
rwellumsudo dd if=/dev/zero of=/data/kolla/cinder-volumes.img bs=5M count=204818:33
sbezverksource keystone_adminrc18:33
*** emccormick has quit IRC18:35
rwellumOk so have not generated one yet as my cluster didn't come all the way up. But when I try to I am getting space issues. So seems I have really hurt this VM for space somehow.18:35
*** Jeffrey4l has quit IRC18:36
sbezverkrwellum: not sure then what to say, cinder-volume VG takes 10G18:36
sbezverk rwellum: how much space you allocated to you VM?18:37
*** numans has quit IRC18:37
rwellum50G - and it's all gone :)18:37
sbezverkrwellum: right, because images takes good chunk of memory18:38
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600718:38
*** ddyer has joined #openstack-kolla18:38
rwellumThen I added 10G and it fell over - quite possible18:38
sbezverkrwellum: I normally allocate 100G (OS + Docker images) for VM and extra voume like vdb for cinder-volume vg18:39
*** zul has joined #openstack-kolla18:41
rwellumsbezverk: ok makes sense.18:42
rwellumWhere are the images stored btw?18:42
*** Jeffrey4l has joined #openstack-kolla18:43
sbezverkrwellum: depends how your docker is configured18:44
sbezverkrwellum: some time ago I started to use Storage Driver: btrfs as a storage driver and keep images on yet separate vdc disk18:45
sbezverkinstead of docker's default loopback18:46
sbezverkit seems a bit better in terms of performance and reliability18:46
sbezverkbut require additional configuration and planning18:46
rwellumInteresting. Yeah the VM is harder to create then.18:47
rwellumWhere is the default loopback?18:47
sbezverkrwellum: well not that much, instead of 1 disk you pass 3 disks to VM18:47
sbezverkrwellum: I think it is /var/lib/docker18:48
rwellumYeah and I've done that for other deployments. But for this was just going with default centos. Which never seems to work that well long-term.18:48
*** emccormick has joined #openstack-kolla18:50
*** mattmceuen has quit IRC18:50
*** mgoddard__ has quit IRC18:50
rwellumYeah looks like /var/lib/docker. Is that something that should be cleaned up between deployments?18:53
sbezverkrwellum: note really, if you pull the same images, then they will just take space they need18:55
rwellumok18:55
sbezverkbut if you deploy different version then, potentially they will eat a lot ;)18:55
rwellumOk makes sense.18:56
rwellumSorry sdake didn't mean to de-rail your debug session...18:56
rwellumsbezverk: how much RAM normally for your VM?19:05
*** athomas has quit IRC19:09
*** itlinux has joined #openstack-kolla19:09
*** ducttape_ has joined #openstack-kolla19:12
*** mgoddard__ has joined #openstack-kolla19:15
*** powerd has joined #openstack-kolla19:16
*** powerd has quit IRC19:21
*** celo_r has joined #openstack-kolla19:26
*** salv-orlando has quit IRC19:38
*** powerd has joined #openstack-kolla19:39
*** celo_r has quit IRC19:43
*** shardy has quit IRC19:46
*** myoung is now known as myoung|pto19:50
*** mgoddard__ has quit IRC19:53
*** mgoddard__ has joined #openstack-kolla19:55
inc0https://review.openstack.org/#/c/466007/ \o/20:01
inc0multinode gate green for kolla-ansible20:01
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600720:03
*** Serlex has quit IRC20:03
*** cali_box has quit IRC20:03
kfox11111.6.4 :)20:05
*** sgrasley has quit IRC20:08
*** sgrasley has joined #openstack-kolla20:08
*** matrohon has joined #openstack-kolla20:09
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600720:09
matrohonJeffrey4l, hi20:10
inc0kfox1111: not quite your league yet, but I'm getting there (talking about number of patchsets) https://review.openstack.org/#/c/466007/4020:10
*** jrist has quit IRC20:11
kfox1111inc0: hehe. looking good. :)20:11
kfox1111and a really important use case. :)20:11
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: Remove workaround for broken 1.6.3  https://review.openstack.org/46639820:12
inc0well at the same time I'm refactoring gates quite a bit20:12
kfox1111it would be nice if we could generalize the kkolla-kubernetes gates a bit and reuse chunks.20:12
inc0so I hope at the end we'll be able to add use cases easily20:12
kfox1111the part that gathers logs is really really good.20:12
inc0agree20:12
kfox1111but could be broken up into a docker vs non docker logging section.20:12
matrohonDoes anyone know if "kolla-ansible upgrade" is supposed to work to upgrade form newton to ocata?20:12
inc0matrohon: it is supposed to20:13
matrohoninc0: good to know, I'm having some troubles20:13
inc0what kind of problems?20:14
matrohonI've try to upgrade from 3.0.3 to 4.0.220:14
*** itlinux has quit IRC20:14
matrohonmay be the gap is to big...20:14
sdakerwellum sup dude its ok - i was taking a nap20:16
matrohoninc0 : the cmd "nova-manage cell_v2 simple_cell_setup" is run from the nova-api container in the 3.0.3 version20:16
rwellumeanylin: still around?20:18
inc0manheim: it should be run from 4.x20:18
inc0did you bump container versions in your globals.yml?20:18
matrohonand the task "running nova bootstrap containers" fails, saying the "nova manage cell..." command should be run first, but it should have been run....20:18
matrohoninc0, I did20:19
*** mgoddard__ has quit IRC20:20
SamYapleyea newton is all funky and stuff20:20
SamYapleim pretty sure its broken20:20
SamYaplelike the instructions work for ocata, but newton doesnt and i havent had a chance to figure out why20:20
SamYaplewhich is wierd because it _was_ working at one point20:20
matrohoninc0, I feel like the "nova manage cell..." should be run in a up-to-date nova-api container, it can't work in a old nova-api container20:21
inc0matrohon: it should20:21
inc0that's why I'm asking about globals.yml, and openstack_release conf20:21
matrohoninc0, it should work even if it is run in the old nova-api container?20:22
inc0no, simple cell setup is done in new container20:23
inc0we might have bug.20:24
inc0but it's strange20:25
inc0also, looking at code and comments it should actually be runnable in newton cotnainers20:25
matrohoninc0, ok that's what I was guessing, but if I look at the upgrade task, it seems the exec command is done in the old container20:25
matrohonhttp://git.openstack.org/cgit/openstack/kolla-ansible/tree/ansible/roles/nova/tasks/upgrade.yml?h=stable/ocata#n1120:26
inc0yeah20:26
inc0that's what I'm looking at20:26
inc0if you try to add cell0 like that manually20:26
*** janki has quit IRC20:26
*** salv-orlando has joined #openstack-kolla20:26
inc0does it work?20:26
inc0(I hate what nova did to N->O upgrades)(20:26
rwellumsdake: you are doing the vip keepalive in your deployments?20:26
inc0especially that it merged 2 weeks before Newton release:/20:26
matrohoninc0, I'm not sure how to figure it did work20:26
sdakerwellum indeed20:27
inc0matrohon: do docker exec -it nova-api bash20:27
inc0and run simple cell setup manually from within container20:27
kfox1111ok.... so... looks like we just need way to delete the nova_cell0 db now...20:28
rwellumsdake: For the bridge to bind the VIP to - anything special? Which int - or just a dump listening bridge?20:28
sdakerwellum moment20:28
matrohoninc0, I need to figure out what was the transport-url parameter!20:31
*** dave-mccowan has quit IRC20:31
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: WIP: v4 gates.  https://review.openstack.org/45484120:31
sdakerwellum https://da.gd/El5P20:31
sdakekfox1111 a bit of help on https://review.openstack.org/#/c/464031/20:32
*** zul has quit IRC20:32
inc0matrohon: you can add - debug task to ansible20:32
sdakekfox1111 the ironic gate locks up 100% of the time and times out when running that workflow with ansibulls20:33
sdakekfox1111 same workflow in bash doesn't lock up20:33
kfox1111thats a little weird...20:33
sdakekfox1111 suspicion is it has to do with the trap operation20:33
sdakethe save logs code is also generating an error20:33
sdakewhich is like a double trap20:33
sdaketypcially when you generatea  signal from within a signal handler (in c) the system implodes20:34
sdakei suspect bash uses the same mechanics but not certain20:34
matrohonincO BTW I also had to change permission on the file /var/log/kolla/nova/nova-manage.log to 77720:34
kfox1111so, the trap should not be set inside that file.20:35
matrohonotherwise the nova-manage command fails with permission denied20:35
kfox1111so disabling it should be a noop.20:35
sbezverksdake: -1 because another ansible script works fine20:35
kfox1111sorry. in gate_capture_logs.sh.20:35
*** zul has joined #openstack-kolla20:35
sbezverkit is something inside of you destroy script20:35
sdakeother ansible script doesn't generate double trap20:35
kfox1111line 3 of destroy_tests.sh starts with 'stray' ?20:36
kfox1111that a typo?20:36
sbezverkif you remove everything from it, i bet it will not gets locked up20:36
kfox1111oh. yeah. it looks like it might be a comment that got munged.20:36
matrohoninc0, do you know how I can tell kolla-ansible to only run nova tasks?20:37
sdakekfox1111 oh ya comment got fubared it appears20:37
inc0matrohon: kolla-ansible upgrade -t nova20:37
matrohoninc0 I've tried --tags, but it runs a lot of other tasks20:37
inc0it will also run common role20:37
sdakesbezverk i need to be able to preserve the double trap to genreate the problem -that means nova has to be deleted20:37
matrohoninc0 -t is an alias of --tags?20:37
inc0yes20:37
sdakeif ndeed that is the problem20:38
rwellumkfox1111: did you try 1.6.4 - or you making the change and seeing if the gate works?20:38
matrohonincO I'll continue this way20:38
sbezverksdake remove everything from ansible except kubectl that gen error20:38
sdakesbezverk there are two interactions - 1 trap occurs in ansible, 1 occurs in virsh20:38
kfox1111rwellum: the latter.20:38
kfox1111the gate's my test. :)20:38
sdakeremoving everything except kubectl i would expect to work20:38
rwellumkfox1111: cool20:39
sbezverkexcep then two things20:39
kfox1111rwellum: very easy to just poke in a test, then forget about it for 30 min, and check back on it later.20:39
sdakesbezverk you mean keep the two operations that result in a failure?20:39
sbezverkyes20:39
sdakeok20:39
sbezverkbut remove everything else20:39
sdakekfox1111 is there a wa yto disable a venv20:40
kfox1111sdake: deactivate20:40
sdakesbezverk we got a different failure this time: http://logs.openstack.org/31/464031/21/check/gate-kolla-kubernetes-deploy-centos-source-4-ironic-nv/ef09ca9/console.html#_2017-05-19_17_53_06_15196820:42
sdakesbezverk this was with a typo in the destroy code - although the destory code was never run20:42
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Add a destroy workflow for kolla-kubernetes  https://review.openstack.org/46403120:43
matrohoninc0, done20:43
matrohoninc0, the nova-manage cmd says "Already setup, nothing to do."20:44
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Add a destroy workflow for kolla-kubernetes  https://review.openstack.org/46640420:46
sdakesbezverk kfox1111 - running two different things now - one with deactive - one with just the two operations that result in a crater in destroy to see if its some other part of destroy causing the problem20:47
sdakekfox1111 do you have any other specualtino as to what could be the problem?20:48
matrohoninc0, but the nova-bootstrap container keeps on failing saying "ValidationError: Cell mappings are not created, but required for Ocata. Please run nova-manage cell_v2 simple_cell_setup before continuing."20:49
*** salv-orlando has quit IRC20:49
matrohoninc0, I'll keep on digging around and report a bug if needed20:49
rwellumAs an aside - went for a walk today down by a lake by our office, and a huge snake shot up the path and stopped an inch from my foot. Then followed me about 20ft down the path... I never saw a snake do that before... Someone told me people have been feeding them...20:49
kfox1111sdake: not really sure... off hand. if its taking that long, usually thats something is wedged.20:49
kfox1111the trap code in the gate log capture shoudl be  a no op.20:50
sdakeit is wedged for sure20:50
kfox1111a double trap shouldn't really be a problem as it crosses bash process bounderies.20:50
sdakethanks for that peice of information - iddin't know that20:50
kfox1111I'm thinking something in the destory_tests.sh script is just g etting stuck and not returning.20:50
kfox1111then getting killed by the gate timeout.20:50
sdakehadn't thought of that20:51
sdakeworth a go to verify20:51
kfox1111might remove most of the stuff out of the ansible script. then try. if it works, add chunks back till it hangs.20:51
sdakekfox1111 ya i've got a line of debugging on that that sbezverk suggested20:51
kfox1111cool.20:51
kfox1111gotoa head out to another meeting.20:51
sdakei like the destroy_tests.shsanalysis20:51
sdakelater kfox1111 thanks20:51
kfox1111bbiab.20:51
kfox1111np. :)20:52
sdakerwellum gah who would feed a snake :)20:52
sdakerwellum actualy i don't mind snakes20:52
sdakeas long as they are not rattlers20:52
sdakerwellum when i was in BSA, summer camp was filled with 20+ hours playing with snakes20:53
rwellumsdake: me neither but they aren't supposed to approach you and ask for snack!20:53
sdakeeven in BSA wee were not permitted to feed the snakes20:53
sdake(unless it was their meal)20:53
sdakethey let us do that - kind of crazy to watch20:53
* rwellum shuddering20:53
sdakethere is a zoo in arizona that does live lion feedings20:54
sdakethat is friegenting20:54
sdakeactually tis raw meat so the lions aren't feeding on live animals20:54
sdakeits live in the sense that its right in front of you :)20:54
rwellumOh phew..20:55
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Kevins' line of debug  https://review.openstack.org/46640820:57
sdakei took my kids once20:57
sdakewhen they were too young20:57
sdake(first itme)20:57
sdakebad idea20:57
sdakealthough they still love that zoo20:58
rwellumYeah I bet! :)20:58
*** itlinux has joined #openstack-kolla20:58
sdakeits really cool - about 5 square miles20:58
sdakeall the animals are in natural habitats etc20:58
sdakethey have a ride in the zoo area where the animals are20:58
sdakeand a giraffe licked my daughter20:59
rwellumSimilar with Lions - but it was mating season. One of those driving through a park deals. Some hard explaining had to occur. :/20:59
openstackgerritMarcus Williams proposed openstack/kolla-ansible master: Add OpenDaylight role  https://review.openstack.org/41636720:59
rwellumGuess she was tasty.20:59
sdakelol - once iin this zoo saw a pair of turtles doing their thing20:59
sdakeallt he kids wer elike"what is that":)20:59
sdakelike 30 kids on this truck20:59
sdakeit was a little emberassing for the adults20:59
sdakebecause of course the kids knew what was going on :)21:00
rwellum:)21:00
*** ssurana has joined #openstack-kolla21:00
*** bmace__ has quit IRC21:03
*** salv-orlando has joined #openstack-kolla21:03
*** bmace__ has joined #openstack-kolla21:03
*** salv-orlando has quit IRC21:04
egonzalezinc0 matrohon may be  late,  N to O need cells created before upgrade thats why command is executed before upgrade  containers21:04
matrohonegonzalez, ack, but the nova-api container with the name nova-bootstrap fails as if the command has never been run...21:05
rwellumkfox1111: 1.6.4 seems to be working smoothly for me locally. So far anyway21:05
egonzaleznova-manage in 3.0.2 had a bug with the behaviour of the command, cannot remember what was,  first  need upgrade to 3.0.321:05
*** zul has quit IRC21:05
sbezverkrwellum: gate is still pulling 1.6.3 at least for Ubunut21:06
*** ssurana has quit IRC21:07
sbezverkwe should wait, maybe until EOB today and then re-check21:07
rwellumsbezverk: https://review.openstack.org/#/c/466398/121:07
matrohonegonzalez, ok, but I'm already in 3.0.321:07
sbezverkrwellum: I know, I commented already..21:07
vhosakotmatrohon: "kolla-ansible upgrade" should work and runs upgrade.yml depending on your openstack_release.  here is how the gate runs upgrade http://logs.openstack.org/52/454752/6/check/gate-kolla-ansible-dsvm-deploy-centos-binary-centos-7-nv/f2ed72a/console.html#_2017-05-19_16_51_06_716478.21:08
rwellumsbezverk: oops sorry!21:08
sbezverkrwellum> no worries21:08
*** JoseMello has quit IRC21:08
egonzalezmatrohon what was the error?21:10
matrohonegonzalez, the "nova-manage sync" cmd run in the nova-bootstrap container fails with : ValidationError: Cell mappings are not created, but required for Ocata. Please run nova-manage cell_v2 simple_cell_setup before continuing.21:13
vhosakotocata and its cells :)21:13
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: DONOTMERGE: test multinode gate  https://review.openstack.org/46600721:13
*** zul has joined #openstack-kolla21:15
egonzalezmatrohon can you share  ansible logs in the nova part?21:15
egonzalezmatrohon have you built your images or pulled from  dockerhub?21:16
matrohonegonzalez, I'm running an new upgrade cmd in vernose mode21:17
matrohonegonzalez, I've build from source21:17
matrohonand pushed in my local repo21:17
vhosakotdevstack stable/ocata OTB was also broken for a long time until recently as devstack's stack.sh failed to create nova cells OTB --> https://github.com/openstack-dev/devstack/blob/stable/ocata/stack.sh#L1369-L138321:20
vhosakotit is fixed now.21:20
emccormickHey all! Quick (hopefully) question. I need to override tunnel_interface and cluster_interface for a couple hosts as they are not identical. Do I need to override it via neutron configs in /etc/kolla/config or is there a way to specify those options per host?21:20
egonzalezemccormick add the  variable in the inventory file21:21
egonzalezemccormick example https://github.com/openstack/kolla-ansible/blob/master/doc/multinode.rst#edit-the-inventory-file21:22
emccormickegonzalez: Ah I thought that was just for ansible-specific options. Cool. I'll give it a go. Thanks!21:24
*** itlinux has quit IRC21:25
*** salv-orlando has joined #openstack-kolla21:25
vhosakotemccormick: right, tunnel_interface is not a neutron config, it is a kolla variable.  You could also set via command line like appending    -e "tunnel_interface=<interface other than cluster_interface>"   at the end of your ansible command.21:26
egonzalezremember one of the issues, simple_cell_setup looked up for flavors in the db, if no flavor was present took the db sync as a fresh deploy, that caused false positives  in  many upgrade gates without load21:26
vhosakotnever used cluster_interface much really, think it is for ceph storage..21:26
*** zul has quit IRC21:27
egonzalezmatrohon just to be sure,  can you  verify if ansible roles are in ocata version, the cell setup in current master  was removed from upgrade phase since is not needed  anymore21:28
*** dave-mccowan has joined #openstack-kolla21:30
matrohonegonzalez, good idea, I'll run the script directly from my kolla-ansible clone, in the stable/ocata branch21:32
emccormickvhosakot: Sorry, meant api_interface. Old habit from my previous puppet stuff. sluster_interface is for the private network of a ceph cluster, yes.21:33
matrohonegonzalez, unfortunately, kolla-ansible doesn't have a --version option21:33
egonzalezyeah, is a bash  script ;)21:33
egonzalezmay  be a good feature to have21:34
*** dave-mccowan has quit IRC21:34
matrohonegonzalez, same error..21:34
vhosakotemccormick: ah ok cool21:35
matrohonegonzalez, I'm not sure to understand how the "nova-manage db-sync " is triggered21:35
egonzalezmatrohon im  running a  deploy/upgrade21:35
matrohonegonzalez, cool, thanks21:35
egonzalezhttps://github.com/openstack/kolla-ansible/blob/stable/ocata/ansible/roles/nova/tasks/upgrade.yml21:36
egonzalezfirst cell0 is created in  newton21:36
*** schwicht has quit IRC21:36
egonzalezdo simple_cell_setup which sync cell0 tables in  current db version21:36
egonzalezthen do the db sync for the schema  version upgrade21:37
matrohonegonzalez, I'd like to give a try on running simple_cell_setuo cmd during the nova_bootstrap phase, before the db_sync cmd...21:38
*** salv-orlando has quit IRC21:39
egonzalezissue was, in newton  cell_setup pointed to  nova_api_cell0 database  instead of  nova_cell021:39
egonzalezthats  why first is created the cell21:39
*** salv-orlando has joined #openstack-kolla21:41
*** srwilkers has quit IRC21:41
matrohonegonzalez, inc0, gtg, thanks for your help, I'll keep on working on that on monday21:42
inc0sorry to hear you had issues matrohon21:43
vhosakotemccormick: I just use the default api_interface (which defaults to network_interface) in group vars.21:43
matrohoninc0, no worry, it's not production, only testing, and I'm learning a lot about ansible :)21:43
inc0it's good knowledge to have if you want to stick with kolla-ansible21:43
*** salv-orlando has quit IRC21:45
inc0egonzalez: check that out :) https://review.openstack.org/#/c/466007/4221:45
vhosakotinc0: 42 patch sets.. I think sbezverk crashed gerrit once with his 829th patch set ;)21:46
egonzaleza big w00t!21:46
emccormickvhosakot: I spread things out a bit more and then I have a bunch of gear from all manner of vendors with all manner of different nic configs so I can't generalize. Beggars can't be choosers ;)21:46
inc0not only enabled multinode21:47
inc0but also simplify a lot to add new scenerios21:47
inc0https://review.openstack.org/#/c/466415/ when this merges I'll work on having super easy mechanism to add new scenerios21:47
vhosakotemccormick: cool, good to isolate network segments/NICs for specific traffic21:48
sdakesbezverk check this out: http://logs.openstack.org/31/464031/22/check/gate-kolla-kubernetes-deploy-centos-source-4-ironic-nv/b2206d4/console.html#_2017-05-19_21_45_28_09439721:50
vhosakotsdake: touch it lol.. touch /var/run/libvirt/libvirt-sock-ro... I just touch all missing things lol21:51
vhosakotj/k21:52
*** ssurana has joined #openstack-kolla21:52
sdakekfox1111 this no worky: https://review.openstack.org/#/c/464031/21..22/tests/bin/destroy_tests.sh - although looking very positive (no gate lockup after the ansible code is run)21:52
sdakekfox1111 which implies that the script is locking up related to testing21:52
sdakekfox1111 any suggestions on how to get that deactivate to work?21:53
sdakeinc0 ^^21:53
* sdake never uses virtualenv21:53
inc0sdake: just call deactivate21:54
sdakeinc0 so ./deactivate?21:55
sdake(what is the path after an activation)21:55
inc0let me check my envs21:55
sdakeinc0 http://logs.openstack.org/31/464031/22/check/gate-kolla-kubernetes-deploy-centos-source-4-ironic-nv/b2206d4/console.html#_2017-05-19_21_45_05_29364521:55
inc0it normally is available just as $deactivate21:55
sdakeso just run from the cmdline $deactivate?21:59
vhosakotsdake: exit also exits from venv, but deactivate is much more graceful and cleaner.22:00
sdakevhosakot which command should be run22:01
sdakevhosakot ./deactivate?22:01
vhosakotthere should be files activate and deactivate inside the venv....   find . | grep 'activate'    should show the path.22:02
*** schwicht has joined #openstack-kolla22:02
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Add a destroy workflow for kolla-kubernetes  https://review.openstack.org/46403122:02
sdakevhosakot i am in a gate job - it takes 45 minute sto run - i really don't want  to hunt for it which is why i am asking22:03
*** matrohon has quit IRC22:03
sdakespend 30 minutes writing code - spend 5 days making the gate work - winning22:03
*** salv-orlando has joined #openstack-kolla22:04
sdakeinc0 is this correct: https://review.openstack.org/#/c/464031/23/tests/bin/destroy_tests.sh22:04
inc0sdake: no22:05
inc0but try just calling deactivate22:05
sdakethat wont be in the path...22:05
inc0well it is, I think it's an alias22:06
inc0try iot22:06
*** sambetts|afk has quit IRC22:06
sdakethat makes sense thnaks i'll try22:06
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Add a destroy workflow for kolla-kubernetes  https://review.openstack.org/46403122:08
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: Enable multinode gate  https://review.openstack.org/46600722:10
vhosakotsdake: ah, I don't know what's happening in the review in gate, sorry... just said how I'm able to deactivate my venv... I use activate and deactivate my venv like this  -->   virtualenv test ; cd test/ ; source bin/activate ; deactivate22:10
sdakethanks vhosakot22:10
*** sambetts_ has joined #openstack-kolla22:10
sdakeespp FTW22:11
*** mgoddard__ has joined #openstack-kolla22:11
*** harlowja has quit IRC22:12
vhosakotsdake: yes, deactivate won't be in the path inside the venv, it is not an alias too, but the command "deactivate" works fine and deactivates the activated venv.22:19
vhosakotsdake: "which deactivate" inside the venv prints "/usr/bin/which: no deactivate in (/root/test/bin:/sbin:/bin:/usr/sbin:/usr/bin)"  even though the command deactivate works..22:19
*** stefan_bo has joined #openstack-kolla22:20
vhosakotdon't know how it works, need to read up on it.. deactivate will not be in the path and not an alias too.. some sort of runtime thing happening inside venv22:20
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Kevins' line of debug  https://review.openstack.org/46640822:21
sdakevhosakot its a shell fucntion22:21
vhosakotinc0: deactivate is not an alias too, "alias | grep deactivate" prints nothing in my venv :)22:22
vhosakotsdake: ah ok, yeah, some sort of shell-level parser invocation thing inside the venv.22:22
egonzalezinc0 just upgraded centos source 3.0.3-> 4.0.0 and went fine,  will try with  4.0.2 just in case  something changed22:22
inc0vhosakot: right, I don't know where it came from;)22:22
inc0thanks egonzalez22:23
vhosakotinc0: me too :)22:23
inc0upgrade gates btw are next after ceph on my gate list22:23
*** ducttape_ has quit IRC22:23
sdakeinc0 a focus of kolla-ansible on gating would be in order i suspect - as the implementation is pretty solid at this point - so more power to ya :)22:24
egonzalezceph w/ cinder will fail  until this get merged https://review.openstack.org/#/c/457993/22:24
sbezverksdake: you need to remove hard coding PV's name even in the gate code we will change them at one point when we need to run multiple Rabbitmq22:24
inc0sdake: https://review.openstack.org/#/c/466007/22:24
inc0so my order of work I'm going to do for next few weeks22:24
*** stefan_bo has quit IRC22:25
inc0this, ceph gates, upgrade gates22:25
inc0then, if we actually get permission to push images to dockerhub22:25
inc0a voting gate set for push job daily22:25
inc0if we won't get this permission22:25
inc0I'll do it anyway just for tarballs22:25
inc0so we can have deploy-tested images in tarballs at all times22:26
inc0after that we can make voting deploy gates22:26
inc0and that will make our gates really really solid22:26
inc0btw please review https://review.openstack.org/#/c/466007/22:27
inc0it's ready to be merged imho22:27
inc0or at least reviewed;)22:27
*** powerd has quit IRC22:29
*** salv-orlando has quit IRC22:29
*** mgoddard__ has quit IRC22:30
*** schwicht has quit IRC22:32
*** sgrasley has quit IRC22:32
*** powerd has joined #openstack-kolla22:35
*** sgrasley has joined #openstack-kolla22:36
kfox1111sbezverk: the name is totally erelevent. there's nothing pinning pvc's to pv's by name anyway.22:38
kfox1111we could just change it to name: {{random()}}22:38
*** amurali has joined #openstack-kolla22:38
sbezverkkfox1111: right but in sdake's destroy, there is a lost of PVs22:39
sbezverkwhich gets removed22:39
sbezverkI think that whole part needs to be removed22:39
kfox1111he's deleting everything I thoguht.22:39
kfox1111"burn it all down"22:39
sbezverkwhat if I choose a different name for PV22:39
sbezverkthen his script will not delete22:39
kfox1111I thought he was for looping and deleting all pv's? mabye Im wrong.22:40
sbezverkit is either to make it flexible or just not delete PVs22:40
sbezverknope, he hard coded 4 PVs22:40
kfox1111depends on the use case.22:40
sbezverkwhich is not right I think22:40
kfox1111if its "user owns the whole k8s and wants to hit the reset button so can deploy kolla-kubernetes again",22:40
kfox1111thats easy to just delete all the things.22:40
sbezverkor ALL22:41
kfox1111if its more complicated then that, it probably should use your cleanout stuff.22:41
*** chas has joined #openstack-kolla22:41
kfox1111then its very precice.22:41
*** amurali has quit IRC22:42
sbezverkkfox1111: example is running multiple rabbitmq, then we will need PV per rabbitmq instance. I would really like to see this scenario tested and working..22:45
kfox1111+122:45
kfox1111but I'm saying, his cleanup stuff should either just delete all pv's, so thats not a problem,22:45
kfox1111or call the cleanup stuff you wrote, which should delete them ok?22:45
*** chas has quit IRC22:46
sbezverkkfox1111: right22:46
*** Pavo has joined #openstack-kolla22:46
*** sgrasley has quit IRC22:46
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: Enable multinode gate  https://review.openstack.org/46600722:47
*** sgrasley has joined #openstack-kolla22:49
*** Pavo has quit IRC22:49
*** harlowja has joined #openstack-kolla22:57
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Add a destroy workflow for kolla-kubernetes  https://review.openstack.org/46403123:08
sdakekfox1111 i don't want to burn down the pvs, as the cluster may have other pvs in it unrelated to kolla and pvs are enot namespaced23:09
kfox1111sdake: then I wonder if we should do something like sbezverk's cleanup script to handle those...23:10
sdakekfox1111 in fact in that last review i removed the pvs23:10
sdakewhich script kfox1111 ?23:10
kfox1111like, helm/service/*-cleanup23:10
sdakethe pvs are to be managed by teh admin and hopefully not deleted at all I think23:10
*** emccormick has quit IRC23:11
kfox1111the whole pv thing is a mess. we should get to dynamic pv's and let the admin deal with manual entirely.23:11
*** powerd has quit IRC23:11
sdakei think for now we can just punt on pvs23:11
sdakethe alternative is for me to list them out and delete those with a mapping of mariadb/glance/rabbitmq/etc23:11
sdakethe cleanup helm jobs are naother optoin as well23:12
sdakealthough last i looked at those, they simply clean up the database entries/users/etc23:12
kfox1111yeah. helm delete <thingy> --purge does most of the rest.23:13
kfox1111the cleanup stuff is for cleaning up stuff helm itself cant.23:13
sdakedeleting pvs vai helm works23:14
sbezverkkfox1111: here is universal way of deleting pvc and pv23:15
sbezverkkubectl get pvc -n kolla | grep Bound | awk '{print "kubectl get pvc -n kolla -o jsonpath={.spec.volumeName} "$1}'23:15
sbezverkwe get all pvc in kolla namespace then get attached volumes and then delete them23:15
sdakesbezverk does that operation print out a list of pvs?23:15
kfox1111that works, but only if the pvcs havent been deleted yet.23:15
sbezverkso we do not hard code anything and we know since it seats in kolla23:15
kfox1111I though helm deleted pvc's?23:16
sdakekfox1111 i can work with that model :)23:16
sdakekfox1111 i can capture the pvs prior to deletion of the helm charts23:16
kfox1111sdake: the other option is to run that, then delete all the charts, then the pv's listed.23:16
sbezverkkfox1111: right in the loop we get info, then delete pvc and then pv23:16
kfox1111yeah.23:16
kfox1111:)23:16
kfox1111isn't it wonderful when a plan comes together. :)23:16
sbezverkkfox1111: man I like so much bash :) really good thing to have23:17
kfox1111ages and ages ago, when I was on the dos platform, I really liked the cli over windows. could do so many more things.23:17
kfox1111oh how wrong I felt when I finally discovered bash. :)23:18
sbezverkkfox1111: :)23:18
sbezverknow windows provides power shell23:18
kfox1111bash is in a nice middle ground between shell and programming language.23:18
kfox1111yeah. I have really mixed feelings about power shell.23:19
kfox1111it has some really cool features, above and beyond bash.23:19
sbezverknever used it, but something tells me it is not as good as bash23:19
kfox1111and some really uglys. :)23:19
kfox1111since it uses .net,23:19
kfox1111its pipes are actually more powerful then bash.23:19
kfox1111in bash, everythings a file stream.23:19
kfox1111in power shell, they are data types, so you can push more complicated things through much faster.23:19
kfox1111tehy actually learned a thing or two from unix rather then just igorning it for once.23:20
sbezverknice to hear that microsoft is still capable to learn from others23:21
kfox1111they aren't what they use to be.23:22
kfox1111they sell a lot of linux now.23:22
kfox1111linux broke their monopoly.23:22
sbezverkhave you tried docker on windows?23:22
kfox1111no.23:22
kfox1111don't realy want to get locked into that. :)23:22
kfox1111but glad they are trying to adapt to the modern world. :)23:22
kfox1111and its good to see them play catch up rather then the open source community trying to play catch up all the time. :)23:23
sdakesbezverk what is $1 in your 1 liner?23:23
sbezverksdake: pvc name23:23
*** bmaltais has quit IRC23:24
kfox1111its the first column of the input data.23:25
kfox1111by default, space delimited.23:25
sbezverksdake: it is also specific to awk, not to confuse with bash parameters23:25
kfox1111dudes.....23:26
kfox1111https://review.openstack.org/#/c/454841/23:26
kfox1111working v4 ceph multi gate ! :)23:26
inc0yay kfox111123:26
sbezverkkfox1111: yeah!!!23:26
inc0I'll prep ansible play to setup disks and such for ceph23:27
inc0we could use it in k8s gates too23:27
kfox1111inc0: why the big push to take existing working bash and rewrite in ansible?23:27
sbezverkkfox1111: what was final change to fix authentication?23:27
kfox1111so... should we merge the ps even though it doesn't do helm-compute and helm-entrypoint v4 yet, or wait for those?23:28
kfox1111sbezverk: it was uploading the nova key in the cinder name by mistake.23:28
kfox1111and v2/3 was always using the nova name, not cinder.23:28
kfox1111v4 always used "cinder" for the user name.23:28
sdake[admin@falkor-node0 oscore]$ kubectl get pvc -n kolla | grep Bound | cut -f1-2 -d ' ' | xargs -i kubectl get pv -n kolla -o jsonpath={.spec.volumeName} {}23:29
sdakeError from server (NotFound): persistentvolumes "glance " not found23:29
sdakeError from server (NotFound): persistentvolumes "mariadb " not found23:29
sdakeError from server (NotFound): persistentvolumes "rabbitmq " not found23:29
inc0kfox1111: well, I'm just writing it from scrach in kolla-ans23:29
sbezverksdake: because you deleted them before23:29
inc0if you don't think it's worth taking, fair enough23:29
inc0:)23:29
kfox1111inc0: yeah. I know. something we like to do a lot. :/23:29
sdakesbezverk the pvs are still rpesent23:29
sdakesbezverk the extra space is the problem23:29
inc0kfox1111: I need to write it from scratch anyway23:30
kfox1111why?23:30
inc0and orchiestrating these things with ansible instead of ssh to node and do it just seems simpler23:30
sbezverksdake: why you run kubectl get pv?????23:30
sdakekfox1111 i have no interest in rewriting  all the gates in ansible23:30
inc0well, I'll copy code from k8s ofc23:30
sbezverkcheck the command I pasted23:30
inc0but execute it with ansible so I won't need to ssh to other nodes23:30
sdakesbezverk will check - ltitle faded today because of knee23:30
kfox1111inc0: I thinhk we can just take the script and wrap it up in a container.23:30
sdakekfox1111 i am not keen to wrap the gate scripts in a container - however23:31
kfox1111I'd much prefer stuff running in k8s rather then needing to install stuff on the system like ansible.23:31
sdake[admin@falkor-node0 oscore]$ kubectl get pvc -n kolla | grep Bound | cut -f1-2 -d ' ' | xargs -i kubectl get pvc -n kolla -o jsonpath={.spec.volumeName} {}23:31
sdakeError from server (NotFound): persistentvolumeclaims "glance " not found23:31
sdakeError from server (NotFound): persistentvolumeclaims "mariadb " not found23:31
sdakeError from server (NotFound): persistentvolumeclaims "rabbitmq " not found23:31
sbezverkalso people use bits from gate to do their stuff23:31
sdakekfox1111 the ansible is being wrapped in a container23:31
inc0well just to be fair, ansible needs only to be installed on deploy node;)23:31
sbezverkif gates are re-written in ansible23:32
sbezverkthen it becomes dependency for other people23:32
sdakei am not rewriting gates in ansibe23:32
sdakei am writing two workflows23:32
kfox1111inc0: I want to be able to deploy with just helm.23:32
inc0I'm nto rewritting gates in ansible too23:32
sdake(just to be clear on the objective of my work)23:32
*** kbaegis1 has quit IRC23:32
*** kbaegis has joined #openstack-kolla23:32
sbezverkthen let's not replace what we already have, but ADD to it23:32
sdakekfox1111 i think deploying just with helm is a good objective - although requires serious ehavy lifting23:33
sdakesbezverk who said anytihng about replacing?23:33
sdakesbezverk i am adding here - not deleting stuff23:33
sdakesbezverk (unless your tlaking to inc)23:33
kfox1111the balancing act is, if we don't test it in gate, it breaks a lot.23:33
kfox1111but its alot of work, of unknown real benifit rewriting it all in ansible.23:33
sdakeyes, which is why i've spent the week writing the gate tests for destroy23:33
sbezverksdake: inc0 mentioned replacing ceph prep bits23:33
inc0but this https://review.openstack.org/#/c/466007/44/tests/templates/globals-default.j2 is much more tidy than this https://github.com/openstack/kolla-ansible/blob/master/tools/deploy_aio.sh#L80-L9423:33
inc0sbezverk: in kolla-ansible23:33
vhosakotFriday past 7:30pm here in Boston area, going for beer, peace pals!  go for a beer and do it on Monday ;)23:34
*** harlowja has quit IRC23:34
sbezverkinc0: Oh I am sorry, I thought you meant in k8s gates23:34
inc0noo23:34
kfox1111inc0: I don't see them too different. its just what your use to reading. ansible or shell.23:34
inc0I just said since I'm writing whole slew of plays23:34
kfox1111inc0: I guess, if you write gate tests for them, then I don't really care too much.23:35
kfox1111I just don't want to have to keep worrying about what I'm breaking when I code stuff in gate.23:35
inc0np, well, just sayin'23:35
kfox1111I want to know what I'm breaking so I can fix it. :)23:36
*** vhosakot has quit IRC23:36
inc0in ansible next step would be to automatically pick config/additional logic per scenerio23:36
sbezverkkfox1111: Have you heard anything about Docker Swarm becoming more popular then k8s? I took a training and the instructor was trying to convience me that it is world wide case :)23:37
*** iniazi_ has joined #openstack-kolla23:38
kfox1111its a shell game.23:38
kfox1111since docker swarm is now called "docker",23:38
kfox1111and users only know to ask for "docker" historically,23:38
sdakesbezverk pretty sure that instructor was high on crack23:38
kfox1111they are playing "statistics" and saying people are asking for docker swarm.23:39
kfox1111(and most of the instructors are hired by docker inc ;)23:39
kfox1111https://trends.google.com/trends/explore?q=kubernetes,docker%20swarm,mesos23:39
sbezverkkfox1111: :) he must be ex docker23:39
kfox1111for a slightlyl less biased answer.23:40
*** iniazi has quit IRC23:40
kfox1111yeah. they tried to do the same to us here for "docker training"23:40
sdakewhat is wrong with this bash: [admin@falkor-node0 oscore]$ kubectl get pvc -n kolla | grep Bound | awk 'print { $1 }'23:40
sdakeawk: cmd. line:1: print { $1 }23:40
sdakeawk: cmd. line:1: ^ syntax error23:40
kfox1111mostly that means " docker inc training"23:40
kfox1111sdake:23:40
kfox1111awk '{print $1}'23:40
sdakethanks23:41
sdakei guess i need to go to bed :)23:41
kfox1111np.23:41
sdakevictory:23:42
sdake[admin@falkor-node0 oscore]$ kubectl get pvc -n kolla | grep Bound | awk '{print $1}' | xargs -i kubectl get pvc -n kolla -o jsonpath={.spec.volumeName} {}23:42
sdakeglancemariadbrabbitmq[admin@falkor-node0 oscore]$23:42
kfox1111cool.23:43
*** rwellum has quit IRC23:43
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: v4 gate.  https://review.openstack.org/45484123:44
kfox1111ok. this one should be good to go. :)23:44
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Kevins' line of debug  https://review.openstack.org/46640823:45
sdakekfox1111 i hope mine is ready to go too :)23:46
*** zul has joined #openstack-kolla23:46
sbezverkkfox1111: other 2 V4 gates do not use the same ceph that is why they are failing, or those are different issues?23:46
kfox1111sbezverk: they need cell0 stuff integrated into the service charts.23:47
kfox1111shouldn't be too hard, but extra work.23:47
sbezverkkfox1111: ahhh cell0, I was starting to forget about it ;)23:47
kfox1111sorry to remind you. ;)23:47
sbezverkkfox1111: yeah it is like a wound ;)23:48
sdakeya cells - pretty much drives me batty23:48
kfox1111especially bad when they dont really work with more then cell1.23:49
kfox1111a lot of extra work with 0 possible benifit. :/23:49
sbezverkkfox1111: they will figure it out around 'z' time frame ;)23:50
kfox1111heh. I know, right? :/23:52
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Add a destroy workflow for kolla-kubernetes  https://review.openstack.org/46403123:52
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Add a destroy workflow for kolla-kubernetes  https://review.openstack.org/46403123:54
inc0ok, I'm calling a Friday too23:55
inc0have a good weekend everyone23:55
kfox1111you too. :)23:55

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!