Tuesday, 2016-08-16

*** v1k0d3n has quit IRC00:02
Pavohmmm seems like something changed00:10
Pavogetting error that seems to be related to ports_checks.yml located in /usr/share/kolla/ansible/roles/prechecks/tasks/00:10
Pavohttp://pastebin.com/qYbyXzzA00:11
*** diogogmt has joined #openstack-kolla00:11
Pavonvm figured it out, 1 of the interfaces on each node wasn't up lol00:18
*** signed8bit is now known as signed8bit_Zzz00:30
*** hieulq has joined #openstack-kolla00:36
*** duonghq has joined #openstack-kolla00:40
Pavoanyone know what this error means?00:46
Pavohttp://pastebin.com/8cYVYE3d00:46
Pavothis is the same spot I got stuck at before00:48
Pavobut also getting this TASK [rabbitmq : Check if all rabbit hostnames are resolvable] *****************00:50
Pavook: [192.168.1.11] => (item=192.168.1.11)00:50
Pavoso.. I have no clue were to start debugging00:50
*** phuongnh has joined #openstack-kolla00:58
openstackgerritWei Cao proposed openstack/kolla: Add solum container  https://review.openstack.org/35540801:00
sbezverkPavo: you need to make sure that destination host where you deploy kolla to, its name should be dns resolved to 192.168.1.1101:04
Pavothey are01:04
Pavohave all IPs and names in all nodes /etc/hosts01:05
Pavodid a ping of IPs, hostnames and even fqdn on all nodes01:05
sbezverkPavo: ping that host by name from your deployment station01:05
Pavothats why I am so confused01:05
*** zhurong has joined #openstack-kolla01:05
Pavo[root@deployer kolla]# ping node201:06
PavoPING node2 (192.168.1.11) 56(84) bytes of data.01:06
Pavo64 bytes from node2 (192.168.1.11): icmp_seq=1 ttl=64 time=0.631 ms01:06
Pavo64 bytes from node2 (192.168.1.11): icmp_seq=2 ttl=64 time=0.377 ms01:06
Pavo64 bytes from node2 (192.168.1.11): icmp_seq=3 ttl=64 time=0.499 ms01:06
sbezverkdo you have different ip assigned to api_interface in globals?01:06
PavoI only have VIP internal IP set in globals01:07
Pavothe one that is not pingable from all nodes01:07
sbezverkPavo: what is this "ahostsv4"01:11
sbezverk?01:11
Pavohave no clue01:11
Pavohere is my globals01:11
Pavohttps://www.dropbox.com/s/2694rq4mkojt9ef/globals.yml?dl=001:11
sbezverkso it is not one of names or anything like that?01:11
Pavono01:11
Pavohere is my multinode01:12
Pavohttps://www.dropbox.com/s/xkhanhb0ysq6gym/multinode?dl=001:12
PavoI hope they are correct01:12
Pavooops I think I see the issue01:13
PavoI have the network interfaces flipped I think on globals01:13
sbezverkPavo: that is the good possibility to cause this issue01:14
Pavotrying again01:14
*** haplo37__ has joined #openstack-kolla01:24
openstackgerritWei Cao proposed openstack/kolla: Ubuntu with systemd support  https://review.openstack.org/34690001:26
Pavolooks like I am getting stuck again01:27
PavoTASK [mariadb : Waiting for MariaDB service to be ready through VIP] ***********01:28
PavoFAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready through VIP (3 retries left).01:28
*** rstarmer has quit IRC01:39
Pavowhere does kolla-ansible genconfig put the generated configs at?01:43
openstackgerritWei Cao proposed openstack/kolla: Ubuntu with systemd support  https://review.openstack.org/34690001:51
*** haplo37__ has quit IRC01:53
openstackgerritLu lei proposed openstack/kolla: Fix oslo.i18n in kolla project  https://review.openstack.org/35534201:56
*** jtriley has joined #openstack-kolla02:02
*** inc0 has joined #openstack-kolla02:03
Pavook I think I am getting really confised on what interface I need to use for a IP for kolla_internal_vip_address02:08
PavoI have 2 interfaces eth0 and eth1 on each node, I am using eth0 for public network ie... routable IPs, and eth1 as non routable IPs02:09
inc0Pavo, one of management iface02:10
Pavothen that would be eth002:10
inc0one that you can access servers over02:10
PavoI gave it an IP out of the IP range on that network that is not being used and it doesn't seem that when I deploy that its giving any ports or IPs to the containers02:11
PavoI keep getting stuck at TASK [mariadb : Waiting for MariaDB service to be ready through VIP] ***********02:12
inc0ip range?02:12
Pavothis is the inspect of that container on that node02:12
Pavohttp://pastebin.com/jVMy8HSJ02:12
inc0it should be single ip02:12
Pavoeth0 is on 192.168.1.0/24 network, eth1 is on 192.168.188.0/24 network02:13
Pavoeth0 is management/internet, eth1 is only between servers02:13
Pavomy nodes have deployer node eth0 192.168.1.33, node1 eth0 192.168.1.45 eth1 192.168.188.129 and node2 has eth0 192.168.1.11, eth1 192.168.188.13002:15
PavoI gave the VIP IP 192.168.1.9002:15
Pavoin the /etc/kolla/globals.yml file02:15
inc0so this seems ok02:18
PavoI thought so to but as you can see from the inspect on the mariadb container there isn't an IP getting added02:18
Pavounless I understand the deployment wrong02:19
*** jtriley has quit IRC02:20
openstackgerritWei Cao proposed openstack/kolla: Ubuntu with systemd support  https://review.openstack.org/34690002:21
openstackgerritWei Cao proposed openstack/kolla: Remove duplicate items  https://review.openstack.org/35537702:25
inc0Pavo, that's because all of our containers are net=host02:26
inc0mariadb inside will have exactly same networking stack as host02:26
Pavothen what IP should I give kolla_internal_vip_address?02:26
Pavothe host IP?02:26
inc0no, not used IP:)02:27
inc0it's for keepalived02:27
Pavook thats what I gave it02:27
Pavoa IP thats on the same network but not being used02:27
inc0if your keepalived is running in container02:27
inc0ip a should show IP you gave it02:27
inc0ip a on host02:27
duonghqanybody has good news about the yesterday neutron_server error?02:31
PavoI have kepalive on node2 and mariadb on node102:33
Pavonot seeing an IP for the keepalive either02:33
inc0hmm, can you show me your inventory?02:34
Pavohttps://www.dropbox.com/s/xkhanhb0ysq6gym/multinode?dl=002:34
inc0can you paste it somewhere?;)02:36
Pavosure02:36
inc0thanks02:36
inc0dropbox would want me to download it02:36
inc0and as I know myself it would stay there forever02:36
*** signed8bit_Zzz is now known as signed8bit02:37
Pavohttps://paste.pound-python.org/show/6XsAEDMTG6JSzinplXQC/02:37
inc0so 1.45 should have the IP02:38
inc0network node should run haproxy container and keepalived container02:38
Pavowhere do you see that?02:38
inc0just ip addr on host02:38
Pavooh ok02:38
Pavoso I have my inventory messed up02:38
inc0well not that bad02:39
inc0but I'd suggest putting network and control on same node02:39
inc0for first deployments;)02:39
Pavoyou mind helping me out, this is the first time I have tried this and don't understand it all02:39
Pavooh ok02:39
inc0so put control and network on .11, compute on .4502:40
inc0and storage whatever, unless you enable ceph/cinder02:40
inc0I suggest starting without these02:40
inc0as both require a bit of additional setup02:40
Pavook02:41
Pavoso I need to remove contol from [cinder:children?02:41
inc0no02:41
*** fragatin_ has joined #openstack-kolla02:42
inc0you specify enable_cinder: true in globals02:42
inc0unless you set that, it should be ok02:42
inc0just put control and network on .11 and compute on .4502:42
inc0or you can put control on both02:43
Pavothis is globals02:43
Pavohttps://paste.pound-python.org/show/ikw04SvnaHQZDpmsp7wa/02:43
inc0just to see ha work02:43
*** zhubingbing has joined #openstack-kolla02:43
zhubingbinghello02:43
inc0ok02:43
inc0so I see the issue02:43
Pavo?02:43
inc0network_interface => management02:43
inc0neutron_external_interface => where vm land02:44
inc0so if you set up network_interface to eth102:44
inc0you need to put kolla_internal_vim_address in same network as eth102:44
inc0ok it seems you did that02:45
Pavook so use eth0 for both since my 192.168.1.0/24 network is being used for both management and internet then right02:45
*** fragatina has quit IRC02:45
inc0no, eth0 will get owned by neutron02:45
inc0which means you shouldn't use it for anything else really02:45
Pavothe 192.168.188.0/24 network is only used for communication between the nodes02:45
inc0as neutron will put bridge there02:46
Pavoah02:46
inc0but that's later02:46
*** klint has joined #openstack-kolla02:46
*** fragatin_ has quit IRC02:46
inc0keepalived will try to setup 192.168.188.254 on eth102:46
inc0of controller02:46
inc0besides usual address02:46
irtermiteinc0: did you figure out your spanning tree issue?02:47
inc0then haproxy will listen on this address for service traffic02:47
inc0irtermite, not yet, I got pulled out02:47
*** klint has quit IRC02:47
inc0will get back to it tomorrow02:47
inc0after I repave whole thing, it seems to behave better02:48
*** klint has joined #openstack-kolla02:48
inc0it might be something on our end02:48
irtermitefrom what I am told, it sounds like an issue within, yes02:48
irtermitewas it traffic between hosts, vms, both?02:48
irtermiteover VPN?02:48
inc0we wanted to put vlan network for vms02:49
*** yuanying has quit IRC02:49
inc0and add tagged iface on deploy host so we can access vms over vlan02:49
inc0but I think we messed up something and put vlan in vlan02:49
inc0anyway, going off02:50
inc0enough of no-lifing in irc02:50
*** jamesdenton has joined #openstack-kolla02:50
inc0cya all tomorrow02:50
Pavothanks for the help inc002:51
inc0np02:51
*** yuanying has joined #openstack-kolla02:52
jamesdentonhi irtermite02:53
irtermiteinc0: ^^^ meet the guy that wrote the book on Openstack Neutron02:53
irtermiteliterally02:53
irtermiteand go02:53
irtermiteMichal -> James -> Michal02:54
jamesdentonhey inc002:54
*** inc0 has quit IRC02:55
irtermite*sadtrombone*02:55
zhubingbingShaun Smekel02:56
*** klint has quit IRC02:56
zhubingbinghello02:56
*** klint has joined #openstack-kolla02:57
zhubingbingAre you there02:57
*** klint has quit IRC02:58
*** klint has joined #openstack-kolla02:58
*** klint has quit IRC02:59
*** signed8bit is now known as signed8bit_Zzz03:00
*** rstarmer has joined #openstack-kolla03:00
openstackgerritWei Cao proposed openstack/kolla: Ubuntu with systemd support  https://review.openstack.org/34690003:01
openstackgerritWei Cao proposed openstack/kolla: Ubuntu with systemd support  https://review.openstack.org/34690003:03
*** signed8bit_Zzz is now known as signed8bit03:09
openstackgerritzhubingbing proposed openstack/kolla: Add aodh role  https://review.openstack.org/35102703:16
*** haplo37__ has joined #openstack-kolla03:22
*** signed8bit has quit IRC03:34
*** diogogmt has quit IRC03:34
*** signed8bit has joined #openstack-kolla03:34
*** signed8bit has quit IRC03:38
*** signed8b_ has joined #openstack-kolla03:39
*** yuanying has quit IRC03:48
*** yuanying has joined #openstack-kolla03:51
*** signed8bit has joined #openstack-kolla03:56
*** jamesdenton has quit IRC03:56
*** signed8b_ has quit IRC03:58
duonghqwhen I checkout my git repository to a revision (and pip install...), and do kolla-build --push, does the repo get the version?04:13
duonghqDaviey: do you have any experience04:17
*** fragatina has joined #openstack-kolla04:24
openstackgerritTin Lam proposed openstack/kolla: Add support for building vmtp container  https://review.openstack.org/35436204:26
*** fragatina has quit IRC04:29
*** hieulq has quit IRC04:39
*** Pavo_ has joined #openstack-kolla04:42
openstackgerritWei Cao proposed openstack/kolla: Add solum container  https://review.openstack.org/35540804:43
*** hieulq has joined #openstack-kolla04:45
openstackgerritWei Cao proposed openstack/kolla: Update instructions for ubuntu with systemd  https://review.openstack.org/34690004:47
openstackgerritWei Cao proposed openstack/kolla: Remove duplicate items  https://review.openstack.org/35537704:50
*** signed8bit has quit IRC04:52
*** zhubingbing has quit IRC04:56
Pavo_is there a place where I can see all the options that can be used in the globals.yml?05:06
*** Pavo is now known as Guest5573905:08
*** Pavo_ has quit IRC05:08
*** senk_ has joined #openstack-kolla05:16
*** zhubingbing has joined #openstack-kolla05:25
*** fragatina has joined #openstack-kolla05:40
*** haplo37__ has quit IRC05:41
*** zhubingbing has quit IRC05:44
*** senk_ has quit IRC05:45
*** fragatina has quit IRC05:45
*** zhubingbing has joined #openstack-kolla05:46
zhubingbingShaun Smekel06:12
zhubingbinghello06:12
duonghqzhubingbing: did you get any error related to neutron-l3-agent?06:13
zhubingbingnetron-l3-agent?06:13
duonghqiup06:13
duonghqyup06:13
zhubingbingNO,06:14
zhubingbingI'm not wrong for neutron-l3-agent06:15
zhubingbingWhat is your fault detail?06:15
duonghqI got kolla_start not found or does not exist06:16
zhubingbingsure,you setting enable it?06:17
duonghqno, just default settings06:17
zhubingbingcan you share VM?06:19
duonghqjust fresh install of ubuntu 16.0406:19
zhubingbingok06:19
zhubingbingyou should run this command mount --make-shared /run06:20
duonghqah, do you get any problem with neutron_server in master branch?06:20
zhubingbinghttp://docs.openstack.org/developer/kolla/quickstart.html06:21
duonghqI remembered that I ran this command06:22
zhubingbingthe system have reboot?06:22
duonghqyeah, but for 16.04, it is in systemd06:22
zhubingbingIf you want to re execute this command after the reboot of the system06:23
duonghqso reboot doesn't affect06:23
zhubingbingok06:23
zhubingbingsure06:23
zhubingbingthen I don't know.06:23
zhubingbing - sorry06:23
duonghqwhich revision are you runnig zhubingbing?06:24
zhubingbingubuntu 14.04  ,kolla is 3.0.006:25
duonghqI mean the git revision06:25
zhubingbinggit06:26
zhubingbinggit version 1.9.106:26
duonghqno, the commit id of kolla06:26
zhubingbingthis my name zhubingbing  the commit id06:27
duonghqso, you build image from latest kolla source code?06:29
*** Jeffrey4l has joined #openstack-kolla06:30
*** unicell has joined #openstack-kolla06:30
zhubingbingmy vm is 52.196.228.195:06:30
zhubingbingyou can ssh it06:30
duonghqyou can cd in to the kolla source and exec git status?06:31
zhubingbingroot@ip-172-31-22-78:~/kolla# git status06:32
zhubingbingOn branch master06:32
zhubingbingYour branch is up-to-date with 'origin/master'.06:32
zhubingbingnothing to commit, working directory cle06:32
duonghqah, ok06:32
duonghqbut do you run kolla-build recently06:33
zhubingbingyes06:33
duonghqok, thank you06:33
zhubingbingok06:34
zhubingbingThat's OK.06:34
*** diga_ has joined #openstack-kolla06:41
*** b_bezak has joined #openstack-kolla07:06
*** rstarmer_ has quit IRC07:09
*** bootsha has joined #openstack-kolla07:21
*** imcsk8 is now known as imcsk8|zZz07:37
*** bjolo has joined #openstack-kolla07:41
*** fragatina has joined #openstack-kolla07:41
*** belmoreira has joined #openstack-kolla07:46
*** fragatina has quit IRC07:46
*** diga_ has left #openstack-kolla08:07
*** athomas has joined #openstack-kolla08:14
*** daneyon has joined #openstack-kolla08:16
*** Serlex has joined #openstack-kolla08:18
*** matrohon has joined #openstack-kolla08:19
*** daneyon has quit IRC08:21
duonghqmntdevops: did you get kolla-start command not found anywhere?08:25
duonghq Client Error: Not Found (\"Container command \\'kolla_start\\' not found or does not exist.\")\\n'08:25
openstackgerritMathias proposed openstack/kolla: Added grafana container  https://review.openstack.org/34644708:35
*** mewald has joined #openstack-kolla08:36
mewaldDo people still care about performance monitoring? The activity in reviewing is rather frustrating. I am waiting for https://review.openstack.org/#/c/346448/ It has no comments, no +1 nor -108:45
patchbotmewald: patch 346448 - kolla - Added telegraf role08:45
*** cristicalin has joined #openstack-kolla08:53
duonghqmewald: did you get command not found error when start container?08:58
mewaldduonghq: which container are we talking about?09:03
mewaldtelegraf?09:03
*** gfidente has joined #openstack-kolla09:03
*** bootsha has quit IRC09:04
duonghqmewald: memcached09:04
mewaldmy patches aren't concerned with memcache at all - are we talking about the monitoring patches or is this a general question?09:05
duonghqah, general question09:05
duonghqjust master branch09:05
mewaldah, no I haven't seen anything like this09:05
*** cristicalin has quit IRC09:06
duonghqthanks09:06
*** MrDan has joined #openstack-kolla09:06
*** bootsha has joined #openstack-kolla09:07
*** bootsha has quit IRC09:14
openstackgerritMathias proposed openstack/kolla: Added influxdb role  https://review.openstack.org/34644909:14
openstackgerritMathias proposed openstack/kolla: Added telegraf role  https://review.openstack.org/34644809:16
openstackgerritMathias proposed openstack/kolla: Added telegraf role  https://review.openstack.org/34644809:17
openstackgerritPaul Bourke proposed openstack/kolla: WIP: attempt to fix gate  https://review.openstack.org/35580809:20
*** kwazar is now known as quasar09:23
*** rstarmer_ has joined #openstack-kolla09:26
openstackgerritSajauddin proposed openstack/kolla: Author: Sajauddin  https://review.openstack.org/35110809:28
*** rstarmer_ has quit IRC09:29
zhubingbinghello09:32
duonghqhello09:40
duonghqhope that this time kolla will up and running09:40
duonghqIt already toke me 2 day09:40
mewaldcrazy - first time I had it up and running after 20min :D09:41
duonghqmewald: me too09:41
duonghqbut after some try it screw up09:41
duonghqno idea09:41
*** fragatina has joined #openstack-kolla09:43
duonghqmewald: do you try recent version on git?09:44
mewaldyeah I am on master09:44
mewaldI am building new images right now, I'll let you know if it worked09:45
duonghqthanks09:45
*** egonzalez90 has joined #openstack-kolla09:46
*** fragatina has quit IRC09:48
*** bootsha has joined #openstack-kolla09:57
*** zhurong has quit IRC10:01
*** daneyon has joined #openstack-kolla10:05
*** daneyon has quit IRC10:09
egonzalez90Hi there!10:14
MrDanhello, I have an issue when i use kolla-ansible pull10:14
duonghqMrDan: can you give me more detail10:15
MrDanfails at pulling kolla-toolbox, but it is a code issue, not by failing to pull it10:15
MrDanAn exception occurred during task execution. The full traceback is:10:15
MrDanTraceback (most recent call last):10:15
MrDan  File "/tmp/ansible_kklOeD/ansible_module_kolla_docker.py", line 703, in <module>10:15
MrDan    main()10:15
MrDan  File "/tmp/ansible_kklOeD/ansible_module_kolla_docker.py", line 673, in main10:15
MrDan    module = generate_nested_module()10:15
MrDan  File "/tmp/ansible_kklOeD/ansible_module_kolla_docker.py", line 659, in generate_nested_module10:15
MrDan    new_args.update(module._load_params()[0])10:15
MrDanTypeError: 'NoneType' object has no attribute '__getitem__'10:16
MrDanfatal: [localhost]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_name": "kolla_docker"}, "module_stderr": "Traceback (most recent call last):\n  File \"/tmp/ansible_kklOeD/ansible_module_kolla_docker.py\", line 703, in <module>\n    main()\n  File \"/tmp/ansible_kklOeD/ansible_module_kolla_docker.py\", line 673, in main\n    module = generate_nested_module()\n  File10:16
MrDan\"/tmp/ansible_kklOeD/ansible_module_kolla_docker.py\", line 659, in generate_nested_module\n    new_args.update(module._load_params()[0])\nTypeError: 'NoneType' object has no attribute '__getitem__'\n", "module_stdout": "", "msg": "MODULE FAILURE", "parsed": false}10:16
MrDankolla at 2.0.210:16
duonghqsound familar10:16
openstackgerritPrithiv proposed openstack/kolla: Add Networking-SFC roles in ansible  https://review.openstack.org/34684210:22
*** duonghq has quit IRC10:27
*** ntpttr has quit IRC10:30
rstarmerwrong ansible versin10:32
rstarmertry with ansible 1.9.410:32
rstarmerMrDan: if you're using the master branch, you should be using ansible 2.0.0 if you're using stable/mitaka, ansible 1.9.410:33
openstackgerritSajauddin proposed openstack/kolla: Skips a debug log during image build  https://review.openstack.org/35110810:35
*** ntpttr has joined #openstack-kolla10:35
*** kbaegis has joined #openstack-kolla10:41
*** fragatina has joined #openstack-kolla10:47
*** rhallisey has joined #openstack-kolla10:49
*** phuongnh has quit IRC10:49
*** dmueller-evoila has joined #openstack-kolla10:56
*** dmueller-evoila has quit IRC11:00
*** vbel has quit IRC11:01
*** vbel has joined #openstack-kolla11:01
*** ad_rien_ has joined #openstack-kolla11:02
*** dmsimard is now known as dmsimard|afk11:03
*** ad_rien_ has quit IRC11:06
*** bootsha has quit IRC11:07
MrDanback, i was on lunch11:15
MrDani am using the default build11:16
MrDanlet me check it11:16
MrDanwhere I can find it, in /etc/kolla/global.yml?11:16
MrDanok, nvm11:16
*** bootsha has joined #openstack-kolla11:17
*** fragatin_ has joined #openstack-kolla11:19
openstackgerritMerged openstack/kolla: Customizations for Swift  https://review.openstack.org/35440511:20
egonzalez90MrDan ansible --version11:20
*** haplo37__ has joined #openstack-kolla11:20
openstackgerritPaul Bourke proposed openstack/kolla: Fix Neutron bootstrap failure due to missing fixtures dependency  https://review.openstack.org/35580811:21
*** fragatina has quit IRC11:23
MrDani am trying with 2.0.0.011:23
MrDanfailed again, trying with 1.9.411:24
egonzalez90as rstarmer said, with stable/mitaka ansible 1.9.4 is needed, migration to ansible 2 is being made at master11:29
*** haplo37__ has quit IRC11:31
*** mbound has joined #openstack-kolla11:34
openstackgerritEduardo Gonzalez proposed openstack/kolla: Missing hosts at haproxy in site.yml  https://review.openstack.org/35586111:34
*** sdake has joined #openstack-kolla11:36
*** bjolo has quit IRC11:36
MrDanwhere can I set the openstack version, in /etc/kolla/globals.yml?11:38
MrDanor ar kolla build with an aoption11:38
*** berendt has joined #openstack-kolla11:39
*** dwalsh has joined #openstack-kolla11:41
*** duonghq has joined #openstack-kolla11:42
sdakemorning cats11:44
sdakeversion 2.0.2 = mitaka11:44
sdake1.1.2 = liberty11:44
duonghqmewald: did you finish building image?11:44
sdakeopenstaack_version: "2.0.2"11:44
sdakecheck out the empel in globals.yml11:44
sdakeMrDan this will control which vrsion is deployed - not built11:46
sdaketo control the built version you can use the --tag option11:46
sdakefrom the appropriate repositroy11:46
duonghqsdake: today is hard to me, building, deploying and failing :(, hope that tomorrow is better11:48
sdakeduonghq sorryto hear it11:48
sdakeneed any help?11:48
duonghqat least, I found working commit at end of day11:49
sdakeduonghq your probably rying to deploy master since your developing11:49
sdakemaster is not super stable atm11:49
pbourkesdake: hey11:49
duonghqsomething screw up my physical dev machine, so I use it only to build and deploy to VM11:49
sdakemorning paul11:49
sdakepbourke any wordo n the networking situation in osic?11:50
sdakei went to bed early yesterday11:50
sdakeafter cratering my $1,800 cartridge11:50
pbourkesdake: was about to ask you the same :) Im a bit unclear on the status the past few days, some of the guys in other TZs have been working on it but not got an update11:50
sdakei couldn't bear to stay up any longer :(11:50
sdakepbourke - email in order i think to help ix that problem11:51
pbourkeok thanks I'll draft something up11:51
pbourkeas right now time is slipping away and we're not progressing11:51
pbourkeor maybe we are and I dont know11:51
sdakei agree totally blocked11:51
sdakei grilled inc0 yesterday about it so hee could get it working for us11:51
sdakeas we have been blocked ofr a week11:51
sdakeat this point i am almsot ready to abandon rally testing11:52
pbourkesdake: also gates are not good lately, I have two patches up to help fix11:52
sdakewe can do the remainder of our testing without totally functional netowrking11:52
sdakepbourke cool thanks :)11:52
pbourkesdake: but there's something wrong with the keys for the package mirrors11:52
sdakewhich mirrors specifically11:52
pbourkethe ubuntu xenial ones11:52
kbaegisI'm curious about this too11:53
sdakewhen the US wakes up i'll bring it up11:53
duonghqhey kbaegis11:53
sdakedo you have evidence of such11:53
kbaegismorning!11:53
*** daneyon has joined #openstack-kolla11:53
sdakethe best way to get that fixed would be an emil to openstack-infra11:53
pbourkehave we always had xenial gates or are these new11:53
sdakethey are new - jeffrey added them11:53
pbourkeok that makes more sense then11:53
sdakeoh the keys in our tree!11:53
sdakenot the mirrors11:53
sdakei know the problem11:53
sdakepossibly11:54
sdakewe don't inject the correct mirror information into the build11:54
sdakefor xenial11:54
sdakegive me 20 misn to get warmed up and i'll look at it11:54
sdakekbaegis are you ahving trouble with xenial as well?11:54
pbourkegood stuff sdake thanks11:55
sdakepbourke after today - if no progress on networking, i think best courseof action is to abandon rally testing11:55
sdakeor atleast the parts of it requring vm access11:56
sdakeand continue on our merry way11:56
pbourkesdake: ok11:56
sdakewe can't stay blocked and have zero output for the osic work for 4 weeks because we don't know how to operate our own software ;)11:56
kbaegissdake Not per-se11:56
sdakefwiw - got this gem - stp is not enabledon the TORs, so when deploying do not enable stp in linuxbridge11:56
sdakeotherwise you will get a stp storm11:57
sdakewhatever all that means ;)11:57
sdakeJeffrey4l ^^11:57
sdakesean-k-mooney was around yesterday - maye he has more data from what happened11:57
sdakei was on a 40 hour bender doing tonearm setup11:57
*** daneyon has quit IRC11:58
duonghqsdake: I thought you made it work before?11:58
kbaegisI can give folks access to my lab if you need it.11:58
kbaegisI think I have spreed around still :)11:58
sdakekbaegis thanks for the offer, but osic has granted us access to 131 nodes for scale testing11:58
sdakethat is what we are talking about here11:59
duonghqkbaegis: finally, I found 1 working commit for Ubuntu host11:59
kbaegissdake Oh now that's cool11:59
sdakepbourke also another gem - ping to the vms works, but ssh does not11:59
kbaegissdake ooc, does ansible scale that effectively?  I saw the appeal of headless mcollective/puppet12:00
kbaegisCurious how that's going12:00
sdakeit takes 20 minutes to deploy 131 nodes12:00
sdakeso I'd say so :)12:00
pbourkesdake: yeah it sounds messy12:00
kbaegisWow, awesome12:00
sdakewhich images areyou guys tryign to ssh into btw12:00
kbaegisThat's w/ 10GBASE links?12:01
sdakeiirc cirros does not include sshd12:01
pbourkesdake: Id like to know where we think the problem is, if it's an osic thing we can file a ticket with them, if its an openstack thing should be plenty of people to help on the ML12:01
sdake10gig yes12:01
sdakepbourke i am not sure on that point - i'm not sure if linuxbridge improved the situation compared to ovs12:01
kbaegisMakes sense.  My labs still on 1gbase.  10 GBASE switches are expensive at 48 port densitites12:01
sdakepbourke i never go tthat feedback and we need to know that information sap12:01
sdakemy personal lab has 10gig at home :)12:01
pbourkesdake: email sent to ML12:01
kbaegisHow much did you have to drop on your switch?12:02
sdake800 bucks12:02
kbaegiswtf?12:02
sdakeneed link? :)12:02
kbaegisYes12:02
sdakei think its a really good value personally12:02
sdakehttps://www.amazon.com/NETGEAR-ProSAFE-XS708E-Ethernet-XS708E-100NES/dp/B00B46AEE612:03
sdakecopper 10gig12:03
sdakerequires cat7 cabling which is about 10-15 bucks a cable12:03
kbaegisOh, 8 port12:03
sdakethey make bigger ones12:03
kbaegisYeah,12:03
sdakebut more expensive12:03
kbaegisThat's what I was saying12:03
sdakein retrospect i wish i bought thee 12 port12:03
kbaegisI have too many systems for an 8 port12:03
kbaegisI'd need 24/4812:03
kbaegisAnd not ready to plunge in for 5k12:04
sdakestill chepeast switch you can buy for the port count12:04
sdakecisco gear is far better perf/design12:04
sdakebut the netgear stuff is functional for testing12:04
kbaegisYeah, but at that density I may as well daisy chain12:04
kbaegisYou're right, it's a good value12:04
*** kbaegis has quit IRC12:08
*** dmueller-evoila has joined #openstack-kolla12:08
*** haplo37__ has joined #openstack-kolla12:09
*** kbaegis has joined #openstack-kolla12:09
kbaegisI mention equationgroup and I get mysteriously dropped :)12:09
sean-k-mooneysdake: you mentioned me12:12
sean-k-mooneyosic?12:12
sdakeroger12:13
sdakepbourke would like an update if you know anything :)12:13
*** haplo37__ has quit IRC12:13
sean-k-mooneyi was around for a few hours but when i left the issue was still not resolve.12:14
sean-k-mooneywe were still seeing some stp traffic on the node.12:14
*** srwilkers has joined #openstack-kolla12:15
sean-k-mooneyinc0 tried a few things12:15
sean-k-mooneyim not sure if he found a way to fix it12:15
sean-k-mooneywe tried simplying the network config by using just bond 0 for neutron and sending all other traffic over a single interface but still had issues12:16
sean-k-mooneyinc0 was able to ping the spawned vm but there was a lot of packet loss still12:16
sean-k-mooneyunfortunetlly i dont know what the outcome was so i guess we will have to ask inc0 when he comes online12:21
kbaegisYou guys were using linuxbridge at scale?12:24
sean-k-mooneyovs12:24
kbaegisOh, good :)12:24
sean-k-mooneylinux brige is a fallback if we can sort out the networking issue we are having with osic but i dont think they are ovs related12:25
kbaegislot of components created.  Docker relies on a bridge doesn't it? (I'm newer to docker than openstack)12:25
kbaegisIf there's a way to have docker terminate its veths on ovs, I'd be all ears on how12:26
sean-k-mooneykbaegis: we use --net=host for our container so they do not use ovs12:28
sean-k-mooneyovs is used by the vms spawned by openstack12:28
sean-k-mooneybut yes you can use docker with ovs also12:29
*** b_bezak_ has joined #openstack-kolla12:29
sean-k-mooneyi just not sure if docker supprot adding the port to ovs itself.12:30
sdakethanks sean-k-mooney12:32
sdakepbourke ^^ - i think there is nothign new there that i didn't already explain12:32
*** b_bezak has quit IRC12:33
openstackgerritEduardo Gonzalez proposed openstack/kolla: Missing hosts at haproxy in site.yml  https://review.openstack.org/35586112:34
kbaegisHa! Kolla deployed from centos-source:3.0.0 on gentoo!  Now to see if I can actually create VMs this time.12:39
sdakesean-k-mooney iiuc this is what kuryr is all about12:43
sdakebut huikang wouldl know for certain12:43
sdake(the ovs networkign link to docker012:43
sdakedocker012:43
sdakedocker)12:43
sdakekeyboard fail12:44
sean-k-mooneykbaegis: interesting... if it has systemd it should work i guess but that is definetly not a tested combination12:44
sdakesean-k-mooney - yup i warned him :)12:44
sdakealso not a supported combination12:44
sdakewe expect the container distro to match the host os12:45
sean-k-mooneysdake: kuryr likns docker networks with neutron so with out the ovs neutron agent to wire up the openflow rules im not sure if it will work12:45
sdakesean-k-mooney cool thanks for the clarification and enlightenment :)12:45
zhubingbinghello12:45
sdakewe have kuryr on the way12:46
sdakewaiting on keystone v3 support12:46
sean-k-mooneykuryr with kolla12:46
sean-k-mooneyi think i remember reviewing that at some point12:46
*** ad_rien_ has joined #openstack-kolla12:46
kbaegissean-k-mooney: Why systemd?  I can't use sysvinit?12:46
openstackgerritEduardo Gonzalez proposed openstack/kolla: Missing hosts at haproxy in site.yml  https://review.openstack.org/35586112:46
sean-k-mooneyi was a little uncomfortable about the docker on the host useing someting form a docker container it was running12:47
sean-k-mooneykbaegis: you can but we have had issues in the past using a container os that expect systemd with a host os that does not use it and vice versa12:47
*** mbound has quit IRC12:48
sean-k-mooneykbaegis: there can also be issue when one distro uses apparmor and the other uses selinux12:48
kbaegisI can recompile or change the security model12:48
sdaketurn off is probably the only answer there12:48
kbaegisI can even alter my init.  I just like sysv better :)12:48
sdake(turn off security)12:49
kbaegisI'll play with it.  Thanks for the warning12:49
sean-k-mooneykbaegis: well the issue is the patch for the profiels dont match the patch for the same apllication in side the contaienr12:49
sdakeand also syscall interface + rtnetllink + ioctl = not compatible betwen distros12:49
kbaegisInteresting12:50
kbaegisWell I do know that horizon, as deployed, is giving me 500s12:50
sean-k-mooneysdake: there are not completely compatible because the tools are built against different kernel headers but somehow they do kind of work12:50
kbaegisI was falling back to the cli12:50
sdakesean-k-mooney right - sort of work being the key thing there ;)12:51
sdakemostly things work12:51
sean-k-mooneysdake: at leaset when the kernels they are expecting are somewhat close to the kernel you are running12:51
sdakebut can't be guaranteed12:51
sean-k-mooneyya12:51
sdakeroger on kernel versions12:51
sean-k-mooneykbaegis: in any case if you do get it working let us know im sure it will be interesting testing it out12:52
kbaegis4.8.0-rc1 :)12:52
kbaegisYeah, it's a good way to learn12:52
kbaegisI think12:52
sean-k-mooneykbaegis:  that might be a little newer then the "3.10" kernel Centos is expecting12:53
sean-k-mooneythe centos kernel isnt really 3.10 as it has backports from 4.x but who am i to argure with there nameing scheme12:53
kbaegisI guess I could try my hand at setting up the containers on gentoo12:54
kbaegisSquare block, round hole12:55
kbaegisBut it would allow you guys to test with the bleeding edge12:55
kbaegisSo I've seen this horizon error before: Dashboard with slug "developer" is not registered12:58
sdakekbaegis our testing is in teh gate - getting new images in the gate is exceedingly difficult12:58
sdakekbaegis create a _member_ role12:58
sdakeI was pretty sure this was fixed - perhaps its not merged yet12:58
kbaegisThat fixes horizon?12:59
sdakeyes12:59
kbaegisI just created the role from cli12:59
kbaegisMaybe it's a cache issue12:59
sdakeJeffrey4l is the patch author12:59
sdakeits possible you found a new problem13:00
sdakento certain - i don't recall seeing that specific slug13:00
egonzalez90was not merged yet https://review.openstack.org/#/c/349198/13:00
patchbotegonzalez90: patch 349198 - kolla - Create the _member_ role in the horizon role13:00
kbaegishttp://hastebin.com/iveweruwex.rb13:00
kbaegisI'll try restarting the container13:00
sdakekbaegis cherry-pick that patch on your repo13:01
*** ad_rien_ has quit IRC13:01
sdakeyou may need to rebuild horizon - not sure13:01
sdakethanks egonzalez90 !13:01
Jeffrey4lkbaegis, you also need  https://review.openstack.org/34919713:01
Jeffrey4lrun deploy again will work. no need remove the container.13:02
sdakepbourke can you review https://review.openstack.org/#/c/349197/ plz13:03
patchbotsdake: patch 349197 - kolla - Implement kolla_keystone_role module13:03
*** bjolo has joined #openstack-kolla13:04
kbaegisAre there any docs that show how gate works?13:04
sdakeits all in our heads :)13:05
sdakethere are some docs13:05
sdakethe best place to get a primer is in the #openstack-infra channel13:05
sdakei can introduce you there if you like13:05
pbourkeJeffrey4l: can we not use ansible 2.1 in toolbox on the stable branch?13:05
sdakealthough its a bit early - many folks may not be around13:05
pbourkeJeffrey4l: in fact I thought we did already13:05
Jeffrey4lpbourke, we are using ansible>2 in toolbox.13:06
pbourkeJeffrey4l: why not update the pin13:06
kbaegisNeat13:06
Jeffrey4li.e. we are using the latest version.13:06
sdakepbourke good question13:06
*** dmueller-evoila has quit IRC13:06
Jeffrey4lwhy not?13:06
pbourkewhy not use ansible 2.1 in toolbox on the stable branch13:06
sdakethat does make ssense to me13:07
Jeffrey4lhmm. stable branch? i have no idea about that :(13:07
sdakewhat we hae now in the stable versions is essentially a beta version of fansible13:07
Jeffrey4lwhen i joined kolla. it  use 2.1 already.13:07
Jeffrey4la rc tag.13:07
sdake(just speaking about kolla-toolbox)13:07
sdakeoh maybe someone fixed that13:08
Jeffrey4lOK. it is me change it from installing from source to installing from pypi ( pip install ansible>2).13:10
Jeffrey4lBut you are right, we should fix it version number. like pip install ansible<2.1 or ansible<=2.113:10
Jeffrey4lit will be more stable. pbourke13:10
kbaegiswell, the vm creation works13:11
pbourkeJeffrey4l: this is what's on stable/mitaka right now https://github.com/openstack/kolla/blob/stable/mitaka/docker/kolla-toolbox/Dockerfile.j2#L43-L4713:11
sdakeya - thats a beta version :)13:12
sdakean ansible engineer told us "use this git commit for now"13:12
sdakean we never got back to it13:12
sdakebut it does work13:12
Jeffrey4lpbourke, yes. ansible>2 is bad.13:13
sdakebut it may notwork with your patches backported Jeffrey4l13:13
sdakeJeffrey4l that is a 2.x beta hash13:13
sdakeJeffrey4l you mean ansible < 2?13:13
Jeffrey4lbeta hash? what does it mean?13:14
Jeffrey4lansible 2.1 is beta version and shouldn't be used?13:14
sdakethe git commit hash in that link from pbourke is 2.x beta13:14
pbourkei know13:14
sdakei.e. we are using beta software in stable branches for kolla-toolbox13:14
Jeffrey4lit is.13:15
sdakei think pbourke 's question is why not just unpin it or pin it to a non-beta version13:15
sdakeor maybe pbourke has something else in mind ?13:15
pbourkeno that's what I meant sdake13:15
sdakesorry - i'll gtfootw :)13:16
pbourkeim saying you are correct :)13:16
openstackgerritEduardo Gonzalez proposed openstack/kolla: Missing hosts at haproxy in site.yml  https://review.openstack.org/35586113:16
Jeffrey4lso you mean: we should move the ansible 2.1 on in kolla-toolbox on mitaka branch. right?13:16
sdakeoh somehow i read "not" in there13:16
sdakeJeffrey4l yes13:16
sdakeJeffrey4l so your backports work properly13:17
Jeffrey4lI think it is OK.13:17
sdakexenial hashes13:17
sdakeJeffrey4l did you do the work o fadding xenail to kolla?13:18
Jeffrey4lto move to ansible 2.1. using a hash commit tag is really bad.13:18
sdakeJeffrey4l it was the best option we had available at th time13:18
sdakewe have better options now13:18
sdakeit took alot of hunting to find a git commit that would work at all with shade in the early days of ansible 2.x13:19
Jeffrey4lsdake, i fix the xenial build gate. the deploy gate is still failing, which is wired.13:19
Jeffrey4lhttps://review.openstack.org/35527413:19
sdakewhich is wired?13:19
sdakeweird?13:19
*** jtriley has joined #openstack-kolla13:20
sdakeagree - its odd13:20
sdakewtb solution to deploy gate13:20
sdakepbourke looks like a review is outstanding for xenial building13:20
Jeffrey4lya weird.13:20
Jeffrey4lhere : http://logs.openstack.org/74/355274/1/check/gate-kolla-dsvm-deploy-ubuntu-source-ubuntu-xenial-nv/2fc5b3c/console.html#_2016-08-15_02_33_08_72648013:20
Jeffrey4l\"msg\": \"the python mysqldb module is required\""13:20
*** imcsk8|zZz is now known as imcsk813:21
*** zhurong has joined #openstack-kolla13:21
Jeffrey4lthe kolla-toolbox has this module( installing by pip ). But it still complain the python-mysqldb do not exist.13:21
sdakethat has to do with the mixing of source and binary installs iirc13:22
Jeffrey4lin another patchset, i install the python-mysqldb by using `apt-get install python-mysqldb`, then it works.    weird.13:22
sdakekolla-toolbox should be source only - no binary at all13:23
sdakein other words - based upon -base, rather then openstack-base13:23
Jeffrey4lyes.13:23
Jeffrey4lit installed the latest pip.13:23
sdakebut that doesn't work without alot of effort13:23
sdakewhat we really need is a new base openstack-source-base13:23
sdake(I think but not 100% certain:)13:23
Jeffrey4lmove the ansible base to openstack-source-base?13:24
Jeffrey4lwhy?13:24
sdakeJeffrey4l no that isn't what i mean13:24
sdakekolla-toolbox inherits from openstack-base13:24
sdakeopenstack-base no mattr how you dice it, installs packges either via rpm or apt13:24
sdakethis is incompiatble with source-only containers13:25
sdakeinstalling with yum then later with pip resultss in teh mysql behavior you see13:25
Jeffrey4lit inherits from base13:25
Jeffrey4lFROM {{ namespace }}/{{ image_prefix }}base:{{ tag }}13:25
Jeffrey4lhttps://github.com/openstack/kolla/blob/master/docker/kolla-toolbox/Dockerfile.j2#L113:25
sdakeoh13:25
Jeffrey4lnot openstack-base13:25
sdakemaybe i didn't get enough sleep ;)13:25
*** dmueller-evoila has joined #openstack-kolla13:25
Jeffrey4l:p13:25
sdakeJeffrey4l cool thanks for the clarification - pretty sure that was not always the case13:26
Jeffrey4lwe installed MySQL-python https://github.com/openstack/kolla/blob/master/docker/kolla-toolbox/Dockerfile.j2#L4913:26
Jeffrey4lbut it complain still. whereas, when i tested it locally, it can not be reproduced.  :(13:27
kbaegisFeel dumb for asking, but how does one git-cherry pick when those aren't in the master branch?13:27
sdakeupper right hand corner13:27
sdakeclick download13:27
sdakeone of hte options is cherry-pick13:27
sdake(upper right hand corner of gerrit)13:28
kbaegisI'm using git from cli13:28
sdakeclic cherry pick - itwil copy to clipboard13:28
sdakepaste it13:28
kbaegisOh13:28
kbaegisNeat13:28
sdakeit will cherry-pick from gerrit13:28
kbaegisty :)13:28
sdakeit/git13:28
Jeffrey4lkbaegis, sdake please use checkout if you do not familiar with git.13:28
sdakeyup13:28
Jeffrey4lcherry-pick is more tricky and powerful :)13:29
*** ad_rien_ has joined #openstack-kolla13:29
sdakei like cherry-pick13:29
kbaegisI'm sort of familiar with git.  I use pull/reset/clean all the time13:30
kbaegisI'm not much of a developer though13:30
Jeffrey4lyes. cherry-pick is the best solution.13:30
Jeffrey4lbut you need cherry-pick two SP.13:31
Jeffrey4lSP/PS13:31
kbaegisSP?13:33
*** diogogmt has joined #openstack-kolla13:33
kbaegisI did both commits13:33
*** inc0 has joined #openstack-kolla13:35
sdakepbourke inc0 has arrived13:36
inc0"carrier has arrived"13:36
inc0wassup13:36
inc0I played with this stuff yesterday13:37
inc0repaved for ovs, deployed flat network13:37
inc0infra networking is ok13:37
inc0for some reason neutron added tagged iface13:37
inc0to flat network13:37
sdakeinc0 so the adding of tagged iface is the problem?13:38
kbaegisSharded interfaces will break ovs13:38
inc0no, vm doesn't have dhcp13:41
kbaegisWell, I cherry picked those commits and horizon is still 500'ing after redeploy13:42
pbourkesmekel_: ping13:42
*** diogogmt has quit IRC13:42
sbezverksdake: have you manage to get docker to use directly LVM instead of loop device?13:42
sdakesbezverk i always setup for btrfs so no13:43
*** zhurong has quit IRC13:43
sbezverkI see some issues with using loop on my kube cluster13:44
sbezverksdake: ok will google it13:44
*** zhurong has joined #openstack-kolla13:44
*** MrDan has quit IRC13:44
Jeffrey4li think the root cause should be the physical swither.13:44
Jeffrey4lswitcher.13:44
sdakeJeffrey4l we dont have access to the tor13:45
sdakeJeffrey4l by we, i mean osic in general can't modify settings13:45
Jeffrey4li set up a ovs bridge and add a vlan port on it manual. when ping the gateway, it has lots of loss.13:45
Jeffrey4lOK.13:45
kbaegisRebuilding horizon.  Just for kicks13:46
sdakeok well t-1 day until lwe abandon vm related testing with any of our tools13:46
Jeffrey4lbtw, the centos gate failed due to this neutron bug: https://review.openstack.org/#/c/355185/13:48
patchbotJeffrey4l: patch 355185 - neutron - Fixed neutron-db-manage without neutron/tests inst... (MERGED)13:48
Jeffrey4land it is merged already. So you can recheck you PS>13:48
*** mbound has joined #openstack-kolla13:48
pbourkeinc0: do you know if its a kolla problem or something else?13:48
sdakeJeffrey4l i did recheck it13:49
Jeffrey4lis it passed?13:49
sdakein t-1 day, we need to take a look at abaonding any vm related tests in rally and just focus on non-network tests13:49
sdakeJeffrey4l not sure - i just did it a bout 1 hour ago for that patch you linked that needs merging13:49
Jeffrey4lOK. thanks.13:49
sdakebecause otherwise we will miss ALL data13:50
sdakesome data is better then none13:50
sdakebut lets try to spend this last day sorting out this problem13:50
pbourkeJeffrey4l: sdake: can you guys review https://review.openstack.org/#/c/355808/13:50
patchbotpbourke: patch 355808 - kolla - Fix Neutron bootstrap failure due to missing fixtu...13:50
sdakeso we can get vm related performance data out of rally13:50
sdakepbourke on it13:50
pbourkewith that + the bandit + Jeffrey4l's patch all gates should be green again13:50
Jeffrey4lno... deploy ubuntu source is still buggy.13:50
Jeffrey4labout this https://review.openstack.org/34919713:51
Jeffrey4lpbourke, you want to use ansible side keystone_role ? ^^13:51
pbourkeJeffrey4l: unless you see a reason not to13:52
sdakepbourke we are using our own modules to decouple kolla from the ansible release cycle13:52
sdakeor lack thereof ;)13:52
Jeffrey4lwe are using lost of our side ansible module. depend on the ansible project is not stable.13:52
sdakeno 1.8.3 disaster in the future13:52
pbourkewe only do that for kolla_docker13:53
pbourkewe can't do that for all modules13:53
Jeffrey4lpbourke, no13:53
Jeffrey4lkolla_keystone_service13:53
sdakethe reason its targetedd at master is agreement between Jeffrey4l and i to do the member role adding work incrementally13:53
inc0sdake, t01 day?13:53
inc0we still have 2 weeks13:53
*** mbound has quit IRC13:53
Jeffrey4lkolla_keystone_user13:53
pbourkesdake: Jeffrey4l: this role is in ansible 2.1 right?13:53
sdakeinc0 what i mean is we will abandon vm related networking tests in 1 day - to unblock our other work13:53
inc0ok13:54
inc0we don't need tpo13:54
Jeffrey4lit is.13:54
pbourkeinc0: can you please summarise the issue? I've lost track of it :(13:54
inc0worst case scenerio I'll hack our way into network ns13:54
sdakei hate needless wheel reinvention, but in this case it is needful13:54
inc0hold on will log onto tmux13:54
pbourkeJeffrey4l: so just pip install ansible==2.1 on the stable branches13:54
Jeffrey4lBut we need upgrade the kolla-tools's ansible version to 2.1 in a stable version.13:54
sdakethe need is to decouple kolla from the ansible release cycle13:54
pbourkewe can't do that for all modules13:55
*** haplo37__ has joined #openstack-kolla13:55
sdakeunless folks feel this module is stable enough13:55
pbourkewe've had no trouble with this module im aware of13:55
sdakeok wfm then13:55
Jeffrey4llet's me check the ansible's code.13:55
sdakeJeffrey4l ya - give it a good review and make sure its up to snuff :)13:55
sdakethanks13:55
pbourkemaybe im missing something here13:55
inc0pbourke, come to tmux13:56
sdakepbourke iiuc we have never used the ansible module before13:56
sdakepbourke gets yanked around ;)13:56
Jeffrey4lbtw, i remove all the container in osic inc013:56
Jeffrey4lwhen try to fix the network issue.13:56
inc0well, they're there, looking at ovs now;)13:56
inc0I repaved13:56
Jeffrey4lcool13:56
pbourkeinc0: so correct me if im wrong, it seems to be a neutron config issue14:00
*** b_bezak_ has quit IRC14:00
inc0Jeffrey4l, btw I think we messed up interfaces in previous conf14:00
inc0pbourke, correct14:00
*** b_bezak has joined #openstack-kolla14:00
Jeffrey4linc0, does it work now?14:02
Jeffrey4li am i14:02
Jeffrey4li am coming14:02
inc0well, we get all traffic through cables14:02
inc0it's ovs issue now14:02
*** jamesdenton has joined #openstack-kolla14:03
*** ad_rien_ has quit IRC14:04
*** Guest55739 is now known as Pavo14:05
PavoI think I finally might have figured this out14:05
pbourkeinc0: im not good with this stuff, but is there any point in creating the provider network with type vlan14:05
inc0if you want multiple of them, yes14:05
*** zhurong has quit IRC14:06
Pavoalso if you want some provider vlans to interact with some services that you host in Openstack14:06
*** zhurong has joined #openstack-kolla14:06
Jeffrey4lwe need make it work first with any configuration.14:07
Jeffrey4lnow, in the dhcp namespace, we can not ping the gateway. here is the root issue.14:08
sdakei hate that problem14:08
sdakeit usually means sthere is a lack of route14:09
*** bootsha has quit IRC14:09
sdakei.e. network config problem14:09
sdakein the hardware..14:09
sdakebut keep at it guys :)14:09
sdakeelrog 845s on the way -> http://www.6moons.com/industryfeatures/elrog/1.html14:12
sdakeyay :)14:12
Pavohow long does it normally take for neutron-server container to start?14:12
Pavoduring deployment14:12
sdakepavo it should be millseconds14:12
sdakedocker ps -a14:12
Pavohmmm, been setting here for about 5 minutes now14:12
sdakeif you see something in restarting state, thats bad14:12
sdakecould you expandon "sitting here"14:13
kbaegisHmm14:13
sdakeyou mean ansible is blocked?14:13
kbaegisRebuilt horizon.  It's still not working, even after cherry picks14:13
sdakekbaegis syptoms of your failure are what?14:13
Jeffrey4lkbaegis, hmm you need rebuild kolla-toolbox, tool14:13
Jeffrey4lthe re-deploy14:14
sdakekbaegis my guess is you would need to cleanu pand deploy14:14
kbaegis500 is the symptom14:14
kbaegisOkay14:14
sdakerather then simply redeploy14:14
Pavobeen setting at this state for about 5 minutes sd14:14
sdakeafter applying jeffrey's suggestion of a toolbox rebuild14:14
Pavosdake14:14
PavoTASK [neutron : Starting neutron-server container] *****************************14:14
Pavoskipping: [node2]14:14
sdakehow many nodes do you have?14:14
sdakepavo ^14:14
*** bjolo has quit IRC14:15
*** narasimha_SV has joined #openstack-kolla14:15
Pavo214:15
sdakewhat is the network node?14:15
Pavodeployer plus 2 target nodes14:15
sdakewhat is the name of the network node14:15
narasimha_SVI am getting this error for openvswitch agent when I check the logs of the container14:15
narasimha_SV]# docker logs 4711df58d518 INFO:__main__:Kolla config strategy set to: COPY_ALWAYS INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json ERROR:__main__:Invalid json file found at /var/lib/kolla/config_files/config.json14:15
Pavonode114:16
sdakenarasimha_SV are you using kolla's json file or one you created?14:16
sdakecan the deployer ssh into node1?14:16
sdakefrom whatever user context your running kolla-ansible deploy?14:16
Pavonot currently14:16
PavoI think it building the bridges now14:17
sdakewell thats a problem14:17
Pavounless I have to do that manually14:17
sdakeyour nuetron network must be a seprate network interface14:17
narasimha_SVsdake: kolla's json file ?? I didn't understand about this14:17
sdakethe management network and neutron network cannot be shared14:17
sdakewhat is happening is your sharing the neutron and managmeenet network in some way, and the bridge setup craters connectivity to node114:18
sdakenarasimha_SV are you working on magnum integration or are you deploying directlly from kolla?14:18
narasimha_SVI am using mitaka stable branch of kolla14:18
narasimha_SVi am deploying directly from kolla14:18
narasimha_SVmagnum is not involved in this14:18
sdakenarasimha_SV - we have an integration effort happenign with upstream magnum is why i asked14:19
Pavothis is my globals https://paste.pound-python.org/show/C1jADxwasIZEmSF3jmJZ/14:19
sdakenarasimha_SV i'm a bit stumped on that one - can you paste the json in /var/lib/kolla/config-files?14:19
narasimha_SVsdake: fine . is the any problem with any configuration which I placed14:20
Pavothis is my inventory https://paste.pound-python.org/show/54zkBzjsPwqKclkI7dzz/14:20
sdakepavo: neutron_external_interface: "eth0"14:20
sdakethis needs to be a unique interface14:20
Pavoso target host need 3 nics?14:20
sdake2 nics14:20
PavoI have 2 nics14:20
sdakeit is possible you ahve eth1 and eth0 switched around14:20
narasimha_SVsdake: # ls -l /var/lib/kolla/ total 0 drwxr-xr-x 1 root root 10 Aug 16 10:16 usr14:21
Pavolet draw a network diagram really quick14:21
narasimha_SVapart from usr folder i dont see any other files in /var/lib/kolla14:21
pbourkeinc0: Jeffrey4l: can we not create flat networks14:21
sdakenarasimha_SV run ansible --version14:21
Jeffrey4lpbourke, we can. But i tried that. not work14:22
pbourkesame problem?14:22
sdakenarasimha_SV it should report 1.9.414:22
Jeffrey4lpbourke, yep14:22
Jeffrey4llinuxbridge should has the same issue, right? inc0 ?14:22
narasimha_SVsdake: ansible 1.9.614:23
sdakenarasimha_SV run pip show jinja214:23
narasimha_SVI am seeing all these files in /etc/kolla folder that config.json14:23
narasimha_SVhttp://paste.openstack.org/show/558401/14:24
sdakenarasimha_SV run pip show kolla as well14:24
sdakewe require jinja 2.8.0 or later14:24
sdakeneed to update that14:24
sdakerun pip show kolla though as well14:24
sdakerhallisey ping14:28
sdakere https://review.openstack.org/#/c/348029/3/doc/deployment-philosophy/deployment-philosophy.rst14:28
patchbotsdake: patch 348029 - kolla - Build a more organized doc structure14:28
Jeffrey4lcould we get some hep from osic guys? i still think it should physical switcher issue. inc0 sdake14:29
Pavosdake this it the kind of network I am running right now https://www.dropbox.com/s/phx32ggavh1uc5p/Screenshot%202016-08-16%2010.28.57.png?dl=014:29
Pavoprobably not ideal14:29
sdakePavo can you put somewhere where I dont have to sign in pls :)14:30
sdakegoogle drive would work for me14:30
Pavoyou shouldn't have to but sure14:30
sdakenm14:30
sdakeyour right don't have to sign in14:30
Pavoyeah didn't think you did14:30
sdakePavo are you running on virtual machines here?14:31
sdakepavo if so, the nat in that diagram will crater your network - you mustuse host networking feature instead (atelast in virtualbox)14:31
Pavobasically I am trying to use eth0 network as management and internet access for openstack and using eth1 network for communication between the nodes14:31
Pavoyeah14:31
sdakepavo the way you ahve it setup now in your globals.yml14:31
sdakeeth0 = neutron interface14:32
sdakeeth1=mgmt interface14:32
sdaketry switching those around first14:32
sdakereboot vms14:32
sdakeand probably your host as well14:32
Pavook14:32
Jeffrey4lsdake, pbourke the os_keystone_role in ansible 2.1 seems OK.14:32
Jeffrey4lBut are u really think it is OK to move 2.1 in the stable/mitaka branch?14:33
sdakewe are not moving all of our deployment to 2.114:33
sdakejust the toolbox14:33
pbourkeJeffrey4l: ok again unless Im missing something Id just use that. we only created our own docker module as the its so central to our project and ansible didnt commit to maintaining it properly14:33
sdakejust the toolbox is okk14:33
Jeffrey4lOK.14:33
pbourkeJeffrey4l: try it and if gates pass should be ok14:33
Jeffrey4lI will try.14:34
Jeffrey4lbut we need another PS to upgrade the toolbox first, it it work14:34
*** satya has joined #openstack-kolla14:34
Pavowait I already have that sdake14:34
*** b_bezak has quit IRC14:35
*** michauds has joined #openstack-kolla14:35
sdakelink globals.yml again - sorry too much conversation goiing on at once14:35
Pavoneutron int is eth0 and network int is eth114:35
sdakeyes14:35
sdakebut you just said above14:35
sdakeyou want eth0 to be your management interface14:35
sdakeand eth1 to be your neutron network14:35
*** daneyon has joined #openstack-kolla14:35
sdakepavo ^14:35
Pavoah ok I get you, but doesn't the kolla_internal_vip_address have to be on the same int as neutron?14:36
satyaI have deployed openstack kolla multinade . while creating the instance most of the time i am getting the error: ERROR neutron.api.v2.resource InvalidRequestError: This Session's transaction has been rolled back by a nested rollback() call.  To begin a new transaction, issue Session.rollback() first.14:36
sdakepavo no it needs to be ont he management network14:36
Jeffrey4linc0, sdake pbourke how can we ask help from osic?14:36
satyaCould you please help me in finding the root cause of the issue14:36
Pavook lol I will try it again14:36
sdakehey satya - weclome to the part y:)14:36
openstackgerritAlexander Reunov proposed openstack/kolla: Fix murano notification driver  https://review.openstack.org/35597914:36
sdakesatya doing an eval or planning to do kolla development?14:37
satyaplanning kolla deployment14:37
*** diogogmt has joined #openstack-kolla14:37
sdakesatya are you running master or a stable branch?14:37
Pavosdake but isn't the neutron_external_interface the int for internet access?14:37
sdakepip show kolla will tell yoou teh answer14:37
sdakePavo yes14:37
sdakeoh vip_external14:37
*** lrensing_ has joined #openstack-kolla14:37
sdakePavo you only need vip_external for TLS14:38
sdakepavo do you have TlS?14:38
Pavothen I am totally confused lol14:38
sdakeif not, then comment it  out14:38
satyai am running master branch14:38
satyathe stacktrace of the error is given below14:38
sdakesatya i'd highly reecommend running a stable branch for eval14:38
satya2016-08-16 12:42:57.991 50 ERROR neutron.api.v2.resource   File "/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/api/v2/resource.py", line 79, in resource 2016-08-16 12:42:57.991 50 ERROR neutron.api.v2.resource     result = method(request=request, **args) 2016-08-16 12:42:57.991 50 ERROR neutron.api.v2.resource   File "/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/api/v2/base.py", line 571, in update 2016-0814:38
sdakesatya openstack is in a constant state of broken/unbroken and an eval of master will just make you sad ^^14:38
Pavook in global/yml network interface is what?14:39
satya2016-08-16 12:42:57.991 50 ERROR neutron.api.v2.resource     obj = obj_updater(request.context, id, **kwargs) 2016-08-16 12:42:57.991 50 ERROR neutron.api.v2.resource   File "/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/common/utils.py", line 618, in inner 2016-08-16 12:42:57.991 50 ERROR neutron.api.v2.resource     return f(self, context, *args, **kwargs) 2016-08-16 12:42:57.991 50 ERROR neutron.api.v2.resource   F14:39
Pavomanagement or communication between host14:39
sdakenetwork_interface is the management wnetwork14:39
Pavook which is on the same network as my internet14:39
sdakethe management network includes the deployment network14:39
pbourkeJeffrey4l: inc0: "These NICs have not been well tested in Ubuntu and as such the upstream i40e driver in the default 14.04.3 Linux kernel will begin showing issues when you setup VLAN tagged interfaces and bridges."14:39
satyadid anybody observed this issue with master branch14:40
sdakepavo by internet, do you mean 192.168 address or somethign ele?14:40
pbourkeJeffrey4l: inc0: "If you will be installing Ubuntu Server 14.04 on these servers, I highly recommend you use an i40e driver no older than 1.3.47."14:40
sdakesatya not yet - our gates are passing14:40
Jeffrey4lpbourke, where did u get the info?14:40
*** daneyon has quit IRC14:40
pbourkeJeffrey4l: its in the original email and also the osic guide14:40
Jeffrey4lpbourke, OK.14:40
Pavothe network I want to be able to access horizon and the instances inside openstack to use as External network14:40
sdakesatya if your doing an eval or deploy, i highly recommend stable/mitaka or stable/liberty14:40
pbourkeJeffrey4l: inc0: we currently seem to have 1.2.214:40
sdakethey start with stable/ for a reason ;)14:40
Jeffrey4lcool found the root cause14:40
Jeffrey4lyes. it is.14:40
Jeffrey4lhow about upgrade the kernel?14:41
satyaour stable/mitaka is running fine14:41
Jeffrey4lor using ubuntu 16.04?14:41
satyanow we want to use master branch14:41
duonghqstaya" commit a2e369982d is quite good for test14:41
sdakesatya roger14:41
pbourkeJeffrey4l: im not sure but lets update the kernel to start with14:41
Jeffrey4lOK14:41
*** bootsha has joined #openstack-kolla14:41
duonghqsatya: commit  a2e369982d is quite good for test14:41
sdakesatya a big chunk of our team is a bit busy atm working on osic scale testing (limited time window of  2 weeks left) so don't have direct time to debug thatissue at this moment14:41
sdakesatya i'd recommend filing a bug14:42
satyacould you please provide any pointers in identifying root cause of this issue14:42
sdakelink it - i'll mark it as critical and confirmed14:42
sdakesatya no clue what would cause that14:42
Jeffrey4lpbourke, how about try just one machine first?14:42
sdakesatya it will require coordination between our team and neutron team and possibly nova14:42
pbourkeegonzalez90: thats boring :p14:42
pbourkeJeffrey4l: ^14:42
satyanova does not have any issue14:42
pbourkeJeffrey4l: joking ok will do14:42
Jeffrey4lwe can test it by using `ping the gateway from the dhcp namespace`14:42
Jeffrey4lpbourke, ugprade the control first?14:43
satyaif i try to create vm 7 times. 6 times this exception is thrown. only one time it is succeeding.14:43
sdakepavo - please paste your globals.yml again14:43
Pavosdake https://paste.pound-python.org/show/C1jADxwasIZEmSF3jmJZ/14:44
sdakesatya google search turn up anything?14:44
satyanova-compute is not able to get network from neutron-server14:44
satyahttps://bugs.launchpad.net/neutron/+bug/140977414:44
openstackLaunchpad bug 1409774 in neutron "sqlalchemy session needs to be rolled back after catching a db exception" [Undecided,Expired]14:44
satyamy issue is same as above bug14:44
sdakepavo you do not have the external vip configured - also don't have tls configured14:45
sdakeso ther ewill be no external vip14:45
sdakeso your good to go14:45
sdakejust switch eth1 and eth0 around14:45
Pavook14:45
satyabut in my case it is happeing when port_update is called14:46
satyacan I reopen the bug 140977414:46
openstackbug 1409774 in neutron "sqlalchemy session needs to be rolled back after catching a db exception" [Undecided,Expired] https://launchpad.net/bugs/140977414:46
sdakesatya - not sure - ask the neutron cats - tell them master is busted14:47
satyaok thanks.14:47
sdakesatya filing a bug would hep :)14:48
satyait should be a neutron bug or kolla bug14:49
sdakekolla could possibly be misconfiguring some new change in neutron14:49
*** mbound has joined #openstack-kolla14:49
satyawill create a new bug14:49
sdakeor more likely neutron is broke n:)14:49
sdakeJeffrey4l did you say you got to the root cause of the connectivity problems?14:50
Jeffrey4lsdake, seem so . pbourke found some useful info. we are testing it.14:50
sdakemind sharing a tldr?14:50
Jeffrey4lsdake, https://github.com/osic/ref-impl/blob/master/documents/bare_metal_provisioning.md#update-linux-kernel-114:50
Jeffrey4lthe nic driver issue14:51
pbourkesdake: the network driver that comes in 14.04 is buggy14:51
sdakeright we were warned about the nic drivers14:51
sdakethanks!14:51
satyaok thanks sdake14:51
*** mbound has quit IRC14:54
*** narasimha_SV has quit IRC14:55
Pavook it finished, what IP do I access horizon with now14:57
duonghqthe internal vip14:57
Pavook I can ping that but not working for web14:58
sdakepavo - cool - see you ahd your networks backwards :)14:59
sdakebrb14:59
duonghqPavo: can you telnet the web service port?14:59
*** ad_rien_ has joined #openstack-kolla14:59
Jeffrey4lseems the solution(upgrade the kernel) works.14:59
sdakehotness!15:00
Pavotelnet 192.168.1.25415:00
PavoTrying 192.168.1.254...15:00
Pavotelnet: connect to address 192.168.1.254: Connection refused15:00
Pavotelnet: Unable to connect to remote host15:00
sdaketry telnet to port 80 on that ip15:01
pbourkeinc0: got a minute for quick question wrt macros15:04
Pavobeen awhile since I telnet lol, the cmd to use a port is just telnet 192.168.1.254 80 right15:04
sdakepbourke Jeffrey4l inc0 are we good to go with sshing into vms now?15:04
duonghqPavo: you deploy on your VM or your lab? iirc the horizon is enabled by default15:04
sdakewith both linuxbridge and ovs?15:04
pbourkesdake: still updating rest of the nodes15:04
pbourkesdake: we'll let you know :)15:04
Jeffrey4lsdake, we should. Just make a small test.15:04
sdakeplease do15:04
openstackgerritEduardo Gonzalez proposed openstack/kolla: Customizations for Senlin  https://review.openstack.org/35201315:04
duonghqPavo: can you check horizon log?15:04
pbourkeJeffrey4l: it didnt seem like therew as 130 nodes in that output15:05
*** zhubingbing has quit IRC15:06
Pavoduonghq horizon logs https://paste.pound-python.org/show/JUgJyZE0I4DtHEICvY1I/15:06
Jeffrey4lpbourke, let's check the result when the nodes is up.15:06
sdakepavo telnet 192.168.1.254 8015:06
pbourkeJeffrey4l: ok cool15:06
Pavosdake yeah can not telnet to it15:07
sdakepavo those logs look ok15:07
sdakecan you ssh to the hosts at all?15:07
Jeffrey4lpbourke, about the `mount --make-shared /run` in ubuntu. Does it work if add this to the fstab?15:07
pbourkeJeffrey4l: not sure15:07
Pavosdake yeah15:07
sdakeJeffrey4l you can't just add that command right in fstab15:07
sdakebut it may be possible to automate that via some other mechanism15:07
inc0pbourke, shoot15:09
pbourkeinc0: smekel_ raised the case where we want to handle an empty package list15:09
pbourkehttps://review.openstack.org/#/c/354429/15:09
patchbotpbourke: patch 354429 - kolla - Handle empty package list for install_packages15:09
sdakeneed to handle that15:09
*** rstarmer has quit IRC15:09
pbourkeinc0: problem with the patch currently is if the macro returns nothing, we still have a "RUN" hardcoded into the Dockerfile15:10
pbourkeinc0: so I propose moving the "RUN" into the macro15:10
inc0that's ok15:10
inc0makes sense15:10
pbourkeinc0: I think it makes sense, just said Id run it by you as it means refactoring all the existing customisations15:10
pbourkenot by much mind you15:10
sdakeshould take him 30 minutes max :)15:10
inc0yeah, we'll need to remove all the RUN's15:10
inc0but that's one grep15:10
pbourkegrand I'll update the patch and see if everything builds15:10
pbourkeyup already done15:11
inc0cool, thanks15:11
inc0hmm you updated kenrle everywhere Jeffrey4l15:11
inc0?15:11
sdakesean-k-mooney - just a heads up - you may not get the full week you were promised originally on osic cluster15:12
Jeffrey4linc0, should pbourke does.15:12
openstackgerritPaul Bourke proposed openstack/kolla: Handle empty package list for install_packages  https://review.openstack.org/35442915:12
sdakepriorities are our currently defined scenarios with tempest+rally, then bifrost scale out testing15:12
pbourkeinc0: any reason we should not have?15:12
Jeffrey4linc0, and it works.15:12
Jeffrey4lya, why not?15:13
inc0 no, just wondering if you're onto anything:_)15:13
*** vhosakot has joined #openstack-kolla15:13
sdakei think kernel update everywhere is mandatory since that nicc is on all the gear15:13
sdakemorning vhosakot15:13
vhosakotsdake: morning!15:14
*** michauds has quit IRC15:15
*** belmoreira has quit IRC15:17
Pavoyeah keep getting no route to host but can ping the internal ip15:17
Pavoat least I got this close15:18
sdakepavo - i need to head to dr soon15:18
sdakeand will be out of office for ~2 hrs15:18
sdakepavo duonghq may be able to help you15:18
sdakepavo otherwise, just  a heads up in case I dont respond :)15:18
Pavono problem, I will continue TSing15:18
duonghqPavo: what is your network topo?15:19
Pavoand I thought openstack networking was a nightmare to understand, now kolla giving me the headache lol15:19
Pavoduonghq https://www.dropbox.com/s/phx32ggavh1uc5p/Screenshot%202016-08-16%2010.28.57.png?dl=015:19
sdakepavo not kolla - its neutron - blame neutron :)15:19
duonghqso you setup 3 VMs?15:20
*** athomas has quit IRC15:20
sdakeduonghq he has his network setup properly but he is using a nat on a virtual machine15:20
Pavolol yeah but how kolla defines what neutron uses is what I need to understand I think15:20
Pavoduonghq yes15:20
sdakei think you can't access nat from a desktop15:20
sdakethat is why you need that host networking bridged mode thing in virtualbox15:20
duonghqwhich hypervisor do you use15:20
PavoI have all the eth0 bridged in VMWare fusion15:21
PavoI have all the eth1s shared ie... NAT15:21
sdakepavo that should work then15:21
sdakealthough i dont have experience with fusion15:21
sdakeonly virtualbox15:21
Pavoeth0 https://www.dropbox.com/s/w0ctrs0uephe7j3/Screenshot%202016-08-16%2011.21.45.png?dl=015:21
duonghqso you set network_interface to eth0?15:22
Pavoeth1 https://www.dropbox.com/s/cbw9pp6706006xh/Screenshot%202016-08-16%2011.22.03.png?dl=015:22
Pavoduonghq yeap15:22
sdakewifi..15:22
openstackgerritLi Yingjun proposed openstack/kolla: Fix no tar command for magnum conductor using ubuntu  https://review.openstack.org/35600815:22
sdakeyour on a laptop?15:22
Pavoduonghq kolla_internal_vip_address: "192.168.1.254"15:23
Pavoduonghq network_interface: "eth0"15:23
Pavoduonghq neutron_external_interface: "eth1"15:23
*** athomas has joined #openstack-kolla15:24
duonghqI'm not pretty sure which node got the VIP15:24
duonghqwhat is your nodes' ip15:24
Pavonode1 192.168.1.45, node2 192.168.1.1115:25
Pavofor eth015:25
openstackgerritEduardo Gonzalez proposed openstack/kolla: Add Senlin Ansible role  https://review.openstack.org/33972515:25
Pavonode1 192.168.188.129, node2 192.168.188.130 eth115:25
openstackgerritLi Yingjun proposed openstack/kolla: Fix no tar command for magnum conductor using ubuntu  https://review.openstack.org/35600815:26
sdakepavo - idea - instead of accessing vip15:26
sdaketry accessing node directly on port 8015:26
Pavook15:26
pbourkeinc0: you around to do that dhcp test again?15:26
Pavonegative for both15:26
sdakeping works for both?15:27
Pavoroger15:27
sdakedisable iptables on the two machines15:27
sdakereboot the vms15:27
sdakecleanup then reboot i mean15:27
Pavook so use the tools files?15:28
sdakepavo right15:28
Pavocleanup-containers and cleanup-host15:28
Pavoroger15:28
sdakepavo are you running centos or ubuntu vms?15:28
Pavocentos 7 for all 315:28
sdakesystemctl disable firewalld15:28
*** daneyon has joined #openstack-kolla15:28
Pavoroger15:28
duonghqPavo: after that, can you inspect horozion container on those VMs?15:29
Pavoroger15:29
sdakethose arguments may be backwards15:29
sdakeon all 3 nodes15:29
sdakereboot even your deployer node15:29
*** bootsha has quit IRC15:29
Pavowill have to redeploy just ran the cleanup scripts15:29
Pavolol15:29
inc0pbourke, give me 10min15:29
sdakeafter that change15:29
pbourkeinc0: cool15:29
*** michauds has joined #openstack-kolla15:30
*** daneyon_ has quit IRC15:32
Pavook did cleanup scripts on target nodes, disabled firewalld on all three nodes and rebooted, now redeploying15:32
*** matrohon has quit IRC15:32
sdakeJeffrey4l - I may havea conflict during our team meeting wednesday - any chance you would like to take on facilitating the team meeting?15:33
sdake(as in charing it)15:33
sdakechairing it15:33
pbourkeJeffrey4l: this is weird, never seen before15:35
pbourkeJeffrey4l: that said dont reboot often15:36
Jeffrey4lpbourke, yes.15:36
Jeffrey4lthe rabbitmq cluster seem not joined up, then failed.15:36
sdakebut it was working prior?15:37
*** zhurong has quit IRC15:37
pbourkeinc0: sdake working!!15:40
pbourkeWOOT15:40
duonghqPavo: anything news?15:40
sdakepbourke as in ssh into vm works?15:41
sean-k-mooneysdake: re osic cluster that fine. if we need to push or drop the bifrost testing to complete the other work items i think that makes sense15:41
openstackgerritChristian Berendt proposed openstack/kolla: Add a note about the sandbox environment to the CONTRIBUTING doc  https://review.openstack.org/35601715:41
sdakesean-k-mooney cool - but i'd like to give you atleast a cuple days crack at the gear15:42
sdakesean-k-mooney i don't know how you feel about weekends, but the gear seems to be available then :)15:42
openstackgerritChristian Berendt proposed openstack/kolla: Add a note about the sandbox environment to the CONTRIBUTING doc  https://review.openstack.org/35601715:42
pbourkesdake: actually celebrated too soon, ping works but ssh not yet15:42
sdakesean-k-mooney but you would probably need help of others who have ramped up all the network setup issues15:42
pbourkesdake: very close though I think15:42
Pavostill deploying15:43
*** daneyon_ has joined #openstack-kolla15:43
pbourkesdake: ssh working15:45
sdakehot - so root cause was 710 driver?15:45
*** daneyon has quit IRC15:45
sdakewhat else did you do?15:45
Jeffrey4lsdake, nothing. it it the driver issue.15:46
pbourkesdake: that's it15:46
sdakecool15:46
sdakethanks!15:46
*** dmueller-evoila has quit IRC15:47
pbourkei have a script to run all rally tests we're intrested in in another tmux15:47
Pavook done and now getting alittle closer15:47
Pavohttps://www.dropbox.com/s/3wugmb0nyrgu10k/Screenshot%202016-08-16%2011.47.03.png?dl=015:47
pbourkeright now I have to do some internal stuff but if someone wants to continue with that let me know15:47
*** haplo37__ has quit IRC15:47
sdakei think we are ready for coolsvap to do the magic with rally15:48
sdakewouldn't hurt if someone else learned dthat as well15:48
sdakei'd take it on, but ogtta jet in 15-20 mins15:48
duonghqPavo: can you check the haproxy/keepalived?15:48
Pavologs?15:48
duonghqyup15:48
sdakevhosakot - available for scale testing ?15:48
sdakevhosakot  - specifically learning and configuring our rally setup so it actually tests something useful :)15:49
pbourkeim familiar enough with the rally stuff15:49
pbourkeso please ping me if you want in15:49
Pavohaproxy logs https://paste.pound-python.org/show/4ybRwDCld95WC6FI2tJa/15:49
Pavokeepalive logs https://paste.pound-python.org/show/fDnYGgrXgEy2eTdpJaRU/15:50
sdakepavo those are not the logs you are looking for15:50
*** athomas has quit IRC15:50
sdakedocker exec heka ls -l /var/log/kolla15:50
Pavoah15:50
Pavoon the networking node?15:51
openstackgerritPaul Bourke proposed openstack/kolla: Handle empty package list for install_packages  https://review.openstack.org/35442915:52
Jeffrey4lthis block the horizon deployment https://review.openstack.org/35523215:53
Jeffrey4lon master.15:53
Pavoduonghq what is the cmd to see the logs you are looking for?15:53
*** hieulq_ has joined #openstack-kolla15:55
duonghqactually, I want to see which node get the VIP, and then horizon log in this node15:55
berendtJeffrey4l horizon change looks good, use of an array for multiple memcache servers for django is correct15:55
Pavohow to tell which one got the VIP15:56
Jeffrey4lberendt, thanks.15:56
duonghqI think "ip addr" in each node is ok15:56
openstackgerritLarry Rensing proposed openstack/kolla: Add support for building vmtp container  https://review.openstack.org/35436215:56
*** athomas has joined #openstack-kolla15:56
NachoDuckHey, sorry to interrupt. If I want to setup a VLAN provider network (i.e edit ml2_conf.ini), how do I approach this in Kolla?15:57
berendtat all i am not sure if it makes sense to specify multiple memcached servers, in my environment i overwrite all memcached settings to only use the local available memcachd server15:57
duonghqbut which node you get the log above?15:57
Pavonode1 https://paste.pound-python.org/show/ZQGULjphXaJmfjoMbHMC/15:57
Jeffrey4lberendt, how about when local memcached crashed?15:57
Pavonode2 https://paste.pound-python.org/show/GaSfXSSFh9IicMIuJwq3/15:57
berendtJeffrey4l than caching is not working, that is fine for me15:57
duonghqso, check node1 horizon log15:57
*** huikang has joined #openstack-kolla15:57
duonghqapache2 log, too15:57
berendtJeffrey4l but i think it makes no sense when a service connects to a memcached service running on an other host15:58
Pavothe container log ie... docker logs blah?15:58
berendtJeffrey4l but i have not benchmarked it...15:58
Jeffrey4lberendt, yes, it is. but using multi memcached will more robust.15:58
duonghqjust use heka container like sdake mentioned15:59
inc0NachoDuck, https://github.com/openstack/kolla/blob/master/doc/advanced-configuration.rst#openstack-service-configuration-in-kolla15:59
duonghqsomething like /var/log/kolla/apache215:59
duonghqis there anything like that?15:59
Jeffrey4lberendt, in some case, ( like murano dashboard ), it require memcached as session storage. In this case, just use local memcached will cause some issue.15:59
sbezverkinc0: do you have a second for qq?15:59
inc0sure sbezverk16:00
berendtJeffrey4l ok, i do not provide murano at the moment, i will re-evaluate this in the future, but at the moment it is working quite good with only one memcached process16:01
Pavoduonghq cat: /var/log/kolla/horizon: Is a directory16:01
sbezverkinc0: since new variable got introduced orchestration_engine, can we then customing services configuration so they would be more consumable by kube?16:01
Pavoduonghq cat: /var/log/kolla/apache2: No such file or directory16:01
inc0sbezverk, so what we wanted to do is to put all of configs to shared dir as images16:02
inc0so I'd say yeah, we want same conf files16:02
duonghqPavo so, let me the horizon log16:02
NachoDuckinc0: I've had a read through that but changes I made don't seem to apply, or rather the file is reset after a reconfigure. I've tried creating it under /etc/kolla/config/neutron/plugins/ml2 and also /etc/kolla/neutron-server/ml2_conf.ini I take I'm doing something wrong here but no too sure what16:02
sbezverkinc0: example glance-api for kolla points to VIP, I need to point it to a specific dns name, can I use if statement to check for orchestration engine and if it is kubernetes then use value I need16:02
sbezverk>16:02
berendtPavo docker exec -it horizon ls /var/log/kolla/horizon16:02
Pavook figured it out16:02
Pavoduonghq horizon log16:02
Pavohttps://paste.pound-python.org/show/8p9K7LPbtPNwgv84JoKW/16:03
sbezverkinc0: thanks16:03
berendtPavo you can also directly access the kolla-logs volume, cd /var/lib/docker/volumes/kolla_logs/_data16:03
*** srwilkers has quit IRC16:03
sdakehttps://twitter.com/steven_dake16:03
Pavook16:04
sdakeenjoy :)16:04
inc0NachoDuck, and what you should do is /etc/kolla/config/neutron/ml2_conf.ini16:04
inc0https://github.com/openstack/kolla/blob/master/ansible/roles/neutron/tasks/config.yml#L6516:04
sdakei wonder if I beg ortofon enough if they will rebuild my cadenza black for no cost ;)16:04
inc0this is code that will deploy the conf16:04
duonghqPavo: ahah, so horizon fails you16:04
inc0sbezverk, so how about something different16:05
Pavosays its up16:05
Pavo575ebd442305        deployer.local:4000/kolla/centos-binary-horizon:3.0.0                     "kolla_start"           19 minutes ago      Up 9 minutes                            horizon16:05
inc0just thinking16:05
inc0see how we use merge_config in ansible?16:05
NachoDuckinc0: I see, thanks for your help :)16:05
inc0 maybe provide this kind of mechanism in k8s16:05
openstackgerritMerged openstack/kolla: Make the enable_isolated_metadata and force_metadata to yes in default  https://review.openstack.org/35270916:05
inc0NachoDuck, no problem, let us know if you have any other issues16:06
inc0sbezverk, but don't let that stop you. I think proper shared configuration would be good work for Ocata16:06
inc0we should discuss that on summit, how exactly we want to do it16:07
inc0we could for example have this block mechanism we use now for dockerfiles16:07
sbezverkinc0: well it makes life very difficult, as everytime I genconfig, I need to go and manually changes 10k of values16:07
duonghqPavo: can you upload full horizon log?16:07
Pavoyeah16:07
inc0yeah sbezverk sure, we need to figure out good way, all I'm saying16:07
sbezverkinc0: it introduces 20k of type errors and delay develoopment16:08
inc0what I don't want to have at the end of the day is 100 ifs in configs16:08
inc0if k8s then elif ansible elif chef...16:08
inc0we need to figure out good way to work with that stuff16:08
sbezverkinc0: got it16:08
sbezverknext engine will be added as elif16:08
*** sdake has quit IRC16:09
inc0at some point it would be great to be able to add new engine without any changes in kolla16:09
Pavoduonghq this is the full log https://paste.pound-python.org/show/YdbzI1xSZnbffUEiMqyG/16:09
inc0kolla will just be consumed16:09
duonghqpavo: let see16:10
PavoI scp it from /var/lib/docker/volumes/kolla_logs/_data/horizon/horizon.log16:10
Pavoon node116:10
Pavolooks like a lot of python errors16:10
duonghqyup16:10
duonghqDjango, indeed16:11
Pavorebuild images?16:11
duonghqnot sure, let me search around16:12
Pavoroger just checked the python version on all nodes and its 2.7.516:12
duonghqI think it is fine16:13
Pavoyou gonna be on for a bit, gotta run to the store for about 30 minutes16:13
inc0Jeffrey4l, pbourke deployment finished16:13
inc0Jeffrey4l, what kind of network you did when it worked?16:13
pbourkeinc0: we didnt change any of the settings16:14
Jeffrey4linc0, current works16:14
pbourkejust rebooted the VM16:14
pbourke(the guest)16:14
Jeffrey4li am fixing the metadata issue.16:14
Jeffrey4lworks. :D16:15
Pavobe back in like 30 duonghq16:15
duonghqPavo: tommorrow I'll recheck the error when I reach my dev machine (if I have time), but I think kbaegis has experience16:16
duonghqso, how can I reach you in case I found something?16:16
PavoI'll PM you my email16:16
duonghqokay16:16
duonghqPavo: I think you can try rollback the docker/horizon some commit and try build and deploy horizon (just kolla-ansible upgrade)16:33
*** unicell has quit IRC16:34
* duonghq head to my bed now 16:34
*** duonghq has left #openstack-kolla16:34
kbaegisHmm16:36
kbaegisStill getting 500 from proxy after patch16:36
kbaegis2.0.1 works, 3.0.0 horizon does not16:36
kbaegiscleaned and rebuilt16:37
kbaegismore accurately patched, reinstalled, cleaned, rebuilt, redeployed16:37
openstackgerritPaul Bourke proposed openstack/kolla: Fix neutron-server section in AIO sample inventory  https://review.openstack.org/35605616:38
sean-k-mooneypbourke: inc0  so out of interest is the networking issue in the osic cluster relsolved16:40
pbourkesean-k-mooney: I think so16:41
sean-k-mooneypbourke: ok cool16:41
pbourkesean-k-mooney: we can boot guests on the VLAN provider net and ssh to them16:41
sean-k-mooneypbourke: what was the issue in the end16:41
kbaegisGoing to roll back just the horizon16:41
inc0pbourke, so at the end of the day...it was kernel issue right?16:41
pbourkesean-k-mooney: the network driver is buggy on the switches osic use16:41
pbourkesean-k-mooney: so we needed to update. The osic docs say this but we were using an ISO which someone told me was up to date16:42
inc0I'm to blame probably16:42
pbourkekind of crazy that was it really, was sure it would be some configuration issue16:42
inc0well16:42
sean-k-mooneypbourke: on the switches? do you mean nics or the TORs?16:42
inc0irtermite, btw ^16:43
*** thumpba has joined #openstack-kolla16:43
inc0sean-k-mooney, nics in servers16:43
pbourkesean-k-mooney: whats a TOR again?16:43
inc0top of the rack switch pbourke16:43
pbourkeinc0: I thought it was the TORs16:43
inc0it were nics16:43
inc0we don't have access to TOR at all16:43
pbourkeah sorry you're right16:44
*** berendt has quit IRC16:44
pbourke" All servers contain two Intel X710 10 GbE NICs. This is a relatively new NIC that has caused us a lot of problems during the setup of the OSIC environment. If you will be installing Ubuntu Server 14.04 on these servers, I highly recommend you use an i40e driver no older than 1.3.47."16:44
pbourkeat least we solved it :)16:44
sean-k-mooneyoh wait your are using ubuntu 14.04. did you upgrade the kernel or use the default kernel16:44
*** ad_rien_ has quit IRC16:45
pbourkesean-k-mooney: we upgraded the kernel to xenial16:45
pbourkei thought the iso we were using had an up to date kernel, so kind of my fault :(16:45
sean-k-mooneyi taught you were using niantics (x520) but yes the x710 dirver in the default ubuntu 14.04 kernel is broken16:45
sean-k-mooneyi should have copped that. i knew that driver was broken but it should be fine if you were useing the vivid kernel or newer but i didnt know you were using those nics16:46
*** egonzalez90 has quit IRC16:47
openstackgerritMerged openstack/kolla: enhancements to install_packages macro  https://review.openstack.org/34856717:02
*** srwilkers has joined #openstack-kolla17:05
pbourkeim off guys - please check latest update that will be arriving to the ML any minute now, add to it if you need17:07
*** david-lyle_ has joined #openstack-kolla17:09
*** srwilkers_ has joined #openstack-kolla17:11
irtermiteinc0: what am I looking at above? the update part? right on17:12
*** david-lyle has quit IRC17:13
irtermiteglad to see someone reads my emails ( thanks pbourke )17:13
*** david-lyle_ is now known as david-lyle17:13
openstackgerritJoseph Horne proposed openstack/kolla: Minor doc fix  https://review.openstack.org/35606817:14
irtermite;)17:14
*** unicell has joined #openstack-kolla17:14
*** srwilkers has quit IRC17:15
*** srwilkers_ is now known as srwilkers17:15
ntpttr___inc0: ping17:15
irtermitentpttr___: I THINK he is at the food trucks17:15
ntpttr___ah that would make sense, it's 12:15 in the great country of texas17:16
irtermitehahaha @ country17:16
irtermiteyea17:16
*** srwilkers_ has joined #openstack-kolla17:16
ntpttr___maybe someone else can help me, I'm having a bit of trouble with a deploy involving ceph17:16
irtermiteneed me to go smack him for you?17:16
ntpttr___idk if the problem is ceph itself or not, because the error is happening in the neutron playbooks17:17
irtermiteah... <not it>17:17
ntpttr___the error is here, it's only failing on the storage servers running ceph http://paste.openstack.org/show/557765/17:17
*** daneyon has joined #openstack-kolla17:18
*** srwilkers has quit IRC17:19
*** srwilkers_ is now known as srwilkers17:19
*** daneyon has quit IRC17:23
*** Serlex has quit IRC17:23
openstackgerritJosh Lothian proposed openstack/kolla: Customizations for heka  https://review.openstack.org/34686117:25
*** mark-casey has joined #openstack-kolla17:26
*** dasTor has quit IRC17:27
sean-k-mooneyntpttr___: its just a guess but i think one of those groups is not defined.17:27
sean-k-mooneyntpttr___: can you check if all the groups are in the inventory file?17:28
kbaegisDo you have to destroy/deploy every time you make a change?17:28
*** hieulq_ has quit IRC17:29
sean-k-mooneykbaegis: it depend on the change. if its a configfile change you can run the reconfigure playbook instead17:30
sean-k-mooneykbaegis: if you are enableing a new service it might be easier to do a cleanup and a redeploy17:30
sean-k-mooneyntpttr___: the failing section is this include https://github.com/openstack/kolla/blob/68ca8942cb1828e801540088e7de9d3dce34f23e/ansible/roles/neutron/tasks/deploy.yml#L8-L1417:31
ntpttr___sean-k-mooney: yeah I'll double check17:33
*** hieulq_ has joined #openstack-kolla17:36
ntpttr___sean-k-mooney: ah I think that neutron-lbaas-agent was missing17:36
ntpttr___I had the inv from mitaka but had upgraded my kolla dir to master17:37
ntpttr___thanks!17:37
sean-k-mooneyno worries hopefully adding that in will fix it :)17:37
*** rstarmer has joined #openstack-kolla17:40
*** athomas has quit IRC17:42
jrich523whats the username used for rabbit? i guess, whats the username that is mapped to the passwords.yml17:42
kbaegisHas anyone been able to get horizon working from master?  I'm still getting 500s17:42
jrich523i was able to, sorta17:43
jrich523set it up last week, off master (V3.0)17:43
PavoI am gettng the same kbaegis17:43
Pavoso its just not me then, thats good to know17:43
sean-k-mooneykbaegis: is it not deploying or are you not able to reach it?17:44
kbaegisThey gave me two cherrypicks, but they're not working17:44
kbaegisIt's deploying just fine17:44
kbaegisIt just doesn't give me a site.  50017:44
Pavomy horizon logs show a total mess of python errors17:44
sean-k-mooneyoh ok strange am if you are deploying from source maybe go back two-three weeks in the logs and pick an older commit17:45
sean-k-mooneyPavo: do you think the error is on the kolla side or horizon?17:45
kbaegisPavo So they recommended two cherrypicks: https://review.openstack.org/#/c/349197/, https://review.openstack.org/#/c/34919817:45
Pavohorizon I think17:45
patchbotkbaegis: patch 349197 - kolla - Implement kolla_keystone_role module17:46
patchbotkbaegis: patch 349198 - kolla - Create the _member_ role in the horizon role17:46
kbaegisUmm17:46
kbaegisI didn't accidentally do anything w/ patchbot did I?17:46
sean-k-mooneywait is the _member_ createtion not merged?17:46
kbaegisNo17:46
kbaegisIt's pushed, not merged17:46
PavoI get Internal Server Error17:46
PavoThe server encountered an internal error or misconfiguration and was unable to complete your request.17:46
PavoPlease contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.17:46
PavoMore information about this error may be available in the server error log.17:46
kbaegisYeah, that's an HTTP 500 error :)17:47
kbaegisSame thing17:47
sean-k-mooneycan ye both check if the _member_ role exists17:48
Pavohow do I do that?17:49
sean-k-mooneyyou need to use the openstack client. let me see if i can find the command17:49
kbaegisopenstack role list17:50
*** hieulq_ has quit IRC17:50
Pavohttps://paste.pound-python.org/show/lmtozB30baPUWed3fYwD/17:51
kbaegisI already tried $(openstack roll create _member_)17:51
Pavodoesn't look liek _member_ role exist17:51
kbaegisDoesn't solve the issue17:51
kbaegisI didn't think to try kolla-ansible reconfigure afterwards though17:53
inc0ntpttr___, you've summoned me17:53
inc0.17:53
inc0or at least you've been summoning me17:54
inc0why did you summon me? speak mortal!17:54
sean-k-mooneykbaegis: you could try to restart horizon container17:54
sean-k-mooneyinc0: he had a bug in his deployment17:54
sean-k-mooneyinc0: i think i answered his question17:54
kbaegisI tried that too17:55
*** bootsha has joined #openstack-kolla17:55
inc0thanks Sean17:55
*** sdake has joined #openstack-kolla17:55
inc0I'm going to look for SamYaple, apperantly he's in building17:55
inc0brb17:55
sean-k-mooneyinc0: since your here any idea what is wrong with horizon17:55
sdakeyo17:55
sean-k-mooneyinc0: oh ok say hi to sam for me17:56
sdakesean-k-mooney is horizon broken foryou as well?17:56
sean-k-mooneyno im not useing master right now17:56
sean-k-mooneybut its broken for kbaegis and Pavo17:56
kbaegisYes.  Log?17:56
PavoI an trying reconfigure right now17:56
jrich523it blows my mind that you guys dev on master17:57
sdakei'll give master a spin in a few hours17:57
sdakejrich523 normally master is stable enough for us to get real work done :)17:57
sean-k-mooneyjrich523: why i generally have no issue with master17:57
sdakemaster is stable enoug hto ddev, not stable enough to eval or deploy imo17:57
jrich523well im normally a windows guy, and have worked in a few dev shops (not linux stuff)17:57
PavoI just follwed the doc on openstacks wiki, don't know what branch I am using lol17:57
ntpttr___inc0: it's been handled, thanks tho17:58
ntpttr___inc0: hope the food carts were tasty17:58
jrich523and its considered bad to use master for anything but stable (released to prod)17:58
jrich523but as i deal with more linux projects i see a lot of folks doing dev on master17:58
sean-k-mooneyjrich523: openstack use a contiusly gated trunk modle17:58
sdakewe dev against master17:58
jrich523i guess the only reason not to, is a lot of people dont understand git/code repos17:58
sdakeand then backport17:58
sean-k-mooneyjrich523: in theroy it should alway be deployable to production17:58
sdakethat is how softwrae is created :)17:58
sean-k-mooneyjrich523: the important word is "should" even with all of openstack ci systems bugs slip through from time to time17:59
jrich523yeah, so large its tough to test it all18:00
openstackgerritJeffrey Zhang proposed openstack/kolla: Create the _member_ role in the horizon role  https://review.openstack.org/35608218:00
jrich523Atlassian had an awesome article on git flow, however gated trunk is a new one to me18:00
*** dmsimard|afk is now known as dmsimard18:01
*** satya has quit IRC18:01
sdakejrich523 gated trunk = ci18:01
jrich523however i have a great excuse to not be an expert on that, im an ops guy :)18:01
sean-k-mooneywhat the difference between https://review.openstack.org/#/c/349198 and https://review.openstack.org/#/c/356082/18:01
patchbotsean-k-mooney: patch 349198 - kolla - Create the _member_ role in the horizon role18:01
patchbotsean-k-mooney: patch 356082 - kolla - Create the _member_ role in the horizon role18:01
jrich523err well with CI you still use the master as stable, the idea is to branch for feature (agile sprint) and then merge back to master when its completed and passes unit tests, which then the CD comes in and its auto deployed off master18:01
sean-k-mooneyjrich523: we do that in openstack but it does not merge to master untill it pass unitest + intergration tests18:02
jrich523oh so then master counts as stable18:03
jrich523or, should18:03
sean-k-mooneyjrich523: yes if our test coverage is good enaough you should always be able to deploy master to production18:03
jrich523yeah.... pesky test coverage18:04
jrich523lol you could probably use a whole team of folks just doing that18:04
jrich523i really hate writing tests18:04
kbaegisPavo: did adding _member_ work for you?18:05
sean-k-mooneythe bit i dislike is when may change is 20% code and 80% tests but if it means i dont have to go back and fix something again later i would perfer to have the tests18:05
Pavohaven't tried that yet, still waiting on reconfigure to finsh18:05
jrich523the last project i worked on was TDD, and well... great idea, just tough to adjust to18:06
*** tummy has joined #openstack-kolla18:08
sean-k-mooneyJeffrey4l:  why do you have two identical patches  https://review.openstack.org/#/c/349198 and https://review.openstack.org/#/c/356082/18:08
patchbotsean-k-mooney: patch 349198 - kolla - Create the _member_ role in the horizon role18:08
patchbotsean-k-mooney: patch 356082 - kolla - Create the _member_ role in the horizon role18:08
kbaegisI have the _member_ and horizon is still broken18:09
Jeffrey4lsean-k-mooney, yes it is. two fix way. the later one may be better. I will abandon one later18:09
sean-k-mooneyJeffrey4l: well one of them is approved and waiting to merge18:10
Pavokbaegis whats the cmd to add the _member_ role?18:10
sean-k-mooneyJeffrey4l: https://review.openstack.org/#/c/349198/18:10
patchbotsean-k-mooney: patch 349198 - kolla - Create the _member_ role in the horizon role18:10
Jeffrey4lsean-k-mooney, pbourke do not like it. and it is block by its parent PS.18:10
sean-k-mooneyJeffrey4l: shoudl it merge or do you have more changes?18:10
Jeffrey4lsean-k-mooney, i will -1 WIP for that PS.18:10
kbaegishttp://hastebin.com/ijefoqeyov.rb18:11
Pavook after I did reconfigure I am able to telnet into VIP on port 8018:11
Pavobut web not working still18:11
kbaegisPavo you have to have an adminrc. $(kolla-ansible post-deploy; source /etc/kolla/adminrc.sh; openstack role create _member)18:11
Jeffrey4lsean-k-mooney, I -2 for my former PS. could u remove your -1?18:12
kbaegisYes, horizon is broken on master.  IDK how, but troubleshooting now.18:12
sean-k-mooneyJeffrey4l: sure will do18:12
Jeffrey4lthanks.18:12
kbaegisimages_panel is not set18:13
kbaegisI don't know django well enough to fix18:13
kbaegisFrustrating.  I can actually create VMs and networks with 3.0.018:16
kbaegis2.0.1 not so much18:16
kbaegisVM creation is broken18:16
kbaegisSo I get to choose between a cli which works or a gui which doesn't18:16
kbaegisMixing 2.0.1 in gives 404s18:19
kbaegisHmm. Maybe I can use docker inspect and manually mount the older image18:20
kbaegisRather than going through kolla for it18:20
Pavokbaegis is it _member or _member_?18:21
kbaegis_member_18:22
Pavook18:22
Pavo[root@deployer kolla]# openstack role list18:22
Pavo+----------------------------------+------------------+18:22
Pavo| ID                               | Name             |18:22
Pavo+----------------------------------+------------------+18:22
Pavo| 2e0dfa24d69e4e23a9db1c54f6ae721e | admin            |18:22
Pavo| 5cb448aeae8c4aab96dbf2a262fe713d | heat_stack_owner |18:22
Pavo| 9fe2ff9ee4384b1894a90878d3e92bab | _member_         |18:22
Pavo| bda3422929494996a957fd00ca48f5e0 | heat_stack_user  |18:22
Pavo+----------------------------------+------------------+18:22
kbaegisuse hastebin18:22
Pavomybad18:23
kbaegisIt exists for you18:23
kbaegisYeah, you're good18:23
Pavoyeah still web not working18:23
Pavobut can still telnet into the VIP and port 8018:23
*** fragatin_ has quit IRC18:24
*** fragatina has joined #openstack-kolla18:24
Pavologs still show a ton of python errors18:26
Pavohttps://paste.pound-python.org/show/DN4CJtgwXOcJnVzPgO3l/18:26
Pavoand seems it all related to KeyError: 'images_panel'18:27
kbaegistry this, if you have a 2.0.1 image handy18:27
kbaegisdocker run -v /etc/localtime:/etc/localtime -v /var/lib/docker/volumes/kolla_logs/_data:/var/log/kolla -v /etc/kolla/horizon:/var/lib/kolla/config_files -e KOLLA_SERVICE_NAME=horizon -e KOLLA_CONFIG_STRATEGY=COPY_ALWAYS -e PATH=/var/lib/kolla/venv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin -e KOLLA_BASE_DISTRO=centos -e 'PS1=$(tput bold)($(printenv KOLLA_SERVICE_NAME))$(tput sgr0)[$(id -un)@$(hostname -s) $(pwd)]$ ' 29c891d46b4618:27
Pavoyeah I would have to build 2.0.2 image18:27
kbaegisyour image id should be whorizon18:27
Pavooops18:27
kbaegisumm18:27
kbaegislol18:27
kbaegis*horizon18:27
PavoI mean 2.0.118:27
Pavoall my images are 3.0.018:27
kbaegiskolla-build horizon will only build that one image18:28
Pavoyeah how do I set only 2.0.118:28
*** berendt has joined #openstack-kolla18:28
*** berendt has quit IRC18:28
kbaegiskolla-build.conf18:29
kbaegisForget where that's documented18:30
PavoI remember seeing it somewhere just can't find it again lol18:31
*** Jeffrey4l has quit IRC18:31
kbaegishttp://docs.openstack.org/developer/kolla/image-building.html18:31
Pavo--base-tag maybe18:31
sdakepavo to get an openrc file run kolla-ansible post-deploy18:32
PavoI have that18:32
Pavotrying to figure out how to build a 2.0.1 horizon image18:32
Pavoinstead of 3.0.018:32
Pavoyeah --base-tag it is18:33
Pavokolla-build --base-tag 2.0.1 horizon18:34
Pavowell nvm18:34
PavoERROR:kolla.image.build.base:Tag 2.0.1 not found in repository docker.io/library/centos18:34
*** michauds has quit IRC18:34
sdakepavo do following18:34
*** fragatina has quit IRC18:35
sdakedocker pull kolla/horizon:2.0.218:35
kbaegissdake I'm trying to run the image manually from docker18:35
kbaegissdake could use some help with the specifics18:35
sdakegood luck with that one :)18:35
kbaegisonly thing I keep getting an error on: make_sock: could not bind to address 192.168.254.3:8018:36
kbaegisNothing bound to 8018:36
sdakerun it as root18:36
kbaegisI am18:36
sdake-u root iirc18:36
sdakenetstat -nl | grep 8018:36
kbaegisuid 018:37
PavoError: image kolla/horizon:2.0.2 not found18:37
kbaegisNo matches18:37
kbaegisno matches on18:37
kbaegisnetstat -nl | grep 8018:37
sdakepavo thta may not be the exeact syntx18:37
kbaegisShould be 2.0.118:37
sdakepavo try docker.io/kolla/centos-binary-horizon:2.0.118:37
sdakeor remoe the docker.io18:37
sdakemy tests machines are not functional atm because of a rebuild18:38
sdakeso i can't get the exact command or you atm18:38
sdakesomeone else can probby help wit h that18:38
*** dwalsh has quit IRC18:40
Pavoyeah that was it, pulling both 2.0.1 and 2.0.218:40
*** dwalsh has joined #openstack-kolla18:41
ntpttr___hey inc0, question about upgrades18:43
inc0go ahead18:44
ntpttr___inc0: I'm running cinder on mitaka, do I need to change any configs before running kolla-ansible upgrade to tell it I want it to be master?18:44
ntpttr___where do I tell it what to upgrade to?18:44
inc0ntpttr___, so you need to have images of master built18:44
ntpttr___inc0: ah okay that makes sense18:44
inc0in globals.yml you have openstack_release where you setup a tag18:45
ntpttr___inc0: I actually had it set in kolla-build.conf18:45
inc0also, keep in mind that kolla-master plays should be used18:45
ntpttr___inc0: if I change that and rebuild is that enough?18:45
ntpttr___inc0: yeah I have kolla on master18:45
inc0no, you need both18:45
inc0kolla-build in mitaka will tag your images as 2.0.218:45
inc0kolla-build with master will tag them as 3.0.018:46
inc0and in globals you set it up, which ones18:46
ntpttr___inc0: but in kolla-build.conf I have the source for cinder set to a mitaka repo18:46
inc0that being said, defaults should work18:46
ntpttr___why wouldn't that be enough?18:46
*** michauds has joined #openstack-kolla18:46
inc0then you need to change this to master and rebuild with different tag18:46
inc0well, you can just rebuild18:46
inc0technically18:46
ntpttr___inc0: sorry I'm not sure I understand the tags18:47
inc0docker images, there is tag there18:47
inc0do docker images18:47
ntpttr___is that a way for having multiple built images at different versions in my registry?18:47
inc0yes18:47
ntpttr___inc0: ah yes I see18:48
ntpttr___they're all at 3.0.018:48
inc0duh...it's a damn bug18:48
ntpttr___I'll just destroy them and rebuild18:48
ntpttr___with master cinder18:48
inc0no, don't need to destroyu18:48
inc0just rebuild with kolla master18:48
inc0kolla-build18:49
ntpttr___inc0: okay18:49
ntpttr___It's running, I'll let you know what happens18:49
ntpttr___the only difference then is that I changed the cinder source to point to master18:49
Pavoif you don't set a tag what does it default to kolla-master?18:49
Pavobecause it built all my images as 3.0.018:50
sdakepavo yup18:50
sdakeit defaults to that18:50
Pavook18:50
sdakereally depends if you are running rom git or have kolla pip installed :)18:50
Pavofrom git18:50
sdakedo you have kolla pip installed as well?18:51
Pavogrr I did a kolla-ansible upgrade and it used 3.0.0 horizon18:51
Pavosdake I just did what the docs say18:51
sdakekolla defaults to looking at containers/ansible (if installed via pip which is what the docs say) rather  then your cwd18:51
sdakethis means your not using whateverr changes you have made in git..18:52
sdakesorry loooking at the pip installed containers/ansible18:52
PavoI did a git clone https://git.openstack.org/openstack/kolla and a pip install kolla/18:52
sdakeright - pip remove kolla18:52
sdakeand your good to go18:52
sdakepip installed?  kolla uses that - even if you have a  git checout18:53
inc0sdake, even mitaka tags 3.018:53
sdakeit is fantastically frustrating that nobody has fixed  that yet18:53
inc0which is bug18:53
sdakeno its not a bug18:53
Pavoso that means I need to do a rebuild of the images?18:53
sdakeit is using code from the pip install18:53
inc0ehh18:53
sdakepavo depends what you changed18:53
PavoI just did a pipi uninstall kolla18:54
sdakethe pip install = 3.0.018:54
sdakeit may be remove not uninstall18:54
sdakenot certain18:54
Pavotried remove and said unknow cmd18:54
sdakedid uninstall work?18:54
Pavohad to do uninstall18:54
Pavoyeah18:54
sdakethey are the sam ehting18:54
sdakei cant' ever remember which one it is ;)18:54
Pavolol18:54
Pavoanyways....18:55
sdakewhy dont you tell me what your trying to do18:55
Pavoprobably best to rebuild images then18:55
sdakeand i can guide from there18:55
sdakeif you followed the instructions, you are using master18:55
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Modifying Keystone bootstrap to use secrets  https://review.openstack.org/35609818:56
Pavowell horizon is all mesed up, so I tried to redeploy using kolla-ansible upgrade to deploy horizon 2.0.2 but it still used 3.0.018:56
sdakeok to do that is easy18:56
sdakethere are a couple options18:56
sdakeactually one option18:56
sdakeyou need to get that horizon 2.0.2 version in your registry first step18:56
Pavook I did a pull from docker.io and have it on deployer images list18:57
Pavohow do I get it pushed to my registry18:57
Pavolocal registry18:57
Pavoas remove 3.0.0 from registry18:57
Pavoand I mean18:58
sdakehttps://github.com/openstack/kolla/blob/master/ansible/roles/horizon/defaults/main.yml#L818:58
sdakethe second step is to set horizon_tag: "2.0.2" in your globals.yml18:58
sdakepavo docker push will do it - but I don't recall exact syntax needed18:59
Pavowhat section does that go in?18:59
sdakeand as I said, my machines are down and out18:59
sdakepavo there are no sections in globals.yml - its a flat file18:59
Pavoso.... horizon_tag:"2.0.2" anywhere in globals.yml?19:00
sdakepavo if its on the deployer images list it doesn't need to be in the registry19:00
sdakeas its already pre-cached now19:00
sdakepavo roger19:00
sdakethen run cleanup scripts (but not cleanup-images)19:00
*** srwilkers has quit IRC19:00
sdakemake sure horizon 2.0.2 is on every node in your cluster19:00
sdakeI think that should work19:00
sdakebut not certain19:00
Pavook19:00
sdakeyou may have to rename it19:01
sdaketo match that of your registry19:01
sdakeanother option is to set horizon_image: "whatever-its-called-from-docker-images"19:01
sdakethis last option is what i'd do19:02
sdakeso two globals.yml overrides19:02
sdakehorizon_tag: "2.0.2"19:02
sdakehorizon_image: "docker.io/kolla/centos-source-horizon"19:02
sdakeor whatever it was called :)19:02
sdakeor maybe its just kolla/centos-source-horizon19:03
sdakeyou will have to play around with it a bit19:03
Pavothis si what I have in deployer19:03
Pavohttps://paste.pound-python.org/show/9EnSVblpCLEM3QMmv7pK/19:03
Pavohow do I get the kolla/centos-binary-horizon into my registry?19:04
sdakecool19:04
sdakepavo I don't have dockr in front of me19:04
sdakeso I can't tell you the command to type19:04
sdakeyou can either read the internets or how to push19:04
Pavook np19:04
sdakeor follow this other direction i provide19:04
sdakewhich is set horizon_image: "kolla/centos-binary-horizon"19:04
sdakein globals.yml19:05
sdakeand make sure you have pulled it on all nodes19:05
sdakenot just the deploy node19:05
sdakewhen you deploy, docker pulls from the registry to the local machine and stores in teh "docker cache"19:05
sdakewhen you do a docker pull the image also gets stored in the docker cache19:05
sdakeif its there its there - no sense pulling it twice ;)19:06
sdakeunderstand or have further questions?19:07
PavoI think I understand19:07
sdakesweet19:08
*** tummy has quit IRC19:12
*** fragatina has joined #openstack-kolla19:13
*** fragatina has quit IRC19:13
*** fragatina has joined #openstack-kolla19:13
*** sdake_ has joined #openstack-kolla19:14
*** sdake has quit IRC19:14
jrich523so... i am trying to build a compute node following these directions, http://docs.openstack.org/mitaka/install-guide-rdo/nova-compute-install.html19:15
jrich523however its having issues connecting to RabbitMQ,  3116 ERROR oslo.messaging._drivers.impl_rabbit [req-82caf02c-a17a-4abd-b247-87e37de81b9d - - - - -] AMQP server on 192.168.11.30:5672 is unreachable:19:15
*** sdake_ has quit IRC19:15
jrich523from what i can tell (netstat -anp|grep 5672) thats the correct IP, 30 is the controller host, but the VIP is 31, however 31 doesnt have port 5672 open, so i used 3019:16
*** sdake has joined #openstack-kolla19:16
Pavook I am gonna rebuild my deployer from the beginning19:16
Pavogonna only do what this site says http://docs.openstack.org/developer/kolla/quickstart.html19:16
jrich523it wont work19:17
jrich523unless it was very recently updated19:17
Pavothen what guide to use? git?19:17
jrich523well, there isnt a guide19:17
jrich523the only reason i got any of it working was because i gave zhugaoxiao ssh access to my VM19:17
jrich523im fairly certain i couldnt reproduce what he did19:18
jrich523even tho i watched all of it and took notes19:18
jrich523he was extremely helpful, however, bit of a language barrier19:18
jrich523i recall a bit issue being the ansible version (1.9.4 is ideal)19:20
jrich523also changing the branch (git checkout stable/mitaka)19:20
PavoCentOS and RHEL package Ansible >2.0 which is suitable for use with Kolla.19:20
jrich523thats what i used at first19:21
jrich523didnt get far19:21
Pavohmm ok19:21
jrich523it was all a bit of a blur, just telling you what i recall that varied from the directions19:21
Pavohow about this guide http://egonzalez.org/openstack-kolla-deployment-from-rdo-packages/19:22
jrich523i think outside of that it came down to modifications to globals.yml19:22
jrich523actually19:23
jrich523that looks good19:23
jrich523seems mostly the same19:23
jrich523but it def takes in to account the branch change, which is huge19:23
jrich523he uses the most current ansible, but, who knows what version was out when he did this19:24
Pavosays April 24th19:24
sdakepavo wait19:25
Pavo?19:25
sdakehere is the deal guys19:25
sdakewe are super busy with alot of stuff and the documentation is deficient19:25
sdakeI get it, and I am working on getting it fixed19:25
jrich523not  complaining, just trying to work through it )19:26
jrich523:)19:26
sdakepavo - your goals are to develop for kolla - then use masater19:26
Pavoyeah me too, its completely understandable19:26
jrich523actually after i get this setup, i was going to build from scratch again, and take better notes, and perhaps update the docs19:26
sdakepavo you said you wanted to learn about openstack programming19:26
sdakeby using msater some things will be broken from time to time19:26
sdakethe core team is here to help smooth over the rough spots for new devs coming up to speed on the code base19:27
sdakeand get their first deployment done19:27
Pavoumm don't think that was me, I know openstack pretty well, just trying to learn how kolla does it, we currently use packstack to deploy openstack but seems like deploying as containers is more efficent19:27
sdakerepaving the deployment host wont help in this case19:27
sdakeit sounds like horizon has a legitimate defect19:27
sdakei don't know the status of this problem - but jeffrey4l submitted a NEW patch for this _member_ thing19:27
jrich523yeah i will say, when i did horizon it was super easy19:27
sdakepavo roger19:28
sdakepavo sorry hard to keep eveyrone straight :)19:28
Pavoits all good19:28
PavoI will provide feedback on what I learn19:28
jrich523if you're just looking to get a feel for it, then using stable/mitaka might help with that19:28
sdakeso if the problem is now "everything works except horizon"19:28
sdakelet me help you with that19:29
*** srwilkers has joined #openstack-kolla19:29
sdakepavo if you don't plan to develop for kolla but only want to eval, I'd highly recommend using stable/mitaka19:34
sdakefor which there are no instructions19:34
Pavowell I can start dev after I get the complete understanding of how it works19:34
Pavoprobably would be best route19:35
Pavoroute19:35
sdakewell if you want to get master rolling let me knwo19:35
sdakeif you want to get stable/mitaka rolling let me know19:35
Pavowill do19:35
sdakeits all pretty easy19:35
sdakeI don't know what the deal is with this horizon problem19:36
sdakeits neews to me as of today19:36
sdakeso probably an upstream regression19:36
sdakei know starting from scratch can be a best practice in many cases, but not in this case;-)19:36
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: WIP- openvswitch ip  https://review.openstack.org/35611419:39
*** bootsha has quit IRC19:42
kbaegisWell with gentoo, I can't use mitaka release19:43
kbaegisSo I'm stuck with you on master sdake :)19:43
*** tummy has joined #openstack-kolla19:43
kbaegis3.0.0 is working perfectly- except for horizon19:43
sdakemitaka broke n on gentoo?19:43
kbaegisThe CLI is good enough for me19:43
kbaegisYes19:43
kbaegisThe libvirt wasn't working at all.  Kept breaking on vm create19:44
kbaegisdeploys fine19:44
*** tummy has quit IRC19:44
kbaegisBut can't create anything19:44
kbaegisAlso ovs had issues19:44
*** bootsha has joined #openstack-kolla19:44
kbaegisI also am using the 4.8 kernel though :)19:44
kbaegisIt'd detect my node w/ 32 available cores, but wouldn't schedule/create19:45
kbaegisretry invoked after first failure19:45
sdakedoes anyone have a backtrace of this horizon problem ?19:46
kbaegispasted it in a while back19:46
sdakemind pasting again - i dont keep a large scroll buffer and dc often because of vpn nonsene19:47
kbaegishttp://hastebin.com/ijefoqeyov.rb19:47
kbaegisimages_panel not set19:48
Pavohere ya go sdake  https://paste.pound-python.org/show/JhzdyKGGs7XL6srQ6xNJ/19:48
*** bootsha has quit IRC19:49
sdakea key error means there is no key like that in the dictionary19:49
sdakemoment let me ask on #openstack-horizon19:49
ntpttr___has anyone here who has deployed cinder w/ ceph using kolla run into an issue where when you ask to create a backup it hangs in 'creating' forever?19:51
*** nihilifer has quit IRC19:54
*** nihilifer has joined #openstack-kolla19:56
*** nihilifer has quit IRC20:00
sdakeok so this horizon problem looks like a kolla usage error20:03
sdakeapparently we are doing it wrong20:03
sdakei dont have enough details to fix it20:03
sdakeand i dont know why it just started happening20:03
sdakebut it will get fixed20:04
sdakeuntil then, hang tight and try out other things :)20:04
*** srwilkers has quit IRC20:04
*** matrohon has joined #openstack-kolla20:09
*** vhosakot has quit IRC20:10
kbaegisWill do :) TY sdake!20:11
*** vhosakot has joined #openstack-kolla20:11
ntpttr___sdake: hey is there an option to turn on debugging in the logs in globals.yml?20:18
ntpttr___nvm found it20:20
*** inc0 has quit IRC20:27
Mech422sdake: well poop - ticketmaster managed to screw me out of $320 worth of Adele tickets tonight20:30
sdaketoo hot anyway :)20:30
Mech422sdake: heh - well, beware - if you get any tickets from them that are 'tied' to your credit card...they have no process for dealing with 're-issued' cards20:31
kbaegisYeah in Phoenix20:31
sdakewasn't that at talking stick anyway?20:32
sdakethat place would be a mad house to have a concern in20:33
Mech422sdake: yeah - talking stick20:33
sdakeconceert in20:33
Mech422sdake: yeah? I've never actually gone... the tickets were an xmas present for the gf.20:33
sdakeoh nice20:33
Mech422yeah :-/20:33
sdakexmas early this year :)20:33
Mech422sdake: nah - the tickets go on sale like 9 months before the concert, then they don't know what to do if your bank issues you a new card20:34
Mech422B.o.A. had a breach like 6 months ago and re-issued my card20:34
*** huikang has quit IRC20:35
*** jtriley has quit IRC20:39
*** rstarmer has quit IRC20:40
*** lrensing_ has quit IRC20:41
*** jamesden_ has joined #openstack-kolla20:41
*** jeh has quit IRC20:44
*** jamesdenton has quit IRC20:44
*** kbaegis has quit IRC20:48
*** jeh has joined #openstack-kolla20:49
*** jeh has quit IRC20:49
*** jeh has joined #openstack-kolla20:49
*** lyncos has joined #openstack-kolla20:52
*** dwalsh has quit IRC20:53
*** daneyon has joined #openstack-kolla20:55
*** kbaegis has joined #openstack-kolla20:55
*** matrohon has quit IRC20:55
*** jeh has quit IRC20:56
kbaegisStep one, Fire BoA and get a credit union account20:57
mark-caseystep two. pay fees :D20:59
*** daneyon has quit IRC20:59
*** jeh has joined #openstack-kolla21:01
*** jeh has quit IRC21:01
*** jeh has joined #openstack-kolla21:01
*** ad_rien_ has joined #openstack-kolla21:07
*** bootsha has joined #openstack-kolla21:08
kbaegisCredit union fees?21:13
kbaegisI'm a member of two and I've never paid a fee.  I had an account at wells fargo for a year though, and they have tons of fees21:14
kbaegissdake any luck from the horizon team?21:18
*** matrohon has joined #openstack-kolla21:18
kbaegisWe're copying from devstack as a short-term hack? :) lol21:18
kbaegisI like it21:18
kbaegisOh I see21:20
kbaegisit was a copy-replace rather than update21:20
*** egonzalez90 has joined #openstack-kolla21:24
*** egonzalez90 has quit IRC21:24
kbaegisHmm21:28
kbaegisI guess I can just edit /etc/kolla/horizon/local_settings in the interrim21:29
imcsk8Pavo: i was reading the backlog, i was recently playing with kolla. i was very impressed21:29
Pavolol did a rebuild of my deployer node now getting something weird21:29
Pavohttps://paste.pound-python.org/show/6U1sDSYedrSSMDaDIKXG/21:29
*** ad_rien_ has quit IRC21:29
kbaegisPavo looks like dhcp failed on your local network Pavo21:30
Pavoon what though?21:30
Pavothere is no ''169.254 anywhere21:30
kbaegisWhatever interface you configured in global21:30
Pavoin the global.yml21:30
kbaegisIt may be a secondary IP21:30
kbaegisOh, that's fine21:30
kbaegisIt's probably grabbing the actual configured address21:31
kbaegisdo ifconfig/ip addr show21:31
PavoI'll reboot and retry prechecks21:31
kbaegisDon't reboot21:31
Pavook21:31
Pavohttps://paste.pound-python.org/show/MwPpvSF67ysgx7CLkxqD/21:31
kbaegisjust do ifconfig 0.0.0.0 up for your neutron21:31
kbaegisneutron interface21:31
kbaegisI bet if you do ip addr show dev eth0; ip addr show dev eth121:32
PavoI don't have anything deployed yet, that error was from prechecks21:32
kbaegisit will show up with a 169 address21:32
*** matrohon has quit IRC21:32
PavoI just checked all nodes ip addr and they all have a IP on eth0 and eth121:33
Pavowhat I just posted was on deployer node21:33
kbaegisAnd it's on the same subnet?21:33
imcsk8Pavo: did you se kolla_internal_vip_address in /etc/kolla/globals.yml?21:33
Pavonode2 https://paste.pound-python.org/show/k9Vo64r4E4K0kJNcqyD0/21:33
kbaegisWell that's either coming from an interface or it's coming from globals21:33
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: WIP- openvswitch ip  https://review.openstack.org/35611421:34
Pavoyeah I set kolla_internal_vip_address in globals to 192.168.1.25421:34
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: WIP- openvswitch ip  https://review.openstack.org/35611421:35
*** rhallisey has quit IRC21:41
*** bootsha has quit IRC21:43
Pavoany luck with your horizon kbaegis21:44
kbaegisyes and no21:45
kbaegisAs we learned on #openstack-horizon, kolla had been overwriting the previous config with a statically generated one21:46
imcsk8Pavo: you can run kolla-ansible -v precheck to get more info21:46
kbaegisSo it's a matter of merging ~300 functional lines from https://github.com/openstack/horizon/blob/master/openstack_dashboard/local/local_settings.py.example with the local_settings21:46
Pavook21:46
Pavoouch21:46
*** matrohon has joined #openstack-kolla21:46
kbaegisI believe sdake is working on the necessary scripts now21:47
*** jamesden_ has quit IRC21:47
kbaegisI'm running reconfigure, will do the merge and share21:47
kbaegisYou should be able to dump some text into /etc/kolla/horizon/local_settings to fix this21:47
kbaegisreally wish kolla-ansible reconfigure supported individual containers21:49
kbaegisoh well :)21:49
Pavook looks like there is something wrong with the precheck script for this section of the precheck21:50
Pavohttps://paste.pound-python.org/show/jz1qqMIX2xAV5nusrkAD/21:50
*** bootsha has joined #openstack-kolla21:51
kbaegisWell, I don't know how to read that21:51
kbaegisBut it's possible that you have multiple IPs assigned21:51
kbaegiswhich is why you use the ip addr show dev <if> command rather than ifconfig21:52
kbaegisifconfig is simpler/less functional than full iproute221:52
kbaegisThat's what I get from "non-iteratable"21:52
PavoI don't have net-tools installed so no ifconfig21:52
Pavousing ip addr cmd21:52
kbaegisHuh21:53
kbaegisWell then I don't know :)21:53
kbaegisThe most absurd solution I can think of is to rename all devs w/ udev rules and reinput the values in global21:54
Pavothis is what node1 shows21:54
Pavohttps://paste.pound-python.org/show/aJyZJo3llYWSXyYT4JgE/21:54
kbaegisYup.  All matches up. 192.168.1/24 192.168.188/2421:54
Pavohave no clue where that 169.254 is coming from on prechecks21:55
Pavonot anywhere in globals or inventory21:55
*** michauds has quit IRC22:02
*** chrichip has quit IRC22:13
*** bootsha has quit IRC22:25
*** sdake has quit IRC22:27
*** dwalsh has joined #openstack-kolla22:27
*** sdake has joined #openstack-kolla22:28
kbaegisWell, my merge with vimdiff didn't work22:33
*** rstarmer has joined #openstack-kolla22:33
sdakekbaegis working on the horizon problem you mean?22:33
kbaegisYes22:35
kbaegisused vimdiff with https://github.com/openstack/horizon/blob/master/openstack_dashboard/local/local_settings.py.example and /etc/kolla/horizon/local_settings22:35
kbaegismanually overwrote local_settings and restarted the horizon container22:36
sdakekbaegis does that fix the eproblem?22:37
sdakeI think there should be something more surgical here :)22:37
kbaegisIt does not. :)22:37
Pavoduring the image build do it use the host repo files for yum cmds or does it use default ones?22:40
*** matrohon has quit IRC22:40
*** daneyon has joined #openstack-kolla22:43
*** thumpba has quit IRC22:46
sdakepavo kolla knows nothing about a rpm or deb host repo except one master location22:46
sdakepavo - that can be reconfigured - but not trivial22:46
Pavook just wondering22:46
sdakeit was designed to be reconfigured22:46
sdakeatleast the from src part22:47
sdakefrom bin part - i think only oen mastaer repo22:47
*** daneyon has quit IRC22:48
*** dave-mccowan has quit IRC22:48
*** thumpba has joined #openstack-kolla22:49
*** thumpba has quit IRC22:49
*** vhosakot has quit IRC22:56
*** chrichip has joined #openstack-kolla22:58
openstackgerritKevin Fox proposed openstack/kolla: Add crudini  https://review.openstack.org/35615522:58
*** thumpba has joined #openstack-kolla22:59
*** thumpba has quit IRC22:59
*** thumpba has joined #openstack-kolla22:59
*** chrichip has quit IRC23:07
kbaegissdake Do you think you'll need a full day for that change?23:19
*** jtriley has joined #openstack-kolla23:20
kbaegisLonger? :)23:27
kbaegisI'm just curious23:27
*** mbound has joined #openstack-kolla23:34
*** thumpba_ has joined #openstack-kolla23:37
imcsk8Pavo: https://bugs.launchpad.net/kolla/+bug/1571612 check comment #623:37
openstackLaunchpad bug 1571612 in kolla "Prechecks fails when checking if kolla_internal_vip_address is in the same network as network_interface on all nodes" [High,Triaged] - Assigned to Hiroki Ito (hrito)23:37
*** thumpba has quit IRC23:39
*** mbound has quit IRC23:39
*** jamesdenton has joined #openstack-kolla23:44
*** zhurong has joined #openstack-kolla23:49
openstackgerritLi Yingjun proposed openstack/kolla: Fix tar command path for magnum conductor using ubuntu  https://review.openstack.org/35600823:53
*** kbaegis has quit IRC23:55
openstackgerritLi Yingjun proposed openstack/kolla: Fix tar command path for magnum conductor using ubuntu  https://review.openstack.org/35600823:55
*** kbaegis has joined #openstack-kolla23:56
Pavothanks imcsk823:57
kbaegisPavo23:57
kbaegisDid you figure it out?23:57
kbaegisThe horizon bug?23:57
Pavonot yet23:57
kbaegisOh :)23:57
kbaegisJust checking23:57
Pavostill waiting on images to finish building lol23:57
Pavothats probably the longest part of this whole thing23:57
mark-caseyPavo: if this is for specific issues and you haven't seen it, look into just rebuilding one image or a few images23:59

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