Tuesday, 2019-01-08

*** macza has quit IRC00:06
*** mathlin has joined #openstack-ansible00:11
*** cshen has joined #openstack-ansible00:15
*** cshen has quit IRC00:20
*** fatdragon has joined #openstack-ansible00:38
*** mathlin has quit IRC00:45
*** fatdragon has joined #openstack-ansible01:05
*** mathlin has joined #openstack-ansible01:08
*** strobelight has joined #openstack-ansible01:14
*** cshen has joined #openstack-ansible01:40
*** mathlin has quit IRC01:41
*** hwoarang has joined #openstack-ansible01:44
*** cshen has quit IRC01:46
*** hwoarang_ has quit IRC01:46
*** mino_ has joined #openstack-ansible01:50
*** macza has joined #openstack-ansible01:55
*** shardy has quit IRC01:57
*** hwoarang has quit IRC02:01
*** hwoarang has joined #openstack-ansible02:02
*** shardy has joined #openstack-ansible02:04
*** mathlin has joined #openstack-ansible02:05
*** DanyC has joined #openstack-ansible02:13
*** DanyC has quit IRC02:17
*** macza has quit IRC02:30
*** mathlin has quit IRC02:39
*** mathlin has joined #openstack-ansible03:02
*** hwoarang_ has joined #openstack-ansible03:30
*** hwoarang has quit IRC03:31
*** macza has joined #openstack-ansible03:32
*** mathlin has quit IRC03:36
*** macza has quit IRC03:36
*** shardy has quit IRC03:52
*** shardy has joined #openstack-ansible03:53
*** mathlin has joined #openstack-ansible03:59
*** mino_ has quit IRC04:03
*** udesale has joined #openstack-ansible04:12
*** spsurya has joined #openstack-ansible04:22
*** mathlin has quit IRC04:32
*** strobelight has quit IRC04:37
openstackgerritKevin Carter (cloudnull) proposed openstack/openstack-ansible-os_keystone master: Cleanup files and templates using smart sources  https://review.openstack.org/58896004:48
*** spsurya has quit IRC05:10
*** spsurya has joined #openstack-ansible05:13
*** cshen has joined #openstack-ansible05:15
openstackgerritChandan Kumar proposed openstack/openstack-ansible-os_tempest master: Synced tempest plugins names and services  https://review.openstack.org/62892605:17
*** cshen has quit IRC05:20
*** mathlin has joined #openstack-ansible05:22
*** cshen has joined #openstack-ansible05:28
*** shyamb has joined #openstack-ansible05:37
*** cshen has quit IRC05:37
*** cshen has joined #openstack-ansible05:38
*** shyamb has quit IRC05:43
*** radeks has joined #openstack-ansible05:48
*** shyamb has joined #openstack-ansible05:51
*** cshen has quit IRC05:54
*** hwoarang has joined #openstack-ansible05:54
*** mathlin has quit IRC05:56
*** hwoarang_ has quit IRC05:57
*** hwoarang_ has joined #openstack-ansible06:08
*** hwoarang has quit IRC06:11
*** radeks has quit IRC06:11
*** fatdragon has quit IRC06:13
*** radeks has joined #openstack-ansible06:20
*** cshen has joined #openstack-ansible06:23
*** gyee has quit IRC06:24
*** cshen has quit IRC06:27
*** mathlin has joined #openstack-ansible06:46
*** shyamb has quit IRC06:50
*** shyamb has joined #openstack-ansible07:03
openstackgerritJonathan Rosser proposed openstack/openstack-ansible-lxc_hosts master: Increasing LXC container default shutdown delay  https://review.openstack.org/62599807:04
openstackgerritJonathan Rosser proposed openstack/openstack-ansible-lxc_hosts master: Use libeatmydata during LXC cache prep  https://review.openstack.org/62150907:05
*** shyamb has quit IRC07:05
*** shyamb has joined #openstack-ansible07:06
*** hamzaachi has joined #openstack-ansible07:09
*** DanyC has joined #openstack-ansible07:13
*** DanyC has quit IRC07:18
*** mathlin has quit IRC07:20
*** cshen has joined #openstack-ansible07:24
*** shyamb has quit IRC07:25
*** cshen has quit IRC07:29
*** cshen has joined #openstack-ansible07:30
*** fatdragon has joined #openstack-ansible07:30
*** shyamb has joined #openstack-ansible07:32
fnpanic hi07:39
fnpanicodyssey4me: Thanks for looking at the proxy patches for rocky07:39
*** fatdragon has quit IRC07:42
*** pcaruana has joined #openstack-ansible07:42
*** jbadiapa has joined #openstack-ansible07:43
*** mathlin has joined #openstack-ansible07:43
*** shyamb has quit IRC07:46
*** gkadam has joined #openstack-ansible07:48
*** gkadam is now known as gkadam-afk07:50
*** kopecmartin|off is now known as kopecmartin08:00
chandankumarjrosser: \o.08:04
chandankumarjrosser: https://review.openstack.org/628926 is good to go :-)08:05
*** mwhahaha has quit IRC08:05
*** jungleboyj has quit IRC08:06
*** jungleboyj has joined #openstack-ansible08:06
*** mwhahaha has joined #openstack-ansible08:06
*** hamzaachi_ has joined #openstack-ansible08:08
*** hamzaachi has quit IRC08:10
*** priteau has joined #openstack-ansible08:12
*** mathlin has quit IRC08:17
*** shardy has quit IRC08:19
*** shardy has joined #openstack-ansible08:20
*** DanyC has joined #openstack-ansible08:21
*** gkadam-afk is now known as gkadam08:24
*** DanyC has quit IRC08:26
*** cshen has quit IRC08:34
*** tosky has joined #openstack-ansible08:37
jrosserchandankumar: nice! done08:38
jrosserhopefully that makes the os_barbican and other role tests go#08:39
*** mathlin has joined #openstack-ansible08:40
*** cshen has joined #openstack-ansible08:40
*** hamzaachi__ has joined #openstack-ansible08:45
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-os_neutron master: cleanup: remove metadata checksum fixes tasks  https://review.openstack.org/62779208:46
*** hamzaachi_ has quit IRC08:47
*** fatdragon has joined #openstack-ansible08:48
*** evrardjp_ has joined #openstack-ansible08:48
*** evrardjp__ has joined #openstack-ansible08:49
*** evrardjp has quit IRC08:51
*** evrardjp_ has quit IRC08:52
*** evrardjp__ has quit IRC08:53
*** fatdragon has quit IRC08:55
*** shyamb has joined #openstack-ansible08:56
*** thuydang has joined #openstack-ansible08:57
*** thuydang has quit IRC09:01
*** evrardjp has joined #openstack-ansible09:03
openstackgerritJonathan Rosser proposed openstack/openstack-ansible-os_keystone master: Cleanup files and templates using smart sources  https://review.openstack.org/58896009:05
*** mathlin has quit IRC09:14
*** sawblade6 has joined #openstack-ansible09:18
*** DanyC has joined #openstack-ansible09:20
openstackgerritMerged openstack/ansible-hardening master: cleanup: use updated conditionals  https://review.openstack.org/62902209:20
odyssey4mejrosser we may still have to tweak the roles a bit, but that'll help start things to move them towards a better working state09:29
*** thuydang has joined #openstack-ansible09:31
*** mkuf_ has joined #openstack-ansible09:31
*** mkuf has quit IRC09:34
jrosserevrardjp: re that arm patch being broken on metal, i think all the metal jobs are brok on master09:40
evrardjpmmm09:41
evrardjpsad09:41
jrosseri believe this may be to blame https://github.com/openstack/openstack-ansible-galera_client/commit/30cb1e72d6736bae9dacbed0c3e6ef8fb174aaeb09:41
evrardjpbut I guess nobody cares.09:41
jrosserthe current fail is galera server tripping over things that u09:42
jrosser*used to have been fiddled in the galera client role09:42
evrardjpI see09:42
evrardjpwell I sadly don't have time to fix that rn09:43
jrosseri didnt know if it was a mistake removing that stuff from galera client or that the same thing needs doing in the server role to match09:44
evrardjpI don't know how it passed in the first place09:44
evrardjpwell I have an idea but ... hey09:44
evrardjpI am not fully aware of the context of this patch in galera-client09:45
jrosserthe galera client role test doesnt test on-metal, nor will it co-install galera_server role09:45
odyssey4mejrosser if galera_Server requires that logic, then we should move it there09:46
*** vnogin has joined #openstack-ansible09:46
jrosserit was in both - now only in one09:46
odyssey4meinteresting - which metal job is now failing?09:47
odyssey4meboth centos & opensuse09:47
odyssey4menot ubuntu09:47
odyssey4menot surprising, because all that stuff was to make centos/suse look like ubuntu09:48
*** mathlin has joined #openstack-ansible09:49
*** Miouge has left #openstack-ansible09:50
*** Miouge has joined #openstack-ansible09:51
openstackgerritArx Cruz proposed openstack/openstack-ansible-os_tempest master: Better tempest black and whitelist management  https://review.openstack.org/62160509:54
jrosserodyssey4me: should we just revert that change from galera_client?09:56
odyssey4mejrosser yeah, I haven't any more time to spend on it09:57
jrosserno me neither - i did prod mnaser about this a day or two ago09:58
odyssey4meI'll do a revert now.09:58
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-galera_client master: Revert "cleanup: stop managing files inside /etc"  https://review.openstack.org/62912209:59
*** shyamb has quit IRC10:00
odyssey4mewell, we can make any roles use the integrated build for testing now - we just can't set them to do any different affinities (to test clustering) just yet10:01
odyssey4meI think perhaps I should get working on that, because that will open the door to switching most roles over to have deploy and upgrade tests.10:01
openstackgerritChandan Kumar proposed openstack/openstack-ansible-os_tempest master: Move role data in share/ansible/roles  https://review.openstack.org/62912710:03
odyssey4mejrosser oh, it looks like the issue could be solved quite simply - lemme push up an alternative patch10:04
*** shyamb has joined #openstack-ansible10:05
evrardjpodyssey4me: interesting , will wait for the patch. Have voted on the first one, should the new approach fail.10:06
*** thuydang has quit IRC10:06
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-galera_server master: Switch galera_install_dnf back to being a symlink  https://review.openstack.org/62913110:10
odyssey4methat fixes one issue I noticed... :p10:11
openstackgerritMerged openstack/openstack-ansible-os_tempest master: Synced tempest plugins names and services  https://review.openstack.org/62892610:11
*** mkuf has joined #openstack-ansible10:12
* jrosser rechecks a designate and barbican review now that tempest change is in ^10:15
*** mkuf_ has quit IRC10:16
*** priteau has quit IRC10:17
*** mathlin has quit IRC10:22
MiougeIt would be cool to get some reviews on this Pike cherry pick: https://review.openstack.org/#/c/623233/ Rocky and Queens are already merged10:27
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-galera_server master: Replace /etc/my.cnf.d if it exists for SUSE/CentOS  https://review.openstack.org/62913510:28
odyssey4mejrosser evrardjp ^ that should so the trick10:28
*** mkuf has quit IRC10:29
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-lxc_container_create stable/rocky: Resolve btrfs backing store variable inconsistency  https://review.openstack.org/62913710:30
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-lxc_container_create stable/queens: Resolve btrfs backing store variable inconsistency  https://review.openstack.org/62913810:30
openstackgerritChristian Zunker proposed openstack/openstack-ansible-os_horizon master: Switch to import_tasks when tags should be applied  https://review.openstack.org/62913910:30
*** shyamb has quit IRC10:33
*** cshen has quit IRC10:34
*** kopecmartin is now known as kopecmartin|afk10:35
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-os_tempest master: Use the inventory to enable/disable services by default  https://review.openstack.org/62897910:35
*** cshen has joined #openstack-ansible10:37
*** mkuf has joined #openstack-ansible10:39
odyssey4meevrardjp could you also vote on this fix please https://review.openstack.org/#/c/629131/110:39
*** cshen has quit IRC10:42
*** priteau has joined #openstack-ansible10:44
*** mathlin has joined #openstack-ansible10:46
*** fatdragon has joined #openstack-ansible10:52
openstackgerritMerged openstack/openstack-ansible-os_neutron master: cleanup: remove metadata checksum fixes tasks  https://review.openstack.org/62779210:53
*** udesale has quit IRC10:57
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/ansible-hardening master: Switch to using import_tasks for static inclusion  https://review.openstack.org/61432910:59
*** fatdragon has quit IRC11:01
admin0\o11:12
*** cshen has joined #openstack-ansible11:12
*** dcdamien has joined #openstack-ansible11:13
admin0what does this mean ? TASK [os_heat : Create DB for service]  = FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}11:16
*** thuydang has joined #openstack-ansible11:16
*** cshen has quit IRC11:17
odyssey4meadmin0 it means that something went wrong, but the log output has been surpressed because there is 'no_log: true' set on that task11:18
*** mathlin has quit IRC11:19
*** thuydang has quit IRC11:22
*** cshen has joined #openstack-ansible11:42
*** mathlin has joined #openstack-ansible11:42
admin0for internal cloud, how do I populate this variable: horizon_keystone_multidomain_dropdown ?   horizon_keystone_multidomain_dropdown: { 'Default', 'domain.com' } ??11:44
odyssey4meadmin0 that's a boolean - so it's true/false11:47
odyssey4meit populates from the keystone service catalog, as far as I know11:48
*** shyamb has joined #openstack-ansible11:48
odyssey4meif not, then it seems like https://docs.openstack.org/django_openstack_auth/latest/configuration/index.html#openstack-keystone-domain-choices might be needed - and there's no support for that right now11:50
odyssey4meperhaps noonedeadpunk can advise when he's back online11:50
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/ansible-hardening master: Switch to using import_tasks for static inclusion  https://review.openstack.org/61432911:54
*** noonedeadpunk has joined #openstack-ansible11:56
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/ansible-hardening stable/rocky: cleanup: use updated conditionals  https://review.openstack.org/62915811:58
dcdamienodyssey4me: I hoped that dependent change would resolve issue with tempest on centos but it doesn't look like -> https://review.openstack.org/#/c/628785/311:59
*** noonedeadpunk has quit IRC12:03
odyssey4medcdamien nope, I didn't think it would - because nothing is setting 'tempest_service_available_designate: true' so that it installs the package12:03
odyssey4methat's what https://review.openstack.org/#/c/628979/4/defaults/main.yml is for, but there's a bug there it seems12:03
*** noonedeadpunk has joined #openstack-ansible12:04
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-os_tempest master: Use the inventory to enable/disable services by default  https://review.openstack.org/62897912:04
*** thuydang has joined #openstack-ansible12:11
*** thuydang has quit IRC12:13
chandankumarodyssey4me: Hello12:15
chandankumarodyssey4me: I am hitting this failure http://logs.openstack.org/82/627482/27/check/python-tempestconf-tempest-os-tempest/6fd8f64/job-output.txt.gz#_2019-01-08_12_00_54_48366512:15
chandankumarodyssey4me: here is the playbook https://review.openstack.org/#/c/627482/12:15
*** mathlin has quit IRC12:17
openstackgerritMerged openstack/openstack-ansible stable/pike: Update all SHAs for 16.0.25  https://review.openstack.org/62708312:17
*** cshen has quit IRC12:17
odyssey4mechandankumar it looks like the path is incomplete12:19
odyssey4meno, that's not it - see http://logs.openstack.org/82/627482/27/check/python-tempestconf-tempest-os-tempest/6fd8f64/ara-report/result/72ec7db5-65c7-4aef-a36a-5ab23f135cbf/12:21
odyssey4mechandankumar the issue is that the parent directory for that path doesn't exist12:21
*** cshen has joined #openstack-ansible12:21
fnpanichi12:21
chandankumarodyssey4me: I need to replace that path with something else then12:22
jamesdenton@mbuil ping me when you're around, please12:22
fnpanicwhen i want to install elatiflow (https://github.com/robcowart/elastiflow) manual to a elastic cluster installed with the elk_metrics_6x playbooks from the ops repo, could this work?12:23
odyssey4mechandankumar well, I'm wondering whether it makes sense for the python-venv-build role to create the parent - or whether the calling role should create it12:23
chandankumarodyssey4me: I think python-venv-build role should create the parent directory12:23
chandankumarlet me propose a patch there12:23
odyssey4mechandankumar yeah, seems sensible to me - thanks12:24
*** cshen has quit IRC12:27
*** gkadam has quit IRC12:29
*** shyamb has quit IRC12:30
*** mathlin has joined #openstack-ansible12:39
openstackgerritChandan Kumar proposed openstack/ansible-role-python_venv_build master: Create venv_install_destination_path parent directory  https://review.openstack.org/62916712:41
chandankumarodyssey4me: ^^12:41
*** shyamb has joined #openstack-ansible12:42
*** ansmith has joined #openstack-ansible12:42
mbuiljamesdenton: back from lunch12:45
*** ansmith has quit IRC12:48
*** hamzaachi__ has quit IRC12:50
*** vnogin has quit IRC12:54
openstackgerritChandan Kumar proposed openstack/ansible-role-python_venv_build master: Create venv_install_destination_path parent directory  https://review.openstack.org/62916712:55
*** dcdamien has quit IRC12:57
*** cshen has joined #openstack-ansible12:58
*** iw_zah has joined #openstack-ansible13:00
*** cshen has quit IRC13:02
*** szaher has joined #openstack-ansible13:08
arxcruzodyssey4me: hey, happy new year :)13:11
arxcruzodyssey4me: I hope now https://review.openstack.org/#/c/621605/ is as you wanted :)13:11
openstackgerritMerged openstack/openstack-ansible stable/queens: Update all SHAs for 17.1.7  https://review.openstack.org/62708113:12
*** mathlin has quit IRC13:13
chandankumararxcruz: mnaser https://review.openstack.org/#/c/629167/13:19
iw_zahIs there a room for some basic problems deploying OS using QSA? I dont want to bother13:20
*** udesale has joined #openstack-ansible13:20
odyssey4meiw_zah what is QSA?13:20
iw_zahOSA, sorry13:21
odyssey4meiw_zah this is the right place13:21
iw_zahDeploying Openstack in a tagged infrastructure should be possible, isn't it?13:22
odyssey4mearxcruz I'm still confused - why the need to move them into vars files at all - I get the sense that you're not understanding how using overrides in ansible works?13:24
openstackgerritJean-Philippe Evrard proposed openstack/openstack-ansible-os_horizon master: Revert "Rename SUSE vpnaas-ui package"  https://review.openstack.org/62917713:24
arxcruzodyssey4me: I believe it's more easyt read than keep everything in the defaults/main.yml but please, enlight me about your idea here13:26
arxcruzodyssey4me: you want me to put int in var_files/all, or keep it in the defaults/main.yml ?13:27
odyssey4mearxcruz if tripleo wants to curate their own list, then that can be done - the defaults in the role can all be overrideen by any other variable precedence - by moving those vars into vars/main.yml, you're removing all the override capabilities making it much harder to override13:27
odyssey4methese should stay in defaults, because role defaults are the lowest precedence, giving *all* options to override13:28
odyssey4mehttps://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable13:28
arxcruzodyssey4me: so, can't we use the same list?13:28
arxcruzodyssey4me: my idea was add the installer type and we can share the list13:29
odyssey4mearxcruz yes, that's what I suggested right from the start13:29
arxcruzodyssey4me: okay, so i'll move it to defaults/main.yml13:29
odyssey4mewell, as I mentioned before, why don't be just use the same list - and if you really want to override it then do that13:29
arxcruzodyssey4me: because on tripleo we have different list based on release13:30
odyssey4methere's no need to distinguish between what we want in the whitelist/blacklist and what tripleo does as far as I can see - if openstack is broken, it's broken for everyone13:30
arxcruzodyssey4me: not reallyin the way tripleo works13:30
odyssey4mebased on release? you mean based on series?13:30
odyssey4meie rocky vs stein?13:30
arxcruzodyssey4me: we test pike, queens, rocky, stein13:30
arxcruznot sure if we still test ocata13:31
odyssey4meok, then that's a different issue which we need ot think about13:31
arxcruzodyssey4me: that's why i move to a file, we can just override the variable file name in vars/13:31
arxcruzlike blacklist_rocky.yml13:32
arxcruzthen it will load rocky black list13:32
arxcruzblacklist_{{ release }}.yml13:32
odyssey4meok, but you can still do that -but do it in the playbook that you use to run this13:32
arxcruzodyssey4me: https://github.com/openstack/tripleo-quickstart-extras/blob/master/roles/validate-tempest/tasks/pre-tempest.yml#L2713:33
odyssey4meleave the defaults there with the master list, which targets master - then for stable branch tests override the default in the playbook13:33
odyssey4meis there a thing that calls this os_tempest role which is being worked on for tripleo?13:34
arxcruzodyssey4me: https://review.openstack.org/#/c/62841513:35
arxcruzchandankumar: is working on that13:35
*** plobo has joined #openstack-ansible13:38
odyssey4meI've commented how you would import an override for the vars you want in there.13:38
odyssey4meThe role doesn't have to be changed at all to accommodate what you want to do.13:38
evrardjpcores: I have discussed with Dirk (from rpm-packaging) about the issues we had this cycle with the SUSE packages. I think, from now on, if we see an issue in SUSE packages that break a build, we can (and should) ping in the #openstack-rpm-packaging to find out the root cause of the issues together.13:38
odyssey4meok, thansk evrardjp13:39
arxcruzodyssey4me: ok, thanks!13:40
*** plobo has quit IRC13:40
odyssey4mearxcruz so the only thing to do is get the data structure the way you'd like it so that it has the annotations, which I love :)13:40
arxcruzodyssey4me: yup, too fast, i was typing about that :P13:40
*** trident has quit IRC13:41
arxcruzchandankumar: ^13:41
*** trident has joined #openstack-ansible13:42
*** jhesketh has quit IRC13:45
*** dcdamien has joined #openstack-ansible13:46
*** szaher has quit IRC13:47
*** jhesketh has joined #openstack-ansible13:47
cloudnullmornings13:48
*** ansmith has joined #openstack-ansible13:49
openstackgerritMerged openstack/openstack-ansible-os_neutron master: Provide support for network interface mappings without override  https://review.openstack.org/62362013:51
*** szaher has joined #openstack-ansible13:52
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-os_heat master: Only implement policy.json if an override is configured  https://review.openstack.org/62919113:55
openstackgerritMerged openstack/openstack-ansible-galera_server master: Switch galera_install_dnf back to being a symlink  https://review.openstack.org/62913113:57
openstackgerritMerged openstack/openstack-ansible-galera_server master: Replace /etc/my.cnf.d if it exists for SUSE/CentOS  https://review.openstack.org/62913513:57
openstackgerritKevin Carter (cloudnull) proposed openstack/openstack-ansible-os_keystone master: Cleanup files and templates using smart sources  https://review.openstack.org/58896013:57
odyssey4mecores - it appears that policy-in-code was done for heat in queens, and we're still carrying our own policy file, which may cause problems and potential security issues - we should get https://review.openstack.org/#/c/629191/1 merged and ported back asap13:59
cloudnulldone14:02
*** trident has quit IRC14:03
cloudnullfnpanic that should work, though I've never done it so hard to say 100%14:03
*** mathlin has joined #openstack-ansible14:03
*** trident has joined #openstack-ansible14:03
*** kopecmartin|afk is now known as kopecmartin14:06
cloudnullfnpanic looks like one the elk cluster is online you can start the installation here https://github.com/robcowart/elastiflow/blob/master/INSTALL.md#2-add-and-update-required-logstash-plugins and it should "Just Work-tm"14:06
jrossermnaser: lxc_hosts seems to be wedged up on centos still - have you seen anything like this? http://logs.openstack.org/78/613078/19/check/openstack-ansible-lxc-btrfs-centos-7/7782654/job-output.txt.gz#_2019-01-07_21_49_54_81136714:09
mnaserclick14:09
cloudnullodyssey4me i'm getting a weird error with python_venv_build - https://pasted.tech/pastes/1004aa3c07952aafd3229ba0baad3ae76ad1c0e9.raw - encountered when re-running the cinder role local tests .14:10
mnaserhmm14:10
jrosserthere was a btrfs fix went in earlier today14:10
jrosserbut sadly thats just revealed that underneath14:10
cloudnullhave you seen anything like that before ?14:10
mnaseris that the btrfs job14:10
jrosserit does it the same on btrsf and overlayfs14:10
cloudnullspecifically - ` [Errno 2] No such file or directory: '/src/local-package-constraints-master.txt'` ?14:10
mnaserok so this just blows up on btrfs and overlayfs only jrosser ? or all of the above14:11
odyssey4mecloudnull yes, I've seen that - it's because you don't have the right env vars set, because you're not using ./run_tests.sh - if you set the WORKING_DIR env var I think it'll solve it14:11
cloudnullok.14:11
jrossermnaser: like this https://review.openstack.org/#/c/613078/14:11
mnaserlemme check sys logs14:12
odyssey4mecloudnull given that cinder is only using the standard functional test jobs - maybe we should switch it over to using the integrated repo for tests now - lemme push up a patch for it14:12
mnaseri dont use any overlay drivers tbh14:12
cloudnullodyssey4me ++14:12
jrosserjust wondered if there was any centos-ism rang a bell there - i was wondering if this all started around the 7.5->7.6 point14:13
mnaserjrosser: http://logs.openstack.org/78/613078/19/check/openstack-ansible-lxc-btrfs-centos-7/7782654/logs/host/lxc/lxc-container1.log.txt.gz14:13
mnaserFailed to rename network device "vethRWE53H" to "eth0": File exists14:13
jrosserit's upset about the networking, yes14:13
mnaserupset about networking when the storage driver changes14:14
* mnaser flips table14:14
odyssey4memnaser are we happy to go ahead with https://review.openstack.org/#/c/623253/ ? that'll make the ceph_client role get tested by the integrated build14:14
mnaserooooou14:14
mnaseryes i love that14:14
mnaserodyssey4me: i was also thinking that for the roles we do metal tests, might be quicker overall, keep the container ones for integrated repo14:15
odyssey4meit doesn't take away the existing role tests using the tests repo - I don't think we should remove those functional tests until we've got better penetration14:15
mnaserbut that's an optimization we can do later14:15
mnaseryeah and because we just project templates, it's just 1 change so..14:16
* mnaser goes back to silly centos network issue14:16
odyssey4mewell, not exactly for all roles - because for each role that's not in the AIO we'll need to add an in-repo job which adds the extra service14:17
mnaserah yes14:17
odyssey4mehere's an example - in the cinder role, do we want to just test cinder & keystone... or do we want to test a full AIO?14:18
odyssey4memy suggestion would be just cinder with keystone - that'll be quick and simpler to spot issues for14:19
mnaserisnt an aio just keystone+nova+cinder anyways?14:19
mnaserwell i worry that if we break something in the volume attach path14:19
admin0TASK [os_heat : Add service/heat user]  -- always fails .. is this a known issue ....  18.1.1 -> 18.1.214:19
odyssey4meaio = keystone, cinder, nova, neutron, horizon, galera, rabbitq14:19
odyssey4meoh, and glance: https://github.com/openstack/openstack-ansible/blob/master/tests/roles/bootstrap-host/vars/main.yml#L2414:20
admin0aio = swift also ?14:20
admin0it has been useful14:20
guilhermespmornings...would we have a meeting today?14:21
odyssey4meno, the AIO no longer has swift in master/rocky14:21
odyssey4meit's easily added, but not there by default14:22
mnaserguilhermesp: yes we will!14:22
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-os_horizon stable/rocky: Revert "Rename SUSE vpnaas-ui package"  https://review.openstack.org/62919414:24
openstackgerritArx Cruz proposed openstack/openstack-ansible-os_tempest master: Better tempest blacklist management  https://review.openstack.org/62160514:24
arxcruzI hope now it's okay14:24
arxcruzodyssey4me: ^14:24
arxcruzprobably won't be14:25
admin0jamesdenton, reading your article on the mnaio, this weekend i am trying 2 nvme on raid0 to see if the time can be brought down even lower14:26
jamesdentonawesome!14:29
*** shyamb has quit IRC14:29
jamesdentoni have a samsung 970 evo showing up tomorrow and will see how much lower it'll go14:29
jamesdentonanything to speed up these tests14:30
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-os_cinder master: Test using integrated build  https://review.openstack.org/62919514:31
chandankumarcloudnull: mnaser small fix https://review.openstack.org/#/c/629167/ for venv_build14:31
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-os_cinder master: Test using integrated build  https://review.openstack.org/62919514:32
admin0same .. 970 evo x2   goes into my crosshair hero VII  .. should be able to get full speeds14:32
odyssey4mejamesdenton admin0 you know, if you have enough RAM on the host you can use a ramdisk instead :p14:33
*** priteau has quit IRC14:33
admin0i only have 6414:34
jamesdentonodyssey4me i remember you mentioning that. 76GB looks like it would handle the base VMs + host14:37
*** mathlin has quit IRC14:37
jrosserif you had some dedupe on the filesystem it may well be significantly less14:38
jrossergiven the basic VM are pretty much all the same14:38
*** shardy has quit IRC14:41
*** ygk_12345 has joined #openstack-ansible14:43
ygk_12345hi all I want to enable log in this context14:43
ygk_12345how can I do that ?14:43
ygk_12345when running os-heat-install playbook I am seeing this "the output has been hidden due to the fact that 'no_log: true"14:43
jamesdentoni retract my statement about 76GB. That was RAM not disk. my bad14:44
ygk_12345FAILED - RETRYING: Add service/heat user (5 retries left).14:44
ygk_12345i wan t to see the exact duplicate entry  and delete it and try again14:44
ygk_12345but I dont know what it is14:44
ygk_12345so I want to see the log14:44
ygk_12345how to enable it in ansible ?14:44
*** hamzaachi has joined #openstack-ansible14:45
mnaserodyssey4me: btw, what do you think of this? https://review.openstack.org/#/c/627784/14:45
ygk_12345this sis the bug I am facing14:45
ygk_12345https://bugs.launchpad.net/openstack-ansible/+bug/180734614:45
openstackLaunchpad bug 1807346 in openstack-ansible "[heat] Installations fails during Update Q->R" [Undecided,New] - Assigned to Guilherme Steinmuller Pimentel (guilhermesp)14:45
*** cshen has joined #openstack-ansible14:48
mnaserMoved network device "vethSFKG8R"/"(null)" to network namespace of 197314:48
mnaseri wonder why it says (null)14:48
odyssey4meygk_12345 at this time the only way is to remark out the no_log line in the task file14:49
mnaserok14:50
mnaserthere is no 'tox_env' called 'btrfs'14:51
*** shardy has joined #openstack-ansible14:51
mnaserin lxc_hosts role14:51
*** shardy has quit IRC14:51
mnaser..so what are those jobs doing14:51
*** shardy has joined #openstack-ansible14:51
odyssey4memnaser it's running a test in lxc_containers_create14:51
odyssey4meit's a cross-repo test14:51
mnasergah14:51
mnaserduh14:51
mnaserokay that makes sense14:51
mnaseri was losing it14:51
mnaserwe really should have those jobs voting14:53
mnaserif we're going to have them cross-gate lxc_hosts14:53
odyssey4memnaser sure, although it's not hard to end up with a circular failure there14:53
mnaseryeah14:54
mnaserequal part awful14:54
*** cshen has quit IRC14:54
openstackgerritMerged openstack/ansible-role-python_venv_build master: Create venv_install_destination_path parent directory  https://review.openstack.org/62916714:54
mnaserhttp://logs.openstack.org/82/628982/3/check/openstack-ansible-btrfs-centos-7/20eaf30/job-output.txt.gz#_2019-01-07_17_37_23_86754514:55
ygk_12345odyssey4me: how to do that ?14:55
mnasershouldn't that be a hard fail?14:55
ygk_12345odyssey4me: I mean which file exactly ?14:56
odyssey4meygk_12345 grep for the task name in that role and you'll find it14:56
ygk_12345odyssey4me: ok14:56
cloudnullgeneral question, has anyone seen this before: https://pasted.tech/pastes/7c4f4463a2c0382b08fab19920a9b03ac772a2b8.raw - in cinder it seems to be throwing SQL errors, though in general the CLI is working (create|show|delete volumes is all working), I'm curious if this is an issue with my smart_sources patch for cinder or just a general issue with c14:57
cloudnullinder at the moment?14:57
odyssey4memnaser according to the comments in code and previous reviews for those tasks, no - apparently centos doesn't always do the right thing with btrfs14:57
*** fatdragon has joined #openstack-ansible14:58
fnpaniccloudnull: Thanks! I will try it and report back!14:58
cloudnull++14:58
odyssey4mecloudnull looks like it passed some tests recently: https://review.openstack.org/62819714:59
odyssey4menot sure if something broken since then upstream or downstream14:59
ygk_12345odyssey4me: the os-heat playbook is failing here "failed: [c1b_heat_api_container-45a01df4 -> localhost] (item={u'project': u'admin', u'role': u'admin', u'user': u'stack_domain_admin'}) => {"attempts": 5, "changed": false, "item": {"project": "admin", "role": "admin", "user": "stack_domain_admin"}, "msg": "User stack_domain_admin is not valid"}"14:59
ygk_12345odyssey4me: TASK [os_heat : Add service user to roles]15:00
*** mathlin has joined #openstack-ansible15:00
odyssey4meygk_12345 and if you look at the tasks before that, should that user have been created - or if you look in keystone, can you see the user?15:01
odyssey4mecan you see what might be wrong there?15:01
chandankumarodyssey4me: http://logs.openstack.org/82/627482/28/check/python-tempestconf-tempest-os-tempest/c6e0056/job-output.txt.gz#_2019-01-08_13_48_10_28039915:01
chandankumarodyssey4me: this time permission error15:01
cloudnullodyssey4me interesting, looks like its doing the same thing there, but the tests are passing: http://logs.openstack.org/97/628197/1/check/openstack-ansible-functional-ubuntu-bionic/02b6f68/logs/openstack/cinder/cinder-scheduler.service.journal.log.txt.gz#_Jan_03_15_24_3315:01
mnaserok, creating a container with backing store btrfs seems *not* to create a btrfs subvolume at /var/lib/lxc/centos-7-amd6415:01
ygk_12345odyssey4me: I see that user. but I deleted them before running that playbook15:02
chandankumarodyssey4me: https://review.openstack.org/#/c/627482/28/playbooks/python-tempestconf-os-tempest.yaml does adding here become:true will help?15:02
*** fatdragon has quit IRC15:03
odyssey4mechandankumar well, it's a remote host and you're accessing it via the root user - so I'd guess not... unless that's a pseudonym for localhost, in which case yes - you need to become15:03
odyssey4mecloudnull how nice :/15:03
odyssey4meygk_12345 I don't see how deleting the user is helpful. Inspecting the user to see whether it's in the right domain, etc might be useful.15:04
chandankumarodyssey4me: thanks, updated :-)15:04
odyssey4mechandankumar you could also given it a path that the user has access to - the /openstack path is a little OSA specific, and really just a legacy thing15:05
odyssey4mecloudnull "Access denied for user 'cinder'@'cinder.openstack.local' (using password: YES)") (Background on this error at: http://sqlalche.me/e/e3q8)"15:05
ygk_12345odyssey4me: the user 'stack_domain_admin' is in heat domain15:06
odyssey4mecloudnull it looks like those errors are until the migrations run, then it has access and starts15:06
ygk_12345odyssey4me: this is how the error looks15:06
ygk_12345odyssey4me: {"attempts": 5, "c hanged": false, "item": {"project": "admin", "role": "admin", "user": "stack_domain_admin"}, "msg": "User stack_domain_admin is not valid"}15:06
openstackgerritMichael Vollman proposed openstack/openstack-ansible-os_manila master: Basic working os_manila role  https://review.openstack.org/61193015:06
odyssey4meygk_12345 I'm not really in a position to trace it all in detail right now - if you inspect the tasks and the variables fed to it, you should be able to see whether each task is doing the right thing or whether there's an issue elsewhere.15:07
odyssey4meygk_12345 right, so if the user exists and the role add task is failing - what does that tell you?15:07
cloudnullhum... ok ima try and reproduce the tempest results and see whats what. but first multiple hours of meetings :)15:07
cloudnullbbl15:08
odyssey4meygk_12345 try doing it via the CLI to see if it works with the same parameters - it might be a bug in ansible15:08
mnaserhm15:12
mnaserlooks like xenial fails too15:13
mnaserso i wonder if this feature is something that needs a newer kernel?15:13
mnaseror a newer release of lxc15:13
mnaserit looks like rhel dropped support for btrfs back in 7.415:16
jrosseri wonder what backends folks are actually using on centos15:18
ygk_12345can someone help me with this error please15:21
ygk_12345{"attempts": 5, "c hanged": false, "item": {"project": "admin", "role": "admin", "user": "stack_domain_admin"}, "msg": "User stack_domain_admin is not valid"}15:21
ygk_12345this is heappening when running the heat playbook15:22
*** markvoelker has joined #openstack-ansible15:23
mnaserhttp://logs.openstack.org/78/613078/19/check/openstack-ansible-lxc-overlayfs-centos-7/dc8f90c/logs/host/lxc/lxc-container1.log.txt.gz15:25
mnaserwhat the15:25
mnaserjrosser: i wonder how many people actually even change the backend beyond 'dir' :\15:25
mnaserit copied things into `/usr/lib64/lxc/rootfs/` for some reason15:26
mnaserOverlayfs: Mounted /var/lib/lxc/centos-7-amd64/rootfs onto /usr/lib64/lxc/rootfs with options upperdir=/var/lib/lxc/container1/delta0,lowerdir=/var/lib/lxc/centos-7-amd64/rootfs,workdir=/var/lib/lxc/container1/olwork.15:26
*** markvoelker has quit IRC15:26
evrardjpmnaser:  if you have question about how people deploy with OSA, maybe we can now leverage the openstack survey. Though I wouldn't use it for low level questions ... But I think we are not using it enough.15:27
*** markvoelker has joined #openstack-ansible15:27
*** markvoelker has quit IRC15:27
mnaserin my personal experience, we've seen people do all sorts of things with OSA but.. rarely use a different backend15:27
mnaserthough we have a few that experiment15:27
evrardjpMy experience is about the same15:28
*** dcdamien has quit IRC15:28
mnasertaken up an hour and a half of my time trying to solve something that i won't ever use and i (have a feeling) not a lot of people use :(15:28
*** cshen has joined #openstack-ansible15:30
mnaserhttps://github.com/lxc/lxc/pull/265615:30
mnaseri think this is it15:30
mnaserhttps://github.com/lxc/lxc/issues/265515:30
*** ygk_12345 has quit IRC15:30
evrardjpmnaser: worth asking cloudnull :p He was the one toying with btrfs and lxc, IIRC, because it's close to nspawn + btrfs15:33
mnaserit looks like any cow stuff is not working on centos-715:33
mnaserprobably because of an lxc-copy bug15:33
mnaseri dont know how much time cloudnull has to look into it but i'm all knowledged-out15:33
*** mathlin has quit IRC15:34
*** cshen has quit IRC15:35
odyssey4meIf we think that it's better to reduce the support matrix, because supporting everything isn't all that feasible, then we should push up a patch to hard stop if any bad combinations are used, and we should remove the tests15:35
cloudnullis it just btrfs on centos? if so maybe we just take that one out ?15:36
* cloudnull haven't been following a long 15:36
odyssey4meit's a little odd that btrfs isn't working, but machinectl is?15:36
mnasercloudnull: its btrfs and overlayfs15:37
mnaserat least overlayfs i've identified one weird thing15:37
cloudnullmachinectl doesn't use the lxc mechanisms to create a copy15:37
mnaser"/var/lib/lxc/centos-7-amd64/rootfs onto /usr/lib64/lxc/rootfs"15:37
mnaserwhich is that it tries to copy to some weird path15:37
odyssey4mecloudnull ah, ok15:37
cloudnullwe've had lots of random issues with overlayfs over the years.15:37
cloudnullcould be some new issues is cropping up ?15:37
odyssey4meperhaps overlayfs should just be ditched as a back-end15:38
cloudnullmaybe its best to make those non-voting/remove them on cent?15:38
jrosserits wierd15:38
odyssey4methen btrfs just made unsupported on centos15:38
jrosseroverlayfs: lxc_network - network.c:lxc_network_move_created_netdev_priv:2417 - Moved network device "veth6GW2PC"/"(null)" to network namespace of 2178815:38
jrossermachinectl: lxc_network - network.c:lxc_network_move_created_netdev_priv:2417 - Moved network device "veth3M0LWR"/"eth1" to network namespace of 35315:39
cloudnull^ odyssey4me we've seen that one before, no ?15:39
cloudnulloverlayfs and vethpair issues?15:39
odyssey4meit rings a bell, but for the life of me I can't recall from what15:39
jrosserbtrfs: lxc_network - network.c:lxc_network_move_created_netdev_priv:2417 - Moved network device "vethW0I3U4"/"(null)" to network namespace of 2210615:39
jrossersame ^15:39
odyssey4mewas this perhaps something we saw in nspawn with the namespace pid conflict?15:40
odyssey4mesomething something old systemd nonsense15:40
jrosser:)15:40
*** cshen has joined #openstack-ansible15:40
odyssey4meif it is the case, then it will be inconsistent and it will happen for any backend15:41
cloudnullOh that could be ^15:42
odyssey4mewe see that on xenial, but on bionic it's fine15:43
mnaserhonestly i'd really love to try and fix it and keep feature parity15:43
cloudnullif its related to the issues we saw in glibc then that's a bummer.15:43
mnaserbut given that btrfs is removed from rhel7.4 and dropped in rhel815:43
chandankumarodyssey4me: cloudnull https://review.openstack.org/629127 please have a look on this when free thanks :-)15:43
mnaserthat one can safely be removed15:43
jrosserthe top 3 here are all the same i think https://review.openstack.org/#/q/project:openstack/openstack-ansible-lxc_hosts+status:open15:43
mnaseri think overlayfs is supposed to stick around15:43
cloudnullmnaser ++15:43
mnaserbut at least the issue in overlayfs is obvious15:44
mnaserit's copying to the wrong folder15:44
odyssey4meI'm stuck in meetings for a while - bbl.15:44
cloudnullRHEL is removing BTRFS entirely in RHEL8. while we still use cent7 maybe its time to sunset that backend on cent15:44
mnasercloudnull: and it was dropped support in 7.4 too15:45
odyssey4mewhere does the btrfs removal put us for machinectl/nspawn?15:45
cloudnullin an odd place.15:45
mnaser"Btrfs is available as a Technology Preview feature in Red Hat Enterprise Linux 7 but has been deprecated since the Red Hat Enterprise Linux 7.4 release. It will be removed in a future major release of Red Hat Enterprise Linux."15:45
*** cshen has quit IRC15:45
mnaserhonestly i've been slowly more and more inching towards metal deployments15:45
openstackgerritArx Cruz proposed openstack/openstack-ansible-os_tempest master: Better tempest blacklist management  https://review.openstack.org/62160515:46
mnaserand unless i can start getting a bit more help in centos, that might be the only scenario i can help keep supported :\15:46
evrardjpmnaser: :)15:46
evrardjpI might now have another padawan! :P15:46
evrardjpmaybe will have*15:46
mnaserwe discussed at the ptg making containers opt-in15:47
evrardjpsimplify things, let people come with their own method of machine containers/virtual machines15:47
openstackgerritArx Cruz proposed openstack/openstack-ansible-os_tempest master: Better tempest blacklist management  https://review.openstack.org/62160515:47
mnaserand having metal be default15:47
cloudnullodyssey4me - with all of the things rhel is removing for rhel8 we're honestly going to have our hands full with it as a supported OS.15:48
mnasercloudnull: around containers i assume/15:48
mnaserbut for the metal deployments, we're probably okay?15:48
cloudnullnetworking, supportined backens, etc.15:48
cloudnullfile systems...15:48
evrardjpcloudnull: systemd-network won't be supported?15:49
odyssey4mecloudnull mnaser then perhaps we should just bite the bullet this cycle and have centos remove all container techs and be metal only15:49
cloudnullI hope everyone like network manager :)15:49
cloudnullevrardjp presently, nope15:49
odyssey4meoh holy hell15:49
cloudnullonly network manager, NMCLI for the win...15:49
mnaserwe don't touch networking in OSA unless we're doing containers (and then we touch the networking inside contaienrs afaik?)15:49
mnaserfilesystems is only an issue for containers too15:49
evrardjpwell if we move to consider metal first for centos, it simplify things, as we say that people have to configure their own networking first.15:49
evrardjpmnaser: yup exactly15:50
odyssey4mefair enough15:50
odyssey4meall storage and networking is in the deployer's hands15:50
mnaseri guess the only place we really touch networking is in os_neutron but thats only ovs and/or linuxbridge15:50
odyssey4mewe just put openstack down15:50
mnaserand i dont think they're removing that bahaha15:50
evrardjpmnaser: that's already conditional,so we can have different "backends" for wiring up the networking15:50
evrardjpit only requires good ansible modules for it15:51
cloudnullits still early but it seems rhel is wanting to support geneveve as their supported network platform when it comes to openstack. -cc jamesdenton15:51
evrardjpmnaser: removing linux bridge would be a gutsy approach :)15:51
cloudnullso i suspect there will be issues there too15:51
jamesdentongeneve w/ OVN15:51
cloudnull^15:51
chandankumararxcruz: https://review.openstack.org/#/c/621605/ since all projects are moving to storyboard can we add entry about storyboard also?15:51
*** strobelight has joined #openstack-ansible15:52
mnaseri mean15:52
mnasergeneve probably needs ovs to operate15:52
mnaserand i doubt they'd rip out linuxbridge15:52
mnaserso i think we're still...ok15:52
jamesdentonyeah, OVN is based on OVS, GENEVE just replaces VXLAN15:53
mnaserodyssey4me: i know you mentioned earlier you're in meetings so feel free to answer this later15:54
cloudnullas RHEL 8 gets out of beta it'll be interesting to see what we have to do to keep is going.15:54
mnaserbut i think we can combine efforts to bring integrated jobs down to roles and move to metal at the same time for centos15:54
cloudnullok, back to being gone. see you all soon.15:54
mnaserthat way we don't have to rewrite all of the functional jobs that leveraged containers15:54
*** shardy has quit IRC15:54
cloudnullhttps://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-beta/html/8.0_beta_release_notes/removed_functionality -- for your reading enjoyment :)15:56
*** mathlin has joined #openstack-ansible15:57
mnaserthats a fun read15:59
mnasercloudnull, DimGR, d34dh0r53, hughsaunders, b3rnard0, palendae, odyssey4me, serverascode, rromans, erikmwilson, mancdaz, _shaps_, BjoernT, claco, echiu, dstanek, jwagner, ayoung, prometheanfire, evrardjp, arbrandes, scarlisle, luckyinva, ntt, javeriak, spotz, vdo, jmccrory, alextricity25, jasondotstar, admin0, michaelgugino, ametts, bgmccollum, darrenc, JRobinson__, colinmcnamara, thorst, adreznec, eil397,15:59
mnaserqwang,nishpatwa_, cathrichardson, drifterza, hwoarang, cshen, ullbeking, mnaser, nicolasbock, jrosser, cjloader, antonym, dcdamien15:59
mnaser1 minute warning :)15:59
spotzo/15:59
mnaser#startmeeting openstack_ansible_meeting16:00
openstackMeeting started Tue Jan  8 16:00:01 2019 UTC and is due to finish in 60 minutes.  The chair is mnaser. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: openstack_ansible_meeting)"16:00
*** hamerins has joined #openstack-ansible16:00
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:00
mnaser#topic rollcall16:00
mnasero/16:00
*** openstack changes topic to "rollcall (Meeting topic: openstack_ansible_meeting)"16:00
jamesdentono/16:00
odyssey4meo/16:00
evrardjpo/16:00
spotzo/16:00
mattto/16:00
chandankumar\o/16:01
mnaseranyone has any last week highlights to bring up? i know we've missed 2 weeks because of holidays :)16:01
cloudnull+/- /o16:01
odyssey4meholidays were a highlight :)16:01
guilhermespo/16:01
*** udesale has quit IRC16:02
mnaserthat's the best highlgiht16:03
mnaser#topic Bug triage16:03
*** openstack changes topic to "Bug triage (Meeting topic: openstack_ansible_meeting)"16:03
mnasercatch up time16:03
mnaser#link https://bugs.launchpad.net/openstack-ansible/+bug/181058416:03
openstackLaunchpad bug 1810584 in openstack-ansible "openstack-ansible setup-hosts.yml fails in task: lxc_hosts Ensure image has been pre-staged" [Undecided,New]16:03
mnaseri can curl that file16:04
evrardjp3 ppl saying it's a problem , I suppose it's real16:04
mnaser"Running the same command a second time, the command succeeds."16:04
evrardjpweirdly it works in gates in one go16:04
mnaserin my experience, cdimage.ubuntu.com isn't the most reliable16:04
mnaseryeah i've never seen gate failures around that16:05
evrardjpmaybe we are using an infra mirror?16:05
mnaser2 people on the same time too16:05
mnaseri don't think we are for this16:05
jrosserthese are multinode though arent they?16:05
evrardjpjrosser: they seem to16:05
evrardjpbut IIRC odyssey4me told me RAX has multinode daily periodics now, which would have shown up the issue16:06
mnaser_lxc_hosts_container_image_url: "http://cdimage.ubuntu.com/ubuntu-base/releases/18.04/release/ubuntu-base-18.04.1-base-{{ lxc_cache_map.arch }}.tar.gz"16:06
odyssey4meyep, we don't see failures there for MNAIO tests as far as I know16:06
evrardjpwe maybe need to document this as a known issue in case of people not overriding the value16:07
mnaserlxc_hosts_container_image_url: "{{ _lxc_hosts_container_image_url }}"16:07
evrardjpodyssey4me: I suppose you're using RAX mirrors for that16:07
odyssey4meor perhaps we should increase the timeout16:07
mnaserodyssey4me: the thing is if you look at the logs16:07
mnaser0B downloaded16:07
odyssey4menope, we're using the upstream sources every time16:07
mnaserso.. it's just not downloading ever16:07
odyssey4mewell, that's nice :/16:07
evrardjpoh god16:07
mnaser64MiB/s later on the same download on the rerun16:07
evrardjplook at the nice can of worms?16:07
mnaserthe 2nd person reported on the same day16:08
*** szaher has quit IRC16:08
odyssey4mewell, we can remove the async and add retries I guess - or figure out another way of having async + retries16:08
odyssey4meor we can ditch containers :p16:08
mnaser:D16:08
mnaserfor the sakes of this bug, i hate to say it but i guess its confirmed because we don't have a retry mechanism16:09
mnasereven though it's not really our fault, but we don't have recovery from this simple failure16:09
*** szaher has joined #openstack-ansible16:09
mnaserconfirmed/low ?16:10
mnaserbecause it's really handling a third party failure16:10
mnaseri guess ill go for that.16:10
evrardjpyeah I'm fine with that triage16:10
mnaser#link https://bugs.launchpad.net/openstack-ansible/+bug/181053816:11
openstackLaunchpad bug 1810538 in openstack-ansible "keepalived.service is not enabled" [Undecided,New]16:11
evrardjpbut we need to explain it's not really our fault in the bug :p16:11
mnaseruh16:11
mnaseri'll add a note16:11
evrardjpthat's weird. It should not pass my functional testing if it's not started16:12
prometheanfireo/16:12
evrardjpoh wait16:12
mnaserevrardjp: enabled not started16:12
evrardjpafter reboot16:12
evrardjpyeah I misread16:12
evrardjpI don't test that16:12
evrardjpbut it's not really my fault if the module is not doing appropriately16:12
evrardjp:p16:12
mnaserhttps://github.com/evrardjp/ansible-keepalived/blob/master/tasks/main.yml#L197-L20016:13
evrardjpcurious16:14
mnaseri somehow doubt16:14
mnaserthat `enabled: yes` is broken16:14
mnaserand i have a feeling something else is breaking it16:14
*** iw_zah has quit IRC16:14
mnaseranyways, i cant reproduce because i've always seen keepalive go back up16:14
evrardjpI can't remember if keepalived can be socket activated16:14
mnaserand i can see it up here `systemctl is-enabled keepalived.service` on a c7 deploy16:15
evrardjpin that case a wrong net config would never activate the socket16:15
evrardjpbut i doubt it's that16:15
mnaserit would still be enabled but stopped16:15
evrardjpwe need a systemd unit log16:15
evrardjpI think there is something else going on16:16
mnaserasked for more info16:16
evrardjpthe enablement of the service resulting in a failure should be in the journal16:16
evrardjpthx16:16
mnaserincomplete16:16
mnasermedium16:16
mnaserfor now..16:16
mnaser#link https://bugs.launchpad.net/openstack-ansible/+bug/181053716:17
openstackLaunchpad bug 1810537 in openstack-ansible "volume creation fails after successful installation" [Undecided,New]16:17
mnaserhey isn't that what you were working on cloudnull ?16:17
mnaserthe fix is icnldued16:17
mnasercc odyssey4me ^16:17
mnaserhttps://review.openstack.org/#/c/628197/16:17
cloudnullmnaser that maybe the issue I was seeing.16:18
mnasercloudnull: can i assign to you? maybe https://review.openstack.org/#/c/628197/ is the fix16:18
mnaserit certainly has to do with it16:18
openstackgerritMohammed Naser proposed openstack/openstack-ansible-os_cinder master: Adds resource_filters.json distribution  https://review.openstack.org/62819716:19
mnaseradded closes-bug16:19
cloudnullsure16:19
mnaserevrardjp: i just did it, lets +2?16:19
evrardjphaha16:19
cloudnullthis was the error from the cinder-api log I was seeing16:19
cloudnullhttps://pasted.tech/pastes/61c4496978d40841ddaf22d0e3ca49936f269a3a.raw16:19
mnaserconsidering noonedeadpunk had it fixed for a while now and we haven't done much :)16:19
cloudnullwhen running tempest.api.volume.test_volumes_list.VolumesListTestJSON16:19
mnasercloudnull: while its not the same traceback, it complains about `common.get_enabled_resource_filters`16:19
cloudnull++16:20
mnaserwhich seems pretty darn close so..16:20
cloudnullso it totally could be the same issue, will tinker in a bit16:20
mnaserkeep https://review.openstack.org/#/c/628197/2 in mind and ill go onto the next16:20
mnaser#link https://bugs.launchpad.net/openstack-ansible/+bug/181053316:20
*** pcaruana has quit IRC16:20
openstackLaunchpad bug 1810533 in openstack-ansible "openstsack-ansible behind a proxy fails when calling apt-key" [Undecided,New]16:20
noonedeadpunkOh, never knew, that there's a bug for this:)16:20
mnasernoonedeadpunk: no problem =)16:20
mnaseroh look a proxy issue16:20
* mnaser looks at jrosser 16:20
evrardjp:)16:21
jrosserdidnt we change these to be in the repo now?16:21
mnaserim going to guess this might be happening in cache prep stage16:21
mnaserunfortunately it doesn't mention which role16:21
odyssey4meMOAR WORKFLOW16:21
evrardjpjrosser: that's true we are carrying things16:21
evrardjpodyssey4me: haha I laughed too16:22
mnaserfine ill join in too16:22
evrardjpBUFFEROVERWORKFLOW16:22
mnaseri dont see any 'apt-key' references using codesearch.openstack.org16:22
mnaseri guess i can ask where that change was done?16:22
odyssey4meoh yeah, I'll take that - I've done all the patches except the rocky patch for rabbitmq_server16:22
odyssey4memaster is all don16:22
odyssey4me*done16:22
evrardjpodyssey4me: thanks16:23
spotzhehe16:23
mnaserokay cool, ill assign then odyssey4me :)16:23
mnaser#link https://bugs.launchpad.net/openstack-ansible/+bug/181031916:23
openstackLaunchpad bug 1810319 in openstack-ansible "Can't set gateway for provider network" [Undecided,New]16:23
odyssey4mehttps://review.openstack.org/#/q/(topic:vendor-gpg-keys+OR+topic:vendor-gpg-keys-stable/rocky)+(status:open+OR+status:merged)16:23
mnaserlooks like that's dcdamien16:24
jrosseri wasnt sure about this one - "specific default gateway" sounds a bit bogus?16:24
jamesdentoni seem to recall looking at the playbooks could not find any reference to 'gateway' other than docs16:24
mnasersounds like the user wants a static route16:24
jrosser^ that, yes16:24
mnaserwas it lxc_container_create that made network configs?16:25
noonedeadpunkI don't think, that it ever created default routes. But several times I've faced with issue of missing nat rules on controller nodes after setup-hosts.yml16:26
noonedeadpunkbut it's probably not related16:26
mnaseri dunno16:27
evrardjplong ago we could inject routes to the process. I remember, I wrote it.16:27
mnaseri mean we have it listed there16:27
jrossertheres an example in the tests https://github.com/openstack/openstack-ansible-lxc_container_create/blob/master/tests/group_vars/all_containers.yml#L17-L2616:27
mnaserfor static routes yeah16:28
mnasernot default16:28
jamesdentonstatic could easily be 0.0.0.0, no?16:28
odyssey4memissing rules on the host is fixed by lxc-system-manage16:28
mnaserwell it would conflict with the lxc one16:28
jamesdentonahh16:28
mnaserthe 10.8.0.0 or whatever16:28
evrardjpjamesdenton: having two 0.0.0.0/0 seems to be problematic16:28
evrardjpfor some ppl :p16:28
evrardjpnot sure what we are talking about anymore16:29
odyssey4meunicorns!16:29
mnaseri added a comment16:29
mnaserand i'll set to invalid i guess16:29
mnaserlinking to jrosser example16:29
evrardjpwe are talking about two different things16:29
evrardjpIMO16:29
mnaseruser wants to define a gateway => not possible16:30
mnaserwe're pretty sure user just wants a static route pointing ?? somewhere ??16:30
mnaserthe default route is always 10.8.0.1 or whatever the lxc host ends up with16:30
mnaserwe use that for natting and all the other fun stuff we need to do to make sure things work16:30
mnaseralso16:30
mnaserdon't we run haproxy inside metal?16:31
mnaseri'm pretty sure we do.. right? keepalived and haproxy16:31
*** mathlin has quit IRC16:31
noonedeadpunkYep16:31
evrardjphttps://github.com/openstack/openstack-ansible-lxc_hosts/blob/a8b96e2e37ffea4b7c3e055b1310b10bb95a7b2a/defaults/main.yml#L10616:31
evrardjplet me backtrack this into the inventory16:31
odyssey4mehaproxy/keepalived are installed on the host for an AIO, yes16:32
mnaserso i guess this seems to be a specific scenario that the user came up with16:32
evrardjpit seems it's not in the inventory anymore.16:32
mnaserrunning haproxy in containers but then wanting the container to not be wired to the internet lxc network but wired to the public network in this case16:33
jrosseri think this is running containerised haproxy, needing eth0 to be natted to install (guess) and the external interface on this new eth1416:33
evrardjpone could run haproxy and keepalived in containers, and use whatever network interface he wants16:33
evrardjpI think it's a valid issue16:34
mnasernot really, because our architecture has a default route of the host16:35
mnaserwhich means that traffic goes in eth1416:35
evrardjpwe probably removed that feature at some point, kept the feature in lxc_hosts, and probably forgot to edit the default template of the inventory.16:35
mnaserbut on the way out, it hits the default route16:35
jrosserimho this is addressed with a static route as i linked16:35
mnaseri'l leave this and lets wait for the user to comment on next week16:36
evrardjpmnaser: not sure to understand16:36
mnaserevrardjp: just because traffic enters from one interface, does not mean it will exit from the same one16:36
evrardjpIMO you could have your own NIC that's not natted in the container, and that would require a default route for reason x16:36
mnaserif your default route is the physical host that runs the container16:36
evrardjpwell no I meant, if you don't run nat at all16:37
evrardjpyou could have just bridges on the host, and ignore lxc nat.16:37
mnaseryou could, but that's a whole another use case16:37
mnaseranyways, i think we've taken abit of time on this16:37
mnaseri dont wanna burn everyone out with all this stuff for now16:37
jrosserevrardjp: yes this is exactly what i do in the new http proxy test, no default route https://review.openstack.org/#/c/625523/16:38
evrardjphaha true :)16:38
mnaseri feel like bug triage drains everyone out and we lose people :(16:38
mnaserso enough of that for today16:38
*** gyee has joined #openstack-ansible16:38
openstackgerritKevin Carter (cloudnull) proposed openstack/openstack-ansible-os_cinder master: Cleanup files and templates using smart sources  https://review.openstack.org/58895316:38
mnaserrhel 8 was an interesting subject cloudnull brought up and odyssey4me evrardjp  was discussing earlier16:38
mnasera lot of stuff has been removed which makes containers even harder16:38
* mnaser is using more and more non-containerized centos deploys16:39
evrardjpmnaser: I checked the link you gave above16:39
guilhermespwith this, cinder as backend for glance is going to be supported by us but just when glance is METAL16:39
evrardjp(might worth giving it here)16:39
mnaseroh yeah cloudnull posted that16:39
mnasercloudnull> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-beta/html/8.0_beta_release_notes/removed_functionality -- for your reading enjoyment :)16:39
evrardjpmnaser: I am scared of the LVM Python bindings have been removed16:39
mnaseryeah guilhermesp also caught a really annoying issue about iscsiadm and containers16:40
mnaserthings like running glance in containers with cinder backend doesn't work for example16:40
odyssey4meyep16:40
odyssey4menothing using iscsi will work in a container16:40
mnaserlearned that the hard way :)16:40
evrardjp:)16:40
guilhermespyep hahaha16:40
prometheanfirethat's been known for a while iirc (we learned the hard way too)16:40
guilhermespI suffered a bit but that's ok16:40
*** kopecmartin is now known as kopecmartin|off16:40
mnaserso given all that stuff, i'd like to propose moving centos off containers into metal16:41
mnaseras a path to eventually maybe make containers an opt-in16:41
mnaserbut making centos more of a canary to see what happens in there16:41
prometheanfirea second cent gate for it?16:41
evrardjpmnaser: that sounds fair. I like the approach.16:41
mnaserprometheanfire: we already gate metal and lxc16:41
mnaserand they're both somewhat reliable, i guess.16:42
evrardjpmnaser: do we have fine tuned the default listen interfaces of all the services?16:42
prometheanfirejust curious what it'd do to coverage is all16:42
mnaserevrardjp: i'll have to pick up that work and maybe JUST maybe multinode metal jobs16:42
evrardjpif there is no 0.0.0.0 anymore, we can pretty much simplify more things16:42
jrosserevrardjp: you need this https://github.com/openstack/openstack-ansible/blob/master/playbooks/listening-port-report.yml16:43
mnaserso i was thinking we can combine some of the efforts that odyssey4me has been doing in order to run integrated for roles16:43
mnaserso that we don't have to rewrite most functional tests to throw them away later16:43
evrardjpmnaser: for now I'd say the only part is haproxy because he listens to the same port as some services, so if you put multinode, just put haproxy on a single node, then all the rest into an infra node, then a compute node16:43
evrardjpa 3 node perfection :)16:43
mnaserevrardjp: yea but ideally i'd like haproxy to be colocatable16:43
mnasermost deployments don't have a dedicated haproxy node16:43
mnaserin my experience at least16:44
mnaserpeople want to reuse their controllers16:44
evrardjpthat's sad, because it helps :p16:44
mnaserrunning everything on it's own machine is nice too because that helps, but then we can do vms to make it easier cause they don't need resources .. but machine containers work easier too cause they're lighter16:44
mnaseroh.16:44
mnaserwait.16:44
mnaser:)16:44
evrardjp:)16:45
odyssey4memaybe we should just use kata containers instead :p16:45
mnaserhey16:45
evrardjpk8s?16:45
mnaseri'm not gonna lie16:45
mnaseri've thought about using docker containers to run some stuff16:45
evrardjpmnaser: it makes sense16:46
mnaserlike imagine how nice it'd be just to pull down memcache, the same way, across all systems16:46
evrardjpbut then ppl will say it's memcache with centos, oh no it's memcache on suse I want, oh no it's memcache on ubuntu I want, OH NO it's not Alpine!16:46
jrosserwe should learn carefully from the tripleo experience there - seems to have turned messy16:47
evrardjpI think run everything on metal is simple16:47
evrardjpif ppl want their own things, they can16:47
prometheanfirenot going to make all people happy all the time16:48
evrardjpfor example, they set their ubuntu nodes with lxd networks, and then install on lxd nodes16:48
evrardjpprometheanfire: that's true16:48
evrardjpprometheanfire: but we don't have to16:48
*** fatdragon has joined #openstack-ansible16:48
mnaseri've used every single deployment tool so far by now lol16:48
prometheanfireevrardjp: just making sure we were not trying to, that path leads to destruction :P16:48
evrardjpif we deliver the minimum amount of code it's easier to maintain in the long run, and people will be happy, even if we lack features16:48
noonedeadpunkbut I'd prefer not to completel reject containers, in favor of metal16:49
mnasernoonedeadpunk: nope, we don't want to do that at all16:49
evrardjpmnaser: fuel too?16:49
mnaserevrardjp: fuel, mos, tripleo, kolla-{ansible,k8s}, puppet openstack16:49
evrardjpnoonedeadpunk: it's not about rejecting it, because they make sense... It's about giving them as opt-in16:49
mnasereven the tripleo before redhat revived it :)16:49
evrardjpmnaser: wow, the HP thing?16:49
mnaseryep16:49
mnasernoonedeadpunk: when you say not rejecting containers, you mean machine containers or app containers16:50
evrardjplike odyssey4me would have said, at that time dinosaurs were roaming on earth16:50
noonedeadpunkmnaser I mean machine containers16:50
cloudnulljrosser ++ totally agree.16:50
mnaseryeah, we don't aim on dropping it16:50
mnaserwe have users that are happy with it16:51
noonedeadpunkYeah, then bare metal is really nice. But kata looks also pretty interesting. But I don't like docker to be honest..16:51
jrosseri'm also here primarily becasue of the attractive architecture / approach16:51
mnaserkata is nothing but a docker runner16:51
mnaserit just runs docker containers in vms, thats' all16:51
odyssey4meit makes sense to me to have lxc only running on ubuntu, which formally supports it - and nspawn/lxc opt-in for those who want it16:51
mnaseryeah, the lxc stuff is pretty hacked up too16:51
mnaserbecause we depend on some other external repo16:51
mnaserand the more we stray away from upstream tooling the harder it gets16:52
evrardjpthe urgency is remove it for centos16:52
evrardjpwhen is 8 official?16:52
mnaserhaving discussed all of this, is anyone not too opposed to removing containers from centos to be able to support rhel 8 and make it a bit more maintainable, i guess16:52
spotzCan we blame mhayden for something here?:)16:52
mhaydenalways16:53
cloudnullI'd really love folks to give the nspawn bits a spin. they need folks to use it and report where its all broken for them and their environments.16:53
spotzheheh, we miss you:)16:53
*** shardy has joined #openstack-ansible16:53
prometheanfiremhayden: we should do tacos this week16:53
mnasercloudnull: i really tried to get nspawn working at gate, 17 patch sets later and i was still struggling16:53
FrankZhangwild Major found16:54
prometheanfirecloudnull: I need to bug you about the state of that16:54
mnaserand unfortunately we haven't been getting traction on it16:54
evrardjpFrankZhang:  :)16:54
mnasermy knowledge in it is limited16:54
odyssey4meto my mind, given that we have a very limited centos/suse support base and people supporting/developing, perhaps we should consider scaling back their support to only without containers16:54
evrardjpodyssey4me: I would be fine with that.16:54
jrossermnaser: theres an important distinction between "we removed this stuff becasue rhel8 broke the world" vs. "we removed this stuff becasue it's the general direction of travel of OSA"16:54
*** mathlin has joined #openstack-ansible16:54
odyssey4mejrosser yep, fair point16:54
jrosseri think we have enough confusion already between containers/metal, with very few actually using metal, and we carry the overhead16:55
mnaserjrosser: i agree.  i don't want to take away from major users who's benefit is containers and the architecture we provide16:55
evrardjpodyssey4me: to be honest, lxc is supposed to be phased out in favor of new lxd/lxc bindings, right?16:55
cloudnullmnaser maybe we could spend some time on a mnaio or some env to get nspawn up and running and answer questions.16:55
* cloudnull has access to hardware to do that 16:55
odyssey4meif we move to containers being opt-in, then we should change the current dynamic inventory to a simpler inventory plugin which can be easily enabled/disabled16:55
mnaserwell, i'd be just happy with passing jobs to start with :(16:55
spotzI know we don't want to wait that long to make a decision but this could be a great Forum or PTG discussioon16:56
evrardjpodyssey4me: indeed16:56
prometheanfireodyssey4me: would we still need the current one to support people if they do opt in to containers?16:56
evrardjpspotz: I tried that though, it didn't bring many supporters16:56
mnaseralso i think making our default deploy tooling simpler but leaving the complex one available is better16:56
evrardjpthat's why I never worked on the removal :p16:56
mnasermost users don't want to throw a /24 at an openstack control plane deployment, they want 3 ips for each of their controllers16:56
evrardjpmnaser: couldn't it be on the side, in ops repo?16:56
spotzevrardjp: Weird, cause the in[ut would help make a design for direction:(16:56
mnaser*if* someone wants to do that, they can do it (and they probably have the knowledge to do it)16:57
evrardjpspotz: oh no I meant the lack of willingness to change was an input in itself16:57
prometheanfiremnaser: swich the control plane to v6, never run out of addresses :P16:57
cloudnull^ :D16:57
mnaserbaha16:57
prometheanfirethen just use haproxy for 62416:57
mnaserlike or maybe as an idea16:57
prometheanfire:P16:57
mnaserwe can decouple the dynamic inventory away out16:57
odyssey4mewe've run around this circle many times, but until it matters enough to someone it's not going to happen16:57
prometheanfire^16:58
mnaserodyssey4me: the ipv6 circle or the metal circle16:58
odyssey4mefor now it's easy to make centos metal only, and perhaps also work on some plays to transition any container deployments to metal when doing the upgrade16:58
spotzevrardjp: hehe, then they need to provide help!:)16:58
odyssey4meperhaps for suse we do the same given that we have a low support base and user base16:58
mnaserif folks are ok with that, i will do the work16:58
odyssey4mewe leave ubuntu as-is until it matter enough to anyone to change up how that's all done16:59
cloudnull+116:59
evrardjplgtm16:59
*** macza has joined #openstack-ansible16:59
spotz+116:59
mnaserawesome16:59
evrardjpand thanks mnaser for the work16:59
evrardjpit shouldn't be that hard if we keep lxc around16:59
mnaserthank you for your patience with my shenanigans dealing with dinosaurs16:59
mnaser:)16:59
evrardjpfor ubuntu16:59
cloudnullwould be sad to see SUSE support / test matrix reduced, but i understand16:59
mnaseranyone else have anything in mind?16:59
odyssey4memnaser I think we can pretty simply just remove centos/suse from the openstack-ansible-tests templates, then add cross-repo integrated build tests to all roles with a metal build17:00
evrardjpas we won't change inventory, methods of deployments, but still simplify code for centos17:00
mnaserodyssey4me: that was my goal pretty much :)17:00
mnaserand then figure out upgrades17:00
evrardjpwell17:00
mnaseranyways, we're kinda at time17:00
prometheanfiremnaser: I have an item to bring up for notice (after this) :P17:00
evrardjpit's not enough for clustering roles17:00
mnaserwhats up prometheanfire ?17:00
prometheanfirethe barbican role seems broken17:00
mnaserevrardjp: i had an idea for that too :)17:00
mnaserorly?17:01
evrardjpmnaser: multinode?17:01
mnaserevrardjp: yep17:01
evrardjpmnaser: good17:01
mnaseroh thats a lot of red17:01
prometheanfireat least in master17:01
mnaserfatal: [infra1]: FAILED! => {"changed": false, "cmd": "set -e\n if [ -d /opt/tempest-testing/bin ];\n then\n . /opt/tempest-testing/bin/activate\n fi\n tempest run  --whitelist-file /root/workspace/etc/tempest_whitelist.txt", "delta": "0:00:02.464257", "end": "2019-01-03 18:26:46.166077", "msg": "non-zero return code", "rc": 1, "start": "2019-01-03 18:26:43.701820", "stderr": "", "stderr_lines": [], "stdout": "The17:01
mnaserspecified regex doesn't match with anything", "stdout_lines": ["The specified regex doesn't match with anything"]}17:01
jrosserthat is due to changes in tempest17:01
mnasermayb arxcruz or chandankumar can help us with that17:01
jrosserand there was a patch this morning merged as the first part of addressing that17:01
odyssey4meyep, I've been doing some work on that front too17:01
mnaserokay cool, so maybe that is a good canary patch to see if it works or not :)17:02
prometheanfiremnaser: k, thanks17:02
odyssey4mehttps://review.openstack.org/628979 has been a bit of a work in progress17:02
chandankumarmnaser: can you point me the log url17:02
mnaserchandankumar: i looked at https://review.openstack.org/#/c/625634/17:02
evrardjpI also have a few things to add for the record of the meeting:17:02
jrosserthis https://github.com/openstack/openstack-ansible-os_tempest/commit/25b5533c30e328c80d29348dff0cfc0f2ac5e88f17:02
jrossereven if that doesnt fix barbican/designate it's the first step17:03
evrardjp1) If there is a problem with SUSE packaging, please query in #openstack-rpm-packaging17:03
odyssey4methe previous issue was that distro installs didn't install the plugins to do the tests - now that's happening, nothing's setting the var that enables the plugin to be installed17:03
chandankumarjrosser: does barbican/designate failure does not got fixed?17:03
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-os_tempest master: Use the inventory to enable/disable services by default  https://review.openstack.org/62897917:04
mnaserevrardjp: anything else for the record of the meeting? or we can wrap up and keep discussing :)17:04
evrardjp2) I am bringing the idea of gating OBS Staging->OBS repo using OSA for more stability17:04
mnaseryay17:05
odyssey4methat should solve it17:05
evrardjpthanks mnaser17:05
evrardjpand everyone!17:05
odyssey4meawesome, thanks evrardjp17:05
odyssey4meeven just trying to install openstack using anythign would e a good start17:05
mnaser++17:06
mnaserokay, we're over but i think we covered most things17:06
mnaseri shall end :)17:06
mnaserthank you everyone!!17:06
mnaser#endmeeting17:06
*** openstack changes topic to "Launchpad: https://launchpad.net/openstack-ansible || Weekly Meetings: https://wiki.openstack.org/wiki/Meetings/openstack-ansible || Review Dashboard: http://bit.ly/2xA1eZC"17:06
spotzThanks!17:06
openstackMeeting ended Tue Jan  8 17:06:17 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2019/openstack_ansible_meeting.2019-01-08-16.00.html17:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2019/openstack_ansible_meeting.2019-01-08-16.00.txt17:06
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2019/openstack_ansible_meeting.2019-01-08-16.00.log.html17:06
mnaserodyssey4me: jrosser btw, regarding keeping containers around17:06
mnaseri have thought about the idea of decoupling the tooling that lays down the containers/networking stack and osa17:06
mnaserthat way, you can just ansible-playbook -i osa-inventory foo.yml OR ansible-playbook -i your-static-file foo.yml17:07
prometheanfirecloudnull: is the networkd stuff merged? (aka, can I move forward on the gentoo stuff)?17:07
mnaserand you can just run a set of playbooks *before* OSA to lay down all of your network/containers17:07
mnaserand feed that into OSA17:07
evrardjpmnaser: I had that using LXD :p17:07
odyssey4mesure, all that it needs is the lxc/nspawn roles and an ansible iventory plugin - and none of that needs to be in OSA specifically, even if it is curated by this community17:07
mnaserso openstack ansible stays an openstack installer first, and it just deploys on different targets17:07
mnaserodyssey4me: yep!  and that way it can even be used for anything else, not necessarily just openstack17:08
odyssey4meand yeah, the lxc stuff could evolve to use lxd - whereas the nspawn stuff can continue in its own right17:08
evrardjpthe good thing with lxd,odyssey4me, is that it has a nice api you can use17:08
mnaserreally, the same way we say: setup your physical hardware the way you want it, because we don't touch it17:08
evrardjpyeah17:09
mnaserwe can do the same about containers, here's all the containers, now deploy openstack17:09
*** DanyC has quit IRC17:09
*** hamzaachi has quit IRC17:09
mnaserand then we can just have jobs that run that role first and feed the inventory to osa17:09
evrardjpit also simplifies ansible quite a lot, we don't need our wrapper anymore for example17:09
*** DanyC has joined #openstack-ansible17:09
evrardjpand we can have our own cli for parallel runs17:09
jrosseri have a whole pile of LXD work in the bag which could be appropriated17:09
evrardjpI would totally love to work on that, but my employer don't give me a second for it :p17:10
mnaserbut my concern is for the bigger deployers with more specific use cases, does the separation of concerns still make things workable?17:10
*** shardy has quit IRC17:10
chandankumarjrosser: can we add a dependson https://review.openstack.org/#/c/628979/ on this one https://review.openstack.org/#/c/625634/17:11
chandankumarjrosser: from above review I am seeing only keystone tempest plugin is getting installed17:11
*** DanyC has quit IRC17:12
chandankumarjrosser: http://logs.openstack.org/34/625634/1/check/openstack-ansible-functional-distro_install-centos-7/66d08ea/logs/ara-report/result/85edc814-2096-4012-b7a3-bf163f893479/17:12
prometheanfirechandankumar: that's my patch, so yes :P17:12
evrardjpmnaser: what do you mean ?17:12
chandankumarprometheanfire: let me do that17:13
openstackgerritMatthew Thode proposed openstack/openstack-ansible-os_barbican master: Force force-tlsv12 only  https://review.openstack.org/62563417:13
prometheanfirealready done :|17:13
chandankumarprometheanfire: cool17:13
evrardjpmnaser: I think it's easier if you're a bigger cloud: Finer tuning of the infra17:13
evrardjpthe only thing that matters between the two parts is the inventory17:13
odyssey4memnaser evrardjp jrosser I think it's something we can do nicely if we combine efforts - but it will need to be a combined effort, not bits and pieces. I'm suggesting it would be a series goal, with no other goals.17:14
evrardjpwhich is easily solvable if you think of writing an inventory of the created containers.17:14
evrardjpodyssey4me: agreed17:14
odyssey4mePerhaps people could hack a few things here and there, but then at the PTG we pull it together.17:14
evrardjpthis is a refactor of the mindset17:14
evrardjpthis cannot be done in one cycle17:14
evrardjpit needs to be spread in multiple steps in at least two cycles17:15
odyssey4meA way to make this easily workable, for example, is to put together a way to use playbooks/roles in a more pluggable way.17:15
odyssey4meSo if you want LXC things, you pull them in. If you don't, then it doesn't have any of that.17:15
evrardjpI was lacking creativity for the user experience tbh.17:16
jrosserdividing the inventory away sounds nice17:17
evrardjpwe can now, as there is no reliance on the inventory anymore (except if that was brought back)17:17
odyssey4methe only reliance right now is container builds17:18
odyssey4meif it's implemented as a plugin, rather than a dynamic inventory, then we'd be able to use standard ansible all the way for all group_vars, host_vars, overrides, etc and the inventory plugin would only be handling the container things17:19
evrardjpyeah so decoupling can be done in multiple phases: Being bare metal first in roles is the first step17:19
jrosserit would be interesting to understand pain points in more complex deployments17:19
odyssey4meand it'd be easy to whitelist/blacklist to enable/disable17:19
jrosserhaving a sane world where you have seperate OSA and ceph deploys17:19
jrosserbut your ops repo ELK stack is across both of those17:19
jrosser^ these kind of things are where i struggle17:20
evrardjpjrosser: I think this is fine already17:20
evrardjpas you can now chain inventoriues17:20
evrardjp-u17:20
odyssey4meI think most of the pain comes from having the inventory being a dynamic inventory at the moment, rather than a plugin17:20
evrardjpif you have no reliance over openstack-ansible CLI, it's just super easy to have that17:20
evrardjpodyssey4me: what kind of plugin you mean?17:21
odyssey4mebecause in this way you have to do a bunch of clunky things to string inventories together17:21
odyssey4meif we convert the dynamic inventory into an inventory plugin then using it will be far simpler17:21
evrardjpyeah but it really doesn't make sense to have that IMO17:22
odyssey4mesure, but some want it17:22
evrardjpthey want the easiness of a yaml edit that manages it all17:22
evrardjpbut that can be changed using native ansible inventory nowadays17:22
noonedeadpunkyeah, getting rid of openstack-ansible cli is nice as gives opportunity to use ansible runner safely for your python scripts17:22
evrardjpit's just that ansible yaml inventory is far more ugly than what we have :)17:24
noonedeadpunkbut inventory migration during some upgrade will be probably a nightmare...17:25
*** mathlin has quit IRC17:28
odyssey4meevrardjp you're forgetting that the dynamic inventory creates containers names and IP's - it's convenient... having that done by a plugin keeps the convenience for those who want it17:28
cloudnullmnaser noonedeadpunk: The issue with JSON test failing (https://bugs.launchpad.net/openstack-ansible/+bug/1810537) is fixed with https://review.openstack.org/#/c/62819717:29
openstackLaunchpad bug 1810537 in openstack-ansible "volume creation fails after successful installation" [Undecided,In progress] - Assigned to Mohammed Naser (mnaser)17:29
odyssey4meand makes it easier to disable for those who don't17:29
evrardjpI like the idea of the toggling tbh17:29
evrardjpand the separation of concerns17:29
evrardjpbecause if you don't want generation of IPs or are running IPv6, you don't need that :p17:30
cloudnullJust locally ran https://review.openstack.org/#/c/588953 and all is good with that patch applied17:30
evrardjpodyssey4me: there is this kind of nice "nmap" inventory that's good enough :D17:30
odyssey4mesomething broke between dec 6 and today - check the zuul logs for the cross-repo integrated test: https://review.openstack.org/#/c/623253/17:30
cloudnullseems the resource_filters.json is not included when the venv is built.17:31
evrardjpif you auto assign ips using dhcp, you don't need that feature odyssey4me :)17:31
odyssey4mecloudnull yeah, that's cos https://github.com/openstack/cinder/blob/master/setup.cfg#L28-L30 doesn't include https://github.com/openstack/cinder/blob/master/etc/cinder/resource_filters.json - we should fix that17:32
cloudnullah ha!17:33
*** kaiokmo has quit IRC17:33
cloudnullhttps://review.openstack.org/629272 odyssey4me17:39
odyssey4meboom, thanks cloudnull17:40
cloudnullso when that, or something like it, and the smart_sources commit for cinder are merged we can drop our template17:40
cloudnullthank you , it looks like your the original committer for the data_files input into cinder :)17:41
*** cshen has joined #openstack-ansible17:41
odyssey4mecloudnull yep, it's all part of the journey to make our lives simpler :)17:42
noonedeadpunkcloudnull odyssey4me oh, great! I've was wondering about how configs gets into venv about for a week:) Glad, that I've got the answer. And thanks for this patch!17:43
ansmithodyssey4me: hello, circling around tempest failure with qdrouterd role, same tempest test passes in oslo.messaging ci with ovs, if i wanted to try ovs in place of lxb, is there more to it than changing neutron_plugin_type?17:45
ansmithodyssey4me: I see there may be a difference to how notifications take place with the plugins which may explain things17:46
odyssey4meansmith I honestly have no idea - mnaser may be able to advise there, or jamesdenton - they know how to use ovs instead of LXB for neutron only.17:47
*** cshen has quit IRC17:47
odyssey4meok folks, I'm out for the night - cheerio!17:47
jamesdentonansmith it is pretty straightforward: https://docs.openstack.org/openstack-ansible-os_neutron/latest/app-openvswitch.html17:47
ansmithjamesdenton: thanks, will give it a whirl17:48
jamesdentonsure, i'll be around if you run into issues17:48
*** DanyC has joined #openstack-ansible17:50
*** mathlin has joined #openstack-ansible17:51
*** DanyC has quit IRC17:54
*** cshen has joined #openstack-ansible17:54
prometheanfirechandankumar: https://review.openstack.org/#/c/625634/ finished it's testing (failed again)18:08
openstackgerritMerged openstack/openstack-ansible-os_cinder master: Adds resource_filters.json distribution  https://review.openstack.org/62819718:09
*** hamerins has quit IRC18:09
openstackgerritDmitriy Rabotjagov (noonedeadpunk) proposed openstack/openstack-ansible-os_cinder stable/rocky: Adds resource_filters.json distribution  https://review.openstack.org/62927818:10
*** hamerins has joined #openstack-ansible18:11
openstackgerritFrank Zhang proposed openstack/openstack-ansible-os_barbican master: Removing stale policy file  https://review.openstack.org/62928018:22
*** mathlin has quit IRC18:25
*** partlycloudy has joined #openstack-ansible18:33
*** thuydang has joined #openstack-ansible18:39
* mnaser read sbuffer18:42
mnasercool, everyone is been helped :)18:44
partlycloudyHi everyone, I have a question: I want to use the same network for the external API endpoints and the provider network. How does OSA assign external IPs on the load balancer nodes? Would it start from the {{ external_lb_vip_address }} and then goes down continuesouly?18:45
*** mathlin has joined #openstack-ansible18:48
cloudnullpartlycloudy in config you specify a CIDR and OSA will pull from that at will. All host addresses will automatically be excluded from the available IP range and should you need there's an additional exclude list where you can add more IPs/Ranges a pool of unavailable IPs.18:51
mnaserpartlycloudy: however for load balancer, haproxy specifically, it runs on in baremetal18:51
mnaserwhich means that it will just use the interface that you configured, yourself18:51
cloudnullthe inventory code will randomly pull an IP from the CIDR you provide so it's non linear.18:51
*** lbragsta_ has joined #openstack-ansible18:52
*** lbragstad has quit IRC18:52
cloudnullalso what mnaser said :)18:52
cloudnullanyone around want to give https://review.openstack.org/#/c/588960/ a review ?18:54
cloudnulland https://review.openstack.org/#/c/60746218:54
*** lbragsta_ is now known as lbragstad18:55
partlycloudyThank you, cloudnull and mnaser. Suppose I use the 3 infra nodes as load balancer, do I need to pre-configure external IPs (in the same range as VIP) on the infra nodes?18:59
mnaserpartlycloudy: yep, that way keepalived can host the vip on those interfaces18:59
mnasercloudnull: checkin18:59
mnaserdeleting mah code19:00
partlycloudymnaser: got it. thank you very much! :-)19:00
noonedeadpunkfolks, can you please check this cherry-pick? https://review.openstack.org/#/c/629278/19:01
*** kaiokmo has joined #openstack-ansible19:01
spotzdone noonedeadpunk19:12
noonedeadpunkthanks!19:16
*** mathlin has quit IRC19:22
*** hamerins has quit IRC19:34
*** hamerins has joined #openstack-ansible19:35
*** cshen has quit IRC19:35
*** SimAloo has joined #openstack-ansible19:36
*** partlycloudy has quit IRC19:37
*** cshen has joined #openstack-ansible19:38
*** thuydang has quit IRC19:40
*** thuydang has joined #openstack-ansible19:43
*** mathlin has joined #openstack-ansible19:45
*** cshen has quit IRC19:46
*** cshen has joined #openstack-ansible19:48
*** cshen has quit IRC19:57
openstackgerritMerged openstack/openstack-ansible-os_cinder stable/rocky: Adds resource_filters.json distribution  https://review.openstack.org/62927819:57
*** gary_perkins has quit IRC20:01
*** gary_perkins has joined #openstack-ansible20:06
*** thuydang has left #openstack-ansible20:13
*** thuydang has joined #openstack-ansible20:15
openstackgerritKevin Carter (cloudnull) proposed openstack/openstack-ansible-os_cinder master: Cleanup files and templates using smart sources  https://review.openstack.org/58895320:24
*** spsurya has quit IRC20:41
openstackgerritJames Denton proposed openstack/openstack-ansible master: Update inventory generator to support container gateway override  https://review.openstack.org/62930920:47
openstackgerritJames Denton proposed openstack/openstack-ansible-lxc_container_create master: Update container interface template to disable DHCP routes when gateway set  https://review.openstack.org/62931020:48
*** tosky has quit IRC20:49
* jrosser looks at this very suspicoiusly https://github.com/ceph/ceph-ansible/commit/416b503476c9859cf38db1d71a64cb77a4117a6b20:52
jamesdentonevrardjp jrosser re: the gateway override for containers... the static_routes are handled on a per network/interface basis, and unless you disable the route pushed via DHCP on eth0 Ivia lxcbr0) you'll have overlapping default routes, as someone mentioned. https://review.openstack.org/629309 and https://review.openstack.org/629310 a first pass if that's really a feature we want to implement. Otherwise we should20:53
jamesdenton probably remove mention of it from docs20:53
jrosser"leseb merged commit 416b503 into stable-3.2  2 days ago" pretty much when our integrated repo ceph jobs stopped working20:53
prometheanfirechandankumar: can you confirm that os_barbican does not set up a web server in front of uwsgi (relies on haproxy)20:59
openstackgerritJonathan Rosser proposed openstack/openstack-ansible master: [DNM] test rolling back last commit of ceph-ansible stable-3.2  https://review.openstack.org/62931220:59
*** cshen has joined #openstack-ansible21:00
openstackgerritFrank Zhang proposed openstack/openstack-ansible-os_barbican master: Removing stale policy file  https://review.openstack.org/62928021:02
*** radeks has quit IRC21:02
*** cshen has quit IRC21:06
logan-jrosser: makes sense, we probably need to run ceph-facts just after the ceph-defaults role21:09
*** jbadiapa has quit IRC21:10
openstackgerritJonathan Rosser proposed openstack/openstack-ansible master: Call ceph-facts role as required by changes to ceph-ansible  https://review.openstack.org/62931721:14
*** hamerins has quit IRC21:14
jrosserlogan-: something like that ^, can you keep an eye on that and https://review.openstack.org/629312 should give a comparison with the ceph-facts patch rolled out21:14
jrosseri'm done for today21:15
logan-will do21:15
jrosserty21:15
logan-thanks21:15
*** hamerins has joined #openstack-ansible21:15
*** cshen has joined #openstack-ansible21:18
*** cshen has quit IRC21:23
openstackgerritJakob Englisch proposed openstack/ansible-hardening master: Chrony: make ntp server options configurable  https://review.openstack.org/62931821:23
*** partlycloudy has joined #openstack-ansible21:23
*** ansmith has quit IRC21:26
*** jamesdenton has quit IRC21:35
openstackgerritKevin Carter (cloudnull) proposed openstack/openstack-ansible-os_cinder master: Cleanup files and templates using smart sources  https://review.openstack.org/58895321:39
*** thuydang has quit IRC21:42
mnaserwe reaaaaaaally gotta stop hardcoding config options ;(21:47
*** jamesdenton has joined #openstack-ansible21:56
*** thuydang has joined #openstack-ansible22:05
*** DanyC has joined #openstack-ansible22:11
spotzmnaser: wasn't me!:)22:11
*** DanyC has quit IRC22:15
*** thuydang has quit IRC22:16
openstackgerritDamian Cikowski (dcdamien) proposed openstack/openstack-ansible-os_designate master: Set project that owns managed resources  https://review.openstack.org/62878522:30
openstackgerritJakob Englisch proposed openstack/ansible-hardening master: Chrony: add an option to sync the hardware clock  https://review.openstack.org/62933022:46
*** tosky has joined #openstack-ansible23:01
*** strobelight has quit IRC23:03
*** SimAloo has quit IRC23:07
*** cshen has joined #openstack-ansible23:08
*** cshen has quit IRC23:13
*** hamerins has quit IRC23:13
*** l-j has joined #openstack-ansible23:37
cloudnullmnaser which hard coded op have you found now?23:40
mnasercloudnull: keystone allowed auth methods23:40
mnaserits token and password23:41
mnaserdoesnt include application_credentials23:41
cloudnulloh...23:41
cloudnullthat's kinda a bummer. but at least you should be able to override that with config_template?23:41
cloudnullhowever, i agree, it should be an array that a user can easily tweak23:42
cloudnullif folks can review https://review.openstack.org/#/c/588953 and https://review.openstack.org/#/c/588960 they now work and get rid of some (most) of the config related templates we're carrying.23:42
cloudnullkinda related :)23:42
openstackgerritLogan V proposed openstack/openstack-ansible master: Call ceph-facts role as required by changes to ceph-ansible  https://review.openstack.org/62931723:52
*** ansmith has joined #openstack-ansible23:53

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