Thursday, 2015-04-09

*** sdake_ has quit IRC00:00
*** sacharya has quit IRC00:04
*** mahito has joined #openstack-ansible00:22
*** bilal has joined #openstack-ansible00:25
bilalany workaround?00:26
bilalhey.. TASK: [container_restart | Test Container Networking] always gives errors and times out00:26
*** bilal has quit IRC00:35
*** bilal has joined #openstack-ansible00:35
bilalwhat is elasticksearch container00:36
cloudnullo/ bilal00:37
cloudnullwhat would you like to know ?00:37
bilalthere is this elasticsearch_container that gets created on the logger host. And when this container gets restarted in the task TASK: [container_restart | Restart containers] during rackspace10 install; it always gives error00:39
cloudnullwhats the error ?00:40
bilal {"err": "Failed to change the state of the container.", "failed": true, "item": "logging_elasticsearch_container-e3833834", "rc": 2}00:40
bilalmsg: State failed to change for container [ logging_elasticsearch_container-e3833834 ] -- [ running ] != [ stopped ]00:42
cloudnullit seems that ansible is not able to stop the container on the logging host.00:43
cloudnullif you login to the logging host00:43
cloudnullcan you do an "lxc-stop -n logging_elasticsearch_container-e3833834"00:43
cloudnulland if you do, does the container stop? which you can tell with "lxc-ls -f"00:44
bilalthe container is already in STOPPED state00:45
bilaland lxc-start is giving this error:00:46
bilallxc-start: conf.c: instantiate_veth: 2978 failed to attach 'vethJOVYLX' to the bridge 'lxcbr0': No such device00:46
cloudnullif you do an ip a l breth000:46
cloudnulldoes that show you an lxc bridge device ?00:47
cloudnullsorry00:47
cloudnullip a l lxcbr000:47
bilalno.. Device "lxcbr0" does not exist.00:47
bilalhow do you create lxcbr0 manually?00:48
cloudnullare you on 10.1.2 ?00:49
cloudnulleither way you can run "lxc-system-manage system-force-rebuild" on the logging host00:50
cloudnullThat will rebuild everything needed to make the lxc system run and it should start the containers00:50
bilalit did.. thanks a lot. Really appreciate the help00:52
cloudnullanytime .00:54
*** sacharya has joined #openstack-ansible01:34
bilalin the TASK: [container_restart | Restart containers] while running host_setup playbook for rackspace 10; 90% of the conatiners on all hosts gets timedout with this error: msg: Timeout when waiting for 10.xx.xx.196:2201:43
bilalfailed: [bilalrsinfra-XS23-TY3] => (item=bilalrsinfra-XS23-TY3_nova_api_os_compute_container-32b91bc2) => {"elapsed": 180, "failed": true, "item": "bilalrsinfra-XS23-TY3_nova_api_os_compute_container-32b91bc2"}01:44
bilaland the playbook ends with: FATAL: all hosts have already failed -- aborting01:48
bilalany help?01:48
cloudnullsounds like an ip conflict, ie the management network is either not ready or unavailable on the host.01:57
cloudnullcan you ssh to the containers on one of the failing hosts ?01:57
bilalTo the host, yes i can ssh from deploy machine. But to that container inside host i cannot even ping from deploy host02:03
*** sacharya has quit IRC02:03
cloudnullso from the deploy host you can not ping or ssh to the containers ?02:05
bilalno i cant02:05
cloudnullthat seems like the host network is not setup or that there is some type of filtering on the hosts that is making networking impossible.02:06
bilalokay. let me check02:11
*** stevemar has joined #openstack-ansible02:12
*** mahito_ has joined #openstack-ansible02:15
*** mahito has quit IRC02:17
openstackgerritMerged stackforge/os-ansible-deployment: Flake8 update - inventory-manage.py  https://review.openstack.org/17110202:31
*** sacharya has joined #openstack-ansible02:33
*** mahito has joined #openstack-ansible02:40
*** mahito_ has quit IRC02:43
*** mahito has quit IRC02:54
*** mahito has joined #openstack-ansible03:19
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated the repo scripts  https://review.openstack.org/17177703:38
*** mahito has quit IRC03:58
*** mahito has joined #openstack-ansible04:03
openstackgerritSudarshan Acharya proposed stackforge/os-ansible-deployment: Managing policy file with default file and user variables.  https://review.openstack.org/16810404:22
*** sacharya has quit IRC04:26
*** raginbajin has quit IRC04:32
*** javeriak has quit IRC04:33
*** bilal has quit IRC04:34
*** raginbajin has joined #openstack-ansible04:35
*** sacharya has joined #openstack-ansible04:35
*** mahito has quit IRC04:39
*** mahito has joined #openstack-ansible04:40
*** stevemar has quit IRC04:57
*** sacharya has quit IRC05:24
*** mahito has quit IRC05:32
*** mahito has joined #openstack-ansible05:33
*** nosleep77 has quit IRC06:00
*** mahito has quit IRC06:10
*** mahito has joined #openstack-ansible06:17
*** mahito has quit IRC06:22
*** mahito has joined #openstack-ansible06:26
*** sdake_ has joined #openstack-ansible06:32
*** javeriak has joined #openstack-ansible06:51
*** sdake_ has quit IRC07:05
*** mahito has quit IRC07:16
*** sdake has joined #openstack-ansible07:18
*** sdake_ has joined #openstack-ansible07:25
*** sdake has quit IRC07:26
*** sdake_ has quit IRC07:30
*** sdake has joined #openstack-ansible07:52
odyssey4mewow, we suddenly have several tempest failures in the gate... everything was operating just fine yesterday - I wonder what changed... perhaps another dependency change in the mix? or... I suppose we're tracking master so it could be any number of patches upstream08:23
*** javeriak has quit IRC09:00
odyssey4meandymccr hughsaunders I'm guessing that we need an environment change to place the ELK containers on a particular host?09:30
andymccrodyssey4me: yeh09:31
odyssey4meas such, it would seem that https://review.openstack.org/170558 is necessary, right?09:31
andymccrive done that09:31
andymccrto make it easiest yeh that'd be required09:31
andymccrotherwise you'd have to manually edit the env file which is more admin/complicated09:32
odyssey4meyeah, without that patch we'd have to ask a deployer to edit the environment file - whereas with the patch we can simply copy a file over09:32
andymccrBut I used the logging to test that patch, so here is a logging.yml to pop inside env.d http://pastie.org/1008205909:32
andymccrtempted to do a separate patch to remove the md5sum stuff cos that becomes even less useful when using env.d09:35
odyssey4meandymccr go for it09:35
andymccrodyssey4me: can you think of another way to solve that issue? (Issue being - if we do an upgrade from say 9-10 or 11-12 or w/e and the default environment file/user_vars have changed we won't know)09:35
andymccrso you will run the playbooks and it will just fail out until you have added all the vars in.09:36
andymccreven though we update the sample user_variables file.09:36
odyssey4meandymccr well, in theory that's technical debt to be handled by the upgrade script - surely?09:36
andymccrodyssey4me: not really09:36
andymccrunless we are having an upgrade script between each version all the time09:36
andymccrexample, the service_profiler_hmac_key vars that were added as part of kilofication09:37
andymccrif you just upgrade from before kilofication to after you will fail out unless you update your vars file, but you don't really have any notifier to update your vars file09:37
odyssey4meandymccr good question, for which I have no answer currently - but my thinking is that we need an upgrade script to handle transitions between variable renames and other upgrading issues for any upgrades09:38
odyssey4mebut I can see how that would get messy quickly09:38
odyssey4methe method thus far appears to be to do the work in isolation first and to consider the upgrade problem while doing so, but not to be hung up on it09:38
andymccrodyssey4me: yeh so the initial md5sum never really solved it, but in theory it would prompt you to check your user_vars/env files to ensure they are updated09:38
andymccrin practice it didnt do that at all, and really didnt do anything09:39
*** sdake_ has joined #openstack-ansible09:46
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Remove md5sum check for environment vs user_config  https://review.openstack.org/17198709:49
*** sdake_ has quit IRC09:49
*** sdake has quit IRC09:50
andymccrhmm ok so cloudnull put a comment on the initial bug - maybe my understanding of the point of the md5sum is wrong. can abandon if necessary but i'm still not sure it solves a problem that anybody has , since your environment will never have changed unless you change it :)09:52
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Adjust AIO swap size to 1.5x RAM  https://review.openstack.org/17199210:15
andymccrwe currently dont have a way to overwrite the size of a container for 1 specific container?10:39
odyssey4meandymccr dunno, don't we?11:00
odyssey4meI just encountered another issue relating to the wheel repo - how do we implement additional wheels to be built for extras?11:01
odyssey4me(without adjusting osad)11:01
andymccrodyssey4me: we don't but im patching it now :D (re: the fs_size)11:03
andymccrthe repo stuff im not sure honestly11:04
andymccri dont think we do or have a good mechanism11:04
andymccrbecause for some of the extras that got moved out i needed to do things like "--isolation" for installing pip packages to avoid the repo :) (which is not ideal)11:04
odyssey4mewell, I know that it's easy enough to add something to the appropriate file, then rebuild the repo... but that's hardly ideal and definitely breaks the 'frozen repo' model11:06
andymccryeh11:06
andymccrquite!11:06
odyssey4mewe have to implement the extras in such a way that it's more integrated, not an after-thought11:06
odyssey4meI had some discussions yesterday for doing that, but want to get this done before going there.11:07
andymccragree, but i think the only way to do that is to treat all things the same - e.g. have an over-arching repo that then pulls in all roles (e.g. any 3rd party roles, and os-a-d roles and extra roles)11:07
andymccrthat way they are all the same, and that one over-arching repo can store your env/vars/playbooks for everything11:07
andymccrbut it raises questions about a community version of that over-arching repo and that'd have to differ so its not quite that simple11:08
odyssey4mebut that's not possible now with all roles in a single repo, so we'll have to fudge it with scripts11:08
odyssey4meansible-galaxy's command-line can do the imports, but only if the roles are in their own repo11:08
andymccrso thats the problem, the "design" works except that how its setup now doesnt match the design11:09
andymccre.g. all the roles should be separate entirely and all be pulled in11:09
andymccrbut as it stands we have basically all the roles already so any 3rd party/extras roles are "after thoughts"11:09
odyssey4meso we have the option of doing our extras roles in separate repositories, and having the extras repo simply housing the plays - then the plays are run from the osad repo root just like all the osad standard stuff11:10
odyssey4methat way we don't have to carry a copy of the inventory module, or any plugins/libraries11:10
andymccrsure but the plays themselves would have to be carried in the os-a-d repo when they are not os-a-d plays11:11
andymccras would the vars/env files11:11
odyssey4meit would change the workflow somewhat, but it would be a lot more integrated and deploy more cohesively11:11
odyssey4meandymccr nope the plays can be external entirely, they're just executed from inside the osad/playbooks directory11:12
andymccrsure but how are you pulling those in then11:12
odyssey4meeg: from /opt/os-ansible-deploy/playbooks you execute: openstack-ansible /opt/rpc-extras/playbooks/blah.yml11:12
andymccrso you are cloning that repo anyway?11:13
odyssey4methe roles in the ansible bootstrap (part of setup) would be imported into the ansible namespace (so it doesn't dirty the osad git tree) - ie they will be located in /etc/ansible/roles/11:13
openstackgerritMerged stackforge/os-ansible-deployment: Update tempest config for current master  https://review.openstack.org/17114211:14
odyssey4meandymccr yeah, the repo cloning is inevitable unless we package the plays - but note that the repo contents are simply the plays and any other convenience scripts... no roles11:14
andymccri understand how the roles get pulled in, but then you are cloning a repo to run a play from within the os-a-d tree (the play exists elsewhere) to then run plays you have pulled in. you could argue thats less integrated11:14
odyssey4meit's the only way I can see it working with the way the repositories are structured now11:15
andymccrid argue you would have a my-common, which pulls in the individual os-a-d roles and any addition 3rd party/extra roles and inside that repo all the plays i need exist.11:15
odyssey4methe better way is to split the roles into repositories, for sure, but that adds much more complexity11:15
andymccris the point not that the way its structured now means there is no ideal solution, so the way it is now is fine since its potato/potato (which doesnt work over irc)11:16
*** subscope has quit IRC11:17
odyssey4meyeah, but now I'm having to build osad - then re-run various osad plays in order to build containers and configure them once I have the extras setup11:17
andymccrnot really? i mean you have to copy over the env files etc11:17
andymccrif you've done that you dont have to run anything extra11:17
andymccrwhich is the same as if you pull in the roles - you would still need to copy the env files11:17
andymccrif you havent done that then sure you will.11:17
odyssey4meyeah, I suppose that's fair - it is possible to do most of the setup initially if you're aware of how to do it all11:18
odyssey4meit's clunky and sucks though :(11:18
andymccrbut that doesnt change if you pull in the role11:18
andymccrbecause the bits that define what gets setup still need to be done, so if you dont know to do that you will pull in the roles fine and they wont work11:18
andymccrthat step of "copy over vars/env" is unavoidable and would still sit in rpc-extras so that step is exactly the same11:19
odyssey4meyeah, agreed - the only difference with the suggested change of workflow is that the extras repo doesn't need to carry libraries/inventory11:19
andymccryeh basically, but trade off is that you then run a play from inside the os-a-d dir space which is quite clunky also11:19
*** subscope has joined #openstack-ansible11:20
odyssey4meblast, with the current implementation you can't do role dependancies11:27
odyssey4meandymccr any thoughts on how I get pip installed into the container using the pip_install role (ideally) in the current setup?11:27
odyssey4meI don't want to use the pip_lockdown - but even if I did the same problem would apply.11:28
andymccri feel like i must've done this lemme look11:29
*** stevemar has joined #openstack-ansible11:43
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Allow lxc_container settings per container type  https://review.openstack.org/17201911:53
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Set the container_fs_size to 12G for Glance  https://review.openstack.org/17202011:55
*** stevemar has quit IRC12:02
odyssey4meandymccr did you figure out your method?12:25
odyssey4me(for pip installs)12:25
odyssey4meas far as I can see, pip_install as a role is depended on by pip_lockdown, which is depended on by each service that uses pip packages12:26
andymccrhmm12:26
andymccrso pip was already installed because im not creating anything new12:26
andymccrso i didnt solve that problem :/12:26
odyssey4meyeah, in this case for the ELK containers there is no pip because nothing installs it - you were working on hosts which have it installed already12:26
andymccryeh12:27
andymccrhmm12:27
andymccrso the problem is that now we want to install pip packages that arent in the repo?12:27
odyssey4meif we were running the plays from inside os-ansible-deployment/playbooks then it would have access to the roles... but we aren't12:27
andymccrso if we run the pip-install role against those hosts then its locked down12:27
odyssey4menope, the pip_install role doesn't lock it down - the problem is that the extras playbooks don't have access to the pip_install role12:28
odyssey4meso either I have to install pip in the elasticsearch role using whatever method I choose, or I need to find a way to depend on the pip_install role12:28
andymccrbut the nova role doesnt call the pip_install role for example12:30
andymccror theyre using a dependency on pip_lockdown12:31
odyssey4meyes, it depends on pip_lockdown, which depends on pip_install12:31
andymccrthats problematic then12:32
odyssey4meI'll symlink it for now, but this provides a pretty hard reason to change how we're implementing the extras.12:34
odyssey4meA way, of course, would be to extract the pip_install into its own role and pull it into the ansible namespace using ansible-galaxy.12:34
andymccri dont think its just extras that needs to change the implementation12:34
andymccrcan we not include roles based on a location?12:35
andymccrinstead of symlinking12:35
odyssey4meyeah, agreed - the point being is that now that we're faced with actually trying to do this it's turning out to be more complex than originally thought12:35
odyssey4meunfortunately ansible-galaxy can't import from a file location12:35
odyssey4mehttp://docs.ansible.com/galaxy.html#advanced-control-over-role-requirements-files12:36
odyssey4meyou can source from ansible galaxy, git, bitbucket, http but not file it seems12:36
andymccrhttp://docs.ansible.com/intro_configuration.html#roles-path12:37
andymccrcould adjust the roles_path in ansible.cfg for the extras12:37
odyssey4meooh, there's an option - let me try that12:38
odyssey4menice one :)12:38
andymccrif only we could do that for library also12:38
odyssey4mehttp://docs.ansible.com/intro_configuration.html#library12:38
andymccroh you can i think. maybe12:38
odyssey4mehahaha12:38
andymccrand inventory...12:39
odyssey4meand http://docs.ansible.com/intro_configuration.html#inventory12:39
andymccrhaha12:39
odyssey4megreat minds...12:39
andymccrwell that'd solve a lot of that fudgery. still not perfect, but at least it resolves the majority12:39
odyssey4meyes, let me try them out and see - this may actually simplify a lot of things12:40
odyssey4meit'll still require a prep script to be run to set the directory, but that's small change12:40
odyssey4meor perhaps just an assumption about where the os-ansible-deployment is located and a documented warning12:40
andymccrwell there is a default i think12:42
andymccrits just that i dont ever deploy it in the default :D12:42
andymccrso if you do it should work without setting that12:42
odyssey4meooh, it works12:46
odyssey4meso you can set the roles path and it still checks the <current directory>/roles12:47
odyssey4mebut with this we can include the os-ansible-deployment/playbooks/roles/ too12:47
odyssey4meand it appears that the dynamic inventory works too12:47
andymccrawesome12:48
andymccrMERGE IT!12:48
odyssey4meyeah, I'll prep a patch for that in particular and include a README edit12:49
cloudnullMorning.13:13
*** Mudpuppy has joined #openstack-ansible13:19
*** Mudpuppy has quit IRC13:25
*** Mudpuppy has joined #openstack-ansible13:25
odyssey4meo/ cloudnull13:26
odyssey4mehas anyone had any luck ferreting out why the gate's broken today?13:35
odyssey4mefor master, at the very least13:35
cloudnulli just started looking at that13:41
*** stevemar has joined #openstack-ansible13:46
andymccrodyssey4me: i have not yet had a chance to.13:46
*** sacharya has joined #openstack-ansible13:49
*** ccrouch has joined #openstack-ansible13:52
*** openstackgerrit has quit IRC13:53
*** openstackgerrit has joined #openstack-ansible13:53
*** markvoelker has quit IRC13:58
*** markvoelker has joined #openstack-ansible13:59
openstackgerritMatthew Kassawara proposed stackforge/os-ansible-deployment: Remove deprecated use_namespaces option  https://review.openstack.org/17206814:05
matttlots of 503 from keystone in gate errors14:06
andymccrmattt: yeh but its weirdly only when tempest seems to install/setup ?14:06
*** sdake has joined #openstack-ansible14:10
matttandymccr: http://logs.openstack.org/36/171036/4/gate/os-ansible-deployment-dsvm-check-commit/f0aa7a7/logs/aio1_nova_api_os_compute_container-fa731224/nova-api-os-compute.log14:14
Sam-I-Ammattt: this happened to me14:18
*** KLevenstein has joined #openstack-ansible14:23
matttSam-I-Am: on your aio?14:23
matttSam-I-Am: do you still have it up?14:23
Sam-I-Ammattt: yeah, and no... i tore it down for a rebuild14:31
Sam-I-Amthinking it was transient14:31
odyssey4meI think it's likely that something upstream has changed and is affecting us.14:32
* Sam-I-Am shockedface14:32
Sam-I-Amthings breaking basic functionality after feature freeze?14:32
Sam-I-Amlike the horizon refactor earlier this week14:33
odyssey4meSam-I-Am typically it ends up being a dependent module, like one of the oslo goodies or something even further afield like requests14:33
matttbuilding an AIO now14:34
odyssey4meand hpcloud-b4's consistant apt install failures aren't helping14:34
Sam-I-Amugh @ dumb14:39
Sam-I-Amhttps://bugs.launchpad.net/ubuntu/+source/nova/+bug/143928014:39
openstackLaunchpad bug 1439280 in nova (Ubuntu) "Libvirt CPU affinity error" [Undecided,Incomplete]14:39
Sam-I-Amthe last post before my reply... obviously didn't read the bug "testing using qemu"14:39
Sam-I-Amit probably works fine with kvm/nesting, but this is not the issue at hand14:40
Sam-I-Amand it only affects the ubuntu packages, not source, so its really an ubuntu problem14:40
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: [WIP] Diagnostic information for gate checks  https://review.openstack.org/17209614:47
*** erikmwilson is now known as Guest8153114:52
*** erikmwilson has joined #openstack-ansible14:52
*** erikmwilson_ has joined #openstack-ansible14:52
odyssey4mecloudnull so no issues on larger cloud server builds? do you think this is a resourcing issue?15:04
cloudnullit looks that way15:04
cloudnullim trying again on p1.815:04
odyssey4meodd, because yesterday all was fine and dandy15:04
cloudnulland will try to narrow it down.15:05
odyssey4methe birds were tweeting in the clouds and stuff :p15:05
cloudnullalso if we can get https://review.openstack.org/#/c/170952/ that eliminates the ec2 container15:06
cloudnullnot that one container makes all the difference, but it might make some .15:06
odyssey4mecloudnull agreed, but I've been rechecking all day with no success15:06
stevellecommunitay15:06
Sam-I-Ami'm testing with affinity = 115:07
Sam-I-Amwhich should reduce some things15:07
odyssey4meheh, ok - only one merge has succeeded since this morning15:07
Sam-I-Amkind of seems like galera might be ooming15:07
Sam-I-Ambecause everything starts 500ing when keystone falls over, and it seems to be having db problems15:07
matttSam-I-Am: that was my guess15:10
Sam-I-Amwe are doing a LOT more things than typical devstack gating15:12
odyssey4meSam-I-Am 'cos we're awesome like that :p15:15
odyssey4meis our reduced cache size for galera still taking effect?15:17
odyssey4meis it perhaps taking too much effect?15:18
matttyeah gcache.size = 50M is still being set15:21
matttmy node just went mental while running tempest playbook15:25
mattt[ 3494.507150] Killed process 14410 (mysqld) total-vm:5564496kB, anon-rss:514892kB, file-rss:0kB15:26
Sam-I-Ammattt: standard aio with affinity > 1 ?15:28
matttSam-I-Am: yeah i just ran the gate-check-commit.sh script to boot the node15:30
Sam-I-Ami'm still running through my aff=115:31
Sam-I-Amso far there's a lot more resources available15:31
Sam-I-Amlike... over a gig of ram free15:31
*** Bjoern__ has joined #openstack-ansible15:32
*** jwagner_away is now known as jwagner15:37
*** jwagner is now known as jwagner_away15:38
Sam-I-Ammattt: tempest passed15:47
Sam-I-Ammattt: some swap used, but almost a gig of ram available15:47
matttSam-I-Am: my aio has 1 GB of swap15:49
matttSam-I-Am: i'm currently running tempest (after having to rerun the tempest playbook)15:49
*** Bjoern__ is now known as BjoernT15:49
matttSam-I-Am: all swap used, ~ 100 MB of memory available15:49
Sam-I-Ameeooo15:53
cloudnullmeeting in 5: cloudnull, mattt, andymccr, d34dh0r53, hughsaunders, b3rnard0, palendae, Sam-I-Am, odyssey4me, serverascode, rromans, mancdaz, dolphm, _shaps_, BjoernT, claco, echiu, dstanek15:54
matttSam-I-Am: yeah, my node is effectively unresponsive15:55
*** BjoernT2 has joined #openstack-ansible15:58
*** jwagner_away is now known as jwagner16:00
*** BjoernT2 has quit IRC16:02
*** BjoernT2 has joined #openstack-ansible16:03
openstackgerritMerged stackforge/os-ansible-deployment: Correct a syntax error in some hosts: patterns  https://review.openstack.org/16950616:20
odyssey4me\o/16:20
* svg would like to know what people here were smoking whenthey designed the flow of variable definitions16:23
BjoernTsvg: +116:27
odyssey4mesvg what is smoked by some, while interesting, is beyond the scope of discussion here :p16:28
odyssey4meheh, what're you referring to16:28
Sam-I-Amvariable definitions? smoke?16:28
odyssey4mebut first, you had best be talking about the master branch and not the previous branches... the older branches have a lot of organically grown mess :)16:29
Sam-I-Amodyssey4me: dont we prefer organic artisinal code over mass-produced gmo code?16:30
odyssey4mesvg in the major re-working done in the master branch, we hope that we have done things in a more sane fashion... if not, then patches welcome :D16:31
odyssey4meSam-I-Am no comment :p16:32
cloudnullsvg community meeting in #openstack-meeting-4 if your interested.16:32
*** mnestheu1 has joined #openstack-ansible16:32
andymccrodyssey4me: im not sure we're on the same page re that bug? what regression is it? it seems to me like an upstream bug in the lineinfile module that miguelgrinberg already fixed17:00
andymccror not fixed but addressed17:00
BjoernTandmccr: As i said in the bug, the regex is not good anyway17:01
andymccrim not sure what the correct resolution would be for fixing exisitng installs except to upgrade ansible17:01
andymccrBjoernT: yeh i agree its not amazing regex17:01
BjoernTit is actually not a regex17:01
d34dh0r53just recheck/reverified all of the failed jobs17:01
andymccrwell it just does a string search so its kinda like .*MaxSessions.*17:01
odyssey4meandymccr all I'm trying to highlight is that we've hit this before, not that we solved it in the right way17:02
odyssey4meas I recall we did two things - one in the plays and one in the gate bash script17:02
andymccrodyssey4me: the upstream lineinfile bug? oh ok. i mean sure we can work around it in the meantime17:03
odyssey4meanyway, glad we're hitting it again and hopefully we can find a better solution this round17:03
andymccrodyssey4me: surely the solution is ensure a version fo ansible > than the one with that bug in it?17:03
odyssey4meandymccr is it resolved in a specific version?17:04
andymccrhttps://github.com/ansible/ansible-modules-core/issues/73617:04
odyssey4mesorry - I haven't looked into miguel's PR in detail17:04
andymccrnot sure what the specific version is17:05
andymccrbut  > 1.6.10 :D17:05
andymccralso since our gate isnt seeing that issue im wondering if we're using a newer version for juno17:05
odyssey4meah, then we have the awesome option of simply using a later version for icehouse/juno - master's already on a newer version17:05
odyssey4methe gate doesn't see it because we fiudge it17:05
odyssey4mehttps://github.com/stackforge/os-ansible-deployment/blob/juno/scripts/bootstrap-aio.sh#L85-L8817:06
odyssey4meunless I'm completely confused about the issue - I did read it rather quickly17:08
*** jwagner is now known as jwagner_away17:13
odyssey4meI've got to run. We'll catch up tomorrow!17:13
andymccrcan't wait odyssey4me!17:13
*** openstack has quit IRC17:13
*** openstack has joined #openstack-ansible17:15
*** BjoernT2 has quit IRC17:20
openstackgerritMatthew Kassawara proposed stackforge/os-ansible-deployment: Update keystone middleware in nova for Kilo  https://review.openstack.org/17215317:27
*** sdake_ has joined #openstack-ansible18:05
*** sdake has quit IRC18:09
*** javeriak has joined #openstack-ansible18:17
*** yaya has joined #openstack-ansible18:22
*** javeriak has quit IRC18:22
*** sdake has joined #openstack-ansible18:25
*** sdake_ has quit IRC18:29
openstackgerritMerged stackforge/os-ansible-deployment: Nova Kilofication Work  https://review.openstack.org/17095218:43
d34dh0r53nova kilofication finally merged, that eliminates a container which I hope will take some of the memory pressure off of the gates18:45
b3rnard0d34dh0r53: cool18:46
*** javeriak has joined #openstack-ansible19:02
*** javeriak_ has joined #openstack-ansible19:07
*** javeriak has quit IRC19:08
*** erikmwilson has quit IRC19:11
*** javeriak has joined #openstack-ansible19:12
*** javeriak_ has quit IRC19:13
*** javeriak_ has joined #openstack-ansible19:14
*** javeriak has quit IRC19:16
*** javeriak has joined #openstack-ansible19:31
*** javeriak_ has quit IRC19:35
*** erikmwilson_ is now known as erikmwilson19:42
*** yaya has quit IRC19:49
*** jwagner_away is now known as jwagner20:01
openstackgerritSteve Lewis proposed stackforge/os-ansible-deployment: Genericize how we update SSL settings for Apache  https://review.openstack.org/17183820:05
stevelleI'm having major issues with irc today. Hoping I have them resolved now but lost some history.  Did any progress happen around the broken gating on master?20:13
BjoernTwho want's to debug #1440784, have one frozen spice console20:28
*** stevelle has quit IRC20:34
*** stevelle has joined #openstack-ansible20:37
*** stevelle_ has joined #openstack-ansible20:38
*** stevelle has quit IRC20:39
*** stevelle_ is now known as stevelle20:52
*** sdake has quit IRC20:53
*** stevemar has quit IRC20:58
*** jwagner is now known as jwagner_away20:59
*** jwagner_away is now known as jwagner21:05
*** mancdaz has quit IRC21:35
*** mancdaz has joined #openstack-ansible21:38
openstackgerritMerged stackforge/os-ansible-deployment: Flake8 update - swift_rings.py  https://review.openstack.org/17103821:40
*** BjoernT has quit IRC21:53
*** jwagner is now known as jwagner_away21:57
*** KLevenstein has quit IRC22:00
openstackgerritSteve Lewis proposed stackforge/os-ansible-deployment: Genericize how we update SSL settings for Apache  https://review.openstack.org/17183822:06
*** sdake has joined #openstack-ansible22:07
*** mnestheu1 has quit IRC22:09
*** sdake_ has joined #openstack-ansible22:10
*** sdake has quit IRC22:14
openstackgerritSteve Lewis proposed stackforge/os-ansible-deployment: Genericize how we update SSL settings for Apache  https://review.openstack.org/17183822:34
*** sdake_ has quit IRC22:47
*** JRobinson__ has joined #openstack-ansible22:48
*** sacharya has quit IRC23:10
*** britthouser has joined #openstack-ansible23:14
*** britthou_ has quit IRC23:17
*** britthouser has quit IRC23:21
*** britthouser has joined #openstack-ansible23:22
*** britthou_ has joined #openstack-ansible23:25
*** britthouser has quit IRC23:27
*** britthou_ has quit IRC23:27
*** britthouser has joined #openstack-ansible23:27
*** britthouser has quit IRC23:49
*** Mudpuppy has quit IRC23:51
*** britthouser has joined #openstack-ansible23:52

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