Sunday, 2018-05-20

*** Adri2000 has quit IRC00:13
*** Adri2000 has joined #openstack-ansible00:21
openstackgerritMerged openstack/openstack-ansible master: zuul: Make openSUSE metal jobs voting  https://review.openstack.org/56877800:37
*** tux_ has joined #openstack-ansible00:56
tux_I am building multi-node openstack, 3 infra and 1 compute and just encounter error when i run " openstack-ansible setup-infrastructure.yml"  but interesting infra1 and infra2 didn't get error but infra3 failed..01:01
tux_http://paste.openstack.org/show/721328/01:01
tux_I am using pike 16.0.1001:04
tux_Do you think this is related to https://bugs.launchpad.net/networking-midonet/+bug/173031401:05
openstackLaunchpad bug 1636567 in openstack-ansible "duplicate for #1730314 devstack mitaka installation fails with error "Running setup.py bdist_wheel for libvirt-python: finished with status 'error'" in Ubuntu 16.10" [High,Confirmed]01:05
tux_why infra1 and infra2 didn't fail?01:05
tux_I am using CentOS701:06
*** rudysp has quit IRC01:07
*** klatouch has quit IRC01:07
*** tux_ has quit IRC01:10
*** spsurya has joined #openstack-ansible01:11
*** markvoelker has quit IRC01:31
*** tux_ has joined #openstack-ansible01:45
*** vnogin has joined #openstack-ansible01:47
*** klatouch has joined #openstack-ansible01:57
*** vnogin has quit IRC02:21
*** bhujay has joined #openstack-ansible02:28
*** dave-mccowan has joined #openstack-ansible02:55
tux_Now my build stuck at repo_build : Wait for the venvs builds to complete03:06
-tux_- TASK [repo_build : Wait for the venvs builds to complete] ***************************************************************************************************03:06
-tux_- Saturday 19 May 2018 22:46:02 -0400 (0:00:47.651) 0:36:32.308 **********03:06
-tux_- FAILED - RETRYING: Wait for the venvs builds to complete (180 retries left).03:06
-tux_- FAILED - RETRYING: Wait for the venvs builds to complete (179 retries left).03:07
-tux_- FAILED - RETRYING: Wait for the venvs builds to complete (178 retries left).03:07
-tux_- FAILED - RETRYING: Wait for the venvs builds to complete (177 retries left).03:07
-tux_- FAILED - RETRYING: Wait for the venvs builds to complete (176 retries left).03:07
-tux_- FAILED - RETRYING: Wait for the venvs builds to complete (175 retries left).03:07
-tux_- FAILED - RETRYING: Wait for the venvs builds to complete (174 retries left).03:07
-tux_- FAILED - RETRYING: Wait for the venvs builds to complete (173 retries left).03:07
*** dave-mccowan has quit IRC03:12
*** vnogin has joined #openstack-ansible03:18
tux_I found my /tmp directory is full on infra3 node03:35
*** weezS has joined #openstack-ansible03:37
*** vnogin has quit IRC03:51
*** armaan has quit IRC04:13
*** armaan has joined #openstack-ansible04:13
*** nsingh has joined #openstack-ansible04:17
*** niraj_singh has quit IRC04:19
*** nsingh has quit IRC04:26
*** spsurya has quit IRC05:15
*** vnogin has joined #openstack-ansible05:19
*** cjloader has joined #openstack-ansible05:19
*** klatouch has quit IRC05:20
*** klatouch has joined #openstack-ansible05:20
*** chhagarw has joined #openstack-ansible05:21
*** rudysp has joined #openstack-ansible05:23
*** cjloader has quit IRC05:24
tux_ internal_lb_vip_address: 172.29.236.9   ( do we need to configure internal_lb_vip_address manually or ansible will create itself? )05:25
*** tux_ has quit IRC05:32
bhujaytux_:  u need to  provide a vip as you have shown  which ansible will configure it automatically in haproxy05:34
*** vnogin has quit IRC05:51
*** radeks has joined #openstack-ansible05:55
*** portante has quit IRC06:02
*** portante has joined #openstack-ansible06:02
*** radeks_ has joined #openstack-ansible06:18
*** cjloader has joined #openstack-ansible06:19
*** cjloader has quit IRC06:24
*** armaan has quit IRC06:34
*** armaan has joined #openstack-ansible06:34
*** armaan has quit IRC06:40
*** armaan has joined #openstack-ansible06:40
*** chhagarw has quit IRC06:53
*** rudysp has quit IRC07:02
*** radeks has quit IRC07:05
*** radeks_ has quit IRC07:05
*** weezS has quit IRC07:10
*** chhagarw has joined #openstack-ansible07:15
*** persia has quit IRC07:36
*** persia has joined #openstack-ansible07:36
*** gkadam has joined #openstack-ansible07:44
*** gkadam has quit IRC07:48
*** armaan has quit IRC07:49
*** armaan_ has joined #openstack-ansible07:49
*** vnogin has joined #openstack-ansible07:50
*** armaan_ has quit IRC07:53
*** armaan has joined #openstack-ansible07:54
*** vnogin has quit IRC07:59
*** chhagarw has quit IRC08:01
*** vnogin has joined #openstack-ansible08:02
*** vnogin has quit IRC08:21
*** armaan has quit IRC08:34
*** armaan has joined #openstack-ansible08:34
*** vnogin has joined #openstack-ansible09:18
*** vnogin has quit IRC09:52
*** yolanda has joined #openstack-ansible09:59
*** yolanda_ has quit IRC10:02
*** bhujay has quit IRC10:03
*** bhujay has joined #openstack-ansible10:04
*** tosky has joined #openstack-ansible10:04
*** armaan has quit IRC10:24
*** armaan has joined #openstack-ansible10:25
*** armaan has quit IRC10:30
*** vnogin has joined #openstack-ansible10:36
*** vnogin has quit IRC11:00
*** markvoelker has joined #openstack-ansible11:37
*** markvoelker has quit IRC12:17
*** yolanda has quit IRC12:27
*** dave-mccowan has joined #openstack-ansible12:43
*** dave-mccowan has quit IRC12:56
*** tux_ has joined #openstack-ansible13:03
tux_??13:06
*** markvoelker has joined #openstack-ansible13:06
tux_what are these to IP address in lxc-ls -f output?14:18
tux_ostack-controller-02_aodh_container-0b5bfe6b                RUNNING 1         onboot, openstack 10.0.3.23, 192.168.100.13614:18
odyssey4metux_ yes, you must provide an ip - but you don't have to bind it if you're using keepalived14:18
tux_i didn't specify 10.0.3.23 anywhere14:18
*** kysse has quit IRC14:18
odyssey4methe first ip is the container's eth0, it's automatically allocated by LXC and host-only... all traffic from that exits the host via a NAT14:19
tux_Oh! so every lxc VM has two IPs14:20
tux_Got it!14:20
tux_@odyssey4me - You are saying ansible create HAproxy internal IP itself right?14:21
odyssey4metmux no, I'm saying you provide the IP in config14:21
odyssey4metux_ ^14:21
*** sawblade6 has quit IRC14:22
tux_I provided IP but should i need to manually configure on host?14:22
tux_i meant create interface br-mgmt and put IP there?14:22
odyssey4mehave you implemented the keepalived config? if so, it will bind the ip you provide14:23
odyssey4mesee https://docs.openstack.org/openstack-ansible/latest/user/prod/example.html#user-variables14:23
odyssey4meunless you only have one host?14:23
tux_I didn't tweak any config in variable yaml file. i believe keepalived is default ON  (on multi node)14:24
*** armaan has joined #openstack-ansible14:24
tux_I have 3 node infra cluster14:24
odyssey4metux_ without those vars, keepalived will not bind the address - you have to tell it where to bind14:25
tux_so this line saying bind to haproxy_keepalived_internal_interface: br-mgmt14:26
*** ivve has joined #openstack-ansible14:26
tux_I have check haproxy config and my external IP is correctly configure in config file. but i didn't see anywhere internal IP so i thought i have to put internal_vip ip on br-mgmt14:28
odyssey4mecheck the keepalived config - it's keepalived that will bind the address14:28
openstackgerritAndy Smith proposed openstack/openstack-ansible master: Restore namespace per service for oslo.messaging update  https://review.openstack.org/56944514:28
tux_I messed up something in my cluster i think :(14:31
tux_I forgot to put my LB IP in used_ip list and LXC gave that ip to one of container :(14:32
tux_How do i fix that or do i need to uninstall everything and restart process?14:32
tux_odyssey4me: should i run destroy_container.yaml ?14:33
*** armaan has quit IRC14:38
*** armaan has joined #openstack-ansible14:38
*** cmart has joined #openstack-ansible14:40
*** tux_ has quit IRC14:41
*** cmart has quit IRC14:42
*** klatouch has quit IRC14:44
*** tosky has quit IRC15:10
*** tosky has joined #openstack-ansible15:13
*** markvoelker has quit IRC15:21
*** markvoelker has joined #openstack-ansible15:22
*** markvoelker has quit IRC15:27
*** kysse has joined #openstack-ansible15:31
*** sawblade6 has joined #openstack-ansible15:49
*** vnogin has joined #openstack-ansible16:00
*** rudysp has joined #openstack-ansible16:04
*** lbragstad has joined #openstack-ansible16:11
*** klatouch has joined #openstack-ansible16:21
*** esberglu has joined #openstack-ansible16:24
*** esberglu has quit IRC16:26
*** yolanda has joined #openstack-ansible16:29
*** markvoelker has joined #openstack-ansible16:38
*** armaan has quit IRC16:43
*** EvilienM is now known as EmilienM16:50
*** radeks has joined #openstack-ansible16:52
*** radeks_ has joined #openstack-ansible16:53
*** klatouch has quit IRC17:27
*** klatouch has joined #openstack-ansible17:31
*** markvoelker has quit IRC17:49
*** tux_ has joined #openstack-ansible17:58
*** markvoelker has joined #openstack-ansible17:59
tux_I did   openstack-ansible lxc-containers-destroy.yml  but i am still seeing containers are running. what is the deal here?18:01
*** ethfci has quit IRC18:27
*** lbragstad[m] has quit IRC18:27
*** toan has quit IRC18:27
*** mgagne has quit IRC18:27
*** dankolbrs has quit IRC18:27
*** jmccrory has quit IRC18:27
*** dankolbrs has joined #openstack-ansible18:27
*** jmccrory_ has joined #openstack-ansible18:27
*** mgagne has joined #openstack-ansible18:27
*** ethfci has joined #openstack-ansible18:27
*** mgagne is now known as Guest7432218:27
*** ebbex has quit IRC18:27
*** ebbex has joined #openstack-ansible18:27
*** toan has joined #openstack-ansible18:28
*** jmccrory_ is now known as jmccrory18:28
*** CobHead has quit IRC18:30
*** CobHead has joined #openstack-ansible18:32
*** lbragstad[m] has joined #openstack-ansible18:42
*** lbragstad[m] has quit IRC18:43
*** CobHead has quit IRC18:43
*** ivve has quit IRC18:43
*** Adri2000 has quit IRC18:43
*** kaiokmo has quit IRC18:43
*** mhayden has quit IRC18:43
*** tinwood has quit IRC18:43
*** MasterofJOKers has quit IRC18:43
*** kaiokmo has joined #openstack-ansible18:44
*** MasterofJOKers has joined #openstack-ansible18:44
*** tinwood has joined #openstack-ansible18:44
*** Adri2000 has joined #openstack-ansible18:44
*** mhayden has joined #openstack-ansible18:44
*** CobHead has joined #openstack-ansible18:45
*** charz has quit IRC18:46
*** exodusftw has quit IRC18:46
*** klatouch has quit IRC18:48
*** exodusftw has joined #openstack-ansible18:49
*** charz has joined #openstack-ansible18:49
*** lbragstad[m] has joined #openstack-ansible18:50
*** armaan has joined #openstack-ansible18:56
*** armaan has quit IRC18:57
*** armaan has joined #openstack-ansible18:58
*** ivve has joined #openstack-ansible19:00
*** radeks__ has joined #openstack-ansible19:04
*** radeks has quit IRC19:06
*** dxiri has joined #openstack-ansible19:13
*** lbragstad has quit IRC19:18
*** markvoelker has quit IRC19:23
*** fghaas has joined #openstack-ansible19:32
*** fghaas has quit IRC19:55
*** fghaas has joined #openstack-ansible19:57
*** radeks__ has quit IRC19:59
*** weezS has joined #openstack-ansible19:59
*** weezS has quit IRC20:14
idlemindtux you can always delete the container that is using the ip and osa will automatically rebuild that container w/a new ip20:18
idlemindtux in the case of multiple haproxy hosts the ip does not need to be bound or configured manually at the linux level that will happen during the keepalived ansible playbooks and you'll see the ip live on a single haproxy server at a time20:18
idlemindtux https://docs.openstack.org/openstack-ansible/latest/admin/maintenance-tasks/containers.html20:19
idlemind^^ the destroy and recreate containers section20:19
odyssey4metux_ and if you ran the delete playbook for the containers, and there are still some running, then it sounds like you somehow previously had some running (maybe inventory changes happened)... so you'd have to clean those up manually from the hosts using "lxc-stop -n <container name>; lxc-destroy -n <container-name>"20:22
*** dxiri has quit IRC20:24
tux_idlemind: Thanks!! i got it, keepalived create floating IP between 3 node for LB20:25
tux_idlemind: does keepalived create floating ip for both external_vip and internal_vip for haproxy?20:26
*** dxiri has joined #openstack-ansible20:26
*** lbragstad has joined #openstack-ansible20:28
*** dxiri has quit IRC20:30
*** vnogin has quit IRC20:51
*** markvoelker has joined #openstack-ansible20:52
*** vnogin has joined #openstack-ansible20:53
*** vnogin has quit IRC20:54
*** tux_ has quit IRC21:03
*** dave-mccowan has joined #openstack-ansible21:34
*** lbragstad has quit IRC21:34
*** dave-mccowan has quit IRC21:59
*** tosky has quit IRC22:28
*** tux_ has joined #openstack-ansible22:30
*** tux_ has quit IRC22:31
*** fghaas has quit IRC22:48
*** lbragstad has joined #openstack-ansible22:59
*** tux_ has joined #openstack-ansible23:17
*** tux_ has quit IRC23:17
*** pmannidi has joined #openstack-ansible23:35
*** masber has joined #openstack-ansible23:37
*** pabelanger has quit IRC23:38
*** pabelanger has joined #openstack-ansible23:38
*** lbragstad has quit IRC23:54
*** rudysp has quit IRC23:58

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