Tuesday, 2020-04-21

*** gyee has quit IRC00:11
*** cshen has joined #openstack-ansible00:19
*** cshen has quit IRC00:23
*** dmsimard1 has joined #openstack-ansible00:50
*** dmsimard has quit IRC00:51
*** dmsimard1 is now known as dmsimard00:52
*** rh-jelabarre has quit IRC01:53
*** cshen has joined #openstack-ansible02:19
*** cshen has quit IRC02:23
*** d34dh0r53 has joined #openstack-ansible03:56
*** d34dh0r53 has quit IRC04:02
*** d34dh0r53 has joined #openstack-ansible04:02
*** d34dh0r53 has joined #openstack-ansible04:04
*** d34dh0r53 has quit IRC04:16
*** evrardjp has quit IRC04:35
*** evrardjp has joined #openstack-ansible04:35
*** udesale has joined #openstack-ansible05:10
*** udesale_ has joined #openstack-ansible05:21
*** udesale has quit IRC05:24
*** thuydang has joined #openstack-ansible05:58
*** udesale_ has quit IRC06:14
*** cshen has joined #openstack-ansible06:21
openstackgerritJonathan Rosser proposed openstack/openstack-ansible-os_tempest stable/stein: Pin neutron-tempest-plugin to 0.9.0 for Stein branch.  https://review.opendev.org/72132006:22
jrossernoonedeadpunk: on https://review.opendev.org/#/c/721319/1/vars/main.yml we could make it use master on py > 2.7, but i thought the complexity wasnt worth it, and just pinning to 0.9.0 regardless of python version would be ok06:24
jrosserinterested to know if you think there is a better way there - perhaps we could define a var in vars/{distro}.yml which sets the version to use?06:25
jrosseri think it't centos on 2.7 and debian-stable on 3.5 which fail with 1.0.006:25
*** udesale has joined #openstack-ansible06:37
*** udesale has quit IRC06:43
noonedeadpunkI don't see really anything bad about just bumping version that way...06:49
noonedeadpunkIt's simple and clean now, so I'd say it's ok06:50
*** this10nly has joined #openstack-ansible06:56
*** rpittau|afk is now known as rpittau07:03
*** cshen_ has joined #openstack-ansible07:06
*** cshen has quit IRC07:09
*** yolanda has joined #openstack-ansible07:13
jrosseri'm just trying to see why the master SHA bump fails everywhere - it's the same tempest keystone error that we fixed with this https://review.opendev.org/#/c/720698/ for bionic/distro07:26
jrosserwhats not so clear is why thats failing still everywhere else even though the tempest SHA has been bumped07:26
noonedeadpunkjrosser: yeah, that's what I didn't get actually. As SHA you've provided should fix tempest and make this test not fail07:27
jrosseri just looked in the venv build log for the utility container and it seems to build the right SHA there07:28
*** fghaas has joined #openstack-ansible07:28
noonedeadpunkyeah, just thought to check that actually:)07:28
noonedeadpunkofc we can adjust 720698 to disable this test everywhere....07:29
jrosseri'm assuming this is doing the right thing https://zuul.opendev.org/t/openstack/build/a6635b2a0b664da88eb4942f63544d6f/log/logs/openstack/aio1_utility_container-ab91122a/python_venv_build.log.txt#21534-2156307:31
jrossersomething is failing here https://zuul.opendev.org/t/openstack/build/a6635b2a0b664da88eb4942f63544d6f/log/logs/openstack/aio1_utility_container-ab91122a/python_venv_build.log.txt#40455-4048407:38
noonedeadpunkhuh07:39
noonedeadpunkI think that https://opendev.org/openstack/tempest/src/commit/30638b53a4f9a277a821f7988d8c18b6de52bf77/tempest/api/identity/admin/v3/test_groups.py is just not supposed to work lol07:39
noonedeadpunkso we're deleting object in for cycle07:39
noonedeadpunkbut for comparison use original object07:39
jrosseroh what07:39
jrosseryou think the actual tempest code is broken?07:39
noonedeadpunkYeah, how is that supposed to work? https://opendev.org/openstack/tempest/src/commit/30638b53a4f9a277a821f7988d8c18b6de52bf77/tempest/api/identity/admin/v3/test_groups.py#L12307:40
noonedeadpunkso in 'g' this key won't be defined, but I think it won't reflect user_groups?07:40
noonedeadpunkor will...07:40
noonedeadpunksorry. my fault07:41
noonedeadpunkJust forgot that it really operates on this object and don't create it's copy...07:43
noonedeadpunkso disregard07:43
*** tosky has joined #openstack-ansible07:44
noonedeadpunkhuh, you know, despite it seems that the correct version of tempest gets isntalled, it fails on L118 https://zuul.opendev.org/t/openstack/build/a6635b2a0b664da88eb4942f63544d6f/log/logs/openstack/aio1_utility_container-ab91122a/utility/tempest_run.log.txt#3907:46
noonedeadpunkand L118 is exactly where assert was before that patch https://opendev.org/openstack/tempest/commit/30638b53a4f9a277a821f7988d8c18b6de52bf7707:47
jrosseryes membership_expires_at is still ther07:47
jrossere07:47
noonedeadpunkthe point is, that if we had this patch on board, it would fail on L12407:48
jrosseryes i see07:48
jrossertheres something else i noticed which is not cool07:49
jrosserlike, wtf https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L69207:49
noonedeadpunko_O07:50
jrosseri'm wondering if this prevents the wheel we build getting installed, because ours is too new07:50
noonedeadpunkLike according to log is's supposed to get isntalled.... but dunno07:50
noonedeadpunk*it's07:50
jrosserbut as you say the assert is on the line for the *old* version.....07:51
jrosseror maybe what you get from pypi....07:51
noonedeadpunkyeah, so it feels that we somehow get an old version.... but I'm not really sure how....07:52
noonedeadpunkso we kinda supposed to drop u-c for master but have them for stable branches...07:53
noonedeadpunk(in terms of tempest)07:53
jrosseri feel that may break things07:54
jrosserin other surprising ways07:54
*** threestrands has quit IRC07:55
jrosserthis is odd enough it deserves an AIO i think07:55
*** thuydang has quit IRC07:56
*** KeithMnemonic has quit IRC08:05
*** udesale has joined #openstack-ansible08:16
*** udesale_ has joined #openstack-ansible08:22
*** udesale has quit IRC08:22
*** udesale has joined #openstack-ansible08:22
*** gshippey has joined #openstack-ansible09:10
*** sshnaidm|afk is now known as sshnaidm09:54
*** thuydang has joined #openstack-ansible09:58
*** jbadiapa has joined #openstack-ansible10:12
*** aedc has joined #openstack-ansible10:20
*** aedc has quit IRC10:30
*** rpittau is now known as rpittau|bbl10:31
*** aedc has joined #openstack-ansible10:32
*** thuydang has quit IRC10:40
jrossernoonedeadpunk: doh! http://paste.openstack.org/show/792457/10:45
*** thuydang has joined #openstack-ansible10:58
*** udesale has quit IRC11:09
openstackgerritamolkahat proposed openstack/openstack-ansible-os_tempest master: Added tempest ironic resources setup.  https://review.opendev.org/72070511:52
*** rh-jelabarre has joined #openstack-ansible11:53
*** thuydang has quit IRC11:57
jrossernoonedeadpunk: i found something else wrong in the tempest role, https://opendev.org/openstack/openstack-ansible-os_tempest/src/branch/master/tasks/tempest_install.yml#L4312:02
jrosserthat var appears to apply to the other times we use python_venv_build in that role12:03
noonedeadpunkoh, so you meen we upgrade tempest once install stackviz...12:06
noonedeadpunk.........12:06
noonedeadpunkwhat a mess...12:06
noonedeadpunkwhy do we do this separatyle12:07
noonedeadpunkto fit both source and distro isntalls I guess...12:07
jrosseri'm not sure what is going on right now tbh12:10
jrosserfirst off that var being set to 'no' means we are not using the repo server at all for the tempest wheel build12:11
noonedeadpunkI think it's just stackviz build12:12
noonedeadpunkAs we don install tempest in tempest_install_source.yml12:12
noonedeadpunk(which is included previously)12:12
jrosserno no12:12
jrosseri added debug12:12
jrosserthat value 'no' is also appying to all the things in here https://opendev.org/openstack/openstack-ansible-os_tempest/src/branch/master/tasks/tempest_install.yml#L32-L3412:13
jrosserwe have overridden the defaults/main.yml expression for venv_wheel_build_enable with a static 'no' for the whole play i think\12:13
noonedeadpunkhm, but we don't have it defined here https://opendev.org/openstack/openstack-ansible-os_tempest/src/branch/master/tasks/tempest_install_source.yml#L16-L2812:16
jrosseri just added venv_wheel_build_enable: "{{ venv_build_host != inventory_hostname }}" to there12:17
jrosserand it makes the behaviour as expected12:17
noonedeadpunkand we have no on stackviz as we install already build package12:17
jrosseryes12:17
jrosserso now i am going to force rebuild of the tempest venv and see what version we get in there12:17
jrosserthis feels like a bad use of ansible we have12:18
jrosserusing something that is defined in defaults/main.yml also somewhere in vars:12:18
noonedeadpunkOut of http://codesearch.openstack.org/?q=venv_wheel_build_enable it doesn't seem we could somewhere "globally" override it for tempest job...12:19
noonedeadpunkso it's totally weird12:19
jrosserbut i think this is a general problem when trying to include a role more than one time in a particular play12:19
jrosserthe vars: you set on each time you include the role are not local to that include12:19
jrosseri neater solution would be to break the stackviz install out into its own play, rahter that just it's own tasks12:20
noonedeadpunkwhat if... to use include instead of import? Wouldn't it change behaviour?12:21
noonedeadpunkbtw was wondering to test speed of import vs include - maybe we have problems because of that...12:22
*** ygk_12345 has joined #openstack-ansible12:24
jrosserok so now i see the right wheel has been built on the repo server for tempest12:26
jrosserbut we do not get the right wheel installed into the venv12:27
*** rpittau|bbl is now known as rpittau12:31
jrosseroh hello Uninstalling tempest-23.0.1.dev92:\n      Successfully uninstalled tempest-23.0.1.dev92\nSuccessfully installed cinder-tempest-plugin-0.3.2.dev5 tempest-23.0.0\n"12:40
ygk_12345can someone look into this    https://bugs.launchpad.net/openstack-ansible/+bug/187406712:43
openstackLaunchpad bug 1874067 in openstack-ansible "Adding new infra host is failing" [Undecided,New]12:43
jrossernoonedeadpunk: so it all gores wrong here https://opendev.org/openstack/openstack-ansible-os_tempest/src/branch/master/tasks/tempest_install_source.yml#L43-L5712:44
jrosserwhen we install the plugins, it downgrades tempest due to u-c12:45
*** _kukacz has joined #openstack-ansible12:45
*** _kukacz has quit IRC12:51
*** _kukacz has joined #openstack-ansible12:52
*** jbadiapa has quit IRC13:00
*** thuydang has joined #openstack-ansible13:01
noonedeadpunkI don't think we can omit using u-c.... And I don;t see a solution either...13:07
noonedeadpunkexcept asking why tempest is in u-c:)13:07
noonedeadpunkjrosser: I'm not really sure, but what if we just place "tempest" somewhere here? https://opendev.org/openstack/openstack-ansible/src/branch/master/global-requirement-pins.txt13:08
noonedeadpunkwould it mean to install jsut whatever version we want?13:08
jrosserwhat i was just looking at was combining the installing of the plugins from source into the same task as installing tempest13:09
jrosserin some ways the problem is this https://github.com/openstack/openstack-ansible-os_tempest/blob/master/tasks/tempest_install_source.yml#L43-L5713:09
jrosserwe use u-c there13:09
noonedeadpunkyeah, I got it. But I'm not sure we can easily combine it into a single task?13:10
noonedeadpunkWhile u-c are kinda needed for plugins (otherwise they were failing to install iirc)13:10
jrosserso i was thinking to add another variable to here https://github.com/openstack/openstack-ansible-os_tempest/blob/master/tasks/tempest_install_source.yml#L2413:11
jrossersomething like venv_pip_packages: "{{ tempest_pip_packages + tempest_pip_plugins }}"13:12
noonedeadpunkoh, why don't we use tempest_git_constraints https://github.com/openstack/openstack-ansible-os_tempest/blob/master/tasks/tempest_install_source.yml#L50 ?13:13
noonedeadpunkSo it would be the same contraints we use for venv build13:13
noonedeadpunkhttps://opendev.org/openstack/openstack-ansible-os_tempest/src/branch/master/defaults/main.yml#L51-L5313:13
noonedeadpunkand temepst will be isntalled from correct SHA then13:14
jrosserthat will still include u-c though13:14
jrosseri can try that easily though13:15
kleinisorry for interrupting tempest discussion. what do I wrong in configuration if the tunnel network address of network hosts is not correctly read for the dynamic inventory? The network host in openstack_inventory.json does not have a address for the network tunnel_address. and that makes the deployment of the ML2 plugin wrong in regards to VXLAN tunnels.13:15
noonedeadpunkyes, but tempest egg should have precedence I guess13:15
jrosserkleini: normally that is for you to set the ip address on br-vxlan yourself as part of provisioning the hosts13:16
jrosserthe only thing that the inventory really knows about is the ip address that ansible uses to ssh to things13:17
noonedeadpunkygk_12345: that is pretty weird, as lxcbr is smth that lxc has by default...13:17
noonedeadpunkdo you have that bridge at all?13:17
ygk_12345noonedeadpunk yes its lxcbr013:17
kleiniokay, so the IP address for the tunnel network is read from the br-vxlan bridge?13:18
noonedeadpunkkleini: or from whatever interface you provided for vxlan network13:18
jrosserkleini: you should check out how this is working http://codesearch.openstack.org/?q=dynamic-address-fact&i=nope&files=&repos=13:20
noonedeadpunkygk_12345: tbh I has never seen such behaviour... can only think that it's because of the limit....13:20
ygk_12345noonedeadpunk what limit ?13:20
noonedeadpunk`--limit "c3v*"`13:21
ygk_12345noonedeadpunk thats the new host13:21
ygk_12345c3v13:21
noonedeadpunkso we generally include lxc_hosts group tyo the limit while creating containers13:21
kleiniI already read the source of that common-task but I still don't understand, why it resolves to the IP on the management interface. it must be some of the fallbacks13:26
ygk_12345noonedeadpunk the issue still persists13:32
noonedeadpunkygk_12345: I think you should delete created containers before trying to re-run13:32
noonedeadpunk(on the new host)13:32
ygk_12345noonedeadpunk the similar hosts with the same OS version are working fine13:32
ygk_12345noonedeadpunk i have indeed deleted the continaers and also the /var/lib/lxc folder as well on the host13:33
noonedeadpunkhm....13:33
noonedeadpunkwhat if you try to re-run without limit at all? I'm not sure this is an issue, but still....13:34
ygk_12345it would fail as well13:34
noonedeadpunkhuh...13:34
ygk_12345when it encounters these contianers13:34
*** spatel has joined #openstack-ansible13:35
ygk_12345noonedeadpunk let me delete the contianers and reboot the host13:35
ygk_12345noonedeadpunk one final try before rerunning the playbook13:36
kleinibr-vxlan has an IP address configured but dynamic-address-fact is not able to read it. I even debugged Ansible and it reads from the interface its MTU and MAC address correctly but not the IP address. What else can I do?13:43
*** KeithMnemonic has joined #openstack-ansible13:44
ygk_12345noonedeadpunk still the same situation. its not adding the container's eth0 and assiging the IP13:45
kleinias far as I understand the Ansible code, it falls back from metal_query to non_metal_query and there to ansible_host.13:45
noonedeadpunkygk_12345: do you have /var/lib/lxc/c3v*/eth0.[ini|hwaddr]?13:47
ygk_12345noonedeadpunk yes its there as well13:47
noonedeadpunkhuh. I think you should look into lxc logs maybe13:48
noonedeadpunkAs it's kinda up to lxc to add interfaces into bridge on stratup13:48
noonedeadpunkygk_12345: oh, and do you have lxc.include of eth0.ini in lxc config?13:48
ygk_12345noonedeadpunk yes its there.13:49
*** fghaas has left #openstack-ansible13:49
noonedeadpunkso I'd say there's defenitely smth going on with lxc, as from what you say I feel like they have been configured correctly...13:50
*** d34dh0r53 has joined #openstack-ansible13:53
*** d34dh0r53 has quit IRC13:54
*** d34dh0r53 has joined #openstack-ansible13:54
ygk_12345noonedeadpunk got the issue now. its the dnsmaq lxc service thats is faulty. i restarted it . now its working fine13:55
jrosserkleini: have you defined the tunnel network in cidr_networks in openstack_user_config.yml?13:55
mgariepywill this one merge at some point ?https://review.opendev.org/#/c/718786/13:58
kleiniyes it is defined according to openstack_user_config.yml.prod-ceph.example13:58
mgariepyor do we need to trigger a recheck ?13:58
*** jbadiapa has joined #openstack-ansible13:59
jrossermgariepy: i am not sure what is happening there13:59
noonedeadpunkWe just needed to push it a bit :p13:59
mgariepyadd +w..13:59
mgariepymight help a bit.13:59
jrosserkleini: have you got access to an all-in-one build as a reference?14:00
kleinihttp://paste.openstack.org/show/792476/ <- this is the top part of my openstack_user_config.yml14:01
kleininope, but I can setup an AIO14:02
kleinibut AIO does not use separate compute and network hosts and therefore I doubt, it establishes an vxlan tunnel14:02
kleinibut let's see14:02
jrosseryes it does, becasue it can run a full tempest test with VM attached by vxlan14:04
*** this10nly has quit IRC14:04
kleiniwill setup AIO14:04
jrosser reason i ask is that i am currently debugging other stuff in an AIO but straight away i can see that the tunnel_address variable is present http://paste.openstack.org/show/792477/14:10
*** ygk_12345 has quit IRC14:45
*** mgariepy has quit IRC15:04
openstackgerritJonathan Rosser proposed openstack/openstack-ansible-os_tempest master: Refactor tempest plugin install from source  https://review.opendev.org/72164515:05
jrossernoonedeadpunk: ^ this gives the right repeat version in the vent locally here15:07
jrosser*tempest version15:07
*** viks____ has quit IRC15:07
spatelhow are you guys!!15:07
spatelQuick question, we are building new datacenter and planning to build on new openstack release (does train stable enough for production?)15:08
noonedeadpunkjrosser: so you didin't get contraints working? or they just were not?15:08
spatelits been a while its out.. so assuming its15:08
jrosserthey were not15:08
*** gshippey has quit IRC15:09
jrosserpython_venv_build carefully splices together the supplied constraints and any that are necessary for things from source15:09
noonedeadpunkbut shouldn't we then also refactor "Install tempest plugins from packages" as well?15:09
*** gshippey has joined #openstack-ansible15:09
jrosserwell - i guess for distro packages you just have to trust that the packaging is good?15:11
*** mgariepy has joined #openstack-ansible15:17
*** yolanda has quit IRC15:21
noonedeadpunkjrosser: no, since we provide the same contraints15:22
noonedeadpunkI guess there packages was meant as pypi packges15:23
noonedeadpunknot distro ones lol15:23
noonedeadpunkthis one https://opendev.org/openstack/openstack-ansible-os_tempest/src/branch/master/tasks/tempest_install_source.yml#L59-L7315:24
*** udesale_ has quit IRC15:41
*** gyee has joined #openstack-ansible15:52
*** yolanda has joined #openstack-ansible15:52
redrobot\o16:01
redrobotIs the weekly meeting still happening today?16:01
jrossernoonedeadpunk: oh i think you are right with those other package installs....... distro vs pypi vs source16:02
jrosserredrobot: it should be i guess.....16:05
* redrobot waits patiently for possible meeting ...16:09
*** _kukacz has quit IRC16:14
redrobotmnaser, no meeting today?16:15
noonedeadpunksorry16:20
noonedeadpunk#startmeeting openstack_ansible_meeting16:20
openstackMeeting started Tue Apr 21 16:20:59 2020 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.16:21
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:21
*** openstack changes topic to " (Meeting topic: openstack_ansible_meeting)"16:21
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:21
noonedeadpunk#topic office hours16:21
*** openstack changes topic to "office hours (Meeting topic: openstack_ansible_meeting)"16:21
noonedeadpunkjrosser: redrobot sorry for the delay - with this summer time got a bit lost in time16:21
redrobotnoonedeadpunk, no worries16:22
noonedeadpunkso, what do we have except broken tempest thing (again)?16:22
redrobotI was hoping mnaser would be here so we can talk about16:23
redrobot#link https://review.opendev.org/#/c/721348/16:23
mnaserhi redrobot , sorry its exactly at 12pm so i grabbed something quick to eat16:23
* mnaser clicks16:23
mnaseroh yes hi16:23
* redrobot waves all around16:24
mnaserredrobot: yeah maybe the ansible sig might be a good home for those, it's not that i "Dont want them" but just feel like its not fair for y'all considering we don't really touch/see those roles :)16:24
redrobotHehe, no worries16:24
redrobotI _think_ we originally asked y'all because it was all Ansible16:24
redrobotbut I would not be opposed to moving them all under the Barbican umbrella16:24
noonedeadpunkI think those days there was no ansible sig, but now it is. So indeed I agree with evrardjp and mnaser that it's probably better to place these roles under ansible sig ubrella (as it is all about ANsible :))16:26
noonedeadpunkas we kinda know ansible but not realy aware of the functional part of these hsm roles16:27
noonedeadpunkso really hard to judge on them while voing on patches16:28
noonedeadpunk*voting16:28
redrobotAnsible SIG != OpenStack Ansible Team?16:28
redrobotI think ultimately the Barbican team will need to have core review permissions on these since we have access to the hardware to test them.16:28
noonedeadpunknope. OpenStack-Ansible is project for deploying openstack with ansible :)16:29
noonedeadpunkso it's more like deployment tool project along with tripleo, kolla, etc16:30
redrobotgotcha16:30
redrobothttps://wiki.openstack.org/wiki/Ansible_SIG then?16:30
noonedeadpunkyeah and #openstack-ansible-sig16:31
redrobotcool, I'll talk to them and see if that might be a good home for our *-hsm roles.16:31
redrobotthanks! :D16:31
noonedeadpunksure, no problems:)16:31
noonedeadpunkok, what I though about today, if should we offer providing a zookeeper cluster installation as a part of infra role?16:33
noonedeadpunkLike some of the projects make use it for coordination (not only telemetry ones) so it might be a nice idea having it.16:34
*** evrardjp has quit IRC16:35
*** evrardjp has joined #openstack-ansible16:35
noonedeadpunkLike I know that the roles is already exist, so as for implementation we will just need to add env.d file and sample to documentation16:35
noonedeadpunkAs a second step we might add defaults to the roles so in case of existing zookepeer projects would use it for coordination by default16:36
*** cyberpear has quit IRC16:38
*** rpittau is now known as rpittau|afk16:39
*** jrosser has quit IRC16:41
*** mnaser has quit IRC16:41
*** vblando has quit IRC16:42
*** Open10K8S has quit IRC16:42
*** cyberpear has joined #openstack-ansible16:42
*** soren has quit IRC16:42
*** Open10K8S has joined #openstack-ansible16:42
*** gshippey has quit IRC16:43
*** cyberpear has quit IRC16:43
*** jrosser has joined #openstack-ansible16:44
*** vblando has joined #openstack-ansible16:44
*** mnaser has joined #openstack-ansible16:44
*** gshippey has joined #openstack-ansible16:44
*** cyberpear has joined #openstack-ansible16:44
*** soren has joined #openstack-ansible16:45
*** mnaser has quit IRC16:46
*** cyberpear has quit IRC16:47
*** mnaser has joined #openstack-ansible16:47
*** cyberpear has joined #openstack-ansible16:47
*** mnaser has quit IRC16:49
*** cyberpear has quit IRC16:49
*** mnaser has joined #openstack-ansible16:50
*** cyberpear has joined #openstack-ansible16:50
*** jbadiapa has quit IRC17:02
openstackgerritJonathan Rosser proposed openstack/openstack-ansible-os_tempest master: Refactor tempest plugin install from source  https://review.opendev.org/72164517:15
jrossernoonedeadpunk: i have massively simplified the tempest source install now17:15
noonedeadpunk#endmeeting17:15
*** openstack changes topic to "Launchpad: https://launchpad.net/openstack-ansible || Weekly Meetings: https://wiki.openstack.org/wiki/Meetings/openstack-ansible || Review Dashboard: https://bit.ly/2SAcGAn"17:15
openstackMeeting ended Tue Apr 21 17:15:51 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2020/openstack_ansible_meeting.2020-04-21-16.20.html17:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2020/openstack_ansible_meeting.2020-04-21-16.20.txt17:15
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2020/openstack_ansible_meeting.2020-04-21-16.20.log.html17:15
noonedeadpunkjrosser: so we all in all ended up that we need to define venv_wheel_build_enable even if it's default one?17:17
*** thuydang has quit IRC17:17
jrosserthat is still set to 'no' otherwise becasue of the setting in the stackviz install17:17
jrosseri can double check that again17:17
noonedeadpunkjrosser: hm wouldn't tempest_pip_plugins be overriden by another set_fact?17:18
noonedeadpunkAs we kinda supposed to have mix of repo and package17:18
jrosserit should append as it takes the existing value from the previous set_fact17:19
jrosserthats pretty much how the set_fact / with_items works anyway17:19
noonedeadpunkoh, yeah, sorry)17:19
jrosserhopefully this is ok as i'm very happy to remove all that previous stuff17:19
jrosseri've only deployed tempest in my AIO, not the rest of openstack17:20
jrosserin the repo server /var/www/repo/os-releases/20.1.0.dev192/tempest-20.1.0.dev192-source-constraints.txt i have http://paste.openstack.org/show/792494/17:22
jrosserand the source installs look correct in the tempest venv also http://paste.openstack.org/show/792495/17:23
noonedeadpunkI hope that we've dropped isolated flag is ok eventually17:24
* jrosser runs away17:25
noonedeadpunkbut yeah, it's much simplified and I think it might also be some speed up because no need in cloning repos in advance17:25
jrosserit moves the cloning into the wheel build17:25
*** yolanda has quit IRC17:33
noonedeadpunkyeah, I mean maybe it's just a bit more fast than would be with ansible (due to connects)17:42
noonedeadpunkanyway we don't have them in required-projects17:42
*** cshen_ has quit IRC17:46
*** cshen has joined #openstack-ansible17:48
*** cshen has quit IRC17:52
*** hamzy__ has quit IRC17:59
*** cshen has joined #openstack-ansible18:20
*** cshen has quit IRC18:25
*** gshippey has quit IRC19:07
jrossernoonedeadpunk: we need to make a plan to merge all this tempest stuff19:11
jrosserbionic distro job is still broken and needs your patch to the integrated repo to fix it19:11
jrosserand thats also needed to land my patch to os_tempest to fix all the other jobs19:12
jrosserso perhaps for now we make bionic/distro non-voting for os_tempest?19:12
*** cshen has joined #openstack-ansible20:02
*** idlemind has joined #openstack-ansible20:04
*** cshen has quit IRC20:06
*** mgariepy has quit IRC20:09
*** mgariepy has joined #openstack-ansible20:12
*** thuydang has joined #openstack-ansible20:53
*** spatel has quit IRC21:30
*** thuydang has quit IRC21:41
*** keeper has left #openstack-ansible22:35
*** spatel has joined #openstack-ansible22:53
*** tosky has quit IRC23:03
openstackgerritJonathan Rosser proposed openstack/openstack-ansible-os_tempest master: Refactor tempest plugin install from source  https://review.opendev.org/72164523:26

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