| *** openstack has joined #openstack-relmgr-office | 00:08 | |
| *** dims has joined #openstack-relmgr-office | 00:27 | |
| *** dims has quit IRC | 01:46 | |
| *** dims has joined #openstack-relmgr-office | 02:47 | |
| *** dims has quit IRC | 02:52 | |
| *** asalkeld has quit IRC | 04:18 | |
| *** asalkeld has joined #openstack-relmgr-office | 04:30 | |
| ttx | redrobot: RC2 done @ https://launchpad.net/barbican/+milestone/kilo-rc2 | 07:03 |
|---|---|---|
| asalkeld | ttx: do we have a 1-1? | 07:50 |
| ttx | asalkeld: we do | 07:51 |
| asalkeld | ok | 07:51 |
| ttx | I'll grab coffee first | 07:51 |
| ttx | meet you in 5 | 07:51 |
| ttx | 5 | 07:56 |
| ttx | #startmeeting ptl_sync | 07:56 |
| openstack | Meeting started Tue Apr 28 07:56:46 2015 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 07:56 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 07:56 |
| openstack | The meeting name has been set to 'ptl_sync' | 07:56 |
| ttx | #topic Heat | 07:56 |
| ttx | asalkeld: o/ | 07:56 |
| asalkeld | yo | 07:56 |
| asalkeld | are we looking at bugs that might cause another rc? | 07:57 |
| ttx | asalkeld: so at this point we only respin in case of a major regression, blatant security hole or stuff that can't be fixed post-release | 07:57 |
| ttx | https://bugs.launchpad.net/heat/+bugs?field.tag=kilo-rc-potential | 07:57 |
| asalkeld | I don't see any like that | 07:57 |
| ttx | Do you have anythign that meets that description there ? | 07:58 |
| asalkeld | not yet | 07:58 |
| ttx | https://bugs.launchpad.net/heat/+bug/1446252 sounds like a typical bug | 07:58 |
| openstack | Launchpad bug 1446252 in heat "Can't rollback update with nested stack in progress" [High,Fix committed] - Assigned to Zane Bitter (zaneb) | 07:58 |
| ttx | can land in stable/kilo post-release alright | 07:58 |
| asalkeld | yes | 07:58 |
| ttx | Quick look at proposed stable/kilo things | 07:59 |
| asalkeld | ok | 07:59 |
| ttx | https://review.openstack.org/#/q/is:open+project:openstack/heat+branch:stable/kilo,n,z | 07:59 |
| ttx | https://review.openstack.org/#/c/177602/ is interesting | 07:59 |
| asalkeld | looking | 08:00 |
| ttx | is it something we can change at any time ? | 08:00 |
| asalkeld | ttx: it is not a security issue | 08:00 |
| ttx | Right, this SHA1 is not actually brute-forceable enough | 08:01 |
| asalkeld | so yeah, can be done any time | 08:01 |
| ttx | ok, looks like you're good (which is good news, since some others are not in such good shape) | 08:01 |
| asalkeld | it's just to make a dynamic version number | 08:01 |
| ttx | You should work on release notes on the remaining time | 08:01 |
| ttx | https://wiki.openstack.org/wiki/ReleaseNotes/Kilo | 08:01 |
| asalkeld | ok will do | 08:02 |
| ttx | #info At RC2, no need for a RC3 at this stage | 08:02 |
| ttx | We need release notes completed by Thursday when we unleash the thing to the world | 08:02 |
| asalkeld | agree | 08:02 |
| ttx | We usually have more time to work on them but we were late this cycle | 08:02 |
| ttx | so the sooner the better (as you get closer you'll get edit conflicts) | 08:03 |
| asalkeld | ok | 08:03 |
| ttx | asalkeld: questions? | 08:03 |
| asalkeld | ttx: no all good | 08:03 |
| ttx | asalkeld: unless I hear from you I'll retag the RC2 as final on release day and play LP tricks | 08:03 |
| asalkeld | sounds good | 08:03 |
| ttx | awesome, thanks ! | 08:04 |
| asalkeld | i'll let you know if there is something critical | 08:04 |
| asalkeld | but i haven't seen any | 08:04 |
| ttx | asalkeld: right | 08:04 |
| ttx | the point is, we'll find significant bugs next week too | 08:04 |
| ttx | so the question at this stage is... can this wait | 08:05 |
| asalkeld | ok | 08:05 |
| asalkeld | ... yes we can | 08:06 |
| asalkeld | (wait) | 08:06 |
| *** zz_johnthetubagu is now known as johnthetubaguy | 09:17 | |
| ttx | johnthetubaguy: o/ talk to you in a minute | 09:18 |
| johnthetubaguy | ttx: ack | 09:20 |
| ttx | #topic Nova | 09:20 |
| ttx | So we have a RC3 window opened, and it's not that easy to close with a busy gate | 09:20 |
| ttx | We opened it for https://bugs.launchpad.net/nova/+bug/1448075 | 09:21 |
| openstack | Launchpad bug 1448075 in OpenStack Compute (nova) kilo "Recent compute RPC API version bump missed out on security group parts of the api" [Critical,In progress] | 09:21 |
| ttx | which didn't merge in master yet | 09:21 |
| ttx | and is failing tests again on the retry | 09:21 |
| ttx | so I'm a bit worried we won't be able to close this one today | 09:22 |
| ttx | One of the reasons I don't want to consider anything not merged in master for RC | 09:22 |
| johnthetubaguy | oh dear, agreed with must be merged in master | 09:23 |
| johnthetubaguy | taking a look | 09:23 |
| ttx | At this point on current load, that patch won't merge in the next 14 hours | 09:23 |
| ttx | which places the RC3 closing, at best, at 26 hours | 09:24 |
| ttx | not sure we can afford that | 09:24 |
| johnthetubaguy | ah, sounds like gate has gone unstable :( | 09:24 |
| johnthetubaguy | aweful timing, as ever with these things | 09:25 |
| ttx | well, I don't agree. We shouldn't depend on last week for anything | 09:25 |
| johnthetubaguy | very true | 09:25 |
| ttx | RCs from last week should have been ok | 09:25 |
| ttx | So I blame lack of test coverage for things that are considered RC | 09:25 |
| johnthetubaguy | thats totally fair | 09:26 |
| ttx | anyway, two things trying to slip in the same RC window | 09:26 |
| johnthetubaguy | I have schedued a session for this | 09:26 |
| ttx | https://bugs.launchpad.net/nova/+bug/1447132 | 09:26 |
| openstack | Launchpad bug 1447132 in OpenStack Compute (nova) kilo "nova-manage db migrate_flavor_data doesn't do instances not in instance_extra" [High,New] | 09:26 |
| ttx | and bug 1444745 | 09:26 |
| openstack | bug 1444745 in OpenStack Compute (nova) "Updates RPC version alias for kilo" [High,Fix committed] https://launchpad.net/bugs/1444745 - Assigned to Alex Xu (xuhj) | 09:26 |
| ttx | That last one is concerning, sounds like something that should be done prerelease | 09:26 |
| ttx | (but hasn't been) | 09:27 |
| johnthetubaguy | yeah, thats the one I am worried about | 09:27 |
| ttx | Both are actually closer to merging than 1448075 | 09:27 |
| ttx | since they are in master already | 09:27 |
| johnthetubaguy | basically, it causes us some upgrade issues for liberty, but I think we could work around it | 09:27 |
| ttx | so two options | 09:27 |
| ttx | 1/ cancel RC3 while nothing has merged in it yet | 09:28 |
| ttx | 2/ Do RC3 (in which case we could add both bugs in) | 09:28 |
| ttx | I'm leaning toward doing it with at least 1448075 and 1444745 in | 09:29 |
| ttx | Not totally sure about 1447132 | 09:29 |
| ttx | That probably means closing RC3 tomorrow | 09:29 |
| ttx | which means it won't see any testing | 09:29 |
| ttx | so this fixes must be 100% safe | 09:29 |
| johnthetubaguy | right | 09:30 |
| ttx | and I have a hard time understanding what those RPC things actually change | 09:30 |
| ttx | what's your take on the options ? | 09:30 |
| johnthetubaguy | so my take is, its all about this one: https://bugs.launchpad.net/nova/+bug/1448075 | 09:30 |
| openstack | Launchpad bug 1448075 in OpenStack Compute (nova) kilo "Recent compute RPC API version bump missed out on security group parts of the api" [Critical,In progress] | 09:30 |
| johnthetubaguy | thats the only real trigger for RC3 | 09:31 |
| ttx | ...and we just added another hour to the lead in, thanks to a patch that was top of line and -2ed | 09:31 |
| ttx | Now at 12:42 | 09:31 |
| johnthetubaguy | if that doesn't make it, then RC3 doesn't matter, I think | 09:31 |
| ttx | 12 hours and 42 minutes | 09:31 |
| johnthetubaguy | right | 09:32 |
| johnthetubaguy | thats kinda crazy | 09:32 |
| johnthetubaguy | so lets just revisit the other ones a second | 09:32 |
| ttx | and that's European morning, so as low as it will be | 09:32 |
| johnthetubaguy | bug 1444745 | 09:32 |
| openstack | bug 1444745 in OpenStack Compute (nova) "Updates RPC version alias for kilo" [High,Fix committed] https://launchpad.net/bugs/1444745 - Assigned to Alex Xu (xuhj) | 09:32 |
| johnthetubaguy | that one can be backported | 09:32 |
| johnthetubaguy | we usually forget to do that, it only really gets used by those using liberty anyway | 09:33 |
| johnthetubaguy | not too major | 09:33 |
| ttx | ok | 09:33 |
| johnthetubaguy | bug 1447132 | 09:33 |
| openstack | bug 1447132 in OpenStack Compute (nova) kilo "nova-manage db migrate_flavor_data doesn't do instances not in instance_extra" [High,New] https://launchpad.net/bugs/1447132 | 09:33 |
| johnthetubaguy | this is a utility that helps force the database to upgrade the data | 09:34 |
| johnthetubaguy | now we plan to force people to run that before some point in liberty, so we can drop the compat code | 09:34 |
| johnthetubaguy | that could be first step during a liberty upgrade, if it really has to be, so we could backport that OK, possibly | 09:34 |
| johnthetubaguy | its fairly risk free, as its changing a util not core code | 09:35 |
| johnthetubaguy | I would like to jam that in, if we had time, but we don't, so I am OK without that I think | 09:35 |
| ttx | So... how about we cancel the RC3 until we know if we have a chance to make one | 09:35 |
| ttx | We get that other fix in master, and once it's in, we see what the lead time is for the stable/kilo patch | 09:36 |
| johnthetubaguy | ttx: OK, so we reopen RC3 if/when bug 1448075 lands | 09:36 |
| openstack | bug 1448075 in OpenStack Compute (nova) kilo "Recent compute RPC API version bump missed out on security group parts of the api" [Critical,In progress] https://launchpad.net/bugs/1448075 | 09:36 |
| ttx | yes | 09:36 |
| ttx | if it lands and the lead time on the gate still lets us do RC3 before Thursday | 09:36 |
| johnthetubaguy | worst case, we give are selves some more compat code to keep during liberty, I think we can keep just those methods, but I need to check | 09:36 |
| johnthetubaguy | ttx: yes true | 09:37 |
| ttx | so let's keep an eye on that patch (https://review.openstack.org/#/c/177186/) and gate queue status today | 09:38 |
| ttx | johnthetubaguy: we can talk at the end of the day | 09:39 |
| johnthetubaguy | ttx: so I think the mistake we made was to be way too late trying to raise the compute RPCAPI, its a long time since we did that, and turns out we didn't really remember everything that was needed | 09:39 |
| ttx | In the mean time I'll kill the RC3 window | 09:39 |
| johnthetubaguy | ttx: OK, thanks | 09:39 |
| johnthetubaguy | ttx: so we have a first draft of Nova summit sessions in an etherpad now | 09:39 |
| johnthetubaguy | ttx: waiting for cross project ones, and finding session leaders before we upload all of those to sched | 09:40 |
| ttx | ok | 09:41 |
| johnthetubaguy | ttx: thanks sorry for the delay, stupid trains | 09:42 |
| ttx | johnthetubaguy: oh, we have option 3 too. Merge stuff in kilo that are not in master yet | 09:42 |
| ttx | Not sure that's a good idea though | 09:42 |
| johnthetubaguy | ttx: yeah, I am not sure I like that idea | 09:42 |
| ttx | ok, RC3 deleted for now | 09:43 |
| johnthetubaguy | ttx: tahnks | 09:43 |
| johnthetubaguy | doh | 09:43 |
| johnthetubaguy | thanks | 09:43 |
| ttx | johnthetubaguy: I'll let you explain the situation to the nova crowd | 09:45 |
| johnthetubaguy | ttx: will do | 09:45 |
| ttx | We could ask peopel to stop approving things, but I know it's useless | 09:46 |
| ttx | johnthetubaguy: oh, and while you wait on gate... https://wiki.openstack.org/wiki/ReleaseNotes/Kilo | 09:46 |
| ttx | We need those done by tomorrow | 09:47 |
| ttx | the earlier, the better to avoid edit conflicts | 09:47 |
| johnthetubaguy | ah, by tomorrow, oops, yes | 09:48 |
| johnthetubaguy | its on the agenda for the meeting on thursday, which is no good | 09:48 |
| johnthetubaguy | will push on that | 09:48 |
| ttx | yeah, at that point release will be out already | 09:49 |
| johnthetubaguy | right | 09:49 |
| *** dims has joined #openstack-relmgr-office | 10:12 | |
| ttx | gate lead-in down to 4h55min | 11:38 |
| *** dims has quit IRC | 11:44 | |
| *** dims has joined #openstack-relmgr-office | 11:51 | |
| *** eglynn has joined #openstack-relmgr-office | 11:58 | |
| eglynn | ttx: knock, knock ... ready when you are | 12:00 |
| eglynn | ttx: re. the ceilometerclient stable/kilo release, I need to discuss that a bit with gordc | 12:01 |
| eglynn | ttx: (on the agenda for our call at 13:30UTC today) | 12:01 |
| ttx | eglynn: ohai | 12:02 |
| ttx | eglynn: it's been published yesterday | 12:02 |
| ttx | #topic Ceilometer | 12:02 |
| eglynn | a-ha, I see https://pypi.python.org/pypi/python-ceilometerclient/1.0.14 | 12:02 |
| eglynn | cool | 12:03 |
| ttx | eglynn: so at this point we only respin in case of a major regression, blatant security hole or stuff that can't be fixed post-release | 12:03 |
| ttx | especially with the gate being on fire | 12:03 |
| eglynn | yep, got it | 12:03 |
| ttx | looking at ceilometer, you seem to be on the good side | 12:03 |
| eglynn | yep, nothing major on the horizon | 12:03 |
| ttx | Even https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Telemetry_.28Ceilometer.29 seems to be in good shape | 12:04 |
| * ttx gives out the "Good Citizen" badge to Ceilometer team | 12:04 | |
| eglynn | ttx: LOL :) ... finally! | 12:04 |
| ttx | eglynn: that doesn't mean you get the "webscale" badge :P | 12:05 |
| eglynn | ttx: touche! | 12:05 |
| ttx | But yeah, I appreciate you guys not being late :) | 12:05 |
| ttx | so, no remark on my side. Will retag RC2 to final on release day, unless you scream before then | 12:06 |
| eglynn | cool, sounds good! | 12:06 |
| ttx | Have a nice day! | 12:06 |
| eglynn | you too, thanks for your time! | 12:07 |
| ttx | SergeyLukjanov: ready when you are | 12:08 |
| ttx | #info No RC3 on the horizon | 12:08 |
| ttx | #topic Sahara | 12:08 |
| *** johnthetubaguy is now known as zz_johnthetubagu | 12:11 | |
| ttx | well, no Sergey | 12:25 |
| ttx | #undo | 12:25 |
| openstack | Removing item from minutes: <ircmeeting.items.Topic object at 0x8cc3350> | 12:25 |
| ttx | dhellmann: you there ? | 12:25 |
| SergeyLukjanov | ttx, hey | 12:25 |
| SergeyLukjanov | ttx, sorry for the delay | 12:25 |
| ttx | bah | 12:25 |
| ttx | #topic Sahara | 12:25 |
| dhellmann | ttx: here, but take SergeyLukjanov first I'm in the middle of a release for oslo.messaging | 12:25 |
| ttx | SergeyLukjanov: as I told eglynn, so at this point we only respin in case of a major regression, blatant security hole or stuff that can't be fixed post-release | 12:26 |
| ttx | especially with gate not behaving | 12:26 |
| SergeyLukjanov | so, no new issues in Sahara, we're ready for release | 12:26 |
| ttx | right, can't spot any such issues in shara backlog | 12:26 |
| ttx | so we are goot to go, will retag on Thursday as final | 12:26 |
| SergeyLukjanov | and I think we already fully finished testing and switched to L dev | 12:26 |
| ttx | SergeyLukjanov: nice. Will you be around to push the "other" shara pieces around release time ? | 12:27 |
| SergeyLukjanov | ttx, yup | 12:27 |
| ttx | SergeyLukjanov: I can do Sahara in the EU morning, so ping me then | 12:27 |
| SergeyLukjanov | ttx, okay | 12:27 |
| ttx | SergeyLukjanov: you need to work on https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Data_Processing_service_.28Sahara.29 | 12:28 |
| ttx | needs ot be finalized before EOD tomorrow | 12:28 |
| ttx | well, not "finalized" | 12:28 |
| ttx | but at least be made presentable | 12:28 |
| ttx | so people reading them don't feel it's WIP | 12:28 |
| SergeyLukjanov | ttx, ack, we have a draft already, will finalize it tomorrow EU morning | 12:28 |
| ttx | ok | 12:28 |
| ttx | that is all | 12:28 |
| ttx | SergeyLukjanov: have a great day! | 12:29 |
| ttx | #topic Oslo | 12:29 |
| SergeyLukjanov | what's about client release from stable/kilo? | 12:29 |
| SergeyLukjanov | with fresh requirements | 12:29 |
| dhellmann | SergeyLukjanov: we can't change the requirements of stable branch clients | 12:29 |
| ttx | #undo | 12:30 |
| openstack | Removing item from minutes: <ircmeeting.items.Topic object at 0x8cac710> | 12:30 |
| SergeyLukjanov | I mean https://github.com/openstack/python-saharaclient/compare/0.8.0...stable/kilo | 12:30 |
| ttx | SergeyLukjanov: is there any critical bug that would warrant a kilo point release ? Or could you just make a liberty release ? | 12:30 |
| SergeyLukjanov | we have requirements synced to stable/kilo branch of python-saharaclient | 12:30 |
| SergeyLukjanov | (Kilo release reqs) | 12:30 |
| SergeyLukjanov | do we need to have a release in this branch that includes them? | 12:30 |
| ttx | SergeyLukjanov: yeah, I don't think that is needed | 12:31 |
| SergeyLukjanov | no bugs | 12:31 |
| dhellmann | SergeyLukjanov: releasing an update of the library with requirements changes would require changing the minor version of the library, which would put it outside of the stable branch release series | 12:31 |
| dhellmann | you should probably revert that commit | 12:31 |
| dhellmann | that way when you have a bug fix later, you can release safely | 12:31 |
| SergeyLukjanov | dhellmann, in master we have 0.9.0 and in stable/kilo the latest one is 0.8.0 | 12:31 |
| ttx | SergeyLukjanov: also I wouldn't backport random fixes to the lib branch, that sounds overkill | 12:32 |
| dhellmann | the old minimums without caps are compatible with the stable branch | 12:32 |
| SergeyLukjanov | okay, so, no need to release client from stable branch | 12:32 |
| ttx | SergeyLukjanov: confirmed | 12:32 |
| SergeyLukjanov | thx | 12:32 |
| ttx | #topic Oslo | 12:32 |
| ttx | dhellmann: so oslo.messaging release was my only topic | 12:33 |
| dhellmann | I just tagged it, and I'm looking for my sandbox with the script for generating the release note mail | 12:33 |
| ttx | ok, so I think we are good. Maybe we can tag stable/kilo oslo-incubator | 12:33 |
| ttx | and release too | 12:34 |
| dhellmann | yes, let's go ahead and do that | 12:34 |
| ttx | i.e. I ca push a 2015.1.0 tag and cut stable/kilo from same commit | 12:34 |
| dhellmann | you mean branch, not tag, right? | 12:34 |
| dhellmann | yeah, ok, both | 12:34 |
| ttx | historically there was a tag too | 12:34 |
| ttx | not that it changes anything, but consistency ftw | 12:34 |
| dhellmann | right, I was a little behind and meant for the stable/kilo name | 12:34 |
| dhellmann | it should be safe to do that from master, let me check | 12:35 |
| ttx | yep | 12:35 |
| *** mordred has quit IRC | 12:35 | |
| *** mordred has joined #openstack-relmgr-office | 12:35 | |
| dhellmann | I have master as 0db1430757e1a33de7d3a20f4dd7048b4374d024 and that should be OK | 12:36 |
| ttx | ack that is what I have | 12:36 |
| ttx | all set | 12:38 |
| ttx | I think we are kilo-done as far as Oslo is concerned | 12:38 |
| ttx | dhellmann: anything on your mind ? | 12:38 |
| dhellmann | we may want to talk about centralizing library releases, since the semver thing continues to be a source of confusion | 12:39 |
| ttx | yes, I have a working session oin RelMgt track for that | 12:39 |
| dhellmann | excellent | 12:39 |
| dhellmann | did you see lifeless' post on requirements management? | 12:39 |
| ttx | I'd like to take a page off oslo book and see how wer can reorg the "release team" to do that | 12:39 |
| ttx | dhellmann: still on my todo | 12:40 |
| dhellmann | #link https://rbtcollins.wordpress.com/2015/04/28/dealing-with-deps-in-openstack/ | 12:40 |
| dhellmann | yes, "central" would need to include several people | 12:40 |
| ttx | I fear that's the only way to enforce some amount of process | 12:41 |
| ttx | The trick is to do it without getting in the way | 12:41 |
| dhellmann | at least until we have enough community knowledge, which I fear we won't be able to build until we stop tweaking the process :-) | 12:41 |
| ttx | but the current process inconsistency is not really looking good anyway | 12:41 |
| dhellmann | I'm thinking of ways to automate the process, but it keeps coming back to having the signed git tags | 12:42 |
| ttx | and as we rely more and more on lib stuff... starts to become a clear issue | 12:42 |
| ttx | dhellmann: if it all boils down to having a way to review tags.... we could push for that support in Gerrit | 12:42 |
| -openstackstatus- NOTICE: Gate is experiencing epic failures due to issues with mirrors, work is underway to mitigate and return to normal levels of sanity | 12:42 | |
| *** ChanServ changes topic to "Gate is experiencing epic failures due to issues with mirrors, work is underway to mitigate and return to normal levels of sanity" | 12:42 | |
| ttx | I like mordred's announcements. | 12:43 |
| dhellmann | yeah, I have no idea what would be involved in making it possible for gerrit to review tags. My thought was to have a file that lists the tags, and review that, and then have a bot apply the tag after the review | 12:43 |
| ttx | anyway, meat for that discussion | 12:43 |
| dhellmann | but we would have to trust the bot's gpg signature, which I suppose isn't a huge issue | 12:43 |
| ttx | dhellmann: https://groups.google.com/forum/#!topic/repo-discuss/VV_xj6ftvoY | 12:44 |
| dhellmann | I need to learn more about gpg's interaction with git | 12:44 |
| dhellmann | oh, interesting, I'll put that on my reading list | 12:44 |
| ttx | well, it's just other people complaining about that feature gap | 12:44 |
| ttx | not really interesting reading | 12:44 |
| dhellmann | ah | 12:45 |
| ttx | just proving it's not completely an openstack thing | 12:45 |
| mordred | dhellmann: I would like very much to get someone to add tag submission to gerrit directly | 12:45 |
| mordred | it really just takes someone being willing to write java | 12:45 |
| ttx | mordred: I'll write Haskell before I'm back to Java code | 12:46 |
| mordred | maybe we can convince mirantis to let SergeyLukjanov do it - he likes java | 12:46 |
| * SergeyLukjanov reading | 12:46 | |
| ttx | Although writing it is less painful than trying to package it, trust me. | 12:46 |
| ttx | dhellmann: so all that is left of https://etherpad.openstack.org/p/the-big-thaw is the external dep pinning on stable/kilo | 12:47 |
| ttx | dhellmann: I think we can postpone that until YVR | 12:47 |
| ttx | no point in doing that if we rebuild a new house of cards | 12:48 |
| dhellmann | yes, I would like to put that off as long as we can | 12:48 |
| dhellmann | right | 12:48 |
| SergeyLukjanov | mordred, I like JVM, not Java, I've been writing on pure Java about 3 or 4 years ago last time ;) | 12:48 |
| mordred | SergeyLukjanov: :) | 12:48 |
| mordred | SergeyLukjanov: but you can do ANYTHING! ;) | 12:48 |
| ttx | SergeyLukjanov: no no you like writing Java code and even more having on Gerrit code. | 12:48 |
| ttx | hacking* | 12:49 |
| dhellmann | SergeyLukjanov: I'll bet it's like riding a bike. You'll pick it up again in no time | 12:49 |
| ttx | dhellmann: it's more like riding a bike without a saddle | 12:49 |
| dhellmann | heh | 12:49 |
| SergeyLukjanov | heh | 12:49 |
| ttx | dhellmann: you can do it, but only if that's the only way to travel | 12:49 |
| SergeyLukjanov | gerrit in build using GWT and that's the main reason IMO to avoid looking in its code | 12:50 |
| * ttx throws up in a remote corner of the office | 12:50 | |
| SergeyLukjanov | but from our PoV gerrit with tags support is very usefull | 12:50 |
| ttx | SergeyLukjanov: right! | 12:51 |
| *** eglynn has quit IRC | 13:08 | |
| *** zz_johnthetubagu is now known as johnthetubaguy | 13:12 | |
| *** eglynn has joined #openstack-relmgr-office | 13:31 | |
| ttx | mestery: ready when you are | 13:43 |
| mestery | ttx: Here | 13:44 |
| ttx | #topic Neutron | 13:44 |
| ttx | mestery: struggling a lot to close that RC3 window | 13:44 |
| mestery | YEs, I see that https://review.openstack.org/177789 is having issues in the check queue | 13:44 |
| ttx | but at least the change is in master | 13:44 |
| ttx | so I still hope we'll get it through | 13:45 |
| mestery | ++ | 13:45 |
| ttx | but shows the danger of late respins | 13:45 |
| ttx | you're at the mercy of gate weather | 13:45 |
| mestery | Totally agree, but on the other hand, I'm glad testing found these issues, so :) | 13:45 |
| ttx | well, I would even more glad if automated testing found those issues 2 months ago | 13:45 |
| mestery | Completely agree | 13:46 |
| ttx | anyway, I think we should get it in by EOD | 13:46 |
| ttx | and we have patches merged for RC3 already so backpedaling is not really a good option | 13:46 |
| ttx | so... full speed ahead! | 13:46 |
| mestery | Agreed | 13:47 |
| mestery | ++ | 13:47 |
| ttx | https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Network_Service_.28Neutron.29 looks in good shape | 13:47 |
| mestery | I've had people working on it, I'll go through it again and update as needed | 13:47 |
| ttx | mestery: if by EOD we don't have that last patch in we have two choices | 13:48 |
| ttx | we can delay RC3 until tomorrow (leaving little time to catch weird errors like corrupted tarballs) | 13:48 |
| ttx | and we can cut without that fix in | 13:49 |
| mestery | Well, lets just see if we can get that in | 13:49 |
| mestery | And not have to look at those options | 13:49 |
| mestery | Though I agree, those are the options should we not succeed | 13:49 |
| ttx | full speed ahead! | 13:49 |
| mestery | :) | 13:49 |
| ttx | suffice to say only really odd stuff will trigger a RC addition at this point | 13:50 |
| mestery | ttx: Just curious, how many other RC3s are in the works? Are we the only one? | 13:50 |
| ttx | There was a Nova one but the fix isn't in master yet so I cancelled it | 13:50 |
| mestery | \++ to that | 13:50 |
| mestery | OK | 13:50 |
| ttx | we may revive it if the fix finally makes it, since it's a pretty critical thing | 13:50 |
| ttx | but in the mean time we wait | 13:51 |
| mestery | OK | 13:51 |
| ttx | there may be a swift one | 13:51 |
| ttx | only news so far | 13:51 |
| mestery | Ack | 13:51 |
| * mestery puts on his zuul monitoring glasses for the day | 13:52 | |
| ttx | the gate os completely desintegrating before my eyes | 13:52 |
| ttx | is* | 13:52 |
| mestery | I know :( | 13:52 |
| mestery | Lots of red on there | 13:52 |
| ttx | let's hope they figure it out | 13:52 |
| mestery | ++ | 13:52 |
| ttx | at least we cut on the lead time. We seem to fail faster now | 13:52 |
| mestery | :) | 13:53 |
| mestery | Positive spin I guess | 13:53 |
| ttx | this morning the lead time was 15 hours | 13:53 |
| mestery | Yikes | 13:53 |
| ttx | so it took 15 hours to fail | 13:53 |
| mestery | If it was like that now, we'd just as well spin RC3 without that last one. | 13:53 |
| ttx | OK, I'll be talking to you later | 13:54 |
| mestery | Yes, talk to you later | 13:54 |
| *** dims has quit IRC | 14:15 | |
| *** dims has joined #openstack-relmgr-office | 14:15 | |
| ttx | nikhil_k_: o/ | 14:20 |
| nikhil_k_ | ttx: hi | 14:21 |
| ttx | #topic Glance | 14:21 |
| ttx | so at this point we only respin in case of a major regression, blatant security hole or stuff that can't be fixed post-release | 14:21 |
| ttx | especially with the gate on fire | 14:21 |
| ttx | nikhil_k_: do you have anything that fits that description | 14:21 |
| nikhil_k_ | makes sense | 14:21 |
| ttx | I don't see anything in the kilo-rc-potential list or the proposed backports | 14:22 |
| ttx | nikhil_k_: in the remaining time (before tomorrow EOD) you should fill out https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Image_Service_.28Glance.29 | 14:27 |
| ttx | so that it's ready for release day | 14:27 |
| nikhil_k_ | ttx: all three? | 14:27 |
| nikhil_k_ | Key New Features, Known Issues and Upgrade Notes ? | 14:27 |
| nikhil_k_ | just trying to make sure if ground is covered | 14:28 |
| ttx | Yes. If you don't have anything to say in the latter sections, just remove them | 14:28 |
| ttx | If you have significant issues that won't get fixed in release, good idea to mention them in "Known Issues" | 14:28 |
| nikhil_k_ | ttx: ok. I don't have anything else for now in Kilo. | 14:28 |
| nikhil_k_ | ok | 14:28 |
| ttx | all good | 14:29 |
| nikhil_k_ | ttx: so about the upgrade notes | 14:29 |
| nikhil_k_ | ttx: we have tried to apply as many UpgradeImpact flags as possible. | 14:29 |
| nikhil_k_ | Where do those flags go? | 14:29 |
| nikhil_k_ | or you get some notification to include them if misses? | 14:30 |
| nikhil_k_ | missed* | 14:30 |
| ttx | They don't automatically go anywhere. But you should be able to grep them in the git log and mention the most significant glitches | 14:30 |
| nikhil_k_ | ok | 14:30 |
| nikhil_k_ | I hoped some digest is already created | 14:30 |
| ttx | They are supposed to help in redacting that section | 14:30 |
| ttx | not that I know of | 14:30 |
| nikhil_k_ | anyways, grepping is always fun | 14:30 |
| ttx | nikhil_k_: OK, so unless we talk again, I'll be releasing RC2 as final on Thursday. You get those release notes filled before then. | 14:31 |
| *** notmyname has quit IRC | 14:31 | |
| ttx | nikhil_k_: talk to you later! | 14:33 |
| ttx | thingee: around? | 14:33 |
| thingee | ttx: hi | 14:33 |
| ttx | #topic Cinder | 14:33 |
| thingee | bug came up with config generator. Unfortunately nova also has it | 14:34 |
| *** notmyname has joined #openstack-relmgr-office | 14:34 | |
| thingee | https://bugs.launchpad.net/cinder/+bug/1447380 | 14:34 |
| openstack | Launchpad bug 1447380 in OpenStack Compute (nova) "wrong cinder.conf.sample generation: missing directives for keystone_authtoken (at least)" [Critical,In progress] - Assigned to John Griffith (john-griffith) | 14:34 |
| ttx | thingee: that was fixed in RC2 for Cinder right | 14:34 |
| ttx | thingee: Nova dismissed it as being broken for a long time | 14:34 |
| thingee | ok sorry missed that on there side. | 14:35 |
| nikhil_k_ | (sorry, got disconnected from IRC. talk to you later) | 14:35 |
| ttx | as I told nikhil; at this point we only respin in case of a major regression, blatant security hole or stuff that can't be fixed post-release | 14:35 |
| ttx | I don't see any such things in the pipe for Cinder | 14:35 |
| ttx | Also the gate is on fire so we can't really respin anything at the moment | 14:35 |
| thingee | I've been watching the incoming bugs pretty closely and caught up. nothing important came in | 14:35 |
| * thingee throws a cup of water at it | 14:36 | |
| ttx | So I'll retag RC2 as final on Thursday, unless we speak again (or you send me an email) | 14:36 |
| ttx | in the mean time, you should apply final polish to https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Block_Storage_.28Cinder.29 | 14:36 |
| thingee | ttx: btw, documentation with release note items. oh my :) | 14:36 |
| thingee | so happy about this | 14:37 |
| ttx | nice | 14:37 |
| ttx | thingee: anything else ? | 14:37 |
| thingee | git log --grep=UpgradeImpact --since=6.month ... I think that does it? | 14:38 |
| thingee | nikhil_k_: ^ | 14:38 |
| nikhil_k_ | nice, thanks | 14:38 |
| thingee | that's it for me. gearing up for sessions and liberty specs :) | 14:38 |
| thingee | ttx: thanks | 14:38 |
| ttx | awesome, ttyl | 14:38 |
| ttx | david-lyle: hi! | 14:38 |
| david-lyle | ttx: o/ | 14:46 |
| ttx | #topic Horizon | 14:46 |
| ttx | As I tell everyone today... at this point we only respin in case of a major regression, blatant security hole or stuff that can't be fixed post-release | 14:46 |
| ttx | especially since the gate decided to burn all day | 14:46 |
| ttx | Looking at Horizon I see one thing that could have qualified | 14:46 |
| ttx | https://bugs.launchpad.net/horizon/+bug/1447288 | 14:47 |
| openstack | Launchpad bug 1447288 in OpenStack Dashboard (Horizon) "create volume from snapshot using horizon error" [Critical,In progress] - Assigned to Masco Kaliyamoorthy (masco) | 14:47 |
| ttx | But since it's not even fixed in master yet, I think that will have to live as a known release bug and get fixed post-release | 14:47 |
| david-lyle | I don't think that's worth a new spin | 14:47 |
| ttx | david-lyle: at least not a very late spin. | 14:47 |
| ttx | david-lyle: ok, so RC2 is still good to go at this point | 14:48 |
| david-lyle | we can backport for the next stable kilo release | 14:48 |
| david-lyle | yes | 14:48 |
| ttx | Time to focus on https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Dashboard_.28Horizon.29 | 14:48 |
| david-lyle | indeed | 14:49 |
| ttx | That should be completed before EOD tomorrow, since the release will happen before you get up on Thursday | 14:49 |
| david-lyle | ok | 14:49 |
| david-lyle | will do | 14:49 |
| ttx | Unless we talk again, will retag RC2 as final on release day. Thanks for your help! | 14:49 |
| david-lyle | thank you | 14:49 |
| ttx | ttyl | 14:50 |
| david-lyle | later | 14:50 |
| *** johnthetubaguy is now known as zz_johnthetubagu | 15:22 | |
| -openstackstatus- NOTICE: gerrit has been restarted to clear an issue with its event stream. any change events between 14:43-15:30 utc should be rechecked or have their approval votes reapplied to trigger jobs | 15:37 | |
| ttx | morganfainberg: around? | 15:48 |
| morganfainberg | Ttx sure am | 15:48 |
| ttx | #topic Keystone | 15:48 |
| ttx | As I tell everyone today... at this point we only respin in case of a major regression, blatant security hole or stuff that can't be fixed post-release | 15:48 |
| morganfainberg | Nothing I've seen qualifies for that in keystone. | 15:49 |
| ttx | right me neither | 15:49 |
| ttx | So I'll retag RC2 as final on thursday, unless we speak again | 15:49 |
| morganfainberg | Sounds good. | 15:49 |
| morganfainberg | Release notes are under way | 15:49 |
| ttx | Yep you should complete those by EOD tomorrow | 15:50 |
| ttx | since the release will be out by the time you get up on thursday | 15:50 |
| ttx | so you can wake up to campagne | 15:50 |
| ttx | err | 15:50 |
| ttx | champagne | 15:50 |
| morganfainberg | I will work on them today. But I am unavailable all tomorrow. | 15:50 |
| ttx | morganfainberg: ok, so TODAY. Or delegate | 15:50 |
| morganfainberg | Will be traveling. I shall delegate as well to another core. | 15:50 |
| morganfainberg | To finalize at our meeting. | 15:50 |
| ttx | Alright | 15:50 |
| morganfainberg | :) | 15:50 |
| ttx | Thanks for everything ! | 15:51 |
| morganfainberg | Yay Kilo release! | 15:51 |
| ttx | I'll be seeing you soon. | 15:51 |
| morganfainberg | Yep! | 15:51 |
| ttx | notmyname: around now if you are | 15:51 |
| morganfainberg | Thanks! | 15:51 |
| notmyname | ttx: I'm here | 15:51 |
| ttx | #topic Swift | 15:51 |
| ttx | notmyname: did you come to a conclusion on what we discussed yesterday ? | 15:52 |
| notmyname | looking at it right now | 15:52 |
| *** ChanServ changes topic to "OpenStack Release Managers office - Where weekly 1:1 sync points between release manager and PTLs happen - Logged at http://eavesdrop.openstack.org/irclogs/%23openstack-relmgr-office/" | 15:53 | |
| ttx | so for the record, we may consider a RC3, but we'll know more later today | 15:58 |
| notmyname | yes | 15:58 |
| notmyname | also, I've started working on the release notes wiki page | 15:59 |
| notmyname | and hope to get to summit scheduling later this week | 15:59 |
| ttx | ok, as far as release notes go, try to get them completed by EOD tomorrow | 16:00 |
| ttx | Release will happen before you get up on Thursday | 16:00 |
| notmyname | ok | 16:00 |
| notmyname | what is the release time? | 16:00 |
| notmyname | 0000UTC? | 16:00 |
| notmyname | or is there a set time? | 16:00 |
| ttx | I starttagging stuff at 0800 UTC and usually finish around 13:00 utc | 16:00 |
| notmyname | ok | 16:00 |
| ttx | PR goes off at 14:00 utc I think | 16:01 |
| ttx | but I just send email when I'm done | 16:01 |
| ttx | Alright, I'll be talking to you later today on that RC3 | 16:01 |
| notmyname | thanks | 16:01 |
| ttx | devananda: raedy when you are | 16:01 |
| ttx | hmm, actually I'll be back in 10min | 16:04 |
| devananda | ttx: mmkay | 16:05 |
| devananda | i'll be here | 16:05 |
| ttx | #topic Ironic | 16:16 |
| ttx | devananda: o/ | 16:17 |
| ttx | devananda: As I tell everyone today... at this point we only respin in case of a major regression, blatant security hole or stuff that can't be fixed post-release | 16:17 |
| ttx | I see no such thing in Ironic kilo-rc-potential or proposed backports | 16:17 |
| devananda | ttx: nor do I | 16:17 |
| ttx | Alright! | 16:18 |
| devananda | one of those seems to be a bug that affects a lot of projects | 16:18 |
| devananda | some of htem have done backports? | 16:18 |
| devananda | so I'm unclear about it | 16:18 |
| ttx | which one ? | 16:18 |
| devananda | https://bugs.launchpad.net/ironic/+bug/1384379 | 16:18 |
| openstack | Launchpad bug 1384379 in OpenStack Compute (nova) "versions resource uses host_url which may be incorrect" [High,In progress] - Assigned to shihanzhang (shihanzhang) | 16:18 |
| ttx | No they don't | 16:18 |
| devananda | ah. or they fixed it earlier in the cycle | 16:19 |
| devananda | gotcha | 16:19 |
| ttx | That leaves https://wiki.openstack.org/wiki/ReleaseNotes/Kilo | 16:19 |
| ttx | you should add a Ironic section to that | 16:19 |
| devananda | https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Kilo | 16:19 |
| ttx | and fill it before EOD tomorrow | 16:19 |
| devananda | how's that look? | 16:19 |
| ttx | Looks good | 16:19 |
| ttx | maybe just copy/paste | 16:20 |
| devananda | cool, will do now | 16:20 |
| devananda | i think that's it :) | 16:20 |
| ttx | a few TODOs still in there | 16:20 |
| devananda | ooh. right. | 16:20 |
| devananda | will do once those are done :) | 16:20 |
| ttx | Also might want to map to the other format, but I don't mind people being original there :) | 16:21 |
| ttx | OK, so unless we speak again I'll retag RC2 as final on release day and make things happen in LP and tarballs and stuff | 16:21 |
| ttx | devananda: ttyl ! | 16:22 |
| devananda | ttx: cheers! | 16:22 |
| ttx | We seem to be out of SlickNiks | 16:22 |
| ttx | let's wait a few | 16:22 |
| ttx | #topic Trove | 16:22 |
| ttx | For the record, nothing critical seems to have crept up there | 16:23 |
| ttx | So that leaves us with a RC3 for Neutron, and potential ones for Swift and Nova. | 16:23 |
| ttx | mestery: that damn change is really not playing ball, failing again in check | 16:26 |
| ttx | that said the gate is now empty so retries might be an option | 16:26 |
| mestery | ttx: Lets give it anotehr spin, I noticed the same. | 16:26 |
| mestery | ttx: But it is being difficult, this time failing in some random way in the functional job unrelated to the change. | 16:26 |
| ttx | zz_johnthetubagu: given that gate seems to be more amenable now, I'm willing to consider the Nova RC3 if https://review.openstack.org/#/c/177186/ makes it to master over the next hours | 16:27 |
| sdague | mestery: what's the pass rate of the neutron functional job? I've seen that failing a lot in the gate | 16:28 |
| mestery | sdague: One second, in another thread I'm unwiding | 16:29 |
| ttx | OK, I'll be abck in a couple of hours to take the temperature on those RC3s again | 16:30 |
| ttx | #endmeeting | 16:30 |
| openstack | Meeting ended Tue Apr 28 16:30:17 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:30 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-04-28-07.56.html | 16:30 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-04-28-07.56.txt | 16:30 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-04-28-07.56.log.html | 16:30 |
| mestery | sdague: http://goo.gl/nzlfV7 | 16:31 |
| mestery | sdague: Looks like it spiked a bit but has come back down since last week,. | 16:32 |
| sdague | yeh, still kind of high, I'd expect the per project jobs to be shooting for much lower fail rates | 16:32 |
| sdague | given the smaller number of moving parts | 16:32 |
| ttx | zz_johnthetubagu: bah, the critical Nova RC3 change fails again in check | 16:34 |
| mestery | sdague: Agreed | 16:35 |
| ttx | mestery: I trust you will recheck it when it finally fails ? | 16:38 |
| mestery | ttx: I am on it. Go and enjoy your evening and we'll see what happens with it on it's next time through the loop :) | 16:39 |
| sdague | ttx: so... keystone middleware is basically spewing hundreds of warning lines all over the place which seems unhelpful | 16:42 |
| sdague | it's actually making it really hard to figure out where real issues might be for these fails | 16:42 |
| sdague | morganfainberg: ^^^ | 16:43 |
| morganfainberg | sdague: ack | 16:44 |
| morganfainberg | sdague: stable or 1.6.x? | 16:44 |
| sdague | http://logs.openstack.org/86/177186/3/check/check-tempest-dsvm-full/38a8915//logs/screen-c-api.txt.gz?level=TRACE#_2015-04-28_16_15_09_574 - kilo | 16:44 |
| sdague | I think both | 16:44 |
| morganfainberg | hm. | 16:45 |
| morganfainberg | let me check wondering if something else changed | 16:45 |
| sdague | so, I brought this up somewhere at least a week ago, and I guess it got lost | 16:45 |
| morganfainberg | hm. | 16:47 |
| sdague | right, so keystonemiddleware.auth_token has emitted 3.5 million warning messages in the last 7 days of gate runs - http://logstash.openstack.org/#eyJzZWFyY2giOiJsb2dsZXZlbDpXQVJOSU5HIEFORCBtb2R1bGU6a2V5c3RvbmVtaWRkbGV3YXJlLmF1dGhfdG9rZW4iLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MzAyMzk2NTQ3MTV9 | 16:48 |
| morganfainberg | sdague: yeah looking at it now for you. | 16:48 |
| sdague | approximately 0% seem to be useful | 16:48 |
| morganfainberg | sdague: seeing when this was introduced so i can figure out why this needs to be a log warn | 16:48 |
| morganfainberg | sdague: or why it originally was marked as such | 16:48 |
| morganfainberg | sdague: i'm inclined to say this could be INFO | 16:49 |
| sdague | honestly, it should be deleted | 16:49 |
| morganfainberg | eh, mixed feelings on that | 16:49 |
| sdague | I don't know anything useful that's being presented with that information | 16:49 |
| morganfainberg | it is useful to know a request didn't pass a x-subject-token | 16:49 |
| morganfainberg | erm x-auth-token | 16:49 |
| morganfainberg | especially in inter-service work | 16:50 |
| sdague | to an operator? | 16:50 |
| sdague | on every single request? | 16:50 |
| morganfainberg | it's not every request | 16:50 |
| morganfainberg | sdague: it is only if we don't have an x-auth-token | 16:50 |
| morganfainberg | sdague: in the request | 16:50 |
| sdague | it looks like it's in most of these requests | 16:50 |
| morganfainberg | sdague: like i said, looking now to see why this was introduced. | 16:50 |
| sdague | and what exactly will an operator do with that information? | 16:51 |
| morganfainberg | sdague: ah crud middelware is pre-request id | 16:51 |
| morganfainberg | nvm | 16:52 |
| morganfainberg | debug might be the right place | 16:52 |
| morganfainberg | sdague: i was thinking if it showed the req-id, then you could at lease correlate people trying to access w/o a token | 16:52 |
| morganfainberg | but i'm wrong. this is likely a debug statement mis-marked as warn | 16:52 |
| sdague | yes, you can not, but even if you could, what would an operator be expected to do? email people and tell them what? | 16:52 |
| morganfainberg | sdague: if someon was complaining about XXX not working when i try and access nova boot | 16:53 |
| morganfainberg | "well your app isn't passing x-auth-token" | 16:53 |
| morganfainberg | it's an edge case | 16:53 |
| morganfainberg | like i said, this is likely a debug thing mismarked as warn | 16:53 |
| sdague | it's a super edge case, given that we do it 3.5 million times and it results in 0 failures | 16:53 |
| sdague | on it's own | 16:53 |
| morganfainberg | sdague wow... | 16:57 |
| morganfainberg | grizzly level of old code here | 16:57 |
| morganfainberg | sdague: so this should be downgraded to debug. | 16:58 |
| morganfainberg | sdague: at most. | 16:58 |
| morganfainberg | sdague: if not removed. | 16:58 |
| morganfainberg | sdague: it could have value at debug but likely not too much | 16:58 |
| sdague | yeh, in it's current form it doesn't seem all that useful. Anyway, it would be good to cut new libs soonish, because this will look like a regression to people given the noise level | 16:59 |
| morganfainberg | sdague: we've been issuing these logs at in the same way (same message) since grizzly | 17:00 |
| sdague | morganfainberg: no, this is new | 17:00 |
| morganfainberg | sdague: something else has changed not providing an x-auth-token header | 17:00 |
| morganfainberg | a bunch of requests | 17:00 |
| sdague | I have definitely not seen this | 17:00 |
| morganfainberg | possibly related to discovery? | 17:00 |
| morganfainberg | sdague: it's not middleware changing in this case trust me. it's something else has changed. | 17:01 |
| sdague | it isn't in juno | 17:01 |
| sdague | http://logs.openstack.org/59/177759/1/check/check-tempest-dsvm-full-juno/fe29052/logs/screen-n-api.txt.gz?level=WARNING | 17:01 |
| morganfainberg | sdague: because whatever else change hadn't happened in juno. juno doesn't issue the requests w/o the x-auth-token header | 17:01 |
| morganfainberg | sdague: it's not a big deal filing a bug and getting this committed | 17:02 |
| sdague | so... keystone client changing things? | 17:02 |
| morganfainberg | sdague: or other clients? | 17:02 |
| sdague | what could change that behavior | 17:02 |
| morganfainberg | sdague: any client. | 17:02 |
| sdague | morganfainberg: it's multiple cross services it looks like | 17:02 |
| morganfainberg | sdague: so might be ksc related, might be other client changes as well | 17:03 |
| sdague | which means keystone client is more likely culprit | 17:03 |
| morganfainberg | sdague: my point was just "it isn't keystonemiddleware" | 17:03 |
| sdague | the session work got pushed into all the clients | 17:03 |
| morganfainberg | but the fix is clearly to just downgrade that in middleware | 17:03 |
| morganfainberg | so we have less spewing. | 17:03 |
| morganfainberg | downgrade/remove/whatever | 17:03 |
| sdague | we have a bunch of keystoneclient warnings as well - http://logs.openstack.org/86/177186/3/check/check-tempest-dsvm-full/38a8915//logs/screen-n-api.txt.gz?level=WARNING | 17:06 |
| sdague | I wonder if there is coupling | 17:06 |
| morganfainberg | possibly | 17:06 |
| morganfainberg | let me bug jamielennox w | 17:06 |
| sdague | so 2.2 million of those in 7 days | 17:07 |
| sdague | http://logstash.openstack.org/#eyJzZWFyY2giOiJtb2R1bGU6a2V5c3RvbmVjbGllbnQuYXV0aC5pZGVudGl0eS5iYXNlIEFORCBsb2dsZXZlbDpXQVJOSU5HIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDMwMjQwODI2NzcwfQ== | 17:08 |
| morganfainberg | sdague: https://review.openstack.org/#/q/Iab569a14a9f3268abef6bc36e46cf15dc16564b9,n,z | 17:08 |
| sdague | yeh, basically it looks like the bulk of the WARNINGs in the system are from keystone.* components | 17:09 |
| morganfainberg | sdague: i'll corner jamielennox about the ksc stuff | 17:13 |
| morganfainberg | but at least middleware i have reviews up and as soon as they merge i'll do the shuffle. | 17:13 |
| morganfainberg | so we can have them out on pypi | 17:14 |
| sdague | sounds good | 17:14 |
| sdague | yeh, because the keystone stuff gets consumed so many other places, I think we need a lot more care to when it starts raising ugly red flags | 17:14 |
| *** eglynn has quit IRC | 18:00 | |
| *** eglynn has joined #openstack-relmgr-office | 18:30 | |
| *** mestery has quit IRC | 19:34 | |
| *** mestery has joined #openstack-relmgr-office | 19:39 | |
| ttx | mestery: alright, I think NeutronRC3 is a go | 19:40 |
| mestery | ttx: Was just going to say the same to you :) | 19:40 |
| ttx | tagging in progress | 19:41 |
| ttx | takes forever to clone git though | 19:44 |
| mestery | I know :( | 19:48 |
| *** openstackstatus has quit IRC | 19:52 | |
| *** openstackstatus has joined #openstack-relmgr-office | 19:54 | |
| *** ChanServ sets mode: +v openstackstatus | 19:54 | |
| *** eglynn has quit IRC | 19:55 | |
| sdague | ttx, so with the nova rc3, we decided not to add https://review.openstack.org/#/c/176806/ to it? | 20:56 |
| ttx | sdague: it wasn't in John's list this morning | 20:57 |
| sdague | ok | 20:57 |
| ttx | at this stage the lesser the better, but it might have been oversight | 20:57 |
| sdague | yeh, that's fine, it would have been nice to have, but I didn't realize the rc3 was happening, and I was firefighting this morning | 20:58 |
| ttx | sdague: yeah, in the morning when we had the discussion the gate was pretty backlogged so we were pretty pessimistic on our RC3 abilities | 21:02 |
| ttx | hence the very conservative approach | 21:03 |
| sdague | yeh, no worries | 21:03 |
| ttx | sdague: but now that you pushed that "alias tox=true" on nodes, it works better | 21:03 |
| sdague | heh | 21:03 |
| sdague | well, if neutron doesn't rando kill top of gate, we'll land a bunch here shortly | 21:05 |
| ttx | dansmith: c | 21:07 |
| ttx | cross those appendage things again | 21:07 |
| ttx | worked well last time | 21:07 |
| dansmith | ttx: crossing | 21:08 |
| dims | sdague: an actual review with that alias? | 21:09 |
| dansmith | dims: you're too easy | 21:09 |
| dims | hahaha | 21:09 |
| dims | i went looking for it dansmith! | 21:09 |
| dansmith | sdague: looks like that test might be hung? | 21:10 |
| dansmith | oh nevermind | 21:10 |
| dansmith | read the timestamp wrong | 21:10 |
| dansmith | it sure has been taking its sweet time | 21:10 |
| dansmith | ttx: I'm going to run off for a bit, but rest assured my appendages will remain crossed until I return | 21:18 |
| ttx | looks like we have a winner again | 21:30 |
| dansmith | woot | 21:51 |
| ttx | dansmith: RC3 on its way, thanks for your help | 21:51 |
| dansmith | ttx: likewise! :) | 21:51 |
| dansmith | ttx: shall I unalias tox now or do you have more to wait for? :P | 21:51 |
| ttx | dansmith: we have swift coming up | 21:52 |
| dansmith | okay, better leave it for a bit longer then :) | 21:52 |
| ttx | yep | 21:53 |
| *** dims_ has joined #openstack-relmgr-office | 23:29 | |
| *** dims has quit IRC | 23:31 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!