Wednesday, 2015-03-11

cloudnullhughsaunders palendae commit https://review.openstack.org/#/c/163006/ and https://review.openstack.org/#/c/163194/ seem to be competing.00:07
cloudnullpost refactor the install branch for tempest was the tag "3"00:08
cloudnullit looks like palendae is changing it to master.00:08
cloudnulland hughsaunders  is changing it to a sha00:08
openstackgerritSteve Lewis proposed stackforge/os-ansible-deployment: Test for fixe of Bug: 1425953  https://review.openstack.org/16323800:17
openstackbug 1425953 in openstack-ansible "Unknown var external_vip_address referenced in os-horizon" [High,New] https://launchpad.net/bugs/1425953 - Assigned to Steve Lewis (steve-lewis)00:17
*** sdake_ has joined #openstack-ansible00:19
openstackgerritSteve Lewis proposed stackforge/os-ansible-deployment: Remove unused external_vip_address reference  https://review.openstack.org/16323800:20
*** BjoernT has quit IRC00:42
*** vmtrooper has joined #openstack-ansible01:05
*** vmtrooper has quit IRC01:11
*** devlaps has joined #openstack-ansible01:31
palendaecloudnull: I need to go look to see where that SHA was - I think it should be master, but I haven't reviewed tempest's git log01:50
*** devlaps has quit IRC01:51
cloudnullyea palendae , +2'd your commit because it looks good however when I saw hughsaunders commit i -2 both so that we can nail down what version we want to use.01:53
palendaeYep yep, saw that01:54
palendaeI don't have a strong opinion without looking that stuff up01:54
cloudnullyea, im sitting on my mobile or i'd go look things up too.01:56
palendaeThe dependency changes seem to apply to master, 3, and the SHA01:57
cloudnullso they changed deps on the stable tag ?01:58
palendaeSeemed so; I might have hit other things02:00
palendae`git branch -a --contains 7c73dd5b18d29f0f3f3be0088514121dade53c8f` in tempest says master contains that commit02:01
*** sdake_ has quit IRC02:04
*** sdake_ has joined #openstack-ansible02:05
*** sdake_ has quit IRC02:20
*** sdake_ has joined #openstack-ansible02:41
*** sdake_ has quit IRC02:45
*** vmtrooper has joined #openstack-ansible02:54
*** vmtrooper has quit IRC02:59
*** stevemar has quit IRC03:34
*** galstrom_zzz is now known as galstrom03:57
*** jmccrory has joined #openstack-ansible03:59
*** galstrom is now known as galstrom_zzz04:27
*** vmtrooper has joined #openstack-ansible04:43
*** vmtrooper has quit IRC04:48
*** jmccrory has quit IRC06:20
*** vmtrooper has joined #openstack-ansible06:32
*** vmtrooper has quit IRC06:37
*** prometheanfire has quit IRC08:04
*** mrodden has quit IRC08:18
*** vmtrooper has joined #openstack-ansible08:21
*** mrodden has joined #openstack-ansible08:24
*** vmtrooper has quit IRC08:26
*** vmtrooper has joined #openstack-ansible10:10
*** vmtrooper has quit IRC10:15
odyssey4meso mattt hughsaunders cloudnull palendae andymccr there's a review to switch tempest to master10:39
odyssey4mehowever, I think that'll present us with too much of a moving target10:39
odyssey4memaster currently uses the tempest tag 310:40
odyssey4mebut that tag doesn't include the needful's from the sha that we're using in all the other gates10:40
odyssey4mewe could try pinning to the same sha, or we could just pick the current sha and pin to that10:41
odyssey4methoughts?10:41
odyssey4methe sha we're pinned to in the other branches is dated jan 2010:42
matttodyssey4me: 3 was tagged back in 2014, so what exactly changed that prevents that from installing?10:42
mattt(installing tempest now to see)10:44
odyssey4mebah, no info in the logs - http://logs.openstack.org/84/162984/1/check/os-ansible-deployment-dsvm-check-commit/ebac74e/console.html#_2015-03-10_13_28_40_592 - will have to deploy something myself to see10:45
matttodyssey4me: i'm running tempest on a deploy from yesterday, gimme 510:46
mattt(although this play may take longer than 5)10:46
odyssey4meI would think that it'd be better for us to target the same sha for now, at least, and to include whatever we need to make that happen10:46
odyssey4mewe can move to a later sha when we have this working10:47
matttodyssey4me: https://gist.github.com/mattt416/22f8f6193fa6d10b07fd10:47
odyssey4meah, so oslo.log-1.0.0 is what changed10:50
odyssey4meit was tagged 3 days ago10:50
matttodyssey4me: i'm guessing we need to pin tempest-lib10:52
matttthat's what brought in the oslo.log change10:52
odyssey4meyup, feb 9 they switched to using oslo.log10:52
odyssey4meand tempest doesn't pin tempest-lib10:52
odyssey4meodd though, feb 9 is ages ago10:53
matttodyssey4me: i'm guessing the tag 0.3 was just cut tho10:54
odyssey4memattt nope, also feb 910:54
odyssey4meoh hang on - latest commit if feb 910:55
odyssey4me*is10:55
odyssey4meit may have been cut more recently10:55
matttodyssey4me: i installed http://rpc-slushee.rackspace.com/python_packages/icehouse/tempest_lib-0.2.1-py2-none-any.whl, tempest still doesn't install10:57
matttso pinning that will be useless i guess11:00
odyssey4mewhat's it error out on then?11:01
matttsame error actually11:01
odyssey4medid you try to remove oslo.log as well11:02
matttit doesn't install oslo.log11:04
matttodyssey4me: https://github.com/openstack/oslo.log/commit/21424056763cc72168d5e69a8a0b22eebcb5263811:07
mattt(i think you pointed that out above)11:07
matttodyssey4me: i'm a bit confused, so shouldn't the repo builder stuff take into account the changed requirement?11:08
odyssey4mesure, but it doesn't make sense - if it isn't using oslo.log then why is this a problem?11:08
odyssey4meyeah, I'm confused too11:08
matttodyssey4me: https://github.com/openstack/tempest-lib/blob/master/requirements.txt#L1111:08
matttodyssey4me: so back to understanding why tempest-lib 0.2.1 doesn't install11:09
odyssey4memattt but you tried downgrading to tempest-lib 0.2.1 and it was still failing, right?11:09
mattt(or rather why tempest still doesn't install w/ tempest-lib 0.2.1)11:09
odyssey4mehttps://gist.github.com/mattt416/22f8f6193fa6d10b07fd#file-gistfile1-txt-L3711:10
cloudnullMorning.11:11
mattthowdy cloudnull11:11
odyssey4mecloudnull morning? you're up early11:11
cloudnullFlying home11:12
cloudnullPresently in iad11:12
cloudnullHow's it going?11:12
matttodyssey4me: https://gist.githubusercontent.com/mattt416/cfc71492c88daee9f08d/raw/06c6f1914b60f62a1fdf3e3869baef885d6cffdc/gistfile1.txt11:12
odyssey4memattt cloudnull so I'm thinking of trying this out - just pinning tempest-lib for now to 0.2.1 in playbooks/vars/repo_packages/openstack_other.yml11:12
matttthat's w/ tempest-lib 0.2.1 installed11:12
matttodyssey4me: but actually, i see the prob there11:13
matttit's still trying to resolve tempest-lib from http://172.29.236.3:8181/os-releases/master/tempest_lib-0.3.0-py2-none-any.whl11:13
odyssey4meah, so if we pin it down a level then all will be well with the world again11:13
matttlet me put the tempest_lib in the repo container11:13
matttand see if that helps11:13
matttodyssey4me: yeah i think so!11:13
cloudnullSo tempest isn't lining things and the recent release doesn't work with anything?11:15
odyssey4mecloudnull the master branch of tempest seemed to work ok11:16
odyssey4mebut the branch '3' and the sha we're using in other branches didn't work11:16
cloudnullOh. Can we pin to a more modern sha?11:17
odyssey4methe concern here is that if we pin to master then we open up another can of worms and spend another few months trying to get tempest working across all the tests11:17
odyssey4meso I'm thinking we pin to the same, later-than-3 sha we're using in the other branches11:17
odyssey4mebut we also pin the offending update11:17
cloudnullThis sound sensible.11:17
odyssey4meonce we have a fully working set of tempest tests again, we can try upping the tempest sha to something more recent11:18
matttok i think we have further issues beyond tempest-lib11:18
odyssey4memattt :(11:18
cloudnullI have access to a computer and the interwebs for an hour or so. If I can help let me know.11:20
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Restore tempest install branch to pre-refactor SHA  https://review.openstack.org/16300611:21
odyssey4mecloudnull did I do the package pin for the wheel repo right?11:21
cloudnullBut it sounds like you guys are hot on the trail. So I might just stay out of the way ;p11:22
odyssey4methe actual name of the lib is 'tempest-lib', so the git_dest might or might not be right11:22
odyssey4mebah, broken - let me fix the naming11:22
matttcloudnull: if i manually downgrade a package on my repo container, do i need to do anything for that to become visible?11:22
matttit's still trying to pull down the old package for whatever reason11:23
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Restore tempest install branch to pre-refactor SHA  https://review.openstack.org/16300611:23
odyssey4memattt I think there's an index of some sort? a json file on the repo server?11:23
matttodyssey4me: ah that could be it11:23
cloudnullIf you could add an inline comment stating why the sha it'll be nice for future supportability.11:23
cloudnullIs comments in the top of the file.11:24
cloudnullMatt it'll replicate out if you did it on the first container.11:24
cloudnullRun the repo-build play with the index tag to regent the indexes.11:25
matttodyssey4me: i think pinning to 0.2.1 will work11:26
matttit's just my repo servers are in a bad state now :P11:26
cloudnullMattt: openstack-ansible repo-build.yml --tags repo-html-indexes11:27
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Restore tempest install branch to pre-refactor SHA  https://review.openstack.org/16300611:27
matttodyssey4me: i think we should stay on the tag11:27
matttit's much cleaner than that random sha11:27
matttodyssey4me: if we pin tempest-lib then we should be ok11:28
matttcloudnull: trying now11:28
odyssey4memattt but all other branches are on that sha11:28
matttcloudnull: trying now!11:28
matttcloudnull: i think the idea was to have master point to a bit more current tempest, without being on master itself11:30
mattt^ odyssey4me instead11:30
odyssey4memattt that sha is later that the tag 311:30
odyssey4meso my thinking is we pin to the same sha as the other branches for now, so that we can deal with the issues across all branches with the same method11:30
odyssey4meonce we have all the desired testing working at that sha, we can pin to a later sha in master - we may have to do this for kilo anyway11:31
matttok fair enough11:32
matttcloudnull: yep that worked thanks11:32
matttand now tempest installs with a downgraded tempest_lib 0.2.111:32
cloudnullIn kilo for defcore were likely going to need an even layer release of tempest.11:32
cloudnullBut I agree functional should be the target for sure.11:33
odyssey4meyeah, so for kilo we'll need to pin to a later sha and possibly remove some other pins... but we cross that bridge when we get there11:34
matttyeah11:34
cloudnull+111:34
odyssey4meaha, here's where the sha was set: https://github.com/stackforge/os-ansible-deployment/commit/278ec800c4ad14534ed4406c0cb6900a6a6f779b11:35
cloudnullI made a few issues against the kilo milestone for that very thing already.11:35
odyssey4mecloudnull yeah, we noticed int he triage yesterday11:36
odyssey4meall the kilo bugs have been marked as medium as a placeholder11:36
cloudnullAh nice. Sorry I could be present11:36
odyssey4mewe'll have to properly go through them when we start to focus on Kilo11:36
cloudnullCouldn't11:36
odyssey4meheh, yeah - no worries - it looks like the operators mid-cycle meet was good11:37
cloudnullYup yup. It was.11:37
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Revert "Trim ansible's output to console.log"  https://review.openstack.org/16298411:42
odyssey4mehmm, it would seem that perhaps nodepool is broken again11:48
cloudnullHa. Just can't catch a break :p11:51
odyssey4meno worries - I'll test it manually at least to get some confirmation that it's working11:52
* cloudnull boarding plane see you all soonish. 11:53
andymccrok so11:54
andymccri think we have galera depency issues also :/11:54
andymccrdependency11:54
mattthahaha11:54
matttcloudnull: have a good flight11:54
andymccrlike the gate jobs are failing before tempest even gets run11:54
andymccrThe following packages have unmet dependencies:11:54
andymccr mariadb-galera-server-5.5 : Depends: galera-3 (>= 25.3) but it is not going to be installed11:54
andymccri thought maybe id screwed something up in my swift only deploy11:55
andymccrbut turns out its not just me11:55
andymccrso....11:55
odyssey4mehmm, master doesn't have a pinned galera any more :(11:55
andymccrif i dont respond for the next while its totally because i threw my laptop against a wall11:55
odyssey4mebut the repo it's using should have everything it needs11:55
matttandymccr: did you say something, i was afk banging my head against the wall11:55
mattt:P11:55
andymccrsrsly... k11:56
andymccrupdate my daily thing - blocked on all the dependency things11:56
andymccrholidaying.11:56
odyssey4meodd, http://mirror.rackspace.com/mariadb/repo/5.5/ubuntu/pool/main/g/galera-3/11:59
*** vmtrooper has joined #openstack-ansible11:59
odyssey4methe package is there and if it depends on it, surely it should fine it?11:59
odyssey4me*find11:59
odyssey4meI have an AIO building from scratch right now - will let you know if it bombs.12:00
matttalso have a build going through right now12:00
matttyep it bombed12:01
odyssey4memattt same dep missed?12:01
mattt   odyssey4me yeah12:02
matttodyssey4me: http://134.213.53.6:8080/job/dev-heat-ansible/28/console12:02
odyssey4meE: Unable to correct problems, you have held broken packages.12:04
*** vmtrooper has quit IRC12:04
odyssey4meI have seen this before when the apt cache wasn't updated after the repo was added - essentially it ends up with packages from the trusty repo instead of the mariadb repo, then at a point it can't install the mariadb packages because the right bits aren't there.12:05
matttodyssey4me: that may be it, becuase if i manually install mariadb-galera-server-5.5 it goes fine12:06
odyssey4memattt is that after an 'apt-get update', or did you just 'apt-get install' and it worked?12:06
matttodyssey4me: i actually just did an apt-get install, no update12:07
cloudnullJust checked back are the rax mirrors jacked up? Should we move master back to upstream marria  repos instead of using our supposed pinned ones?12:11
odyssey4meodd mattt I have exactly the same thing - apt-get install mariadb-galera-server-5.5 just works12:11
andymccrok well i'll ask for a tl;dr on how to fix that after i get back from having some lunch :D12:11
odyssey4mebut for ansible it does not12:12
andymccrteam team team.12:12
odyssey4mecloudnull in master we have no pinning at all right now for mariadb12:12
odyssey4methat's part of the whole discussion around whether pinning belongs inside the project or not12:12
odyssey4methis problem seems to be a little different12:13
cloudnullBut the repo is the rax  repo which is supposed to be a maria mirror12:13
odyssey4mecloudnull it is, and it works12:13
odyssey4mejust for some reason it's not working in the ansible play12:13
cloudnullAh.12:13
cloudnullIf you rerun the play does it work ?12:14
odyssey4metrying that now12:14
*** markvoelker has joined #openstack-ansible12:14
cloudnullOr only by hand does it succeed?12:14
cloudnullOk12:14
odyssey4meI checked the apt-cache policy first, and the right repo was there and apt knew about it12:15
odyssey4menope, not working - let me try a few things here12:16
*** britthouser has quit IRC12:18
cloudnullWelp  that sux12:19
odyssey4meok, easy fix and root cause is amusing12:19
odyssey4methe package galera is now galera-312:19
cloudnullAnd the dep  is not getting the correct package name ?12:20
odyssey4me'galera' is coming from somewhere else12:20
cloudnullOr were calling it by the transition package ?12:20
odyssey4meand that's breaking it somehow12:20
odyssey4mewaiting for my play to finish to look12:21
matttwe must pass in galera12:21
odyssey4megalera only has the debian builds: http://mirror.stshosting.co.uk/mariadb/repo/5.5/ubuntu/pool/main/g/galera/12:21
matttwe specify 'galera' in teh galera_apt_packages list12:21
odyssey4meit seems that the packages got renamed12:21
matttso we need to update that12:21
odyssey4meyeah mattt so that's what I updated to 'galera-3' to make it wor12:22
odyssey4me*work12:22
cloudnullWell this is all good. Its better to know this now and to know it in master ;)12:22
matttyeah but we should go back to pinning in master :x12:22
odyssey4meso here's the question - how do we get two upstream breaks past the gate to merge the fixes?12:22
cloudnullNot in some stable release in a customer deployment.12:22
matttodyssey4me: haha12:23
cloudnullMattt I disagree on pinning apt packages in master.12:23
matttcloudnull: really12:23
matttbut then we're chasing this sort of stuff all day long12:23
matttodyssey4me: i imagine we have to double up a commit to fix both :(  dirty but what other options?12:23
odyssey4meperhaps I could do a patch to fix galera, but also disable tempest temporarily - then a subsequent patch to re-enable tempest and apply the fixes there?12:23
cloudnullIt should be relatively unstable and our pins will likely not be someone else's pins in productions.12:23
odyssey4meat least then the patches are still focused on one issue at a time12:24
cloudnullRax  should pin , others that use this system should pin. But to what they pin should be up to them.12:24
matttodyssey4me: seems long-winded, i'd rather just fix both and not disable gating12:25
cloudnull+1 single patch commit message "fixes gating..." And be done with it.12:26
odyssey4meok, will sort that out now then12:26
andymccrunfortunately, i think we should do that. in general though probably not the best, but srsly what are the odds of this shit happening at the same time12:26
odyssey4meI guess juno and icehouse aren't affected, as they're still pinned12:26
andymccris tempest pinned odyssey4me?12:26
andymccrlike the packages for tempest.12:26
andymccrin juno/icehouse12:26
andymccrgalera should be ok12:27
matttandymccr: yes but not tempest_lib12:27
matttthat change will need to get backported12:27
odyssey4me^ what mattt said12:27
andymccrcool yeh thought that was the case12:27
odyssey4mebut we can do a modified cherry-pick I guess12:27
odyssey4meor a fresh patch for juno and cherry pick that back to icehouse12:27
matttafk for a bit12:30
cloudnullI'd say fresh patch to Juno cherry pick to icehouse. At this point were only Pretending that we can cherrypick from master to Juno.12:30
cloudnullOK so it seems that the plane has sat on the tarmac for the requisite amount of time and the captain has been sufficiently convinced to fly the thing. So now I'm going to go. Afk for a few hours.12:31
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Fix gate: tempest and galera updates  https://review.openstack.org/16300612:35
odyssey4mewhile I wait for that build - time for lunch... afk for a bit12:38
*** KLevenstein has joined #openstack-ansible12:39
*** galstrom_zzz is now known as galstrom12:43
*** KLevenstein has quit IRC12:43
*** KLevenstein has joined #openstack-ansible12:47
*** galstrom is now known as galstrom_zzz13:11
matttodyssey4me: will cloudnull need to remove his -1 before we can merge https://review.openstack.org/163006?13:13
matttmaybe he'll have arrived before gate jobs have run :P13:13
*** sdake_ has joined #openstack-ansible13:15
sdake_morning13:16
odyssey4memattt yeah, he'll have to remove the -2 before it can merge13:20
matttsdake_: good morning to you13:20
*** vmtrooper has joined #openstack-ansible13:48
*** vmtrooper has quit IRC13:53
*** Mudpuppy has joined #openstack-ansible14:19
palendaeodyssey4me: Just back. Your patch duplicates https://review.openstack.org/#/c/163194/14:21
palendaeOr not14:21
palendaeYou pin lib, I pin oslo.context14:22
*** Mudpuppy has quit IRC14:22
palendaeHeh, and I emailed hugh and andy hoping this wouldn't get duplicated again today14:22
*** Mudpuppy has joined #openstack-ansible14:23
odyssey4mepalendae yeah, so mattt and I have been looking into it today..14:24
palendaeI noticed14:24
odyssey4meyou'll notice that there was also a galera issue, which we've resolved14:24
palendaeI didn't see that manifesting yesterday, but yeah14:25
odyssey4mealso, I've aimed to pin tempest at the same sha as we do in the other branches - that way we are able to get tempest to the right level of completeness in all branches before we go adventurating to newer sha's for tempest.14:25
palendaeSo did you see the patch and it was insufficient, or?14:25
matttpalendae: yeah we saw both14:25
palendaeOk, just making sure14:26
odyssey4meyour method is good if we're choosing to move to using the moving target of master and changing the other dependancies with it14:26
palendaeodyssey4me: Not the tempest pin14:26
palendaeEverything else14:27
odyssey4mepersonally I don't think we should be doing that just yet14:27
palendaeIgnoring the tempest sha14:27
palendaeThe requirements fixes14:27
matttpalendae: we figured it didn't make sense to pin an oslo library because it was getting pulled in by a non-pinned tempest_lib14:27
palendaeOk14:27
*** sigmavirus24_awa is now known as sigmavirus2414:27
palendaeSo we have competing patches14:27
odyssey4meyeah, everything else was primarily there because of the tempest switch to master, or because of tempest-lib having no cap in the requirements14:28
palendaeWhat I was trhying to avoid was one side of the ocean knowing something and the other having to wait14:28
palendaeWhich is where I was stuck yesterday afternoon14:28
palendaeI guess I'll toss those few hours of work then14:28
odyssey4mewell, I was kinda thinking it'd be good to get to a point of having two approaches to discuss when y'all came online :)14:29
palendaeI guess that's fair14:29
odyssey4metwo working approaches :)14:29
palendaeIt is reasonable to pin tempest-lib14:30
palendaeI was seeing requirements failures on both 'the SHA' and master14:30
palendaeI get what you're saying about master being a moving target; either's better than '3' IMO14:30
palendaeSince '3' doesn't have the neutron tests that we need14:30
matttpalendae: i think not addressing tempest_lib doesn't solve the problem14:30
palendaeOk14:31
palendaeWould you mind commenting on the review so it's documented?14:31
matttpalendae: rather, i think it may not solve the problem long-term14:32
palendaeSame request :)14:32
matttbecause it's oslo.context <- oslo.log <- tempest_lib14:32
matttso without controlling tempest_lib you don't control the other two14:33
palendaeOk14:33
palendaeWould you mind putting that on my review>14:33
matttpalendae: sure14:33
odyssey4megood call :)14:34
odyssey4mepalendae agreed on not using 3, and in fact for this project I would recommend that we always target something specific at least on a per sprint basis14:34
palendaeThat's reasonable14:34
mattti was less concerned about using 3 :P14:35
palendaeBetter to have a known quantity14:35
palendaemattt: You weren't writing neutron tests then :)14:35
palendaeOur master and juno weren't on parity for tests14:35
odyssey4meso I would certainly advocate targeting a newer sha if we need to, but for now we don't know whether we need to14:35
palendaeNewer than the 7.... ?14:35
odyssey4mepalendae yep14:37
palendaeGotcha14:37
palendaeI'm for 'the SHA'14:37
odyssey4meif you say you do need newer than that for neutron to work, then I'm down with that - for all branches though, which will be fun (not!)14:37
palendaeThough left a comment about the SHA being in the role14:37
palendaeNo, the 7 one works for juno at least14:37
palendaeI'm less concerned about icehouse right now14:38
palendaeAgreed that maintaining pins for all branches will be a pain, but it's also kind of the nature of the beast14:38
odyssey4meok palendae mattt let me ensure I understand you correctly - you're suggesting that in the role we default to something like master, but that in the user_config we override that for the gate?14:39
palendaeodyssey4me: It's being pinned here https://review.openstack.org/#/c/163006/5/playbooks/vars/repo_packages/openstack_services.yml14:40
matttit just looks cleaner not having the sha as a default value14:40
matttand as palendae says we are already overriding it14:40
matttso from a gate perspective nothing needs changing14:41
odyssey4meah fair enough - the wheel repo only provides one version to install anyway14:41
palendaeYeah14:41
odyssey4methe stuff in the defaults is only used if the frozen repo isn't used14:41
odyssey4me(I guess)14:41
palendaeI actually don't know if they've done a tag newer than 314:42
odyssey4mepalendae they haven't14:42
palendae=\14:42
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Fix gate: tempest and galera updates  https://review.openstack.org/16300614:48
odyssey4meI've updated the commit message to try to explain everything more clearly.14:48
odyssey4meand also removed the role default pin target change, so it stays at master14:49
matttsweet14:51
palendaeodyssey4me: I +1'd the review. You guys changed my mind, I think your patch is the better approach :)14:58
*** stevemar has joined #openstack-ansible15:02
odyssey4mepalendae :)15:02
odyssey4memattt and hughsaunders have wasted many hours on tempest15:03
odyssey4medon't fall into the trap :p15:03
odyssey4mebut it'd be nice to see networking working ;)15:03
palendaeIt would15:04
palendaeI also got bitten because '-s' is not '--serial'15:04
palendaeSo I think a bunch of failures I was seeing were invalid15:04
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Revert "Trim ansible's output to console.log"  https://review.openstack.org/16298415:04
*** galstrom_zzz is now known as galstrom15:25
*** vmtrooper has joined #openstack-ansible15:36
Apsupalendae: For this I blame you :)15:38
palendaeyeah, that was my fault15:39
palendaeI will take the blame for that one15:39
Apsuhehe15:39
*** vmtrooper has quit IRC15:42
*** jwagner_away is now known as jwagner15:42
*** britthouser has joined #openstack-ansible15:48
openstackgerritEvan Callicoat proposed stackforge/os-ansible-deployment: Enable offline compression for resource files  https://review.openstack.org/16318315:56
matttApsu: the only blame we do in here is a git-blame16:01
Apsumattt: Uh oh. Time to cover my digital tracks16:02
palendaegit config --global user.name "Not It"16:03
Apsu^16:03
cloudnullJust landed and removed my -216:04
cloudnullHopefully gate completes sometime today ;)16:04
matttcloudnull: :)16:05
palendaecloudnull: Did you give a +2?16:05
palendaeOr just a 0? :)16:05
cloudnullNope16:06
cloudnull+116:06
odyssey4me+1 until gate succeeds16:06
cloudnullWaiting on gate16:06
palendaeOk16:06
cloudnullAre we abandoning https://review.openstack.org/#/c/163194/16:12
palendaecloudnull: yes16:12
cloudnullOK. So I'll leave my -2 as is.16:13
palendaecloudnull: Writing the abandon message now16:13
cloudnullKk16:13
*** britthouser has quit IRC16:13
*** erikmwilson has quit IRC16:13
*** d34dh0r53 has quit IRC16:13
*** sdake__ has joined #openstack-ansible16:13
*** matt__ has joined #openstack-ansible16:14
*** darrenc_ has joined #openstack-ansible16:14
*** bgmccollum has quit IRC16:14
*** lbragstad has quit IRC16:14
*** jmeridth has quit IRC16:14
*** b3rnard0 has quit IRC16:14
*** odyssey4me has quit IRC16:14
*** jroll has quit IRC16:14
*** darrenc has quit IRC16:14
*** mattoliverau has quit IRC16:14
*** dolphm has quit IRC16:14
*** erikmwilson has joined #openstack-ansible16:15
*** b3rnard0 has joined #openstack-ansible16:15
*** d34dh0r53 has joined #openstack-ansible16:15
*** bgmccollum has joined #openstack-ansible16:15
*** jroll has joined #openstack-ansible16:15
*** dolphm has joined #openstack-ansible16:15
*** lbragstad has joined #openstack-ansible16:15
*** jmeridth has joined #openstack-ansible16:15
*** britthouser has joined #openstack-ansible16:16
*** odyssey4me has joined #openstack-ansible16:16
*** jroll has quit IRC16:16
*** jroll has joined #openstack-ansible16:16
*** sdake_ has quit IRC16:17
*** jmccrory has joined #openstack-ansible16:19
*** jwagner is now known as jwagner_lunch16:21
*** jwagner_lunch is now known as jwagner_away16:22
daneyonIf I am running my network_host on the same server as my compute_host, can I still follow the instructions for adding a compute host: http://docs.rackspace.com/rpc/api/v10/bk-rpc-installation/content/sec-operations-add-compute-host.html16:24
daneyonJust add the neutron-all playbook run?16:24
Apsudaneyon: Should be able to mix and match host 'roles' at will.16:27
ApsuThat's why AIOs work. There's some minor caveats in a full AIO (which is why we have scripts for ours, such as for gating), but for your purpose probably will Just Work™16:28
ApsuLet us know if not16:28
*** galstrom is now known as galstrom_zzz16:32
*** sdake_ has joined #openstack-ansible16:33
*** sdake__ has quit IRC16:37
daneyonApsu: thanks!16:38
ApsuSure thing!16:38
*** britthouser has quit IRC16:39
odyssey4mewe have a winnner: https://review.openstack.org/163006 :)16:40
Apsuyey16:41
*** openstack has joined #openstack-ansible16:56
odyssey4meoh dear, several requirements updates going on in openstack - expect more breakage :/17:03
*** jwagner_away is now known as jwagner17:14
*** vmtrooper has joined #openstack-ansible17:25
*** vmtrooper has quit IRC17:31
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Dont look for used_ips on containerless hosts  https://review.openstack.org/16308317:38
*** nosleep77 has joined #openstack-ansible17:38
*** devlaps has joined #openstack-ansible17:42
*** jmccrory has quit IRC17:42
openstackgerritNolan Brubaker proposed stackforge/os-ansible-deployment: Enable network basic ops tests  https://review.openstack.org/16354417:48
*** stevemar has quit IRC18:04
*** stevemar has joined #openstack-ansible18:05
*** jmccrory has joined #openstack-ansible18:08
*** galstrom_zzz is now known as galstrom18:27
*** jaypipes is now known as jaypipes-afk18:34
*** galstrom is now known as galstrom_zzz18:36
*** jmccrory has quit IRC18:39
*** jmccrory has joined #openstack-ansible18:39
jwagneri stopped all the services on the cimputes18:40
jwagneroops wrong channel18:41
palendaereviews plz https://review.openstack.org/#/c/163544/18:45
*** galstrom_zzz is now known as galstrom18:50
*** jmccrory has quit IRC19:02
*** sdake__ has joined #openstack-ansible19:08
*** sdake_ has quit IRC19:12
*** vmtrooper has joined #openstack-ansible19:14
*** vmtrooper has quit IRC19:19
*** galstrom is now known as galstrom_zzz19:20
*** jmccrory has joined #openstack-ansible19:31
palendaeIs there a place I can check my review's place in the zuul line?19:33
stevellemaybe at http://status.openstack.org/zuul/19:38
palendaestevelle: Thanks!19:38
*** galstrom_zzz is now known as galstrom19:41
*** BjoernT has joined #openstack-ansible19:52
BjoernTquick questions, if I want to rewrite the openrc in all containers with ansible, what would be the best way ? a custom playbook with just few common roles?19:53
stevellesounds good, targeting should be easy enough if you just want all containers19:56
*** galstrom is now known as galstrom_zzz19:56
bgmccollumBjoernT: is this a one off?20:00
jwagnerodyssey4me are u around?20:05
jwagnerls20:05
openstackgerritMerged stackforge/os-ansible-deployment: Fix gate: tempest and galera updates  https://review.openstack.org/16300620:10
*** galstrom_zzz is now known as galstrom20:13
palendaehttps://jenkins07.openstack.org/job/os-ansible-deployment-dsvm-check-commit/72/ !!! neutron tests passing on the gate20:36
palendaeHasn't updated gerrit yet though20:37
*** sdake__ has quit IRC20:51
*** sdake_ has joined #openstack-ansible20:53
daneyonI deployed v10. The initial deployment was 3 controller nodes clustered. These nodes were not running the neutron api. I added 2 combined network/compute hosts using the add-host, nova-all, neutron-all playbooks. The plays all ran successfully, but the nova-api containers never were updated to communicate with the neutron-api containers. SO, I ran the openstack-setup play again, but still the nova-api containers were n21:02
daneyonever updated with the neutron container info. Am I missing something?21:02
*** vmtrooper has joined #openstack-ansible21:03
*** vmtrooper has quit IRC21:08
daneyoncloudnull ^21:08
palendaedaneyon: They were adding to the user_config.yml file?21:11
palendaeadded*21:11
daneyonpalendae: yes: network_hosts: compute-server71: ip: 192.168.220.71 The compute hosts have the neutron containers running. That seems to work. But updtaing the existing 3 control nodes (separate hardware) seems to be missing. The nova api containers running on my 3 controllers do not know how to speak with the neutron api (running on compute 71 and 73) because nova.conf was never updated with the req info and the necess21:14
daneyonary services restarted.21:14
daneyonpalendae: So, I was wondering of I missed a step, but I have successfully ran all the plays- add-host, nova-all, neutron-all. The I reran openstack-setup and still don;t see the nova-api containers updated with the info needed to talk to the neutron api container21:16
andymccrdaneyon: are you using the haproxy loadbalancer?21:17
daneyonandymccr: how funny, I just thought about that. I think i need to update the haproxy node. let me try that21:18
andymccrlet me know if thats not it21:19
daneyonandymccr: that was it. I keep forgetting to update my haproxy host... urgh!21:20
andymccri do that pretty much all the time. i think its probably because we never really made the haproxy as a "permanent" solution but more of a "do this so we can see it work and dev on it"21:20
andymccrbut it should probably be fixed/updated to be a bit better21:20
daneyonandymccr: If I wanted to run the neutron api on my controller cluster and run the agents on compute nodes, do the playbooks support this?21:22
daneyonandymccr: I can del with it for now. If all goes well with my eval, I should be able to make the load-balancer a 1st class citizen in the project.21:23
palendaeyeah, haproxy isn't really supported. It's there and kinda works21:23
daneyondeal21:23
palendaeI think it's mostly for AIOs really21:23
daneyonI like some of the new service discovery stuff that works well with haproxy and I need to have a good open source server load-balancing option. I can deal with that stuff after getting through the basics.21:25
*** matt__ is now known as mattoliverau21:25
daneyonI come from a Puppet background, so I'm trying to bring muyself up to speed with Ansible and understand all the awesome work y'all have accomplished.21:25
*** darrenc_ is now known as darrenc21:26
*** galstrom is now known as galstrom_zzz21:30
*** jmccrory has quit IRC21:31
*** jmccrory1 has joined #openstack-ansible21:31
andymccrdaneyon: re: the neutron question, i don't think its possible from what i can see - cloudnull will probably correct me on that :)21:34
*** sc has quit IRC21:40
*** Mudpuppy has quit IRC21:45
*** sdake_ has quit IRC21:46
*** sdake_ has joined #openstack-ansible21:48
*** sdake_ has quit IRC21:48
*** sdake_ has joined #openstack-ansible21:48
daneyonandymccr: I'm reviewing the neutron configs and I see that physical_interface_mappings in ml2 conf. I thought eth10 is used within the agents container and I figured that eth10 would be in the conf file.21:48
daneyonandymccr: I'm a little fuzzy on where the neutron public network fits into this. If the vxlan network is used to interconnect the instances between hosts, where do I specify a network to use for floating ips. I'm used to bringing a network to eth1 on compute hosts running the neutron agents used for floating ips21:50
*** KLevenstein has quit IRC21:56
daneyonpalendae ^22:00
*** nosleep77 has quit IRC22:00
*** sdake_ has quit IRC22:00
daneyonpalendae andymccr nm I figured out my question22:01
*** jwagner is now known as jwagner_away22:09
*** nosleep77 has joined #openstack-ansible22:22
*** movielovers has joined #openstack-ansible22:23
*** movielovers has left #openstack-ansible22:23
*** jwagner_away is now known as jwagner22:31
*** jaypipes-afk is now known as jaypipes22:31
*** BjoernT has quit IRC22:31
*** vmtrooper has joined #openstack-ansible22:52
*** sdake_ has joined #openstack-ansible22:55
*** vmtrooper has quit IRC22:57
*** sdake__ has joined #openstack-ansible22:57
*** sdake_ has quit IRC23:00
*** jwagner is now known as jwagner_away23:02
*** sdake__ has quit IRC23:06
bgmccollumany reason why the swift *-server.conf files don't have a [*-replicator] section? the replicator services are not starting...23:08
*** sdake_ has joined #openstack-ansible23:09
*** sdake_ has quit IRC23:14
bgmccollumor maybe something else is amuck...either way replicators (and a few other) services arent running23:15
andymccrbgmccollum: are you running master?23:18
bgmccollum10.1.223:18
andymccris replication-network specified in your user_config or swift config?23:18
bgmccollumnot explicitly...23:18
bgmccollumlet me check23:18
bgmccollum    storage_network: 'br-storage'23:19
bgmccollum    replication_network: 'br-storage'23:19
andymccrok cool. so there is a bug that has already been fixed but wasnt backported23:20
andymccrif you specify replication_network to be the same as storage_network it will treat it like a dedicated replication network but since it tries to start 2 services on the same IP/Port the second (replicator) fails23:20
bgmccollummakes sense23:21
andymccrif you had a dedicated replication network the replicator conf would be split into a second conf (which ahs happened here) but would be on a separate ip23:21
andymccrso it wouldn't conflict and would start fine23:21
andymccrits been fixed in that it will now check and if they are the same will not split out the conf23:21
bgmccollumso nix the repl network23:21
andymccryeh23:21
bgmccollumcool23:21
andymccryou "might" have to do some manual remova;l of the dedicated replicator confs23:21
andymccrwhich other services arent started?23:22
bgmccollumas is...i dont see a single conf file for object / account / container servers23:22
bgmccollumno replicator specific confs23:22
bgmccollumrather I *only* see a single conf for ...23:23
andymccroh weird...23:23
andymccri mean it should either dump down the conf file incl replicator or not at all in which case replicator goes into the server specific confs23:23
andymccrhmm wonder if the fix didnt work properly for 10 branch23:23
bgmccollumi see what it should be doing, but isn't haha23:24
andymccrif the conf still has a conditional that is incorrect it wont drop the new conf or the replicator section23:24
bgmccollumi have to run, ill poke it some more this evening23:24
andymccrlemme check23:24
andymccrbut yeh drop the replication_network and it should work23:24
bgmccollumok...thanks23:24
*** sdake_ has joined #openstack-ansible23:26
*** jmccrory1 has quit IRC23:28

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