Tuesday, 2015-03-24

*** markvoelker has joined #openstack-ansible00:02
*** sdake has quit IRC00:22
miguelgrinbergcloudnull: quick question when you have a moment. I updated the git tag for horizon in vars/repo_packages/openstack_services.yml and then launched the repo-server play, expecting it will add a wheel for the new version I requested. But it does not seem to work that way. What do I need to do to add a new version to the repo-server?01:01
palendaemiguelgrinberg: I think I had to use repo-install01:09
miguelgrinbergpalendae: oh, okay, let me try that01:09
palendaeOh, http://git.openstack.org/cgit/stackforge/os-ansible-deployment/tree/playbooks/repo-build.yml01:09
palendaerepo-build does the packages01:10
miguelgrinbergyeah, seems repo-build is the one, thanks01:11
*** appprod0 has joined #openstack-ansible02:11
*** appprod0 has left #openstack-ansible02:11
cloudnullMiguelgrinberg did you make it go?02:17
*** jsm has quit IRC02:26
*** hj-hp has quit IRC02:41
miguelgrinbergcloudnull: yes, it worked, but have a bunch of other dependencies that I need to bring. I think I'm going to wait until your patch lands, you've done all the work already.02:50
palendaeShould probably have all the people doing individual services reviewing the configs02:52
*** jsm has joined #openstack-ansible02:58
cloudnullYea the kilo patch is the basic kilo functionality once that's we'll need to go through the individual services and make sure they are prod ready.03:10
cloudnullThat'll take a bit03:11
cloudnullAlso there will need to be some discovery because several APIs are now deprecated in kilo. Which will effect our upgrade process.03:11
cloudnullPalendae assuming the minimal kilo patch goes through all of the configs are going to need further review and a lot of testing.03:13
palendaeYeah03:14
*** galstrom_zzz is now known as galstrom03:14
*** galstrom is now known as galstrom_zzz03:33
*** sdake has joined #openstack-ansible03:36
*** sdake has quit IRC03:42
*** sdake has joined #openstack-ansible03:44
*** sdake has quit IRC03:55
*** ishant has joined #openstack-ansible04:48
*** stevemar has quit IRC07:58
*** markvoelker has quit IRC10:26
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment-specs: Adds swift_standalone for Juno spec  https://review.openstack.org/16685411:05
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Allow swift stand alone to be installed for Juno  https://review.openstack.org/16717011:09
*** markvoelker has joined #openstack-ansible11:26
*** markvoelker has quit IRC11:31
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Fix dedicated replication network logic  https://review.openstack.org/16717711:33
openstackgerritDarren Birkett proposed stackforge/os-ansible-deployment: Add support for passing api version to glance module  https://review.openstack.org/16718811:58
*** markvoelker has joined #openstack-ansible11:58
*** KLevenstein has joined #openstack-ansible12:05
*** jaypipes has quit IRC12:06
*** jaypipes has joined #openstack-ansible12:07
*** galstrom_zzz is now known as galstrom12:09
openstackgerritDarren Birkett proposed stackforge/os-ansible-deployment: Add support for passing api version to glance module  https://review.openstack.org/16718812:14
openstackgerritDarren Birkett proposed stackforge/os-ansible-deployment: Add support for passing api version to glance module  https://review.openstack.org/16718812:16
*** ishant has quit IRC12:36
openstackgerritAndy McCrae proposed stackforge/os-ansible-deployment: Fix dedicated replication network logic  https://review.openstack.org/16719812:45
*** galstrom is now known as galstrom_zzz12:56
*** gregdek has joined #openstack-ansible13:01
*** dstanek has joined #openstack-ansible13:33
*** Mudpuppy has joined #openstack-ansible14:07
*** sdake has joined #openstack-ansible14:10
cloudnullmattt: ping14:10
cloudnullit seems that im replying to your inline comments as your writing them14:10
cloudnull:)14:10
matttcloudnull: oops :P14:10
matttcloudnull: sorry for the barrage of comments14:10
cloudnullno, on the contrary, bring them on14:11
matttcloudnull: i guess the main concern mancdaz and i had was the glance v1 deprecation14:11
matttis that absolutely necessary in this commit?14:11
cloudnullit is. because of `fatal_deprecations`.14:11
cloudnullglance / cinder v1 have been deprecated and the services will not start because of it14:12
mancdazcloudnull deprecated !+ unsupported14:12
matttcloudnull: hmm, when i updated my checkout to re-enable v1 glance restarted fine14:12
mancdaz!=14:12
openstackmancdaz: Error: "=" is not a valid command.14:12
matttcloudnull: the same applied to cinder, everything continued to work afterwards14:12
mancdazok deprecated doesn't mean you HAVE to remove now14:12
mancdazwe have committed in 11.0.0 to as little end user impact as possible14:13
cloudnullmancdaz it does when we have fatal_deprecations on the gate job14:13
mancdazthe only reason we're being forced down this route is because we arbitrarily turned on fatel deps14:13
cloudnullright.14:13
mancdazso let's turn that off and reduce the scope of this change14:13
git-harryYeah, I'm not convinced by using fatal deprecations14:13
mattti have fatal deprecations on and didn't run into those issues14:13
*** KLevenstein has quit IRC14:14
mattt(i built using the AIO script)14:14
git-harrymattt: you won't unless you run the appropriate bit of code14:14
cloudnull^14:14
matttok but i hit v1 api afterwards14:15
matttand it returned a response14:15
*** sigmavirus24_awa is now known as sigmavirus2414:15
mancdazno matter - we can't just drop glance api v1 support in this release14:15
mancdazsame for cinder14:15
cloudnullwell we can in the project, its configurable for that reason.14:15
cloudnullbut if we remove the toggle for the gate job then we can ship with cinder/glance v1.14:16
cloudnullyou'll also notice that ec2 and s3 api's have been removed, due to deprecations.14:17
mattti haven't gotten that far yet :P14:17
cloudnullbut its not like those worked anyway14:17
mattt(got sidelined trying to get those scenario tests to pass)14:17
cloudnullmattt the scenario tests will not pass at this point.14:18
matttcloudnull: why is that?14:18
matttcloudnull: i'm running into networking issues on my AIO, so i couldn't properly test them14:18
matttcloudnull: i also commented on bumping tempest sha, i'm wondering if we're a bit premature on that one14:19
cloudnullmainly because of cinder interacting with quota options that cause it to fault. and a couple of the neutron tests do not pass because the expected output is incorrect.14:19
cloudnullmattt i replied on that comment.14:19
matttcloudnull: wonder if the quota issues go away if we go back to v1?14:20
cloudnullthe old sha is no longer compatible because it has dependencies that are below what kilo requires.14:20
matttcloudnull: ok that makes sense14:20
cloudnullas for cinder and the quota issues. its only because of fatal deprecations.14:20
*** git-harry has quit IRC14:21
matttcloudnull: yep14:21
cloudnulland cinder seems to have a bug at this stage.14:21
mancdazthis is also outside of the scope of the initial spec14:21
*** git-harry has joined #openstack-ansible14:21
mancdaz"No changes to the current testing and or gating framework will be made. The minimum viable Kilo deployment will be required to pass the same gate tests as are required by our production systems."14:21
cloudnullmancdaz its certainly in scope, if we adhere to what we're presently set to gate on.14:21
cloudnullmancdaz its passing the same multi-node commit tests instead of the scenario tests.14:22
mancdazcloudnull these are not the tests we are looking for14:22
* mancdaz waves hand14:22
cloudnullhaha14:22
matttoh no you di'int14:22
cloudnullbut it wont pass.14:22
cloudnulland we cant use the older tempest sha that we know works14:23
cloudnullso we iterate or we stagnate.14:23
cloudnullim for removing the fatal deprecations.14:23
mancdazyes14:24
cloudnulland setting v1 cinder glance to enabled by defaultl.14:24
*** hughsaunders has quit IRC14:24
mancdazwe are being forced down an unwanted path by this14:24
mancdazyes!14:24
cloudnullbut if we reimplement it, this is whats coming :)14:24
mancdazsure thing - but that's in a more controlled manner with proper informed decisions around what's coming14:24
matttcloudnull: regarding glance v214:25
cloudnullthat said, we still wont be able to pass the scenario test.14:25
*** hughsaunders has joined #openstack-ansible14:25
mattt'nova image-list' didn't even work for me14:25
mattthow do you pass it a version?14:25
*** claco has joined #openstack-ansible14:25
mancdazcloudnull I'd love to be able to pass the scenario tests, and tbh they will need to pass for the release, so assuming we go back to v1 glance/cinder, is it not possible to get those tests passing then?14:26
mancdazas in, what would still be broken that would not allow those tests to pass?14:26
cloudnullneutron i would suspect14:27
cloudnullthe tests themselves pass, be a few of them are returning a 200 when tempest expects a 20214:27
mancdazcloudnull upstream must be passing with the current b3 code though?14:28
cloudnulli would suspect they aren't running the same tests.14:28
mancdazso mostly we think some neutron tests might not pass - perhaps it's worth spending a bit of time (after going back to v1 apis) trying to get this stuff going. At least we can get a clear answer about what upstream is doing and why we might absolutely need to change the tests that we have in the gate for the short term14:30
mancdazchanging tests because the ones we want to pass are failing, seems such wrong14:30
*** git-harry has quit IRC14:31
cloudnullit does seem wrong, but we're also testing on a mid release version of tempest that is likely broken in some fun ways.14:31
andymccrso wrong that it has angered git-harry to a state where he had to leave!14:31
cloudnulland i think we should get kilo to be operational and then we can re-introduce the tests that the system should be passing.14:32
cloudnullwhile everyone is in a reviewing mood. please go review https://review.openstack.org/#/c/166095/ and https://review.openstack.org/#/c/166574/14:37
*** git-harry has joined #openstack-ansible14:38
cloudnullwith https://review.openstack.org/#/c/166095/ of particular interest because it seems that with that change neutron gating is passing more often than not.14:38
mattti'm reviewed out14:38
palendae-1s all around14:40
*** KLevenstein has joined #openstack-ansible14:40
matttcloudnull: i'm still on the fence w/ that rpc/api_workers change, i've been running those settings in the heat multi node and still get sporadic neutron failures14:40
Apsumattt: It definitely still fails with just rpc_workers = 0.14:40
cloudnullsporadic seems to be better than roughly 50% of the time.14:40
*** sdake__ has joined #openstack-ansible14:41
palendaeSounds like it's true that this doesn't fix it completely, but it does succeed more than it did14:41
ApsuI just +1'd it because even though it's not the final answer, it's still the correct change to make.14:41
ApsuWorking on the bigger swap change now, because that's another failure reduction.14:42
mattthaha14:42
matttok i can get on board w/ that14:42
palendaeI think it's got more impact on AIOs vs the multinode tests from what you're saying mattt14:43
palendaeIs that accurate?14:43
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Removes the fatal_deprecations from the gate job  https://review.openstack.org/16725714:43
*** sdake has quit IRC14:44
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Removes the fatal_deprecations from the gate job  https://review.openstack.org/16725714:46
matttpalendae: that sounds right14:47
*** git-harry has quit IRC14:47
*** git-harry has joined #openstack-ansible14:47
palendaecloudnull: Did you just rebase that?14:47
palendaeHas the workers change in bootstrap-aio.sh14:47
cloudnulli did for the deps14:48
sigmavirus24Anyone going to look at https://review.openstack.org/#/c/166574/ ?14:48
*** stevemar has joined #openstack-ansible14:48
sigmavirus24o/ stevemar14:49
*** git-harry has quit IRC14:50
*** git-harry has joined #openstack-ansible14:50
stevemarsigmavirus24, o/14:50
Apsupalendae: mattt: cloudnull: Digging into the actual root cause, with debug = True. Time to drink from the firehose14:51
matttcloudnull: didn't want to just revert the actual commit for the fatal deprecations stuff?14:52
palendaeDrink deep14:52
matttcloudnull: i think we leave some cruft behind by not reverting14:53
cloudnullthe vars that were added to the roles are valuable.14:53
cloudnullwe can turn it on in testing locally using ansible .14:53
matttcloudnull: ok14:53
cloudnullbut removing it from the gate is what we're after.14:53
matttcloudnull: will we ever turn them back on in gate?  if so maybe we jsut want to comment where it writes to user vars14:55
cloudnullwe could do that.14:55
matttcloudnull: because we leave a bunch of exports on those vars in bootstrap-aio.sh and gate-check-commit.sh which go nowhere right now14:56
matttcloudnull: https://github.com/stackforge/os-ansible-deployment/blob/master/scripts/gate-check-commit.sh#L44-L51 and https://github.com/stackforge/os-ansible-deployment/blob/master/scripts/bootstrap-aio.sh#L32-L3914:56
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Removes the fatal_deprecations from the gate job  https://review.openstack.org/16725714:59
cloudnullmattt that removes the exports to enable14:59
cloudnullbut leaves the scaffolding in place.15:00
*** git-harry has quit IRC15:00
cloudnullgit-harry has rage quit once again.15:00
Sam-I-Amlol15:00
*** git-harry has joined #openstack-ansible15:01
cloudnulland he returns!15:01
matttcloudnull: +2d15:02
cloudnullty sir15:02
Sam-I-Ammeetingses?15:04
palendaeSam-I-Am: Still have an hour15:05
*** jaypipes has quit IRC15:05
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Set the neutron default workers  https://review.openstack.org/16609515:07
Sam-I-Amoh, utc :/15:07
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Adds new provider_networks module and reformats ml2_conf.ini  https://review.openstack.org/16657415:07
*** hj-hp has joined #openstack-ansible15:07
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Removes the fatal_deprecations from the gate job  https://review.openstack.org/16725715:07
palendaeI just correctedmy entry15:07
cloudnull"UTC – Coordinated Universal Time"  not this DST/CST/SOME SHIT time we have here.15:08
palendaeCDT*15:08
palendaeIt's noon to 1 for me15:08
palendaeTHANKS A LOT CLOUDNULL15:08
cloudnullyw?15:09
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated repository for minimum viable kilo install  https://review.openstack.org/16698615:14
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated repository for minimum viable kilo install  https://review.openstack.org/16698615:16
cloudnullmattt mancdaz palendae ^ kilo commit with the deps for the removal of the fatal_deprecations.15:17
mancdazcloudnull thankyou15:18
cloudnullno thank you for reviewing all the things15:18
mancdazno thank you for making things to review15:18
cloudnullso this commit is a go: "https://review.openstack.org/#/c/167257/4" which depends on "https://review.openstack.org/#/c/166574" which itself depends on "https://review.openstack.org/#/c/166095/4"15:19
palendaewooo wooo all aboard the dependency train15:19
cloudnullso if we're all happy with  "https://review.openstack.org/#/c/167257/4" can we get core reviewers to do the needfuls on the other two.15:19
matttcloudnull: can you revert that stuff in tempest resources?15:20
mancdazcloudnull my comments were not addressed in the last of those15:20
mancdazit's a question really15:20
mancdazon https://review.openstack.org/#/c/166095/315:21
matttcloudnull: also tempest.conf.j2 wasn't reverted to continue to work w/ the older apis15:21
mancdazpatchset 315:21
mancdazoh wait15:21
cloudnullmancdaz: i replied inline https://review.openstack.org/#/c/166095/3/playbooks/roles/os_neutron/templates/neutron.conf.j215:21
mancdazyou did15:21
cloudnulland the commit message was change15:21
cloudnull*changed.15:21
cloudnullmattt let me address that in the kilo patch.15:22
matttcloudnull: k thanks15:23
*** sdake has joined #openstack-ansible15:25
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated repository for minimum viable kilo install  https://review.openstack.org/16698615:26
cloudnullmattt ^ that should do it. but let me know if im still being an idiot15:26
cloudnull:)15:26
matttcloudnull: there are no idiots here sir15:27
*** sdake__ has quit IRC15:29
matttcloudnull: https://review.openstack.org/#/c/166986/6/playbooks/roles/os_tempest/tasks/tempest_resources.yml15:33
matttcloudnull: all that can be reverted right?15:33
*** jwagner_away is now known as jwagner15:34
*** galstrom_zzz is now known as galstrom15:39
*** nosleep77 has joined #openstack-ansible15:43
*** hj-hp has quit IRC15:51
cloudnullmattt we can revert that. though i think its still worth while to fix our glance module to support v215:54
matttcloudnull: yeah i think mancdaz was working on an independent review to do that15:56
*** rromans has quit IRC15:57
*** sdake has quit IRC15:58
*** Bjoern__ has joined #openstack-ansible16:01
*** rrrobbb has joined #openstack-ansible16:01
cloudnullbug triage time.16:01
cloudnullcloudnull, mattt, andymccr, d34dh0r53, hughsaunders, b3rnard0, palendae, Sam-I-Am, odyssey4me, serverascode, rromans, mancdaz, dolphm, _shaps_, BjoernT, claco, echiu, dstanek - triage time16:02
palendaeHi16:02
hughsaundershey16:02
b3rnard0Notes are here: https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-03-24-16.0016:02
mattt\o16:02
sigmavirus24o/16:02
Sam-I-Amhi16:02
Sam-I-Amb3rnard0: time to fire it up, captain launchpad16:03
b3rnard0np Admiral Diagram16:04
Sam-I-Amheh16:04
Sam-I-Amso i guess we have no bugs?16:05
cloudnullso lets get started.16:05
cloudnullfirst up https://bugs.launchpad.net/openstack-ansible/+bug/143559716:05
openstackLaunchpad bug 1435597 in openstack-ansible "scripts/bootstrap-ansible.sh creates openstack-ansible without support for unprivileged users" [Undecided,New]16:05
cloudnulli think dolphm patched that already.16:06
dstanekhi16:06
cloudnullhi dstanek16:06
cloudnullyup. - fixed. https://review.openstack.org/#/c/167010/ <- needs gating love16:06
andymccrdang gate!16:07
cloudnullso next: https://bugs.launchpad.net/openstack-ansible/+bug/143547216:08
openstackLaunchpad bug 1435472 in openstack-ansible "Create VIP for rsyslog logging destination" [Undecided,New]16:08
cloudnullBjoern__ you around ?16:08
*** Bjoern__ is now known as BjoernT16:08
BjoernTyes16:08
BjoernTthats a wishlist16:09
BjoernTany question to the context?16:09
cloudnullso that would only effect Juno.16:09
ApsuNone from me. Seems sensible.16:09
BjoernTalright next bug i guess16:10
cloudnullin master rsyslog at the service level is shipping to an rsyslog server for which will give you access to the raw logs on a single host.16:10
cloudnullor multiple if you scale it out that way16:10
*** IRTermite has joined #openstack-ansible16:11
BjoernTright, once you have VIP or support multiple destionations16:11
cloudnullyea in master we have multi destinations.16:11
cloudnullnext: https://bugs.launchpad.net/openstack-ansible/+bug/143535016:12
openstackLaunchpad bug 1435350 in openstack-ansible "We need a swift_standalone play for Juno" [Undecided,New] - Assigned to Andy McCrae (andrew-mccrae)16:12
* cloudnull hands mic to andymccr16:12
andymccrpr is in16:12
andymccrbut basically, for swift standalone to work nicely in juno we need a new play - its really not impactful in that you dont have to run that play if you dont want16:12
andymccrmainly because keystone sets up ALL services at the start which will break if you dont specify the other services and their vars.16:13
cloudnullok. so i tagged the bug for juno / invalid in master.16:13
andymccryeh not valid for master16:14
andymccrhttps://review.openstack.org/#/c/167170/16:14
cloudnullnext: https://bugs.launchpad.net/openstack-ansible/+bug/143459716:14
openstackLaunchpad bug 1434597 in openstack-ansible "nova-compute logs are not in the logging node" [Undecided,Confirmed]16:14
cloudnullmiguelgrinberg: needs more datas.16:14
cloudnullnext: https://bugs.launchpad.net/openstack-ansible/+bug/143431516:15
openstackLaunchpad bug 1434315 in openstack-ansible "SYMLINK_DIR used in scripts/bootstrap_aio.sh but not defined" [Undecided,New]16:15
cloudnullpalendae: ^16:15
palendaeYeah - I wastrying the boostrap_aio.sh script without the gate check commit, and it required SYMLINK_DIR, which wasn't defined inside bootstrap_aio16:16
palendaeI'm not sure exactly where we should fix that, but it seems fairly simple16:16
cloudnullimo we should fix that in the `boostrap_aio.sh ` script if thats where its being required.16:17
Sam-I-Ami found this issue too16:17
palendaeOk16:17
palendaeI think it's as simple as moving the definition over16:17
Sam-I-Amtypey typey16:18
palendaeI can take it16:18
cloudnullassigned and triaged.16:18
palendaekk16:19
cloudnullnext: https://bugs.launchpad.net/openstack-ansible/+bug/143423316:19
openstackLaunchpad bug 1434233 in openstack-ansible "Non-existent variable in os_glance role" [Undecided,New] - Assigned to Matt Thompson (mattt416)16:19
matttcloudnull: so we uncovered this one while playing w/ stacktach16:20
cloudnullmattt looks like we should just remove that var16:20
matttcloudnull: yeah, some of the variable names have changed, it may get cleaned up as we move to kilo and scrutinise all the configs16:20
cloudnullits not being used.16:20
cloudnullsounds good.16:21
cloudnullill target it to kilo.16:21
matttcloudnull: but i also think we have a bigger issue on hand in that we cannot consistently turn on notifications across projects in o-a-d16:21
matttcloudnull: but i will raise a spec/blueprint for that one later16:21
cloudnullyea, i was talking to alextricity about that very thing just today.16:21
cloudnullmattt can you and alextricity sync up on that ?16:22
matttcloudnull: certainly16:22
cloudnullnext:  https://bugs.launchpad.net/openstack-ansible/+bug/143361916:22
openstackLaunchpad bug 1433619 in openstack-ansible "Please layout the swift-drive-audit configuration" [Undecided,New]16:22
*** sdake has joined #openstack-ansible16:22
cloudnullBjoernT andymccr ^16:23
BjoernTyup another wishlist16:23
cloudnullandymccr is that something that we can target at Kilo?16:23
BjoernTI like actually earlier, a juno release16:23
andymccri mean we can, i dont think it provides much - its just a trawl through kern.log for disk errors16:23
andymccrwe should disk errors far more reliably via the dell monitoring stuff16:24
*** sdake__ has joined #openstack-ansible16:24
BjoernTandymccr: Yes dell is installed here but we have cdc installs too16:25
BjoernTand the os usuallr reports io errors earlier than dell tool16:25
andymccrBjoernT: its fine to add it although regex on loop devices seems weird, and drive-audit is not (imo) a great way to detect failures.16:26
BjoernTin many cases it will be the only way, especially if you do disk passthrough16:27
*** sdake has quit IRC16:27
andymccrand if the regex is wrong nobody will know or care and it just wont say anything16:28
andymccrbut sure adding it is easy16:28
BjoernTalright we take this offline, I don't see your concerns16:28
cloudnullok. so next. https://bugs.launchpad.net/openstack-ansible/+bug/143329116:30
openstackLaunchpad bug 1433291 in openstack-ansible "rpc_deploy/conf.d/swift.yml file should be inert by default" [Undecided,New]16:30
cloudnullrevdr around ?16:30
BjoernThe is but not here16:30
andymccri thought that used to be the case (swift.yml commented out) and it should be16:30
andymccrso makes sense.16:30
andymccror make the default in the etc dir in the repo like swift.yml.sample or something so it isn't automatically read in.16:31
BjoernTswift.yml is not commented out16:31
BjoernTif you do a cp from /opt/os-ansible-deployment/etc/rpc_deploy/conf.d you'll copy that aio configuration accidentially16:32
andymccrBjoernT: "used to be the case" e.g. not the case now16:32
BjoernTI think that's his concern16:32
BjoernTthe issues is, you get inventory errors running normal playbooks16:33
andymccrhmm it was added by odyssey4me for the aio gate i believe. so i think that would have an impact there16:34
Sam-I-Ami thought all the stock configs do aio now16:34
cloudnullso we should look at tagging the configs used by the AIO gate jobs such that they are not impacting when someone blindly copies the configs into place.16:34
Sam-I-Amand i thought that only applied to v1116:34
andymccrcloudnull: yeh16:34
Sam-I-Ambut maybe it does v10 too?16:35
andymccrcloudnull: perhaps the aio could copy it from like .sample or .aio16:35
cloudnullyea that sounds reasonable.16:35
andymccrthat way blind copy wont error and it will still work for gate16:35
andymccrand as a sample16:35
Sam-I-Amideally there should be no config files you can just blindly copy16:35
Sam-I-Amthey should all be .sample or .aio or something16:35
Sam-I-Am(unless they dont require editing, of course)16:35
Sam-I-Ami clear out crowds...16:39
cloudnullok so lets update that issue and work through getting the example configs tagged with aio / sample or something.16:39
Sam-I-Ammakes sense16:40
*** jaypipes_ has joined #openstack-ansible16:41
cloudnullnext: https://bugs.launchpad.net/openstack-ansible/+bug/143324016:41
openstackLaunchpad bug 1433240 in openstack-ansible "Move cinder-volumes onto bare metal host" [Undecided,New]16:42
openstackgerritNolan Brubaker proposed stackforge/os-ansible-deployment: Move SYMLINK_DIR declaration to bootstrap-aio.sh  https://review.openstack.org/16731616:42
openstackgerritNolan Brubaker proposed stackforge/os-ansible-deployment: Move SYMLINK_DIR declaration to bootstrap-aio.sh  https://review.openstack.org/16731616:42
cloudnullim kind of in agreement that cinder in a container-volume in a container is kind of like swift storage nodes / nova compute in a container.16:42
cloudnullits cool, it has its uses, but the service just lends itself to being on the physical machine.16:43
clacomy only concern is upgrades16:43
Sam-I-Amany hope for containerizing nova again?16:43
cloudnullnot until a kernel bug is fixe.d16:43
clacothat seems like a 10 -> 11, or 11-> 12 thing, but not great for minor/revision releases16:43
cloudnullagreeded.16:44
Sam-I-Amcloudnull: i thought Apsu was working on a workaround with veth magic or something.16:44
cloudnullif we decided to make that change it would not effect prior branches.16:44
BjoernTWhy would be containerize single use boxes ?16:44
clacooh, yeah...because of the inventory setting16:44
ApsuSam-I-Am: That won't work, sadly16:44
*** sdake has joined #openstack-ansible16:44
Sam-I-AmBjoernT: does cinder volume always run on a separate host?16:44
ApsuThe iSCSI kernel module is where the problem seems to lie16:45
Sam-I-AmApsu: patchy patchy make the goes16:45
BjoernTnormally yes, but not in NFS case16:45
ApsuNeeds to be patched to support generic netlink16:45
Apsus/patched/rewritten/16:45
Sam-I-Amrewritety rewritety16:45
BjoernTwe still see issues at tgt inside containers and don't know where they are coming from16:45
cloudnullso can we spike on this?16:46
cloudnulland does anyone want to take owner ship of it ?16:46
Sam-I-Amcloudnull: the tgt issue, or un-containerizing cinder?16:48
Sam-I-Amthe latter seems like is_metal = True, goes.16:48
*** sdake__ has quit IRC16:49
cloudnullSam-I-Am: yes.16:49
cloudnullthat is true. but what does an upgrade look like?16:49
cloudnulland changing from in container to out of container will cause volume downtime.16:50
andymccrit would be a good idea to have documented issues we're solving for on this though.otherwise i have no way of telling if its better or the same16:50
cloudnullso spiking on that would be really helpful to understanding all of the impacts.16:50
cloudnullalso what andymccr said.16:50
cloudnullso who wants it? is it important to us?16:51
andymccrin principle i agree with the volumes on physical host but we're already in containers so there should be some benefit to moving to physical host, at which point we need to be able to tell/measure whether its improved.16:51
ApsuI'd like to know what the symptoms are with tgt16:51
ApsuSo we can adequately analyze them and figure out what we need to do from there16:51
andymccrApsu: +116:51
cloudnullApsu you volunteering ?16:52
andymccrvoluntolding16:52
Apsucloudnull: Why the hell not, you know I love me the cinder16:52
*** sdake__ has joined #openstack-ansible16:52
Sam-I-AmApsu: is it better than neutron?16:52
ApsuHe says as he reads the source code of brctl...16:52
Sam-I-AmApsu: masochist16:52
palendaeGood thing brctl has unit tests >.>16:52
palendae<.<16:52
Apsu... yeah...16:53
Sam-I-AmApsu: this wouldnt be a problem with OVS16:53
ApsuGood thing it's been updated in the past 9 years. Oh wait16:53
clacofocus16:53
Sam-I-Amisnt there a newer command to replace brctl?16:53
Sam-I-Ambridge216:53
Apsucloudnull: More to triage?16:53
clacoI have a log for the fire: https://bugs.launchpad.net/openstack-ansible/+bug/139938216:54
openstackLaunchpad bug 1399382 in openstack-ansible "F5 Pool Monitoring in Kilo" [High,New] - Assigned to Evan Callicoat (apsu-2)16:54
clacolike should be moved to extras16:54
cloudnullyup.16:54
Apsu+116:55
claco* your card16:55
claco^ do the thing16:55
cloudnullwe have one more issue: https://bugs.launchpad.net/openstack-ansible/+bug/143226916:55
openstackLaunchpad bug 1432269 in openstack-ansible "Adding a new Cinder storage node fails api service check" [Undecided,New]16:55
*** sdake has quit IRC16:56
ApsuI don't know how to move bugs. Unless you mean close this bug and reopen on other project. If there is an LP project for extras.16:56
cloudnulldaneyon you around ?16:56
cloudnullwere we ever able to nail this down16:56
cloudnullhughsaunders you we're working on that too right?16:56
clacoApsu: move to github extras repo issues, link them, close the lp16:56
Apsuclaco: roger16:56
hughsaunderscloudnull: I did look at it, I couldn't reproduce16:57
hughsaundersdaneyon mentioned that he was going to rebuild his lab and let us know if he comes across the same error again16:57
daneyoncloudnull here16:57
cloudnullhey there :)16:58
daneyonhughsaunders I have not been able to rebuild mt lab.16:58
daneyonhughsaunders After writing-up osad, I've been busy cutting the M3 release for Kolla16:58
hughsaundersdaneyon: no problem, just means the bug is probably incomplete as we haven't been able to reproduce16:59
cloudnullso i've marked the issue as incomplete. hughsaunders can you update the issue with some bits noting what you tested and that you cant reproduce?16:59
hughsaunderscloudnull: yep16:59
cloudnullno worries daneyon. thanks for all the testing that you did though. much appreciated.16:59
cloudnulland thanks for the mention on twitter :)17:00
b3rnard0wow, did we just finish on time17:00
cloudnullso we're done here.17:00
Sam-I-Amb3rnard0: you did an amazing job with time, sir17:00
cloudnullare there any other items that people want to lobby for ?17:00
b3rnard0https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-03-24-16.0017:00
BjoernTno17:00
cloudnullgreat. thanks everyone !17:01
andymccrgreat job!17:02
palendaehttps://review.openstack.org/#/c/167316/ reviews please17:02
ApsuSam-I-Am: Strongly thinking about trying to remove all use of brctl in neutron and replace with ip/bridge. Apparently the brctl backend (libbridge) uses ioctls that were deprecated pre kernel 2.517:03
alextricityQuestion: In the openstack_environment.yml file, what defines the os-infra_containers group?17:03
ApsuAnd it uses the result of that as part of figuring out its exit code as successful or not...17:03
Sam-I-AmApsu: have you talked to matt about that?17:04
ApsuSam-I-Am: mattt or ...17:04
Sam-I-Amyay for screen scraping17:04
Sam-I-AmApsu: uhh... matt that wanders over to our area sometimes?17:04
Sam-I-Amlong hair?17:04
Apsuoh, thode17:04
Sam-I-Amyeah, thats it17:04
clacoyeah. neutron contrib17:04
cloudnullalso review https://review.openstack.org/#/c/166095 <- please, now. :)17:06
Sam-I-Amclaco: yeah, until he gets fed up (which i imagine is soon)17:06
Sam-I-Amcloudnull: reviewerated17:07
*** jwagner is now known as jwagner_away17:07
cloudnullalso mattt mancdaz  it looks like glance v1 is not passing even the api testing "http://logs.openstack.org/86/166986/6/check/os-ansible-deployment-dsvm-check-commit/d2cc18d/console.html#_2015-03-24_16_20_51_944"17:08
*** jmccrory has joined #openstack-ansible17:10
mancdazcloudnull mattt gone, I'm just about to head out. We were both going to re-test and review that patch in the morning if it hadn't already been done by everyone else today17:14
cloudnullok.17:14
cloudnullim kicking it too. se if i can determine why it hates glance.17:14
openstackgerritJustin Shepherd proposed stackforge/os-ansible-deployment: Fixing defcore test list generation  https://review.openstack.org/16732917:17
galstromto all: I am sorry ^17:17
clacoha17:17
andymccr-217:17
andymccryoure welcome17:17
galstrombut the defcore list will now actually run the right set of tests17:17
andymccrwhat part of -2 was unclear?17:17
galstromandymccr: did you mean +2 for amazing bash-ness17:18
galstromcause that shit is awesome17:18
mancdazgalstrom defcore don't care17:19
mancdazscenario is where the cool kids hang out17:19
galstrom:)17:19
galstromthis can make us OG defcore17:20
Apsugalstrom: Wow, that's kind of awful.17:20
galstromdefcore before there was a defcore17:20
mancdazwe're not going to use the defcore tests anywhere in the very short term17:20
galstromApsu: right.. i am actually a little proud of that horribleness17:20
mancdazgalstrom still doesn't beat that ruby shit you did in chef17:20
galstrommancdaz: agreed.. but this way.. if I run an install.. i can just run that script with the defcore argument..17:20
galstrommancdaz: did you see that is still in there17:21
mancdazgalstrom haha no17:21
mancdazI don't look back - only forwards17:21
mancdazthat's our matra right?17:21
mancdaz*mantra17:21
mancdazcloudnull I blame sigmavirus2417:22
galstrommancdaz: just for you https://github.com/stackforge/cookbook-openstack-compute/blob/master/templates/default/api-paste.ini.erb#L100-L10317:22
mancdazhe broked glance so bad17:22
mancdazMY EYES17:22
cloudnullhe's core. which means it is his fault.17:22
galstromyou are welcome17:22
mancdazactually it's not quite as bad as I remember17:23
mancdazbut it's still hideous17:23
Apsugalstrom: I'm going to need you to fill out an Ishikawa diagram and answer 5 "Why?"s for your crimes.17:24
ApsuActually, 5 might not be enough17:24
galstromyeah.. 5 is probably a bit low17:24
galstrommancdaz: s/hideous/perfectly clear/17:25
ApsuSam-I-Am: Neat: https://bugzilla.redhat.com/show_bug.cgi?id=1160815#c1 verifies my suspicion that setting the forward_delay is only relevant to stp!=0, and LB agent sets stp=0. Also this indicates the kernel wouldn't accept forward_delay=0 anyway.17:31
openstackbugzilla.redhat.com bug 1160815 in NetworkManager "DELAY=0 in bridge configuration results in default (30 second) listening/learning delay" [Unspecified,Closed: currentrelease] - Assigned to lrintel17:31
ApsuSo... going to try the bridge stoofs with ip link and ignore fd.17:31
Sam-I-Amhmmmmm17:41
Sam-I-Aminteresting17:41
*** jwagner_away is now known as jwagner17:43
sigmavirus24mancdaz: I broked glance, eh?17:50
rackertomclaco: I think in general the issues have all been perfect storm situations. But that's usually when you want things to be least frustrating the most.18:04
*** jmccrory has quit IRC18:09
*** jmccrory has joined #openstack-ansible18:09
*** Mudpuppy_ has joined #openstack-ansible18:19
*** Mudpuppy has quit IRC18:21
*** jwagner is now known as jwagner_away18:50
*** KLevenstein has quit IRC18:57
*** KLevenstein has joined #openstack-ansible19:06
*** rromans has joined #openstack-ansible19:14
*** sigmavirus24 is now known as sigmavirus24_awa19:17
*** sigmavirus24_awa is now known as sigmavirus2419:17
*** rrrobbb has quit IRC19:17
*** Mudpuppy_ has quit IRC19:18
*** Mudpuppy has joined #openstack-ansible19:18
*** KLevenstein has quit IRC19:55
*** KLevenstein has joined #openstack-ansible20:22
dstanekcloudnull: what was that tempest error you were saying to watch out for?20:24
*** hj-hp has joined #openstack-ansible20:24
dstanekright now i'm getting an ssh timeout20:25
palendaeyeah, that one's been pretty prevalent20:25
dstanekok, if it's not just me i'll move on20:26
palendaeNope, lots of us20:27
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated repository for minimum viable kilo install  https://review.openstack.org/16698620:29
*** jmccrory1 has joined #openstack-ansible20:34
*** jmccrory has quit IRC20:34
*** jmccrory has joined #openstack-ansible20:39
*** jmccrory1 has quit IRC20:42
dstanekif i run ./scripts/teardown.sh should i expect to be able to run ./scripts/gate-check-commit.sh again on the same node?20:59
*** openstackgerrit has quit IRC21:07
*** openstackgerrit has joined #openstack-ansible21:07
cloudnulldstanek yes it should.21:10
dstanekcloudnull: i got a crazy hard drive error - if i can reproduce i'll file a bug21:10
*** Mudpuppy_ has joined #openstack-ansible21:11
cloudnullwhats the error ?21:12
*** Mudpuppy has quit IRC21:13
dstanekcloudnull: gone now :-(21:14
cloudnullyw?21:14
cloudnull:)21:14
dstanekcloudnull: no i just close that tmux window. so i have no way to know21:15
cloudnullah.21:15
dstaneknew machine is being provisioned now so i'll know shortly21:17
*** DustD1_ has left #openstack-ansible21:33
matttanyone know what these memcache failures are?21:34
matttis it limited in scope to HP instances?21:34
*** jmccrory has quit IRC21:34
cloudnullwhat failures mattt ?21:36
matttcloudnull: http://logs.openstack.org/09/167009/1/gate/os-ansible-deployment-dsvm-check-commit/cd57ee9/console.html21:37
mattti've seen a ton of these in the past 12 hours21:37
matttcloudnull: more specifically http://logs.openstack.org/09/167009/1/gate/os-ansible-deployment-dsvm-check-commit/cd57ee9/console.html#_2015-03-24_21_32_35_10821:37
cloudnulllooks like [ 2015-03-24 21:32:35,057 p=30505 u=root |  failed: [aio1_memcached_container-9084a693] => (item=memcached) => {"attempts": 5, "failed": true, "item": "memcached"} ]21:39
cloudnullwhich seems to indicate that apt repo is dead or down.21:39
matttwe don't pin memcached do we ?21:40
matttalways seems to fail there21:40
cloudnullno its going back to the apt repo at archive.ubuntu or mirror.rackspace.21:41
cloudnullbut it does seem to fail a lot on the hp instances.21:42
matttcloudnull: that's what i'm noticing21:44
mattti've built a bunch of RS instances today and have not hit that once21:44
*** sc has quit IRC21:50
Apsumirror.rackspace.com is a much better mirror than archive21:50
ApsuWell, much less loaded21:50
*** sc has joined #openstack-ansible21:52
*** jmccrory has joined #openstack-ansible21:53
*** jmccrory has quit IRC21:53
*** daneyon_ has joined #openstack-ansible21:56
*** daneyon has quit IRC21:59
*** dstanek has quit IRC22:01
*** hj-hp has quit IRC22:06
*** hj-hp has joined #openstack-ansible22:07
mattti'm not even sure neutron is getting set up properly on this kilo patch22:11
matttcloudnull: did you have any luck booting instances and assigning floats etc?22:11
*** dstanek has joined #openstack-ansible22:14
*** Mudpuppy_ has quit IRC22:26
*** KLevenstein has quit IRC22:37
*** BjoernT has quit IRC22:59
*** markvoelker has quit IRC23:06
*** sdake__ has quit IRC23:10
*** hj-hp has quit IRC23:12
*** galstrom is now known as galstrom_zzz23:12
*** dstanek has quit IRC23:17
*** dstanek has joined #openstack-ansible23:18
dstanekcloudnull: i'm getting this after running gate-check-commit.sh && teardown.sh && gate-check-commit.sh - http://paste.openstack.org/raw/196245/23:20
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated repository for minimum viable kilo install  https://review.openstack.org/16698623:24
cloudnulldstanek: that issue is when a partion table is re-written and the host is having issues informing the kernel of the change.23:26
cloudnulli've seen that a few times when the lxc containers on the /var/lib/lxc are on a partition that is not empty.23:27
*** jmccrory has joined #openstack-ansible23:27
dstanekcloudnull: how can i recover?23:30
dstaneki could try a reboot, but that's harder to automate23:30
cloudnullwhen the host goes into that state a reboot is just about all you can do.23:30
cloudnullare you automating the teardown / rebuild ?23:30
cloudnullare you looking to try and automate the redeployment of keystone ?23:31
dstaneknot at this point. but i was doing similar things with devstack23:31
cloudnulllike build destroy, build again ?23:31
dstaneki have some script that configure devstack, run tests, teardown and start a new configuration23:32
dstaneksimilar to what the gate does, except that i am on the same node23:32
cloudnullrax pub cloud image ?23:33
cloudnullif so, which one ?23:33
dstanekyeah. for the devstack tests i use a 4g performance instance running 14.0423:33
*** stevemar has quit IRC23:34
cloudnulli've had really good success with the "Ubuntu 14.04 LTS (Trusty Tahr) (PVHVM)" image and the flavor Performance1-8/General1-823:34
dstanekthat's what i'm using right now for this node23:34
*** stevemar has joined #openstack-ansible23:35
cloudnullso we can attack it another way.23:36
cloudnullwhen you build and then test, you can run the lxc-container-destory.yml plau23:36
cloudnullwhich will destroy all of the containers and their resulting binds/bits23:36
cloudnulland then rerun the setup-everything.yml play23:37
cloudnullto rebuild.23:37
dstaneki'll give that a try23:37
dstaneknone of this is really necessary just yet. trying to get a feel for what i can do23:37
cloudnulldoing it that way would be the fastest way to rebuild all the things. as the partitioning and base system packages would already be resolved.23:38
cloudnullworkflow might be -- build: openstack-ansible haproxy-install.yml setup-everything.yml, destroy: openstack-ansible lxc-container-destroy.yml, rebuild: openstack-ansible setup-everything.yml23:40
cloudnullwhich is essentially what the scripts are running for you. except the teardown one, which is doing a lot more to nuke everything from orbit.23:41
dstanekyeah, that really does nuke everything23:45
cloudnullit tries its best, but may be a bit to aggressive. I made it a script instead of a base play because i didn't want someone accidentally executing it destroying parts of their cloud by accident.23:46
*** markvoelker has joined #openstack-ansible23:47
dstanekeven after the reboot i can't get it recreated, but i haven't look into it much yet23:49
*** markvoelker has quit IRC23:52
dstanekok, looking better. small bug in one of the scripts23:53

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