Thursday, 2016-03-31

vhosakotJeffrey4l_: sdake corrected it.. check like 62 in PS 8   https://review.openstack.org/#/c/298479/8/docker/kolla-toolbox/Dockerfile.j200:03
Jeffrey4l_vhosakot, saw that, thanks.00:03
vhosakotcool.. np...00:03
sdakeatleat we have a low count of triaged bugs00:03
sdakeeverything is either confirmed or in progress00:04
vhosakotas far as I know, haproxy is the only container running as root, and I am working on dropping it00:05
sdakeswift00:06
sdakehaproxy cannot drop root00:06
manjeetssdake is horizon logging centralized with kolla ?00:08
manjeetsI mean can i find all in just one horizon.log ?00:08
sdakeyup if you enable_central_looggin:yes00:08
manjeetsoke00:08
manjeetswhere do i enable that ?00:08
manjeetswhich file ?00:08
sdakeut it will be stored on the controller nodes in the heka container as well00:08
*** salv-orl_ has quit IRC00:09
sdakeenable_central_logging is hard to use because we lack a kibana dashboard for it00:09
sdakejust use the heka container on the controller node00:09
sdakedocker exec heka cat /var/log/kolla/horizon/*00:09
sdakenote horizon changes are either in flight or just recently landed00:09
sdakeso your code may not have them in it atm00:09
*** jtriley has joined #openstack-kolla00:10
gmmahasdake: vhosakot: once the containers are created, should libvirtd start in the host?00:12
*** rajathagasthya has quit IRC00:14
Jeffrey4l_gmmaha, libvirtd is ran in the docker too and the ansible will start it automatically.00:18
gmmahaJeffrey4l_: on the host as well?00:19
gmmahaJust checking.. cause all this while i was beating to get it removed from the system00:19
Jeffrey4l_gmmaha, in a container.00:19
Jeffrey4l_yea. you need remove the libvirt in the host.00:19
gmmahaJeffrey4l_: aah ok.. Yeah then something is wrong..00:20
gmmahai removed it from the host and post deploy i see libvirtd running on the host00:20
gmmaha:|00:20
Jeffrey4l_gmmaha, that is not happend. can u make sure is there a container named nova_libvirt?00:21
gmmahaJeffrey4l_: yeah it is there..00:22
gmmahaand ight after i remove the containers the livirtd --listen process is gone :O00:22
gmmaha:(00:22
Jeffrey4l_gmmaha, that's right. why u remove the container00:22
*** diogogmt has joined #openstack-kolla00:22
gmmahaJeffrey4l_: the deployment failed..00:22
gmmahawhen it gets to rabbitmq00:23
openstackgerritMerged openstack/kolla: Update swift name  https://review.openstack.org/29935100:23
Jeffrey4l_please post the config file and deploy log.00:23
gmmahahttp://paste.openstack.org/show/492520/00:23
vhosakotgmmaha: correct.. libvirt must not be running on the compute host... it will run inside the nova_libvirt container...00:23
vhosakotgmmaha: can you do        docker exec nova_libvirt ps aux | grep libvirt00:23
gmmahavhosakot: just cleaned up the container..00:24
gmmahavhosakot: but the libvirtd --listen process is runnin gon the host00:24
gmmahaand thats right after all the nova containers are deployed00:24
vhosakotthe is te same process inside the nova_libvirt container.. the PID matches both inside the cotnainer and on host00:25
gmmahavhosakot: aaah00:25
*** jtriley has quit IRC00:25
gmmahahmm00:25
vhosakotthat is fine and expected00:25
gmmahaOk..00:25
gmmahabut then the deployment is failing for sure00:25
* gmmaha goes to disable heat and see if that works00:25
*** jtriley has joined #openstack-kolla00:26
gmmahavhosakot: youa re right..00:32
gmmahaits the same PID00:32
vhosakotyep.. that is fine.. not an issue00:32
vhosakotann processes inside container have same PID on host00:33
vhosakotthe way docker setups process tables I think00:33
gmmahavhosakot: aah ok..00:33
gmmahai ned to read up on docker more00:33
*** sdake has quit IRC00:34
*** weiyu_ has joined #openstack-kolla00:34
ccesario_hey, someone did run deploy from master branch  today ?00:35
gmmahaccesario_: are you hitting with it?00:36
*** sdake has joined #openstack-kolla00:36
gmmahai am seeing these errors.. http://paste.openstack.org/show/492520/00:36
*** Jeffrey4l_ has quit IRC00:38
ccesario_I'm just update my local rep  cleanup all nodes and try deploy .... I 'm getting problem on maridb task00:38
*** achanda has quit IRC00:41
ccesario_gmmaha: checking the error00:42
gmmahaccesario_: thanks00:42
*** asalkeld_ has quit IRC00:45
*** rhallisey has quit IRC00:45
ccesario_http://sprunge.us/RTHO?debug  my error it s different..... generic error.....00:45
*** Marga_ has quit IRC00:48
openstackgerritHui Kang proposed openstack/kolla: Add Kuryr ansible role  https://review.openstack.org/29889400:50
*** dave-mccowan has quit IRC00:53
*** banix has quit IRC00:55
*** dave-mccowan has joined #openstack-kolla00:58
*** banix has joined #openstack-kolla00:59
gmmahavhosakot: its not the latest master.. My deployments even with previous code where they worked is halting now with the same error..01:00
vhosakotlibvirt permission error ?01:01
gmmahavhosakot: no.. libvirt is fine now01:01
gmmahabut this. http://paste.openstack.org/show/492520/01:01
gmmahavhosakot: https://github.com/openstack/kolla/blob/master/ansible/site.yml#L13301:02
gmmahaat that spot01:02
* manjeets just built 2000 vms01:04
* manjeets crosses fingers01:05
ccesario_manjeets: O_o01:07
* manjeets sees 600 active so and 0 with error status01:08
manjeetsso far8801:08
sdakegmmaha i am avaialble again for 1:1 debug01:11
sdakemanjeets did the2000 vms produce useful data01:12
sdakesuch as highwter mark on database connectivity01:12
manjeetson did not see more than 1600 connections01:13
manjeetsrunning a watch on connection list01:13
gmmahasdake: sweet.. let me start it again and send you an invite01:13
gmmahagive me 201:13
sdakehow long id it take to deploy 2000 vms01:14
sdakegmmaha give me a few too01:15
ccesario_vhosakot: https://bugs.launchpad.net/kolla/+bug/1563506 it is extremly important .... without it the generic error is reported ... http://paste.openstack.org/show/492524/01:15
openstackLaunchpad bug 1563506 in kolla "prechecks must check empty passwords in /etc/kolla/passwords.yml" [Undecided,In progress] - Assigned to Vikram Hosakote (vhosakot)01:15
manjeets23 minutes still counting01:15
sdakei am setting up my daugther's computer01:15
manjeetsnova list is not showing me more than 110001:16
manjeetsgood news is 1100 are active but 900 missing01:16
manjeetshorizon is back to business viewing 100 per page01:17
manjeetssdake i delete 100 vms 3 4 times01:25
manjeetsdatabase still shows 100001:25
manjeetsfeels like 2000 were active somehow database is enable to show all at once01:25
sdakesounds like a hard limit somewhere01:25
sdakeook at the hpervisor tab in horizon01:25
manjeetshorizon is on and off nova list is nicer than horizon01:26
manjeetssdake may be tomorrow need to figure out multiple ip issue that still exists for some vms01:27
manjeetsbarely 5 or 10 out of 1000 have that problem01:27
kklimondamanjeets: what storage do you use for spawning them?01:28
manjeetsstorage ?01:28
manjeetsu mean storage driver ?01:28
kklimondayeah, underlying storage for VM images01:28
manjeetsi choose one of default flavors01:28
manjeetsm1.tiny01:29
kklimondaI remember spawning ~1k VMs while testing, and quite a few of them unable to boot, due to I/O starvation01:29
manjeetsi saw active status of all of them01:30
manjeetsactually i deleted 400 vms it still shows 1000 active no error 600 are lost01:31
manjeetsnova list | grep ACTIVE | wc -l01:31
manjeets100001:31
*** weiyu_ has quit IRC01:33
openstackgerritDave McCowan proposed openstack/kolla: When two interfaces are used for two VIPs, tie them together  https://review.openstack.org/29970401:33
manjeetssdake i see on average 32 instances per compute node01:34
openstackgerritJeffrey Zhang proposed openstack/kolla: Fix gate by adding MariaDB-shared dependnecy  https://review.openstack.org/29968101:34
manjeetsfor 53 computes01:34
manjeetsthat means more than 1700 vms and nova list grep error gives me 001:34
manjeetsneed to figure where 600 or 700 are hiding01:35
vhosakotccesario_: yes, I am working on flagging an error if kolla is run with all empty passwords.. will keep upi psted01:37
*** weiyu has joined #openstack-kolla01:38
sdakemanjeets i think you could be running into another quota01:38
ccesario_vhosakot: and if this check was added into kolla-genpw ?01:39
sdakemanjeets nm i see what you mean01:39
sdakeyou see 32 qemu processes01:39
vhosakotccesario_: no,, I am adding a precehck01:40
vhosakotccesario_: run kolla-genpwd to resolve errors due to empty passwords01:41
*** weiyu has quit IRC01:41
*** achanda has joined #openstack-kolla01:41
ccesario_vhosakot: yes yes .. I meant this.... but kolla-genpwd check if is empty and then precheck call kolla-genpwd --check :P01:42
vhosakotccesario_: hmmm... dont know if kolla-genpwd should be automated... I think operators must know what passwrods they set for which service and also if they use a random-generator like kolla-genpwd...01:45
vhosakotlet us now force/automate passwords that operators want :)  right ?  :)01:46
*** achanda has quit IRC01:46
ccesario_vhosakot: yes yes I agree..... but think about.. If the operator run kolla-genpwd, and deploy ... and after that he run again (unintentionally) it overwrite the passwords ... it can cause a big problem for operator :P01:48
*** sdake_ has joined #openstack-kolla01:49
ccesario_vhosakot: ohhh ignore my comment....01:49
*** Marga_ has joined #openstack-kolla01:49
ccesario_double kolla-genpw does not overwrite the pass :P01:50
vhosakotyep :)01:50
vhosakotthat is what I meant01:50
vhosakot:)01:50
*** sdake has quit IRC01:50
ccesario_vhosakot: sorry :)01:50
vhosakotcool, np01:50
vhosakotbbiab 30 mins01:50
*** vhosakot has quit IRC01:51
*** Marga_ has quit IRC01:54
*** achanda has joined #openstack-kolla01:56
*** weiyu has joined #openstack-kolla01:59
*** unicell1 has quit IRC02:02
*** Marga_ has joined #openstack-kolla02:10
*** Marga_ has quit IRC02:14
*** banix has quit IRC02:16
*** Jeffrey4l has joined #openstack-kolla02:17
Jeffrey4lvhosakot, pls stop using `recheck` on the mitaka branch. the gate is broken. recheck is not helpful.02:20
Jeffrey4lvhosakot, when this https://review.openstack.org/299681 is merged, the gate will be fixed.02:20
*** tfukushima has joined #openstack-kolla02:21
*** salv-orlando has joined #openstack-kolla02:21
*** alisonh has quit IRC02:21
ccesario_gmmaha: only to keep you notfied .... y deployment it is working ... the problem it was empty passwords :P02:26
gmmahaccesario_: thanks.. :)02:26
gmmahaguessing i am a special breed with toooo many ways of destroying kolla.. :P02:26
ccesario_gmmaha: any news in your deployment ?02:27
*** salv-orlando has quit IRC02:32
*** salv-orlando has joined #openstack-kolla02:36
*** alisonh has joined #openstack-kolla02:39
*** alisonh has quit IRC02:44
*** Marga_ has joined #openstack-kolla02:48
*** alisonh has joined #openstack-kolla02:50
*** salv-orlando has quit IRC02:52
*** Marga_ has quit IRC02:53
*** tfukushima has quit IRC02:59
*** ccesario_ has quit IRC03:03
*** achanda has quit IRC03:03
*** sdake has joined #openstack-kolla03:07
*** Marga_ has joined #openstack-kolla03:07
*** Marga_ has quit IRC03:07
*** Marga_ has joined #openstack-kolla03:08
*** Marga_ has quit IRC03:08
*** weiyu has quit IRC03:08
*** Marga_ has joined #openstack-kolla03:09
*** weiyu has joined #openstack-kolla03:09
*** sdake_ has quit IRC03:10
*** yuanying has quit IRC03:21
*** jeblair_ has joined #openstack-kolla03:27
sdakeJeffrey4l ping03:28
Jeffrey4lsdake, pong03:28
sdakeneutron problem03:28
*** vhosakot has joined #openstack-kolla03:28
sdakecomplains aout incorrect json format03:28
Jeffrey4lsdake, neutron reconfigure?03:28
sdakenot reconfigure deploy03:28
vhosakotevening03:29
sdakethere was a workaround in the bug log03:29
sdakehey vhosakot03:29
sdakei dont knwo where the bug log is03:29
Jeffrey4lsdake, could you paste the log out?03:29
sdakeit involved moving something in site.yml03:29
Jeffrey4lsdake, I haven't meet that when deploy multi node.03:29
sdakedoes tht ring a bell?03:29
Jeffrey4lso logs will be helpful.03:29
sdakeJeffrey4l can you join a google hangout03:29
Jeffrey4lnp03:30
Jeffrey4llink?03:30
vhosakotI remmeber reordering hosts in multinode inventory to work-around Ansible 1.9.4 bug.. is that what you're talking about sdake03:30
Jeffrey4lbtw, fyi the neutron reconfigure is buggy, which i am working on it.03:30
sdakevhosakot yes link on the bug needed plz03:30
Jeffrey4lvhosakot, maybe.03:30
vhosakotI'd like to join google hangout too03:30
vhosakotwell, ccesario or mlima submitted a PS for that, and Sam ask to abandon it.. let me search.. 1 sec03:31
sdakeits broken it needs fixing i dont care how03:31
sdakei thin kthe problem is its a global variable03:31
sdakeJeffrey4l doe register prodce globals or locals?03:31
Jeffrey4lgmmaha, sent the link to me03:31
gmmahaJeffrey4l: hey yeah03:32
*** jeblair has quit IRC03:32
*** serverascode has quit IRC03:33
*** tfukushima has joined #openstack-kolla03:34
*** Jeffrey4l_ has joined #openstack-kolla03:34
Jeffrey4l_sdake, whats mean by 'doe register prodce globals or locals'03:35
sdakeregister: xyz03:35
sdakedoes that produce a global03:35
sdakeor a local to the role03:35
sdakebecause we have alot of register; database operations03:35
*** jtriley has quit IRC03:37
vhosakothttps://review.openstack.org/#/c/285408/103:37
*** Jeffrey4l has quit IRC03:37
*** coolsvap has joined #openstack-kolla03:38
*** serverascode has joined #openstack-kolla03:38
vhosakothttps://bugs.launchpad.net/kolla/+bug/154678903:38
openstackLaunchpad bug 1546789 in kolla mitaka "neutron failed to deploy in a multi-node deployment" [High,Confirmed] - Assigned to Michał Jastrzębski (inc007)03:38
sdakehttp://eavesdrop.openstack.org/irclogs/%23kolla/%23kolla.2016-03-11.log.html#t2016-03-11T19:56:3903:38
Jeffrey4l_sdake, sorry still do not get your point. I know the register stuff now. whats means by `global or a local to the role`03:43
vhosakothttps://github.com/openstack/kolla/blob/master/ansible/roles/neutron/tasks/bootstrap.yml#L1403:51
*** salv-orlando has joined #openstack-kolla03:52
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/kolla: Update swift name  https://review.openstack.org/29973603:52
*** salv-orlando has quit IRC03:55
dave-mccowanmy deploy is failing on image does not exist for centos-binary-cron.  has anyone else seen this?04:01
*** achanda has joined #openstack-kolla04:04
*** yuanying has joined #openstack-kolla04:07
*** achanda has quit IRC04:09
*** achanda has joined #openstack-kolla04:09
Jeffrey4l_dave-mccowan, pull the latest code and rebuild the code. then try deploy again.04:09
dave-mccowanJeffrey4l_ thanks.  i figured it out.  i forgot to specify my local registry when i did the build.04:10
vhosakotgroups['neutron-server']04:18
*** salv-orlando has joined #openstack-kolla04:19
Jeffrey4l_vhosakot, sorry , i can not speak in the hangout. but could you post the multinode inventory and ansible run result out?04:19
vhosakotJeffrey4l_: sure, I will.. 1 sec04:21
Jeffrey4l_vhosakot, thanks.04:22
*** salv-orlando has quit IRC04:23
*** sdake_ has joined #openstack-kolla04:28
gmmahawhen: inventory_hostname == neutron-server[0]04:30
sdake_my a dio no beuno04:30
sdake_why not and all three variables04:30
sdake_is there a way to do such a thing04:30
*** sdake has quit IRC04:30
sdake_AND04:30
sdake_andthe sets04:30
sdake_we tried in04:32
sdake_bu we didn't try ==04:32
sdake_dont use in04:32
sdake_use ==04:32
sdake_wtb buy working audio04:33
sdake_because that could break something else04:33
sdake_if delegate_to is broken we need to nuke it04:34
*** Jeffrey4l_ has quit IRC04:34
gmmahasdake_: you are showing as on mute :)04:35
sdake_lets try == now tho beuseits multinode04:35
*** weiyu has quit IRC04:37
gmmahahttps://github.com/ansible/ansible/issues/1468404:41
gmmahahttps://github.com/ansible/ansible/pull/1502404:41
sdake_run once means i runs only one time ever04:47
sdake_bootstrap only runs once ever04:47
sdake_otherwise its skipped04:47
sdake_sorry my adio is bad04:48
gmmahahttps://github.com/ansible/ansible/issues/1322604:48
sdake_i would highly recommend anding the 3 variables04:48
sdake_i think that would work04:48
sdake_becasue its not == and not in04:48
vhosakothttps://www.elmund.io/configuration%20management/2015/07/23/ansible-delegate_to-and-variables/04:49
sdake_== = in04:49
sdake_anding the 3 lists will produce 1 item04:50
sdake_[a,b,c] & [a] & [a] = a04:50
sdake_i can hear but cant speak04:50
sdake_if that can be done in ansible its a different syntax04:51
sdake_and might avoid the problem04:51
sdake_because debug works with the printing the 3 variables04:51
sdake_i dont now the syntax04:52
sdake_yes right04:52
sdake_but it will produce th correct variable without indexing ;)04:52
sdake_and without = nor in04:52
sdake_git diff04:53
sdake_real quick04:53
sdake_whatever was in th edebug ;)04:53
sdake_i dont no wif that is correct syntax04:54
sdake_and the sets04:55
sdake_and the sets04:55
sdake_not and in boolean04:55
sdake_dont treat it like a bollean treat it like a set04:55
openstackgerritDave McCowan proposed openstack/kolla: When two interfaces are used for two VIPs, tie them together  https://review.openstack.org/29970404:56
sdake_ok thorw that one out04:56
sdake_no in04:56
sdake_dont use in04:56
sdake_it needs to get a set and04:56
sdake_no dont try that04:56
sdake_wait just a sec04:56
sdake_['a,b,c']&['a','b'] = [a,b]04:57
sdake_this is a set and04:57
sdake_we need a set and not a boolean and04:57
*** bigjools has joined #openstack-kolla05:04
*** bigjools has left #openstack-kolla05:05
*** asalkeld_ has joined #openstack-kolla05:07
*** dave-mccowan has quit IRC05:13
*** sdake_ is now known as sdake05:14
*** coolsvap has quit IRC05:17
*** coolsvap has joined #openstack-kolla05:17
*** unicell has joined #openstack-kolla05:23
*** salv-orlando has joined #openstack-kolla05:23
*** coolsvap has quit IRC05:26
*** salv-orlando has quit IRC05:28
gmmahahttps://bugs.launchpad.net/kolla/+bug/154678905:28
openstackLaunchpad bug 1546789 in kolla mitaka "neutron failed to deploy in a multi-node deployment" [High,Confirmed] - Assigned to Michał Jastrzębski (inc007)05:28
vhosakothttps://bugs.launchpad.net/kolla/+bug/154678905:29
*** coolsvap has joined #openstack-kolla05:32
*** Jeffrey4l_ has joined #openstack-kolla05:39
sdakehttp://docs.ansible.com/ansible/playbooks_delegation.html#run-once05:43
*** daneyon_ has joined #openstack-kolla05:53
*** weiyu has joined #openstack-kolla05:53
*** Jeffrey4l_ has quit IRC05:54
*** daneyon_ has quit IRC05:58
*** unicell has quit IRC06:16
*** weiyu has quit IRC06:17
*** unicell has joined #openstack-kolla06:17
*** vhosakot has quit IRC06:18
*** mikelk has joined #openstack-kolla06:21
*** allen_gao has joined #openstack-kolla06:24
*** jiriprox has quit IRC06:24
*** SiRiuS_ has joined #openstack-kolla06:28
*** mikelk has quit IRC06:29
*** mikelk has joined #openstack-kolla06:34
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/kolla: Fix gate by adding MariaDB-shared dependnecy  https://review.openstack.org/29968106:35
*** sdake_ has joined #openstack-kolla06:37
*** sdake has quit IRC06:40
*** weiyu has joined #openstack-kolla06:41
openstackgerritMerged openstack/kolla: Revert libvirt change in heka-openstack.toml.j2 in master  https://review.openstack.org/29664906:43
*** sdake has joined #openstack-kolla06:45
coolsvapsdake: you wanted to do Workflow +1 or -1 for the keystone change set?06:46
*** salv-orlando has joined #openstack-kolla06:48
*** sdake_ has quit IRC06:48
sdakeworkflow -106:49
sdakedid I do =1?06:49
sdake=etired06:50
*** salv-orlando has quit IRC06:51
*** Serlex has joined #openstack-kolla07:15
*** coolsvap has quit IRC07:28
*** coolsvap has joined #openstack-kolla07:29
*** wuhg has joined #openstack-kolla07:38
*** coolsvap has quit IRC07:39
*** coolsvap has joined #openstack-kolla07:42
openstackgerritSteven Dake proposed openstack/kolla: Increase database connections to 10000  https://review.openstack.org/29979107:42
*** shardy has joined #openstack-kolla07:48
sdakehey shardy07:49
*** mgoddard has joined #openstack-kolla07:50
coolsvapwe need the sudo -E and mariadb-shared changes merged for the stable/mitaka gate07:58
*** mbound has joined #openstack-kolla07:59
*** cristicalin has joined #openstack-kolla07:59
*** salv-orlando has joined #openstack-kolla08:07
sdakecoolsvap yup08:09
sdakecoolsvap i'm pretty sure they have been cherrypicked08:09
*** salv-orlando has quit IRC08:09
coolsvapsdake: yes08:10
sdakeasalkeld if your around to approv08:10
sdakeor nihilifer08:10
sdakeor pbourke08:11
openstackgerritSteven Dake proposed openstack/kolla: [WIP] Workaround ansible bug related to delegate_to  https://review.openstack.org/29980308:11
*** kproskurin has joined #openstack-kolla08:12
coolsvaphttps://review.openstack.org/#/c/299681 and  https://review.openstack.org/#/c/29968108:12
coolsvappbourke: nihilifer asalkeld ^^08:12
*** stvnoyes has joined #openstack-kolla08:13
*** sdake_ has joined #openstack-kolla08:17
SiRiuS_kproskurin, ping08:18
*** sdake has quit IRC08:19
kproskurinSiRiuS_: Hi!08:20
SiRiuS_kproskurin, Hi :), so I tried deploying, and something is just weird08:20
kproskurin:-D08:20
kproskurinSiRiuS_: Make sure you use latest master, we fixed like 2-3 bugs yesterday btw and still fixing08:21
SiRiuS_kproskurin, http://paste.openstack.org/show/492541/08:21
SiRiuS_kproskurin, I cherrypicked everything :)08:22
*** sdake has joined #openstack-kolla08:22
SiRiuS_it says all the apps are started08:22
SiRiuS_but sometime I only get kolla_toolbox08:22
SiRiuS_sometimes I get nothing08:23
kproskurinSiRiuS_: Open marathon UI and go into mariadb container for example08:23
kproskurinOpen configuration and paste it to me08:23
*** sdake_ has quit IRC08:24
SiRiuS_kproskurin, checking08:25
SiRiuS_kproskurin, all the apps appear to be suspended08:25
SiRiuS_21 suspended08:25
kproskurinI belive you still could get configuration from an app08:26
kproskurinCould you?08:26
*** achanda has quit IRC08:30
SiRiuS_kproskurin, http://paste.openstack.org/show/492543/08:31
SiRiuS_is there a better way to paste the config from the web page?08:32
kproskurinSiRiuS_, Alright, so we need to check few things. 1) "image": "operator.local:5000/kollaglue/centos-source-mariadb:2.0.0" - is this a right path to your docker registry and image?08:32
SiRiuS_yes08:33
*** achanda has joined #openstack-kolla08:34
*** daneyon_ has joined #openstack-kolla08:35
kproskurinSiRiuS_: 2) Could you exec into your mesos-slave container on this host and check something like “ps axuf” and look for “--attributes=openstack_role:controller”08:36
*** mbound has quit IRC08:38
*** daneyon_ has quit IRC08:39
SiRiuS_kproskurin, if I run ps aux inside mesos_slave container on controller01, I don't see “--attributes=openstack_role:controller”08:41
SiRiuS_root        25  0.0  0.1  13372  2020 ?        S    08:39   0:00 -bash08:41
SiRiuS_root        41  0.0  0.0  49016  1704 ?        R+   08:40   0:00  \_ ps axuf08:41
SiRiuS_root         1  0.1  1.0 949136 19160 ?        Ssl+ 08:12   0:03 mesos-slave08:41
kproskurinoh, we pass it via envs, 1 sec08:42
kproskurinSiRiuS_: exec: “env | grep MESOS_ATTRIBUTES”08:43
kproskurininside the container08:43
SiRiuS_kproskurin, quick question: does the IP address for the mesos host inside the kolla-mesos.conf file need to be the leader? because I have it set to the master03 node, and now the leader is master0108:43
*** pbourke has quit IRC08:43
*** pbourke has joined #openstack-kolla08:44
kproskurinSiRiuS_: mesos slaver do an election of their own and chose leader08:44
*** sbezverk has quit IRC08:44
*** sbezverk has joined #openstack-kolla08:44
kproskurinBut the redirect all calls  to current leader, no matter to which mesos you are connected, so dont worry08:44
*** jiriprox has joined #openstack-kolla08:46
SiRiuS_kproskurin, I did not find the attributes in the environment08:46
SiRiuS_kproskurin, this is all I have08:46
SiRiuS_kproskurin, http://paste.openstack.org/show/492545/08:46
*** cristicalin has quit IRC08:47
*** achanda has quit IRC08:48
kproskurinSiRiuS_, Im confused. :-( Sadly I dont use this ansible mesos stack myself right now, but it clearly set a lot of stuff via envs: https://github.com/openstack/kolla-mesos/blob/master/ansible/roles/mesos-slave/tasks/start.yml08:48
SiRiuS_kproskurin, the thing is, sometimes it starts some containers, sometimes it does not start any at all08:49
SiRiuS_without doing anything to the config08:49
*** achanda has joined #openstack-kolla08:49
kproskurinSiRiuS_: last one thing to check is resourses avalible08:50
kproskurinhttps://www.dropbox.com/s/g9jlaiay3nflvwa/HW.png?dl=008:50
kproskurinIt will loke something like this ^^08:50
kproskurinRAM and CPU08:50
kproskurinTo check how much does your mesos-slave have you need to go to “http://mesos-master-ip:5050/#/slaves”08:51
kproskurinand if it has less that marathon expect - it will not run any apps08:52
*** achanda has quit IRC08:52
SiRiuS_kproskurin, it says I have 4 slaves (which I do)08:53
SiRiuS_7 CPUs08:53
SiRiuS_3.6GB ram08:53
SiRiuS_used 0 CPUs08:54
kproskurinSiRiuS_: compare it with marathon expectations from marathon UI08:54
SiRiuS_used 0 ram08:54
SiRiuS_kproskurin, in marathon it appear to be 0.0 CPU and O B ram08:54
SiRiuS_hmm08:54
kproskurinOh, I see08:55
kproskurinSo, my bet it’s a attributes problem08:55
kproskurinAttributes is not set and marathon dont know to which mesos it should pass the app, since it expects this constrains. And kolla-toolbox is a chronos job, which dont use constrains yet, so it works08:56
SiRiuS_kproskurin, funny thing is, I cleaned everything up, I deployed the mesos cluster again, and deployed the apps again, and this time I don't even have kolla_toolbox running :D08:57
kproskurinCould be a chronos problem, but it’s not the main case right now.Im thinking how to check attributes…08:58
*** achanda has joined #openstack-kolla08:59
nihiliferare they obstackles to get this one merged, except the failing gate? https://review.openstack.org/#/c/297517/09:01
nihiliferi see that two +2 were given some time ago09:01
nihiliferjust wondering whether it needs more cores or discussion09:01
SiRiuS_kproskurin,09:01
SiRiuS_kproskurin, http://paste.fedoraproject.org/347780/4148911409:01
SiRiuS_kproskurin, http://paste.fedoraproject.org/347782/5941492809:02
SiRiuS_kproskurin, that's how my config files look like09:02
kproskurinSiRiuS_: looks ok09:02
kproskurinnihilifer: Do you remember mesos url to check attributes? :-)09:03
kproskurinFiund it09:04
kproskurinSiRiuS_: http://mesos-master-ip:5050/state09:04
nihilifer:5050/slaves09:04
nihiliferor if it doesn't work, then :5050/state.json09:04
kproskurinYeah, slaves are better09:04
kproskurinSiRiuS_: ^^09:04
SiRiuS_kproskurin, I've just cleaned up and redeployed the mesos cluster, but did not deploy the apps yet09:05
kproskurinIt doest matter09:05
kproskurinAttributes should be set at mesos-slave start09:06
SiRiuS_kproskurin, should I deploy the apps and debug, or is there something interesting to look at before deploying the apps09:06
SiRiuS_?09:06
SiRiuS_ok09:06
kproskurinSiRiuS_: http://mesos-master-ip:5050/slaves09:06
kproskurinAnd paste it09:06
*** coolsvap has quit IRC09:07
SiRiuS_http://paste.openstack.org/show/492548/09:07
SiRiuS_also this is only for master03, because for master01:5050/slaves and master02:5050/slaves I get only {"slaves":[]}09:09
openstackgerritSteven Dake proposed openstack/kolla: A Fix gate to use world writeable docker socket  https://review.openstack.org/29809809:09
openstackgerritSteven Dake proposed openstack/kolla: A Fix gate by adding MariaDB-shared dependnecy  https://review.openstack.org/29968109:09
openstackgerritSteven Dake proposed openstack/kolla: Fix gate to use world writeable docker socket  https://review.openstack.org/29809809:10
openstackgerritSteven Dake proposed openstack/kolla: Fix gate by adding MariaDB-shared dependnecy  https://review.openstack.org/29968109:10
sdakecore reviewers - need some love on those two patches ^^09:10
kproskurinSiRiuS_: it does look ok. ;-\ Alright, pls run this: “kolla-mesos --profiles-default mariadb deployment run”09:11
sdakenihilifer asalkeld pbourke ^^09:11
kproskurinSiRiuS_: it will deploy only mariadb, go to it in marathon UI and chose “debug” section09:11
pbourkelooking now09:11
sdakethanks09:12
sdakepbourke do y ouhae a ultinode setup?09:12
pbourkeyes09:12
SiRiuS_kproskurin, output of command:09:13
SiRiuS_INFO - Marathon framework: marathon09:13
SiRiuS_INFO - Marathon app "/default/infra/mariadb/mariadb" is started09:13
SiRiuS_INFO - Written OpenStack env to "default-openrc"09:13
kproskurinSiRiuS_: its ok, just go to marathon UI09:13
sdakepbourke cn yu test https://review.openstack.org/#/c/299803/09:13
sdakepbourke and see if it implodes or works09:13
sdakecurrently ansible has a bug - this is a workaround09:14
sdakeif not i'll see if manjeets or nttptr can test in the morning09:14
SiRiuS_kproskurin, I have mariadb in "Waiting" state09:14
sdakei am ptfoing09:14
sdakenight09:14
kproskurinSiRiuS_: open it and push “Debug” tab, near the “configuration”09:15
SiRiuS_kproskurin, "This app does not have failed tasks"09:16
SiRiuS_This app does not have task statistics09:16
SiRiuS_No operation since last config change09:16
kproskurinSiRiuS_, Alright, so it cant run it09:16
kproskurinSiRiuS_: so it attributes error OR resourses error09:17
SiRiuS_CPU 0.9 Memory 38409:17
kproskurinSiRiuS_: let me think a bit09:18
SiRiuS_kproskurin, ok :)09:18
jiriproxHi, my kolla deployment with HAproxy is failing in "haproxy | Waiting for virtual IP to appear" msg: Timeout when waiting for x.x.x.x:3306. It was working two weeks back. Do you know what was changed? What needs to be changed to resolve it?09:20
sdake/query nihilifer09:21
kproskurinSiRiuS_: Add to globals.yml:09:21
kproskurinmariadb_mem: “32”09:21
kproskurinmariadb_cpus: “0.1”09:21
kproskurinand re-run deploy09:21
*** salv-orlando has joined #openstack-kolla09:23
kproskurinSiRiuS_: Than, open marathon UI for mariadb in the tab “Instances”(left of configuration)09:23
kproskurinYou should see 3 instances below(on each “controller” node)09:24
kproskurinIf you could make a screenshoot, it will be helpful09:24
*** achanda has quit IRC09:26
*** Jeffrey4l_ has joined #openstack-kolla09:26
SiRiuS_kproskurin, http://picpaste.com/SD1GGpZ1.png09:28
SiRiuS_kproskurin, now it is suspended09:29
kproskurinSiRiuS_: :-\09:29
*** coolsvap has joined #openstack-kolla09:30
*** sdake_ has joined #openstack-kolla09:32
*** sdake has quit IRC09:32
*** sdake has joined #openstack-kolla09:33
*** sdake_ has quit IRC09:36
kproskurinSiRiuS_: we have a plan to patch mesos\marathon stuff to be more verbose on wtf is wrong with deploy, but its not done yet, so right now only option is to go through mesos huge logs and look at the reason09:37
SiRiuS_kproskurin, yeah, right now it does not even enter waiting state09:39
SiRiuS_kproskurin, I cleaned everything up, redeployed the mesos stack09:39
*** salv-orlando has quit IRC09:39
SiRiuS_kproskurin, and still it won't reply mariadb,09:39
SiRiuS_kproskurin, it's in suspended state09:39
SiRiuS_kproskurin, it's random, that's the problem :)09:40
kproskurinSiRiuS_: suspended means it doesnt have some resourses OR constrains to launch.09:40
kproskurinBut I dunno why in your case09:40
SiRiuS_kproskurin, where are those huge mesos logs located?09:42
kproskurinSiRiuS_: Try to deploy AIO. Uncomment “mesos_aio_hostname” in globals.yml and put some any mesos-slave hostname in it. And set multinode: no09:42
kproskurinSiRiuS_: I just wonder if AIO will deploy ok09:43
SiRiuS_if I connect to the mesos UI, there is a LOG uri09:43
kproskurinSiRiuS_: its not in the UI, it should be in “docker logs CONT_ID”09:43
SiRiuS_but if I click it I receive :"Failed to initialize ... retrying"09:43
kproskurinSiRiuS_: there is logs for deployment, but you dont have any, so it is useless foe you right now, you need logs of the meos itself and you could access it via “docker logs”09:44
kproskurinSiRiuS_: Try AIO in a spare time, if it will work, then problem is with constrains if not - I give up :-(09:45
SiRiuS_kproskurin, http://paste.openstack.org/show/492552/09:47
SiRiuS_docker logs for mesos_slave on controller0109:48
kproskurinSiRiuS_, Looks totaly fine but I dont see any deployment atempt, so maybe its marathon logs what we needed09:50
*** coolsvap has quit IRC09:54
*** coolsvap has joined #openstack-kolla09:55
sdakecool we got a good haul for summit09:55
sdake14 sessions09:55
*** rmart04 has joined #openstack-kolla09:59
*** kproskurin has quit IRC10:02
*** sdake has quit IRC10:03
*** ccesario_ has joined #openstack-kolla10:04
*** kproskurin has joined #openstack-kolla10:13
*** ccesario_ has quit IRC10:15
openstackgerritMerged openstack/kolla-mesos: Move memcached deps to bootstrap section for horizon  https://review.openstack.org/29874110:20
*** coolsvap has quit IRC10:24
*** banix has joined #openstack-kolla10:30
*** rhallisey has joined #openstack-kolla10:34
*** coolsvap has joined #openstack-kolla10:38
dims_howdy folks : trying quickstart steps, can't seem to get past this problem with mariadb not coming up - http://paste.openstack.org/show/492559/10:45
dims_mkdir: cannot create directory '/var/log/kolla/mariadb': Permission denied10:45
rhalliseyadd a sudo10:46
rhalliseyin front of your start command10:46
rhalliseyonly need to do that once because we need to create those directories on the host10:47
*** tfukushima has quit IRC10:49
*** mbound has joined #openstack-kolla10:50
*** salv-orlando has joined #openstack-kolla10:51
dims_rhallisey : y, does not seem to help will try again10:58
rhalliseydo you get past the perm error though?10:59
dims_nope10:59
dims_rhallisey : i removed the mariadb container, tried deploy again as root.11:00
dims_tried creating that directory by hand with 777 no luck11:00
dims_rhallisey : heka memcached etc started ok11:05
rhalliseyweird11:05
*** weiyu has quit IRC11:08
ccesariogood morning11:08
dims_rhallisey : ack will dig more11:09
ccesariorhallisey, testing the second deploy based in directory structure11:09
rhalliseydims_, ya not sure.  Usually only perms is required to make the dir11:10
rhalliseyccesario, how's it going?11:10
ccesariorhallisey, just fixing some prechecks on test node.... give me a bit time11:12
rhalliseysure11:12
*** mbound has quit IRC11:13
*** mbound has joined #openstack-kolla11:13
*** coolsvap has quit IRC11:14
*** mbound has quit IRC11:15
*** SiRiuS_ has quit IRC11:22
*** unicell has quit IRC11:22
*** allen_gao has quit IRC11:22
*** allen_ga- has joined #openstack-kolla11:22
*** unicell has joined #openstack-kolla11:23
*** banix has quit IRC11:34
*** kjelly has joined #openstack-kolla11:35
*** rbrady has joined #openstack-kolla11:41
*** alyson_ has joined #openstack-kolla11:51
*** gfidente has joined #openstack-kolla12:06
*** dwalsh has joined #openstack-kolla12:08
*** ayoung has quit IRC12:10
*** banix has joined #openstack-kolla12:15
*** dave-mccowan has joined #openstack-kolla12:20
*** ccesario_ has joined #openstack-kolla12:25
sbezverkgood morning12:27
sbezverkrhallisey qq if I want to split one PS into pieces, do I abandon the original PS? what is the right aproach here?12:28
rhalliseysbezverk, probably easiest to abandon and split into pieces12:30
*** banix has quit IRC12:31
sbezverkrhallisey got it, thank you12:32
rhalliseyno problem12:33
*** dwalsh has quit IRC12:41
*** dwalsh has joined #openstack-kolla12:41
*** patchbot has joined #openstack-kolla12:48
*** mbound has joined #openstack-kolla12:48
*** mbound has quit IRC12:49
*** mbound has joined #openstack-kolla12:49
dims_rhallisey : am getting the hang of this hopefully :) did a docker inspect on mariadb container, (http://paste.openstack.org/show/492568/) looked at "Mounts"/"Source" and ensured that those directories are present with appropriate permissions12:50
*** mbound has quit IRC12:51
*** achanda has joined #openstack-kolla13:00
ccesariorhallisey, the second deploy pause on this task:   TASK: [haproxy | Waiting for virtual IP to appear] ****************************13:01
ccesarioit seems the HA address does not  goes "UP"13:01
ccesariohttp://paste.openstack.org/show/492571/13:02
rhalliseydims_, do you have selinux on or something?13:02
rhalliseydims_, I don't know why that originally happened13:03
dims_rhallisey : "15.10 (Wily Werewolf)"13:03
dims_ccesario : i did (enable_haproxy: "No")13:04
rhalliseydims_, gotcha.. so did making those dirs by hand work?13:04
rhalliseyseems like you got past the issue13:05
ccesariodo you know if is there any "exception" when running two hapry in same subnet ?13:05
ccesariodims_, in the first deploy it is running with haproxy Yes13:05
dims_rhallisey : yes thanks, got past heka, mariadb... now keystone centos is not building, going to try keystone ubuntu13:06
*** achanda has quit IRC13:06
*** daneyon_ has joined #openstack-kolla13:06
ccesariothe config of the both "deploys"  http://paste.openstack.org/show/492572/13:06
rhalliseydims_, maybe that's the issue. Ya use ubuntu since that is your base os13:06
dims_rhallisey : interesting13:07
*** stvnoyes has quit IRC13:07
*** kjelly has quit IRC13:09
*** daneyon_ has quit IRC13:10
ccesariorhallisey, it seems a haproxy behaivor ....   because if I deploy firtly the "cloud2"  it works.... and "cloud1" presents the same problem13:15
rhalliseyccesario, can you explain this in different way.  You have one cloud that's working (cloud1) and cloud2 is having the haprxy issue?13:17
rhalliseyis that what your seeing?13:17
ccesarioyes.....13:17
ccesarioand now I cleanup cloud1 containers13:18
*** salv-orlando has quit IRC13:18
rhalliseyok let me just do some reading13:18
ccesarioand run cloud2 deploy (without touch in config files)13:18
ccesarioand the deploy it is running :)13:19
*** salv-orlando has joined #openstack-kolla13:19
ccesariowhen the cloud2 deploy finish, I will try deploy cloud1 (without cleanup cloud2 containers)13:19
rhalliseyccesario, ok13:20
*** stvnoyes has joined #openstack-kolla13:20
ccesariorhallisey, cloud2 finish!!13:20
ccesarioPLAY RECAP ********************************************************************13:20
ccesario192.168.201.3              : ok=293  changed=98   unreachable=0    failed=013:20
rhalliseyccesario, you are using the multinode inventory correct?13:21
ccesarioyes (with 1 node only)13:22
ccesariothe prechecks in cloud1 it is OK ....13:23
ccesarioPLAY RECAP ********************************************************************13:23
ccesario192.168.201.2              : ok=58   changed=0    unreachable=0    failed=013:23
ccesariolet me try deploy cloud113:23
rhalliseyk13:23
*** salv-orl_ has joined #openstack-kolla13:24
*** salv-orlando has quit IRC13:26
openstackgerritMerged openstack/kolla-mesos: Fix rabbitmq version for centos  https://review.openstack.org/29872013:30
*** diogogmt has quit IRC13:30
ccesariorhallisey, http://sprunge.us/XfVh?log13:32
ccesariothe process stops in the same point that previous deploy13:32
*** diogogmt has joined #openstack-kolla13:35
rhalliseyccesario, ya you need to use a different vip address since that one is in use13:36
ccesariorhallisey, but I 'm using13:37
ccesariolook the http://paste.openstack.org/show/49257113:37
ccesario:D13:38
*** salv-orl_ has quit IRC13:38
ccesarioso it is that running IP is 192.168.201.100 :)13:38
rhalliseywhat do you have for kolla_internal_vip_address13:39
rhalliseyit's that ^ right?13:39
ccesarioif I cleanup all and run cloud1 deploy the running ip 192.168.201.200 it works13:39
rhalliseyccesario, I thought you said you are using the same globals.yml13:42
rhalliseyso you're using 192.168.201.100 &  192.168.201.200 as your vips for cloud 1 and 213:42
rhallisey?13:42
ccesariorhallisey, no no....  specific config for each "cloud"13:42
ccesarioyes yes13:42
ccesario192.168.201.100 &  192.168.201.20013:42
*** salv-orlando has joined #openstack-kolla13:43
ccesariorhallisey, about kolla_internal_vip_address ... in this case are the address defined in kolla_internal_address in each config.... right!?13:44
ccesario--->>>  ansible/group_vars/all.yml:kolla_internal_vip_address: "{{ kolla_internal_address }}"13:45
*** vhosakot has joined #openstack-kolla13:45
*** daneyon has quit IRC13:45
*** daneyon has joined #openstack-kolla13:46
ccesariorhallisey, right!!?13:47
rhalliseyya13:47
vhosakotmorning!13:48
*** huikang has joined #openstack-kolla13:49
ccesariomorning vhosakot !13:49
openstackgerritDavanum Srinivas (dims) proposed openstack/kolla: Update Quickstart with example for distro and install type  https://review.openstack.org/29994513:50
*** ayoung has joined #openstack-kolla13:50
ccesariorhallisey, any clue!?13:51
rhalliseyccesario, are you setting kolla_internal_address ?13:51
rhalliseylet me get my setup going13:51
ccesariorhallisey, ya13:52
ccesariohttp://paste.openstack.org/show/49257213:52
rhalliseyah ok13:52
ccesario:D13:52
*** salv-orlando has quit IRC13:52
*** diogogmt has quit IRC13:54
rhalliseyccesario, just need to do some reading on this13:54
ccesariorhallisey, do not worry with a lot enable_{Service}  .... only tests :P13:54
rhalliseygotcha13:54
ccesariorhallisey, tell me13:54
*** banix has joined #openstack-kolla13:56
*** mgoddard_ has joined #openstack-kolla14:00
*** salv-orlando has joined #openstack-kolla14:02
*** achanda has joined #openstack-kolla14:02
*** mgoddard has quit IRC14:03
*** ccesario_ has quit IRC14:03
*** dougs1 has quit IRC14:04
openstackgerritSerguei Bezverkhi proposed openstack/kolla: lvm2/iscsi backend support for cinder  https://review.openstack.org/29995614:07
*** achanda has quit IRC14:08
*** pmisiak has joined #openstack-kolla14:18
pmisiakhi, hello14:18
ccesariorhallisey, tried again.... the same problem returned14:20
rhalliseyccesario, still reading about how to properly config this14:21
rhalliseyyou get a 301 error from haproxy14:21
openstackgerritSerguei Bezverkhi proposed openstack/kolla: lvm2/iscsi backend support for cinder  https://review.openstack.org/29995614:22
dave-mccowanare there still some issues with rabbit and hostnames?  i'm getting the error "Hostname has to resolve to IP address of api_interface" with an all-in-one deploy.14:23
ccesariorhallisey, let me try check heka logs14:24
vhosakotdave-mccowan: yes, seen just with rax gate.... https://bugs.launchpad.net/kolla/+bug/156156314:25
openstackLaunchpad bug 1561563 in kolla "rax gates fail with ip != hostname" [High,In progress] - Assigned to Sam Yaple (s8m)14:25
ccesariorhallisey, http://paste.openstack.org/show/492589/14:25
vhosakotdave-mccowan: not able to reproduce it in my local env on Ubuntu...14:25
vhosakotdave-mccowan: looks like /etc/hosts gets bad often on rax gate..14:25
rhalliseydave-mccowan, ping `hostname`14:26
*** SiRiuS_ has joined #openstack-kolla14:26
huikangping: vhosakot14:26
vhosakothuikang: saw all your comments :)14:26
huikanggreat14:26
vhosakothuikang: I need to some to reply :)14:26
rhalliseydave-mccowan, add you hostname into /etc/hosts and it should work14:26
huikangvhosakot, no problem : )14:27
dave-mccowanwhat's weird is the error message doesn't have my hostname address, it has my kolla_external_vip_address14:30
vhosakotrhallisey: don't we already add hostname into /etc/hosts in setup_gate.sh ?    https://github.com/openstack/kolla/blob/master/tools/setup_gate.sh#L80-L89     for some reason, that code does not work on rax gate14:30
dave-mccowani can reproduce it on my local setup.  i'd hate to "fix" it, if there is a hard to reproduce bug that needs to be debugged.14:31
rhalliseyvhosakot, I thought he was just doing a regular deployment14:32
vhosakotah ok.. I thought dave-mccowan saw the error in gate... ok14:32
dave-mccowanall in one on centos714:33
vhosakotdave-mccowan: if you know the fix and busy to fix, you could send the steps please, and one of us can fix it and add you as co-author sure14:33
openstackgerritJeffrey Zhang proposed openstack/kolla: Enable the kibana access from the external network  https://review.openstack.org/29999414:34
*** Jeffrey4l_ has quit IRC14:35
*** Jeffrey4l_ has joined #openstack-kolla14:35
dave-mccowani'm happy to debug and fix.  what i'm not sure is what this check is supposed to do.  it says my hostname doesn't match the address on api_interface, but the values it's giving are not my hostname and not the address on api_interface.14:35
openstackgerritSerguei Bezverkhi proposed openstack/kolla: lvm2/iscsi backend support for cinder (part 2)  https://review.openstack.org/29999514:35
dave-mccowanwhere does the value for ansible_hostname come from, that might be the root of my error.14:37
rhalliseydave-mccowan, what address does your hostname resolve to?14:38
dave-mccowanah... the wrong fqdn name.  looks like i messed up my linux config.14:40
openstackgerritMerged openstack/kolla-mesos: Fix marathon framework autodetection  https://review.openstack.org/29705414:40
ccesariorhallisey, fresh haproxy logs http://paste.openstack.org/show/492595/14:41
openstackgerritMerged openstack/kolla: Fix gate to use world writeable docker socket  https://review.openstack.org/29809814:41
openstackgerritMerged openstack/kolla: Fix gate by adding MariaDB-shared dependnecy  https://review.openstack.org/29968114:41
dims_rhallisey : thanks! i got a deploy to succeed (http://paste.openstack.org/show/492594/) with one doc suggestion :) https://review.openstack.org/#/c/299945/14:42
patchbotdims_: patch 299945 - kolla - Update Quickstart with example for distro and inst...14:42
openstackgerritDavanum Srinivas (dims) proposed openstack/kolla: Update Quickstart with example for distro and install type  https://review.openstack.org/29994514:42
openstackgerritSerguei Bezverkhi proposed openstack/kolla: lvm2/iscsi backend support for cinder (part 3)  https://review.openstack.org/30000414:42
rhalliseydims_, excellent!14:43
rhalliseyccesario, ok so connection refused..14:47
rhalliseyccesario, what containers do you have up at this point?14:47
rhalliseyin cloud 1 I think it is14:47
rhalliseywhichever one is getting the error14:47
*** wuhg has quit IRC14:49
ccesariorhallisey, http://paste.openstack.org/show/492597/14:51
ccesarioon "cloud1"14:51
*** sdake has joined #openstack-kolla14:57
huikangmorning, sdake14:57
*** mgoddard_ has quit IRC14:57
sdakemorning huikang14:58
sdakehey is gmmaha around14:58
*** mgoddard has joined #openstack-kolla14:58
huikangsdake, is there a kolla design session in austin summit?14:58
sdakeyes we have 14 sessions14:58
huikangsdake, sounds great14:59
sdakelast time we had 614:59
huikangI can join this time14:59
sdakesweet15:02
sdakeon tuesday is a complete cross-sesssion day15:02
sdakemonday is the ops susmmit -i'd recommend attending that15:02
openstackgerritSerguei Bezverkhi proposed openstack/kolla: lvm2/iscsi backend support for cinder (part 3)  https://review.openstack.org/30000415:03
huikangis the schedule available online?15:03
kproskurinrhallisey: Hey, looks like you didnt create a patch\bug about nova chown. Something wrong?15:04
rhalliseykproskurin, not sure if that solved the issue15:05
rhalliseykproskurin, I also don't think we need chown -R15:06
rhalliseythe perms are being set properly15:06
rhalliseyuser rather15:06
kproskurinrhallisey: What do you mean? I rebuilt nova-compute with chown -R /var/lib/nova and everything start to work for me. Right now ew have a situation what /var/lib/nova/instanses call is not working at all. But fixing it not solve all problemes, since there is a subdirts inside instances15:07
rhalliseyI started the container by hand and saw everything was given the nova user15:08
rhalliseykproskurin, I guess -R won't really cause any harm here, but I'm not seeing the same issue15:10
kproskurinrhallisey: are you sure you checked subdirs?15:10
rhalliseykproskurin, ya I'm seeing everything as 'nova nova'15:11
kproskurinrhallisey: I cant imagene how it could be different in Kolla… its the same call. And sudo 100% wrong for instances15:11
*** salv-orlando has quit IRC15:11
rhalliseykproskurin, so this was just in kolla-mesos you saw this right?15:12
kproskurinrhallisey: yes… BUT it’s same container, built from kolla master. And it’s the same code, with the same calls, same sudo and everything15:12
ccesariorhallisey, I tried increase the timeout  of  task ... but no sucess too :(15:12
rhalliseyya it's odd15:13
sdakegmmaha ping15:13
rhalliseyccesario, still investigating the cause of 'connection refused'15:13
rhalliseyccesario, I'll get back to it in a minute15:14
ccesariorhallisey, http://paste.openstack.org/show/492601/  stopped in this point15:14
ccesarioonly to keep you notified :)15:14
rhalliseythanks :_15:14
rhallisey:)15:14
rhalliseykproskurin, does kolla-mesos use all of kolla's containers?15:15
rhalliseywondering if there is some disconnect here15:15
rhalliseyeither way I'll add -R15:15
rhalliseybut just curious15:15
kproskurinrhallisey: yes it does, we use most of the things from Kolla, Ill do some basic re-check right now about this issue...15:16
rhalliseykproskurin, is /var/lib/nova 'nova nova' user & group15:17
*** pmisiak has quit IRC15:18
*** blahRus has joined #openstack-kolla15:22
*** ayoung has quit IRC15:24
*** ayoung has joined #openstack-kolla15:25
*** kproskurin has quit IRC15:35
*** kproskurin has joined #openstack-kolla15:39
*** tobe has joined #openstack-kolla15:43
dims_ccesario : rhallisey : like what i see here? http://paste.openstack.org/show/492605/15:45
dims_libvirtError: unable to connect to server at '10.0.0.3:16509': Connection refused15:45
rhalliseydims_, ccesario is doing something different. He is created 2 clouds and haproxy is giving connections refused on the second15:47
sdakedims is libvirtd running on the host?15:47
rhalliseydims_, what's the libvirt container status?15:48
*** tobe has quit IRC15:48
dims_rhallisey : sdake : no. i did the "service libvirt-bin stop;update-rc.d libvirt-bin disable" per quickstart15:49
dims_rhallisey : ah ok15:49
sdakedims_ docker ps -a | grep libvirt15:49
dims_ah. its running but ran into trouble15:50
dims_Running command: '/usr/sbin/libvirtd --listen'15:50
dims_ /usr/sbin/libvirtd: error while loading shared libraries: libvirt-admin.so.0: cannot open shared object file: Permission denied15:50
sdakedims_ if you type dmesg I'm sure you will see the problem - apparmor15:51
rhalliseythis needs to be in the quickstart..15:52
rhalliseyhow do you turn off apparmor15:52
rhalliseyI'll add it in there15:52
dims_sdake rhallisey : ah thanks15:53
*** rmart04 has quit IRC15:56
*** mgoddard_ has joined #openstack-kolla15:59
*** sdake has quit IRC16:01
ccesariorhallisey, http://paste.openstack.org/show/492615/16:02
ccesario:D16:02
*** mgoddard has quit IRC16:02
*** Jeffrey4l_ has quit IRC16:04
dims_rhallisey : got a tip for me to try?16:05
*** Jeffrey4l_ has joined #openstack-kolla16:05
*** achanda has joined #openstack-kolla16:05
ccesariorhallisey, bingo! discovered the problem!!!16:08
*** salv-orlando has joined #openstack-kolla16:08
rhalliseyccesario, what is it!?16:08
rhalliseydims_, did you disable it?16:09
*** daneyon_ has joined #openstack-kolla16:09
rhalliseysudo /etc/init.d/apparmor stop16:09
rhalliseysudo update-rc.d -f apparmor remove16:09
*** achanda has quit IRC16:11
ccesariorhallisey, http://paste.openstack.org/show/492615/  from the "kolla deployer"16:11
dims_rhallisey : ack. after that should i just nuke nova-compute and libvirt containers and try deploy again?16:11
rhalliseydims_, ya16:11
*** Jeffrey4l_ has quit IRC16:12
ccesariothe problem is in keepalive.... due the default template usage virtual_router_id with static value 5116:12
*** daneyon has quit IRC16:12
ccesarioI have changed the config of cloud1 to virtual_router_id 52 ... and redeploy16:13
ccesariothe Ip address goes UP and the tasks run as expected16:13
rhalliseynice16:14
*** unicell1 has joined #openstack-kolla16:15
ccesariorhallisey, now, just know how to solve this  in the code :P16:15
*** unicell has quit IRC16:15
rhalliseyccesario, I think it just needs to be configurable16:16
dims_rhallisey : did not help16:16
rhalliseydims_, sudo apparmour status16:16
rhalliseyjust curious if that disable it16:16
ccesariorhallisey, kind of param on globals ?16:16
rhalliseyccesario, ya16:16
rhalliseyccesario, we also need to document what you did16:17
rhalliseyccesario, because people will be asking about it16:17
dims_rhallisey : http://paste.openstack.org/show/492618/16:17
ccesariorhallisey, until this point I think important tw things/(maybe features)16:18
dims_am running it on my box (ubuntu-brix) not in the libvirt container to be specific16:18
*** shardy has quit IRC16:19
rhalliseydims_, let me check the irc logs.. someone got this working yesterday16:19
ccesariorhallisey, these points16:20
ccesario1 - make kolla-genpwd optionaly write on specifc folder16:20
ccesario2 - make virtual_router_id keepalive param configurable16:20
rhalliseyccesario, ok.  I'll make a bp for N16:20
*** jiriprox has quit IRC16:21
rhalliseyshouldn't be too hard16:21
*** shardy has joined #openstack-kolla16:21
ccesariountil now I have mapped these two points16:22
dims_rhallisey : thanks a ton you have been very helpful16:22
ccesariorhallisey, good...! if you could make a bp, would be nice!16:22
rhalliseydims_, no problem16:23
rhalliseyccesario, ya will do16:23
*** ChanServ changes topic to "Kolla IRC meetngs on Wednesdays @ 16:30 UTC even weeks, 23:00 UTC odd weeks - see agenda @ https://goo.gl/OXB0DL - IRC channel is *LOGGED* @ http://goo.gl/3mzZ7b (old logs from #kolla http://goo.gl/VKpPzA)"16:24
*** mikelk has quit IRC16:24
*** sdake has joined #openstack-kolla16:24
*** inc0 has joined #openstack-kolla16:26
inc0howdy16:26
ccesariorhallisey, other point16:27
rhalliseydims_, goo.gl/2F4suI16:27
rhalliseyhttp://goo.gl/2F4suI16:27
ccesariothe param vrrp_instance needs to be diferent16:27
ccesarioby default it is vrrp_instance kolla_internal_vip16:28
*** sdake has quit IRC16:28
*** sdake has joined #openstack-kolla16:29
rhalliseyccesario, I think the issue is having two vrrp_instances with the same router_id16:29
*** sdake has quit IRC16:30
rhalliseygmmaha, where did you disable apparmor to get libvirt working? On your host?16:31
ccesarioan automation like this can be easly too....   vrrp_instance kolla_internal_vip_{{ router_id_var }}16:31
*** mbound has joined #openstack-kolla16:31
*** daneyon has joined #openstack-kolla16:32
rhalliseyccesario, ya I think it's an easy patch16:32
rhalliseybrb a min lunch16:32
*** daneyon_ has quit IRC16:33
ccesariorhallisey, have a good lunch!16:33
*** mbound has quit IRC16:33
rhalliseythanks :)16:33
*** daneyon_ has joined #openstack-kolla16:36
*** daneyon__ has joined #openstack-kolla16:38
*** daneyon has quit IRC16:38
*** daneyon_ has quit IRC16:41
*** daneyon has joined #openstack-kolla16:42
gmmaharhallisey: i just pulled it out.. apt-get remove -y apparmor16:42
gmmahacrude, yes i know! :(16:42
rhalliseydims_, ^^ see if that helps16:43
*** daneyon has quit IRC16:43
*** daneyon__ has quit IRC16:43
*** daneyon has joined #openstack-kolla16:43
gmmahadims_: that and make sure you disable libvirtd on the host.. (update-rc.d libvirt-bin disable)16:43
*** daneyon has quit IRC16:44
dims_gmmaha : y already did the libvirtd. will try removing apparmor completely16:45
*** kproskurin has quit IRC16:47
*** sdake has joined #openstack-kolla16:48
*** vhosakot has quit IRC16:48
gmmahadims_: cool..16:49
gmmahasdake: hey16:49
sdakegmmaha ping re tet16:49
sdakehey bro16:49
sdakedid you try my patch16:49
gmmahasorry couldnt get up early16:49
gmmahasdake: did you push a patch? I didnt see any yet..16:49
sdakegmma moment i'll give you a link16:49
gmmahasdake: thanks16:50
sdakehttps://review.openstack.org/#/c/299803/16:50
patchbotsdake: patch 299803 - kolla - [WIP] Workaround ansible bug related to delegate_to16:50
gmmahasdake: testing it now16:51
sdakesort of bsed aroudn vhosakot's idea at the last minute before i ptfoed16:51
sdakemake sure to revert any other changes you have in your repo16:51
sdakebut you know that I htink :)16:51
gmmahasdake: aaaahhh16:51
gmmahathis might work16:51
sdakei am hoepful16:51
gmmahasdake: for sure..16:51
sdakei dont know enough about ansible variable calculation to know for certain16:51
*** inc0 has quit IRC16:53
gmmahasdake: might work, given that we arent dynamically reading that value when that play is being run..16:53
*** mgoddard has joined #openstack-kolla17:01
*** diogogmt has joined #openstack-kolla17:01
*** mgoddard_ has quit IRC17:02
*** gfidente has quit IRC17:02
gmmahasdake: that didnt work :(17:06
gmmahabut run once failed completely17:06
gmmahahttp://paste.openstack.org/show/492628/17:06
openstackgerritSerguei Bezverkhi proposed openstack/kolla: lvm2/iscsi backend support for cinder (part 3)  https://review.openstack.org/30000417:07
openstackgerritSerguei Bezverkhi proposed openstack/kolla: lvm2/iscsi backend support for cinder  https://review.openstack.org/29128517:07
openstackgerritSerguei Bezverkhi proposed openstack/kolla: lvm2/iscsi backend support for cinder (part 2)  https://review.openstack.org/29999517:07
*** mlima has joined #openstack-kolla17:08
gmmahasdake: sorry run once works.. :)17:08
*** jmccarthy has quit IRC17:08
*** daneyon has joined #openstack-kolla17:09
sdakegmmaha so did the patch work or not work?17:09
gmmahasdake: no.. didnt work17:09
gmmahait still tried runnign it on the compute node17:09
sdakesam error?17:09
*** jmccarthy has joined #openstack-kolla17:09
sdakesam/same17:09
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Add integration with Kolla infrastructure  https://review.openstack.org/30000417:10
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Adds iscsid and tgtd docker containers  https://review.openstack.org/29128517:10
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Adds ansible code for iscsid and tgtd containers  https://review.openstack.org/29999517:10
*** mlima_ has quit IRC17:10
gmmahasdake: yeah17:11
sdakegmmaha damn i really thought that might work17:14
sdakegmmaha can you leave a note in the review its no beuno17:14
gmmahasdake: for sure17:14
*** mlima_ has joined #openstack-kolla17:14
gmmahai thought the same.. let me test something out17:14
*** achanda has joined #openstack-kolla17:15
*** mlima has quit IRC17:17
*** vhosakot has joined #openstack-kolla17:18
*** mbound has joined #openstack-kolla17:19
manjeetswhere all configs are saved ?17:21
manjeetsi want to edit nova config for api_return result limit ?17:22
vhosakotmanjeets: /etc/kolla/nova-compute/nova.conf17:23
manjeetsi see that on control node17:23
vhosakot  /etc/kolla/nova  has nova confis17:23
manjeetsI don't see this on host from where i deployed17:24
sdakefrom host you deploy ou need to override in /etc/kolla/config17:24
sdakemanjeets this technique is currently undocumented17:24
sdakebut basically create a file called nova-compute.ini17:25
sdakein /etc/kolla/config17:25
sdakeadd [iniheader]17:25
sdakekey=value17:25
*** stvnoyes has left #openstack-kolla17:25
sdakeand run reconfgiure17:25
sdakeif reconfigure is still broken run redeploy and it will merge the configs in with the defaults17:25
sdakesorry file should be called nova-compute.conf17:26
sdakeif you want it to apply to all of nova, call it nova.conf17:26
sdakeI think17:26
manjeetsthere is no config dir in /etc/kolla17:27
manjeetsi created one and copied nova.conf17:28
manjeetssdake should libvirt-bin be stopped before i run re configure17:30
manjeets?17:30
manjeetsor anything that need to be stopped17:30
*** alyson_ has quit IRC17:32
*** inc0 has joined #openstack-kolla17:33
ccesariosdake,  do you have feedback about this ticket ? #29980317:36
ccesariorhallisey, ping ?17:37
rhalliseyccesario, hey17:37
manjeetsvhosakot if i changed in /etc/nova-compute/nova.conf and restarted nova_api container is that enough to reflect the changes17:38
ccesariorhallisey, http://sprunge.us/JFTR?diff17:38
vhosakotmanjeets: can you follow this for reconfig   -   https://etherpad.openstack.org/p/kolla-mitaka-testing-reconfigure17:39
ccesariorhallisey, I just test it now..... working as expected ... only changing the  keepalived_virtual_router_id: "100" in second "cloud"17:39
*** dims_ has quit IRC17:39
rhalliseyccesario, looks good17:40
*** dims has joined #openstack-kolla17:40
ccesariorhallisey, ;)17:42
manjeetsvhosakot i need to add only the option i want to chane ?17:43
vhosakotyes.. along with the section name17:43
manjeetsokay cool thansk17:44
ccesariorhallisey, when you create a bp or bug ... ping me that I submit it17:44
rhalliseyk will do17:44
ccesariorhallisey, do you think that need more test abou it ?17:44
*** shardy has quit IRC17:45
rhalliseythat patch shouldn't disrupt anything17:45
rhalliseysince it's beingdefaulted17:45
ccesariorhallisey, yes.... I think too... in my tests nothing it was broken :P17:47
ccesarioexpect if I did not change the param, the second deploy stops (as previously I told you)17:47
ccesarioexcept*17:47
ccesario1 - make kolla-genpwd optionaly write on specifc folder17:49
ccesario2 - make virtual_router_id keepalive param configurable17:49
ccesario3 - vrrp_instance kolla_internal_vip_{{ router_id_var }}17:49
ccesario2 and 3 ... done17:49
*** unicell has joined #openstack-kolla17:54
mlima_guys, have i can two identical containers ( two cinder_volume container ), but each container with your backend?17:54
sdakenot wit hthe same name17:54
mlima_hmm17:55
*** dwalsh has quit IRC17:55
sdakename it cinder_voolume_bakcendname17:55
inc0not sure how it will work tho17:55
inc0not a normal use case17:55
sdakeyup a new one17:55
mlima_it need some configurations17:55
inc0on that note, how do we look like  on iscsi+lvm front?17:55
*** unicell1 has quit IRC17:56
sdakeccesario can you link the bug plz you are talking about17:56
sdakemanjeets libvirt-bin should not be running at aall!17:56
sdakemanjeets you have to mkdir /etc/kolla/config17:56
manjeetssdake http://paste.openstack.org/show/492634/ vhosakot got this issue while reconfigure17:56
sdakeapologie sfor lag was in security meeting17:56
manjeetsi guess my libvirt-bin is running17:56
sdakemanjeets thats a problem - with gmmaha we removed libvirt-bin17:57
manjeetsI had that problem yesterday kolla cleanups do not force stop libvirt bin17:57
manjeetsi froze yesterday i did reboot and still its was giving me issues17:58
manjeetsit**17:58
manjeetsthen i manually stopped the container and killed the libvirt processes in every single node and redeploy worked without reboot17:58
inc0yeah libvirt needs to die17:59
inc0on host17:59
gmmahasdake: i have a theory17:59
gmmahaabout the bug..17:59
gmmahavhosakot: ^^17:59
gmmahaand i think re-ordering wont be a bad thing..17:59
gmmahawant me to put it down in an email and send it your way?17:59
manjeetslibvirt did not die even after reboot17:59
inc0gmmaha, what's your idea?17:59
sdakegmmaha use the ebug tracker18:00
manjeetsnot sure if it should or not18:00
inc0also, do you have an env on which this is constantly failing?18:00
inc0mind if I do some debugging on my own18:00
inc0?18:00
ccesariosdake, https://review.openstack.org/#/c/299803/18:00
patchbotccesario: patch 299803 - kolla - [WIP] Workaround ansible bug related to delegate_to18:00
gmmahainc0: are you talking about the neutron play failing?18:00
gmmahasdake: sure..18:00
inc0that's the one gmmaha18:00
sdakeinc0 we had a 6 hour debug session on google groups last night with 6 people18:00
sdakeit is definately an ansible bug18:00
inc0sure, which one?18:00
inc0anyone know what is exactly happening?18:00
sdakeyup18:00
gmmahainc0: sure..18:00
sdakeits running bootstrap on compute18:00
inc0do share18:01
inc0but why?18:01
gmmahainc0: let me put it down18:01
gmmahaon the bug18:01
sdakeand running the check of the bootstrap results on some other node18:01
inc0yeah18:01
* gmmaha goes to find the bug18:01
inc0it's about delegate_to right?18:01
gmmahainc0: a little.. i think its clear delegate_to is broken in this version18:02
gmmahaand there are bugs around that18:02
gmmahaits about how we can fix it18:02
*** rajathagasthya has joined #openstack-kolla18:02
manjeetssdake vhosakot i stoped nova_libvirt and then did refconfigure it failed18:03
sdakeya reconfigure may be busted atm18:04
sdakeinc0 look t my review where i made an attempt at a fix18:05
inc0I -1 it, it's not how we should do it18:05
inc0so my guess is18:05
sdakeoh i see you already did18:05
rhalliseyccesario, https://blueprints.launchpad.net/kolla/+spec/multiple-clouds18:06
inc0https://github.com/openstack/kolla/blob/master/ansible/site.yml#L10718:06
rhalliseyccesario, going to also add a bug18:06
inc0ansible probably builds a list of servers18:06
inc0based on order we used in site.yml18:06
sdakeinc0  Ihadn't thought of that!18:06
inc0and takes first one from this18:07
inc0we can try to change order in our very own site.yml and it should help in most cases18:07
sdakegmmaha revert my chnges and enable manila and repdeloy please18:07
inc0that too18:07
sdakei am not keen on order change18:07
inc0why? what does it change really?18:07
sdakelets see if i ts its the enable manila thing18:07
sdakeinc0 my concern is delegate-to is broken in genernal18:08
sdakeand we use it in all our bootstrap scriips18:08
sdakeso I'd rather fix it everywhere then where it happens to pop up randomly18:08
inc0sdake, move to ansible 2.0 is on top of my priorities for N18:08
sdakeinc0 that isn't an ansswer for mitaka18:08
inc0so see if you can enable manila and it helps18:08
rhalliseyccesario, https://bugs.launchpad.net/kolla/+bug/156454718:09
openstackLaunchpad bug 1564547 in kolla "The virtual_router_id needs to be configurable" [Medium,New]18:09
sdakegmmaha inc0's theory is that enable_manila bool is breaking the playbook18:09
sdakebecause it always  evaluates to false18:09
gmmahasdake: inc0: vhosakot: https://bugs.launchpad.net/kolla/+bug/1546789/comments/1118:09
openstackLaunchpad bug 1546789 in kolla "neutron failed to deploy in a multi-node deployment" [Critical,In progress] - Assigned to Steven Dake (sdake)18:09
gmmahasdake: aaah i can try it out18:09
gmmahalet me see18:09
sdake"where did you get that theory from? A unicorn's ass?  He isn't some zulu warrior." :)18:10
vhosakothahahahahahahahahahahahahahahahahahahaha18:10
ntpttrgmmaha: I don't think that it's delegate_to that's broken, but just the group lookup itself18:10
*** jasonsb has joined #openstack-kolla18:10
gmmahasdake: are you talking about me?18:11
gmmaha:)18:11
ntpttrgmmaha: since a bunch of different options that didn't use delegate_to had the same result18:11
vhosakotyes, let us move to Ansible 2.0.... it has better error handling I read18:11
gmmahantpttr: the other ones the first that runs is the right host.. check nova18:11
inc0ntpttr, that's my take as well18:11
dmsimardvhosakot: you have the blocks feature for error handling18:11
dmsimardbut it's still fairly limited18:12
inc0also try adding this to play18:12
ntpttrgmmaha: I know, it's a bit of a random bug. Don't know why it only happens some of the time18:12
vhosakotdmsimard: what is blocks feature ?18:12
dmsimardvhosakot: http://docs.ansible.com/ansible/playbooks_blocks.html18:12
inc0http://paste.openstack.org/show/492640/ ntpttr gmmaha18:13
ntpttrinc0: I believe we did that, it's getting the compute host18:13
gmmahainc0: that was there..18:13
dmsimardvhosakot: I'm personally keeping an eye on two feature requests that'll greatly improve things: https://github.com/ansible/ansible/issues/13587 and https://github.com/ansible/ansible/issues/1234118:13
*** Serlex has left #openstack-kolla18:13
ntpttrinc0: the group lookup in just that one instance in the whole ansible run is incurring this bug, for who knows what reason >.<18:13
*** jasonsb has quit IRC18:13
vhosakotso, it blocks similar to tags ? group tasks together ?18:14
dmsimardvhosakot: no, blocks are like "try except finally"18:14
dmsimardvhosakot: kind of18:14
vhosakotah ok.. wow18:14
inc0ntpttr, remove [0] and let's see what it thinks "neutron-server" is18:14
inc0what hosts are there18:14
dmsimardexcept instead of "try except finally", it's "block rescue always" :)18:14
vhosakotah18:15
ntpttrinc0: we checked that too, and it's the compute group :)18:15
gmmahainc0: we ran through all these last night.. :)18:15
gmmahahence the completely bonkers theory of mine18:15
inc0ok...and ordering change changes?:)18:15
dmsimardvhosakot: it's pretty nice, but you can't wrap anything you want in it right now18:15
gmmahabut atleast the logs seem to be consistent to what i am seeing18:15
ntpttrgmmaha: what's your theory then?18:15
ntpttrinc0: yeah putting the neutron groups at the top of the hosts list makes it resolve correctly for that play18:16
vhosakotyep, updating kolla playbooks with new Ansible syntax and testing them is a huge task also18:16
*** diogogmt_ has joined #openstack-kolla18:16
*** diogogmt has quit IRC18:17
*** diogogmt_ is now known as diogogmt18:17
inc0gmmaha your theory makes sense18:18
inc0gmmaha, try to remove run_once and see if it helps18:18
gmmahainc0: the problem with that is that it will try to create the db 3 times.. :(18:18
inc0no matter18:19
inc0will validate theory18:19
inc0and then we can think how to resolve it18:19
gmmahainc0: yeah that worked yesterday..18:19
gmmahawhen we remove the run_once18:19
*** dwalsh has joined #openstack-kolla18:20
* manjeets how nova_libvirt automatically restarts 18:21
manjeetsi killed 2 3 times and did reboor18:21
vhosakotall DB creation plays have run_once:True... dont think that should be removed and causing any issue...18:21
gmmahasdake: inc0: with enable_manila it still doesnt work18:22
inc0that would confirm your theory18:22
inc0sooo18:22
inc0hmm18:22
gmmahainc0: and if i remvoe run_once it will worjk18:22
inc0getting neutron-servers to top of the list will work18:22
gmmahainc0: right18:23
inc0and find all other places like that18:23
inc0we need to make it work for Mitaka18:23
gmmahaand I & ntpttr think its a less risky change18:23
vhosakotgmmaha: you'll need to first do  https://github.com/openstack/kolla/blob/master/doc/manila-guide.rst   before enabling manila18:23
inc0and we have only so many places that match this criterion18:23
sdakereading backlog18:23
inc0and focus on move to Ansible 2.0 in N18:23
inc0vhosakot, that was just to check if neutron fails18:23
sdakematch which criteria inc018:24
vhosakotinc0: ah ok18:24
sdakeinc0 that doesn't confirm the theory18:24
inc0has run_once: True and delegate_to18:24
inc0in same task18:24
*** dims_ has joined #openstack-kolla18:24
*** dims has quit IRC18:24
sdakeoh the runonce delgate_to theory18:24
sdakenot the boolean theory18:24
sdakeevery bootstrap has runonce and delegate to18:25
sdakehow do you propose to move them all to the top ;)18:25
vhosakotsdake: when does kolla move to Ansible 2.0 ?18:25
sdakegmmaha the unicorns ass thing is a quote from a riddick movie :)18:26
*** salv-orlando has quit IRC18:26
sdakeit wasnt dircted at anyone i just thought it was funny :)18:26
vhosakotsdake: when does kolla move to Ansible 2.0 ?18:26
gmmahasdake: the move to top is only needed for neutron18:26
gmmahaall the other services have the right server names at the top18:26
gmmahanova, keystone, heat, murano etc18:27
gmmahaits just neutron where compute is the top of the host list18:27
ntpttrgmmaha: +1, this would actually make the site.yml more consistent18:27
gmmahavhosakot: thanks for the link.. fixed the config, bulding the containers now and will test deploy18:28
gmmahainc0: give me afew18:28
sdakegmmaha ok here is my problem and i wnat you to repeat it in your own words if you dont mind :)18:28
gmmahasdake: :) sure..18:29
sdakewe don't know why delgate and run to when used in conjunction cause incorrect lookup of the inventory file18:29
sdakeso if someone does something different then you have done, kolla might break in a different way because of the same bug18:29
sdakemy proposal is to work around them by finding something that works and using that pattern instead18:30
sdakei reallly dont understand why my change didn't solve the problem18:31
sdakentpttr did you look at my suggested change based upo nvhosakots idea?18:31
gmmahasdake: let me phrase what i understood..18:31
vhosakotwhich idea.. we tried many things last night18:31
sdakevhosakot i tried something new this morning18:31
sdakecheck rview queue18:32
vhosakotah ok... will check18:32
*** Marga_ has quit IRC18:32
gmmahadelegate_to and run_once together isnt working as expected, instead of relying on a funky theory of the order of hosts will make a difference without understanding the full implications of it, you would rather have a change that is more reliable and quantifiable.18:33
gmmahasdake: is that a fair understanding18:33
sdakegmmaha bingo18:33
ntpttrsdake: the patch you put up for review you mean?18:34
sdakeif we had a root cause18:34
sdakentpttr yes18:34
sdakerather then "shits broke"18:34
ntpttrsdake: I thought that you were getting the same issue with that18:34
sdakei could go with a reorder18:34
sdakentpttr yes but i dont understand why18:34
ntpttrsdake: I think if we could contact some ansible experts, maybe some people who fixed this issue, we could get a clearer understanding of how to fix it18:35
sdakentpttr which makes me think something else is wrong in our playbooks18:35
vhosakotsdake: ntpttr gmmaha: I like sdake's fix to ask neutron_bootstrap_server from the operator... was this fix tested ?18:35
sdakemy wife said most ansibl  bugs are related to incorrect " and { usage in 1.918:35
ntpttrvhosakot: yeah it was tested, but it didn't work18:35
sdakevhosakot that would clearly work18:35
sdakehow about this18:35
vhosakotdid not work... why ? same error.. ah18:35
sdakewe define a new group18:35
sdakecalled [bootstrap]18:35
sdakevhosakot same error18:36
vhosakotah..18:36
sdakethen bootstrap code always runs on the bootstrap node18:37
ntpttrsdake: that would be cool, worth trying18:37
openstackgerritCarlos Cesario proposed openstack/kolla: Make keepalived virtual_router_id param configurable  https://review.openstack.org/30014318:37
sdakegmmaha can you try that out?18:37
ntpttrsdake: so a new role entirely?18:37
gmmahasdake: sure..18:38
vhosakoti dont think new role... a new group18:38
dims_sdake : rhallisey : removed apparmour completely, rebooted, then kolla-build, kolla-ansible deploy and things are better with libvirt and nova-compute containers18:38
sdakei think our current working theory is the fact that network and controller have the same nodes confuses ansible18:38
rhalliseydims_, nice18:38
dims_sdake : rhallisey : horizon seems to have tripped now http://paste.openstack.org/show/492644/18:38
dims_:)18:38
sdakeya horion is busted in my env too18:39
sdakedims are you running apache on your host?18:39
vhosakotit was fix it master... stale apache pid file.. 1 sec18:39
dims_sdake : nope, i stopped apache on my host18:40
sdakevhosakot read dims log18:40
sdakei haven't seeen this one before18:40
dims_sdake : quick start without haproxy18:41
*** dave-mccowan has quit IRC18:41
vhosakotno listening sockets available18:41
sdakethe address is already in use18:41
dims_this is all i have in my globals.yml http://paste.openstack.org/show/492648/18:41
inc0sdake, adding bootstrap group18:42
sdakeAddress already in use: AH0007218:42
vhosakothttps://bugs.launchpad.net/kolla/+bug/155703618:42
openstackLaunchpad bug 1557036 in kolla "httpd (pid 1) already running when starting keystone or horizon container" [Critical,Fix released] - Assigned to Sam Yaple (s8m)18:42
inc0would require us to either use some ansible magics to fill it out18:42
inc0ot make it users job which isn't too good either18:42
vhosakotsearch for   "Set the 'ServerName' directive globally to"    in that bug18:42
sdakentpttr not a new role a new group18:42
vhosakotah, the bug does not have  socket message... ok18:43
sdakei dont care how this neutron bug is fixed, i just dont want it to replicate to other parts of our code base where we reuse this same pattern18:45
sdakeneutron-servers[0] is resolving to compute[0]18:45
gmmahainc0: vhosakot: neutron issue doesnt get fixed iwth the manila enabled18:46
vhosakotI dont understand where and how manila came from :)18:46
gmmahasdake: vhosakot: you still want me to test the bootstrap group?18:46
gmmahaand guessing you would like a nova_bootstrap, neutron_bootstrap etc?18:46
sdakegmmaha lets try that18:46
vhosakotI'm thinking about the new [bootstrap] group... code must be updated to use this new group also18:46
gmmahavhosakot: that was an inc0 suggestion18:47
vhosakothow will it be _used_ in neutron bootstrap ?18:47
sdakedelegates_to: bootstrap18:47
sdakebootstrap may onl yhve 1 entry18:48
sdakepossible anible magic to populate it with controller[0]18:48
sdakei dont know how to do that last bit18:48
ntpttrsdake: +1 sounds good. Just add the bootstrap group in the inventory and maybe make it a child of control by default18:49
ntpttrthen you can delegate to bootstrap[0] and it should work18:49
sdakeits an ugly ugly hack but we are out off other options18:50
gmmahasdake: let me see how it works18:50
sdakewhy does the ubuntu source deploy gate always fail18:51
* sdake groans18:51
sdakehttp://logs.openstack.org/91/299791/1/check/gate-kolla-dsvm-deploy-ubuntu-source/3cf5406/console.html#_2016-03-31_07_55_47_16318:53
vhosakotsdake: becasue of    http://logs.openstack.org/91/299791/1/check/gate-kolla-dsvm-deploy-ubuntu-source/3cf5406/console.html#_2016-03-31_07_55_26_98518:53
sdakevhosakot is there a bug for that18:54
huikangsdake, I remember there is a PS for that18:54
huikangresolving the hostname for rabbitmq18:54
sdakehuikang i think this is  a separate issue18:55
huikangsdake, I see18:55
openstackgerritMichal Rostecki proposed openstack/kolla: Fix IP resolve check for RabbitMQ on AIO  https://review.openstack.org/30015218:55
sdakevhosakot if you llook at y link the failure is different18:55
sdakefolks if you know how to fix these  gat ebugs make it a prioirty to fix them18:57
sdakethey slow down the review process significantly18:57
sdakei've got a 30 min meeting - bbiaf :)18:57
vhosakotlet me check the queue for the PS proposed to fix it18:57
sdakesome people may need to take over sam's reviews18:58
sdakehe was working on alot of the ubuntu gating problems18:58
*** openstackgerrit has quit IRC19:03
*** openstackgerrit has joined #openstack-kolla19:04
*** dave-mccowan has joined #openstack-kolla19:04
*** rajathagasthya has quit IRC19:05
*** Marga_ has joined #openstack-kolla19:09
*** alyson_ has joined #openstack-kolla19:12
*** dwalsh has quit IRC19:14
elmikosdake: posted the a message about threat analysis, but forget to add a [kolla] tag, sorry :/19:20
elmikofyi, http://lists.openstack.org/pipermail/openstack-dev/2016-March/091075.html19:21
*** rajathagasthya has joined #openstack-kolla19:26
openstackgerritRyan Hallisey proposed openstack/kolla: Nova-compute should chown -R /var/lib/nova  https://review.openstack.org/30018019:29
*** dwalsh has joined #openstack-kolla19:30
SiRiuS_nihilifer, ping19:30
openstackgerritRyan Hallisey proposed openstack/kolla: Add remove apparmor reminder to the quickstart  https://review.openstack.org/30018419:37
*** mgoddard has quit IRC19:41
*** sdake_ has joined #openstack-kolla19:43
nihiliferSiRiuS_: pong19:43
sdake_hey folks19:44
*** sdake has quit IRC19:44
sdake_I know this is an extremely bad time19:44
sdake_but I have an emergency that I need to deal with thta will consume the next 24 hours of my life that i wont get back19:44
SiRiuS_nihilifer, I tried to deploy kolla-mesos all-in-one, and now it deploys the apps19:44
SiRiuS_nihilifer, but I get an error19:44
sdake_i am going to drop off irc during that period19:45
sdake_if something pressing needs attentin please use email19:45
*** dwalsh has quit IRC19:45
sdake_please work together as we always do to get the job done on the remaining bugs where possible ;)19:45
SiRiuS_nihilifer, http://paste.openstack.org/show/492661/19:45
SiRiuS_that is for mariadb19:45
SiRiuS_I tried memchached as well, but I get the same error19:46
nihiliferSiRiuS_: you're doing bare metal deployment or vagrant?19:46
SiRiuS_vagran19:46
SiRiuS_the mesos cluster is deployed19:46
SiRiuS_but the apps don't deploy on multi-node at all19:47
SiRiuS_and an all-in-one i get the error above19:47
SiRiuS_but at least they deploy19:47
mlima_are gates ok?19:47
SiRiuS_nihilifer, that log is from docker logs19:49
nihiliferSiRiuS_: what are your interfaces and ip addresses?19:49
nihiliferSiRiuS_: i mean, the output of "ip a"19:50
SiRiuS_nihilifer,  http://paste.fedoraproject.org/347983/1459453819:51
nihilifereth2 didn't receive ip address from bridge, that may be a problem19:51
nihiliferyou're using libvirt or virtualbox?19:52
SiRiuS_nihilifer, virtualbox, but isn't eth2 used for the neutron external network ?19:52
SiRiuS_nihilifer, here is my cfgs19:53
SiRiuS_http://paste.fedoraproject.org/347985/59453903/19:53
g3ekhello, during build I have this :            INFO:kolla.cmd.build:base:Step 3 : LABEL kolla_version "0.0.1"         instead of                   INFO:kolla.cmd.build:base:Step 3 : LABEL kolla_version "2.0.0"19:53
SiRiuS_and http://paste.fedoraproject.org/347987/45391014/19:53
g3ekDo someone can help me to put it back to 2.0.019:53
g3ek?19:53
*** sdake_ has quit IRC19:56
nihiliferSiRiuS_: yes, it is. but the start script inside containers wants to be aware both of private and public interface19:56
SiRiuS_nihilifer, I could give it an address, but let me try something real quick19:57
nihiliferplease try with assigning an addres, that should help19:57
nihiliferin general, the start script is fetching variables which are used for generating configuration files19:58
nihiliferso to generate i.e. neutron configs well, it has to be aware of all ifaces19:58
gmmahavhosakot: the suggestion from sdake works..20:06
gmmahantpttr: inc0: ^^20:06
gmmahashall i go ahead and update his patch?20:07
gmmahanevermind20:07
gmmahait was nova..20:07
gmmahabah!20:07
*** salv-orlando has joined #openstack-kolla20:08
sbezverkfolks, I need a bit help from git expert who worked with patch stream, anybody out there? ;-)20:13
manjeetssdake kolla need warmup and test fires to get ready for bigger shot is a sure thing20:14
*** inc0 has quit IRC20:20
vhosakotsbezverk: what is patch stream ?20:21
g3ekhello, I found where the problem is, but I dont know where the default var is set : /usr/local/share/kolla/docker/base/Dockerfile.j2 : {{ kolla_version }} seems to be set to 0.0.1 instead of 2.0.0. How can I change it ?20:23
sbezverkvhosakot I have three patches sitting in the same kolla folder20:26
vhosakotthree different branches ?20:26
sbezverkvhosakot nope I split iscsi patch into three, sdake walked me through the process.. but I forgot to ask him how to commit changes if there is change only in one of those patches..20:27
gmmahasbezverk: which patch has the change? lets say patch 2 has the change, this is what i would do20:28
patchbotgmmaha: https://review.openstack.org/#/c/2/20:28
gmmahacherry-pick 1st patch, take the new updated 2nd patch, commit it, cherry-pick 3rd patch and git review20:29
gmmahathe 1st patch should go without change and the other two patches will get updated20:29
vhosakotsbezverk: git branch <name of the branch that has the change>, git add *, git commit, git review.... is this what you're looking for ?20:30
sbezverkvhosakot but if the file I changed is already exist, I still need to git add {file}??20:31
vhosakotyes... to add you changes to an already existing file in the repo20:31
sbezverkvhosakot thanks, let me try it20:32
vhosakotsure.. np20:32
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Add integration with Kolla infrastructure  https://review.openstack.org/30000420:34
sbezverkvhosakot, it looks like it worked :-)20:35
vhosakotsbezverk: ah ok.. cool.. great! :)  will review when I get a chance!20:36
sbezverkvhosakot, please do and do not forget now there are three parts!20:36
vhosakotyep.. saw that :)20:36
*** unicell has quit IRC20:42
*** ayoung has quit IRC20:43
SiRiuS_nihilifer, cool it works now (took some time because of buggy vbox networking), eth2 needed an IP address20:44
SiRiuS_nihilifer, but here is something interesting20:44
SiRiuS_nihilifer, in the globals.yml I should have multimode set to "no"20:45
gmmahavhosakot: the suggestion from sdake didnt work20:46
gmmahadelegate_to is really busted in ansible 1.9.X20:47
gmmahalet me try one more thing20:47
SiRiuS_nihilifer, because I'm deploying all-in-one20:50
SiRiuS_nihilifer, but if I do that, it does not deploy the app20:50
SiRiuS_nihilifer, the app remains in "waiting" state in marathon20:51
ccesariorhallisey, ping!?20:51
*** dave-mccowan has quit IRC20:51
rhalliseycbaesema, hey20:51
rhalliseyccesario, hey20:51
SiRiuS_nihilifer, it's weird because the only way I can deploy an app (like mariadb) is if a deploy all-in-one but with the multinode  set to "yes"20:52
ccesariorhallisey, I need an opinion ....  https://review.openstack.org/#/c/300143/1/ansible/roles/haproxy/templates/keepalived.conf.j2@32  needs a diferent Id too.... when external address is set20:53
patchbotccesario: patch 300143 - kolla - Make keepalived virtual_router_id param configurable20:53
ccesariorhallisey, what is the best way to do it ? create other variable too ?20:53
ccesariokeepalived_virtual_router_id_internal  and keepalived_virtual_router_id_external ?20:54
rhalliseyccesario, I'll comment20:55
rhalliseyya20:55
rhallisey^ that would work20:55
ccesariorhallisey, thanks20:56
rhalliseyno prob20:56
dims_rhallisey : gmmaha : hurray, got a live one..deployed a cirros vm20:58
rhalliseydims_, nice!20:58
dims_just have to doc the apparmor thing20:58
g3ekwhere can I found the code of this : version.cached_version_string()20:58
dims_g3ek : http://codesearch.openstack.org/?q=def%20cached_version_string&i=nope&files=&repos=20:59
g3ekdims_: thanks, I dont know why the content of my cached version is 0.0.1 instead of 2.0.0. Someone know where can I change it?21:01
rhalliseydims_, https://review.openstack.org/#/c/300184/21:02
patchbotrhallisey: patch 300184 - kolla - Add remove apparmor reminder to the quickstart21:02
rhalliseydims_, add to that if there's more to it21:03
*** unicell has joined #openstack-kolla21:05
*** fbarilla has joined #openstack-kolla21:12
gmmahadims_: awesome.. guesssing it was apparmor21:15
vhosakotg3ek: if you use master, you should get 2.0.021:15
gmmahavhosakot: none of my tries are working :(21:15
gmmahaand i have a feeling i am starting to get brain-dead on this issue..21:16
gmmahashall i throw up a patch on this for you to take a look at and see how to best re-structure it ?21:16
vhosakotkolla_version is not set by the user/operator I think21:16
vhosakotg3ek: ^^21:16
*** wuhg has joined #openstack-kolla21:16
g3ekvhosakot : I know, the problem is that I have clone the master repo and I dont know why the version i get is now 0.0.1. I just found that my pip list show that kolla is 0.0.1-dev something21:18
vhosakotg3ek: my output21:19
vhosakot$ pip list | grep kolla21:19
vhosakotkolla (2.0.0.0rc2.dev151)21:19
vhosakotg3ek: ^^^21:19
vhosakotg3ek: after cloning the master repo, did you install it as well ?21:19
nihiliferSiRiuS_: hmmm... can you post the exact configuration in marathon of one of these apps?21:19
nihiliferprobably something is bad with "constraints"21:20
g3ekyes with pip install --upgrade . (from the clone folder)21:20
g3ekvhosakot: check above21:20
vhosakotg3ek: can you try this ?21:20
vhosakotpip uninstall kolla21:20
vhosakotclone master21:20
vhosakotpip install kolla21:20
dims_gmmaha : yep it was apparmor21:21
g3ekIt work, but I did a lot of modification to the clone repository and I cant lose them ... I will try to merge with caution...21:21
gmmahadims_: coool.. thanks for confirming21:22
dims_rhallisey : +1'ed21:22
*** achanda has quit IRC21:22
dims_rhallisey : this was my super simple globals.yml https://gist.github.com/dims/04a046e7286f73a87274f2a7af37f75221:22
SiRiuS_nihilifer, http://picpaste.com/3WMuzaIR.png21:25
SiRiuS_for memcached21:25
SiRiuS_this is all-in-one but with the multimode variable in globals.yml set to "yes"21:26
*** banix has quit IRC21:27
*** haplo37 has joined #openstack-kolla21:29
*** sdake has joined #openstack-kolla21:30
*** ccesario_ has joined #openstack-kolla21:34
sdakevhosakot around?21:35
vhosakotyep\21:36
gmmahavhosakot: sdake: your suggestion worked.. let me update your patch21:37
vhosakotsdake: o/21:37
sdakei dumped state in prep for emergency21:38
sdakeso i'll be back when its over ;)21:38
*** fbarilla has quit IRC21:38
*** ccesario_ has quit IRC21:40
*** haplo37 has quit IRC21:42
vhosakotg3ek: you dont need to... installing master will install 2.0.0.0rc2.dev15121:48
openstackgerritGanesh Maharaj Mahalingam proposed openstack/kolla: Workaround ansible bug related to delegate_to  https://review.openstack.org/29980321:48
gmmahavhosakot: ^^21:52
gmmahawith this patch it seems to work fine21:52
gmmahai will try and test more tonight if possible21:52
gmmahabut this seems ok21:52
sdakegmmaha does that patch work with the neutron bootstrap thing you sent up22:03
sbezverksdake what emergecy you are talking about? Something happened in the area?22:04
g3ekvhosakot : Thanks a lot! I finally make it work again! So I had to change the pip install like you suggest : pip install kolla==2.0.0.0rc2.dev151 instead of pip install . (from the folder). With that I have the good version and everything works again. I just dont understand why it was working before and not anymore (the pip install .)22:04
sdakesbezverk nah just personal thing22:04
sdakenothing to be concerned about22:04
*** unicell has quit IRC22:04
sbezverksdake ok :-) I thought you have incoming avalanche or something22:04
sdakeavalancheof heat in arizona incoming;)22:05
vhosakotg3ek: cool, cheers! :)22:07
sbezverksdake sorry not strong on US geography ;-)22:10
*** huikang has quit IRC22:11
*** rajathagasthya has quit IRC22:23
*** unicell has joined #openstack-kolla22:38
*** dave-mccowan has joined #openstack-kolla22:40
*** SiRiuS_ has quit IRC22:43
*** ayoung has joined #openstack-kolla22:45
*** dave-mccowan has quit IRC22:50
*** sdake has quit IRC22:57
*** weiyu has joined #openstack-kolla23:00
*** blahRus has quit IRC23:05
openstackgerritCarlos Cesario proposed openstack/kolla: Make keepalived virtual_router_id param configurable  https://review.openstack.org/30014323:08
*** sdake has joined #openstack-kolla23:09
*** weiyu has quit IRC23:10
*** salv-orlando has quit IRC23:11
*** gm__ has joined #openstack-kolla23:11
*** sdake_ has joined #openstack-kolla23:12
*** sdake has quit IRC23:13
*** gm__ has quit IRC23:13
*** weiyu_ has joined #openstack-kolla23:16
*** ccesario_ has joined #openstack-kolla23:16
ccesario_vhosakot: ping?23:16
vhosakotccesario_: pong23:17
ccesario_vhosakot: about your comment https://review.openstack.org/#/c/300143/23:17
patchbotccesario_: patch 300143 - kolla - Make keepalived virtual_router_id param configurable23:17
ccesario_why is not needed ?  could you please explain ?23:17
vhosakotccesario_: sure23:18
ccesario_because, it is needed when we deploy two or more clouds using "single"  kolla deployer23:18
ccesario_rhallisey follow me in the tests today at morning...23:19
gmmahasdake_: yes it does23:19
vhosakot"vrrp_instance kolla_internal_vip"  already has "internal" in it which is different from "vrrp_instance kolla_external_vip" that has "external" in it...23:19
gmmahaworked on my local setup23:19
gmmahawe have been debugging the last gew days23:19
sdake_gmmaha so does it work without set_facts?23:20
vhosakotccesario_: so, why do you think vrrp_instance kolla_internal_vip   must be   vrrp_instance kolla_internal_vip_5123:20
vhosakotinternal and external are already differentiated23:20
gmmahasdake_: hmm, dont think so.. i tried setting thew variable in other places and it wasnt playing along well23:20
sdake_so set_facts is global23:22
sdake_i think that makes sense23:23
sdake_that is what I wanted in my original change23:23
sdake_I woonder though if the other change is needed in your patch23:23
openstackgerritGanesh Maharaj Mahalingam proposed openstack/kolla: Workaround ansible bug related to delegate_to  https://review.openstack.org/29980323:24
ccesario_vhosakot: weel, in my tests using the same network segment for both clouds, the deploy stop when the virtual_router_id and vrrp_instance it was set previously23:24
gmmahasdake_: which other change?23:24
gmmahawhere i am changing it from delegate_to to when?23:25
gmmahayeah, without that i found those respective plays dont happen and skip like before23:25
sdake_https://review.openstack.org/#/c/299803/3/ansible/roles/neutron/tasks/deploy.yml23:25
patchbotsdake_: patch 299803 - kolla - Workaround ansible bug related to delegate_to23:25
gmmahai had to dump run_once and force it to do that23:25
vhosakotccesario_: yes, I agree about the virtual_router_id being different for internal and external23:25
vhosakotccesario_: here is what I mean23:25
gmmahasdake_: hmmm.. we can try and test without it23:25
gmmahabut it worked this way for sure23:25
vhosakotccesario_: first cloud - 51 and 5223:25
vhosakotccesario_: second cloud - 53 and 5423:26
sdake_delegate_to doesn't work?23:26
sdake_I hadn't noticed that changed to a when23:26
gmmahasdake_: yeah.. not in the play for sure23:26
sdake_we need run_once: True23:26
*** ayoung has quit IRC23:26
gmmahasdake_: if thats there. it still bails out with the first ocmpute node23:26
vhosakotso, the internal ID (51) of first cloud will not conflict with internal ID (53) of second cloud23:26
ccesario_vhosakot: yes yes, but too when the vrrp_instance is equal  it caused problem too....23:27
sdake_http://docs.ansible.com/ansible/playbooks_delegation.html23:27
vhosakotccesario_: ah23:27
ccesario_therefore I force the rename23:27
*** weiyu_ has quit IRC23:27
ccesario_did you understand ?23:27
vhosakotccesario_: after changing, did it work for both clouds ?23:28
ccesario_the name make reference to the router id23:28
ccesario_yes yes23:28
ccesario_:)23:28
gmmahasdake_: let me test by adding run_once back23:28
gmmahabut i doubt it works23:28
ccesario_let me paste the keepalived content23:28
vhosakotplease23:28
sdake_If you want to perform a task on one host with reference to other hosts, use the ‘delegate_to’ keyword on a task. This is ideal for placing nodes in a load balanced pool, or removing them. It is also very useful for controlling outage windows. Using this with the ‘serial’ keyword to control the number of hosts executing at one time is also a good idea:23:28
sdake_i dont understand why delegate_to is used instead of when in the current code23:29
ccesario_vhosakot: http://pastebin.com/5beCtH0P23:31
sdake_delegated facts are only available in 2.0 which is probably why set_facts with delegate_to doesnt work23:31
sdake_By default, any fact gathered by a delegated task are assigned to the inventory_hostname (the current host) instead of the host which actually produced the facts (the delegated to host). In 2.0, the directive delegate_facts may be set to True to assign the task’s gathered facts to the delegated host instead of the current one.:23:32
sdake_this documentation implies he issue is where the facts are produced23:32
sdake_If you want to run a task that's associated with a host, but on different host, you should try delegate_to.23:34
sdake_i think the issue is the facts are not delgated with delegate_to23:35
sdake_but delegate_to seems more correct23:35
sdake_which is why when wasn't used23:35
sdake_true/false?23:35
gmmahasdake_: with run_once included it fails.. http://paste.openstack.org/show/492684/23:36
sdake_see liue 2 and line 523:36
sdake_same hostname23:36
sdake_06 is  a compute node right?23:37
gmmahasdake_: not using delegate_to here.. Just run_once with when23:37
gmmahasdake_: yeah23:37
sdake_why is it in the neutron server list?23:37
gmmahaso the facts are gathered given to the curren host once and done23:37
sdake_or does when just run across all hosts?23:38
gmmahai think for the plan it runs it through the list of hosts it created for it..23:38
gmmahaand the ordering has to do somethign with it23:38
gmmahaso it triies on the first host there (compute -> 06) and tries once to run it..23:38
gmmahairrespective of the outcome its done23:38
sdake_this is why delegate_to is running on 0623:39
gmmahasoemone had created a feature request to add run_once_until_success for ansible23:39
gmmaharight23:39
gmmahabut its not delegating it to the variable outside23:39
gmmahaare you thinking if we use something otehr than set_fact delegate_to wil lwork?23:39
sdake_no but i think we want delegte_to23:39
gmmahasdake_: i have to hit the road to avoid traffic.. will be back online in half hour23:40
sdake_sounds good23:40
sdake_delegate_to to me seems like an optimization23:40
sdake_what we really need here is delegate_facts23:40
sdake_can you git review the patch that generated that last log?23:41
*** vhosakot has quit IRC23:42
sbezverksdake_ I want to add a variale pointing to the location of custom rpms which kolla's user would like to add to the base? do you think it would be supported by community?23:42
sdake_that already exissts23:43
sdake_config option to build23:43
sdake_bbi1 hr need quick powernap23:43
*** sdake_ has quit IRC23:43
sbezverksdake_ ok23:43
*** unicell has quit IRC23:57

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