17:02:52 <tnurlygayanov> #startmeeting Murano Bug Scrub
17:02:53 <openstack> Meeting started Mon Jun  2 17:02:52 2014 UTC and is due to finish in 60 minutes.  The chair is tnurlygayanov. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:02:54 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:02:57 <openstack> The meeting name has been set to 'murano_bug_scrub'
17:03:26 <sjmc7> i'm on a phone call but i'll be keeping an eye on this
17:03:27 <ativelkov> o/
17:03:29 <tnurlygayanov> ok, we have many new issues
17:03:57 <akuznetsova_> hi
17:04:13 <ruhe> tnurlygayanov: where should we look for a list of bugs to be scrubbed?
17:04:22 <tnurlygayanov> so, we can discuss all issues assigned to the next milestone and after that discuss all new issues and assign/change the statuses
17:04:56 <ruhe> ok
17:05:19 <tsufiev> suppose, we start with https://launchpad.net/murano/+milestone/juno-1 ?
17:05:20 <tnurlygayanov> ok, let's review all bugs, whih assigned to the next milestone: https://launchpad.net/murano/+milestone/juno-1
17:05:58 <tnurlygayanov> tsufiev, yes :)
17:06:23 <tnurlygayanov> so, we have 36 bugs for this mailstone
17:07:05 <tnurlygayanov> and only 10 from this list have status 'Fix Commited/Fix Released'
17:07:29 <tnurlygayanov> https://bugs.launchpad.net/murano/+bug/1311534 - with High priority
17:07:48 <tnurlygayanov> this is assigned to Sergey
17:08:12 <tnurlygayanov> sergmelikyan, do you plan to fix it in juno-1?
17:08:13 <tsufiev> it was reported by me, and i'm not sure whether it is already fixed or not
17:08:48 <tsufiev> there were a lot of issues with integration, maybe it was a consequence of some other bug...
17:09:25 <tnurlygayanov> tsufiev, yes, probably, need to recheck and update the description of this issue, now it is unclear
17:09:45 <ruhe> let's leave it as is for now. tnurlygayanov: will you try to reproduce it?
17:09:58 <sergmelikyan> tnurlygayanov, no, this will not be fixed in juno-1, since we need to redesign statuses
17:10:01 <tnurlygayanov> yes, I will try to reproduce it
17:10:15 <tnurlygayanov> so...
17:10:37 <tnurlygayanov> this issue has High priority...
17:11:01 <tnurlygayanov> ok, le'ts move this issue to the next milestone, I hope this is not blocker for our release.
17:11:26 <ruhe> tnurlygayanov: cool, assign it on yourself then please
17:11:45 <tnurlygayanov> ok
17:11:50 <tnurlygayanov> next issue is https://bugs.launchpad.net/murano/+bug/1314106
17:12:38 <tsufiev> sjmc7, you are the assignee
17:13:04 <sjmc7> i'l lget this done in juno.1
17:13:04 <tnurlygayanov> sjmc7, any comments? :) do you plan to fix it in juno-1 release?
17:13:15 <tnurlygayanov> ok, cool
17:13:22 <katyafervent2> everything is ok with this issue
17:13:22 <sjmc7> if we make environment names unique within a tenant it will fix it
17:14:00 <tnurlygayanov> the next one: https://bugs.launchpad.net/murano/+bug/1314180
17:14:27 <tnurlygayanov> sjmc7 , katyafervent2: today we discussed this issue with slagun
17:14:45 <tnurlygayanov> he is agreed with this idea
17:15:09 <ruhe> i'd mark 1314180 as "want' fix" because we're moving this functionality to the python-muranoclient
17:15:22 <ruhe> ativelkov: what do you think?
17:15:49 <ativelkov> ruhe: I agree, this should not be done in manage
17:16:21 <ativelkov> IMO, manage should do only the DB migrations
17:16:26 <tnurlygayanov> ok, status was chaged and I add your comments to this issue
17:16:35 <tsufiev> does python-muranoclient import-package handle 'owned' properly?
17:16:36 <ruhe> tnurlygayanov: already
17:16:43 <ativelkov> tsufiev: yes
17:16:55 <tsufiev> ok, then won't fix indeed :)
17:16:59 <ativelkov> as it uses the API, which natively sets the owner to the current user
17:17:10 <ruhe> tsufiev: even if it didn't, it should be much easier to do in python client, since it has all the needed context
17:17:31 <tnurlygayanov> ok, next issue is https://bugs.launchpad.net/murano/+bug/1318095
17:17:40 <tnurlygayanov> it is unassigned
17:17:44 <tsufiev> ruhe, just checked whether we had to reformulate that one
17:18:33 <tsufiev> funny one :)
17:18:38 <ruhe> 1318095 needs volunteers
17:18:58 <tsufiev> http://comics.soup.io/post/87788721/PNG-vs-JPG :)))
17:19:15 <tnurlygayanov> looks like we have hardcoded file type for logo?
17:19:39 <tnurlygayanov> ruhe, ok, what about 'fruit' tag?
17:19:55 <tnurlygayanov> *for this issue?
17:20:03 <ruhe> tnurlygayanov: description says that package definition had .png while actual file was .jpeg
17:20:14 <tnurlygayanov> yes
17:20:27 <ruhe> tnurlygayanov: i wouldn't mark high priority bug as a low-hanging-fruit
17:20:30 <ativelkov> afair, the pakcage validation enforces png
17:20:34 <tsufiev> the right solution is to validate package at the import stage
17:21:05 <ativelkov> It should be done, and, I think, it is done
17:21:13 <tnurlygayanov> so, who can fix it?
17:21:24 <ruhe> tnurlygayanov: let's just leave it as is. i hope we'll find volunteers later
17:21:36 <tnurlygayanov> hm.. ok.
17:21:44 <ativelkov> however if you import the package with manage.py, then no validation will be run
17:21:50 <sjmc7> i think we can fix this one
17:21:55 <sjmc7> at least validate the image
17:22:05 <ativelkov> So, what should be the correct fix for it?
17:22:10 <ruhe> ativelkov: i'm going to remove the import logic from manage.py soon
17:22:13 <ativelkov> It is validated, I believe\
17:22:29 <sjmc7> where we can, we should not allow invalid packages
17:22:54 <ativelkov> https://github.com/stackforge/murano/blob/master/murano/packages/application_package.py#L163
17:23:02 <ativelkov> This is the validation for PNG
17:23:15 <tnurlygayanov> ok, I will add these comments to this issue
17:23:20 <tnurlygayanov> next one: https://bugs.launchpad.net/murano/+bug/1321318
17:24:09 <sergmelikyan> This issue related to issue with not-unique stack names for env
17:24:16 <tnurlygayanov> it is unasigned too
17:24:20 <slagun> AFAIK it is fixed already
17:24:22 <ativelkov> yes
17:24:23 <sjmc7> yeah - this is related to stack name duplication
17:24:27 <tnurlygayanov> cool
17:24:35 <ativelkov> It duplicates the issue on me
17:24:38 <sergmelikyan> slagun, fix?
17:24:41 <ativelkov> and there is a fix waiting for review
17:24:46 <dteselkin> Will it work with python-heatclient from master branch?
17:25:03 <slagun> https://review.openstack.org/#/c/96174/
17:25:08 <ativelkov> That is not the issue of python-client
17:25:24 <ativelkov> https://bugs.launchpad.net/murano/+bug/1324094
17:25:28 <tnurlygayanov> ok, marked as duplicate for 1314106
17:25:54 <tnurlygayanov> is it ok?
17:26:11 <ativelkov> why 1314106?
17:26:21 <tnurlygayanov> which id is correct?
17:26:36 <ativelkov> 1314094
17:26:44 <ativelkov> 1324094
17:27:09 <tnurlygayanov> hm, ok
17:27:40 <tnurlygayanov> next issue https://bugs.launchpad.net/murano/+bug/1267737
17:27:48 <tnurlygayanov> unassigned too
17:28:01 <tnurlygayanov> looks like it is not critical
17:28:15 <tsufiev> yep, not critical at all
17:28:27 <tnurlygayanov> tsufiev, so, should we fix it in juno-1?
17:28:36 <katyafervent2> do we have time for it in j-2?
17:28:46 <katyafervent2> * j-1 i meant
17:28:46 <tsufiev> tnurlygayanov, no need to hurry
17:28:59 <ativelkov> I am sure we have lots or much more important UI fixes
17:29:02 <ruhe> i wouldn't call this one a bug. this one deserves a whole blueprint :)
17:29:05 <ativelkov> and this is not a bug, imho
17:29:12 <ativelkov> ruhe +1 )
17:29:41 <tsufiev> 'won't fix'?
17:29:43 <ruhe> tsufiev: would you please transfer this idea to a blueprint?
17:29:51 <tnurlygayanov> yes, looks like a small blueprint
17:30:11 <tsufiev> https://blueprints.launchpad.net/murano/+spec/separate-muranodashboard-config we have one already
17:30:16 <katyafervent2> so let's approve this fix https://review.openstack.org/#/c/95102/
17:30:39 <ruhe> katyafervent2: with a -1 from tsufiev? :)
17:30:39 <katyafervent2> if we moved 1267737 for j-2
17:31:10 <katyafervent2> please, read comments and do not ignore patches with -1, but this is a separate story)
17:31:18 <tsufiev> it is -1, not -2
17:31:23 <ruhe> tnurlygayanov: i think you can close 1267737 with a comment about corresponding BP
17:31:29 <tsufiev> i'll close my eyes while you're approving it :)
17:31:39 <tnurlygayanov> ruhe, ok, thank you
17:32:27 <katyafervent2> what's next?
17:32:40 <tnurlygayanov> https://bugs.launchpad.net/murano/+bug/1285024
17:33:25 <tsufiev> iyozhikov, ping
17:33:33 <tnurlygayanov> iyozhikov, what abou this issue?
17:34:05 <tnurlygayanov> one more bug, which lloks like a bp
17:34:22 <tnurlygayanov> / looks
17:34:32 <ruhe> tnurlygayanov: i think this bug is for Fuel, not for Murano
17:35:09 <tnurlygayanov> I will descuss this issue with Igor personaly. go to the next
17:35:14 <iyozhikov> as I know Fuel use syslog daemon, without any additional set-up dashboard should use the same logger as used by horizon
17:35:15 <ruhe> and i think that i've asked iyozhikov already to move this bug-report to Fuel space
17:35:51 <tnurlygayanov> next is https://bugs.launchpad.net/murano/+bug/1285624
17:36:07 <tnurlygayanov> dteselkin, what about this issue?
17:36:12 <dteselkin> I'll check it and fix in next few days
17:36:22 <dteselkin> As I'm currently working on MsSQL
17:36:25 <tnurlygayanov> cool
17:36:43 <tnurlygayanov> next https://bugs.launchpad.net/murano/+bug/1311755
17:37:24 <tnurlygayanov> hm, we already moved this bug from previous release to juno-1
17:37:36 <sjmc7> oo, this was me
17:37:56 <sjmc7> we absolutely need to make sure the engine can report errors back to the API
17:38:09 <tnurlygayanov> yes, it is important
17:38:13 <sjmc7> especially since at the moment, the heat and murano records can be inconsistent
17:38:39 * ruhe rised importance to high
17:39:25 <sergmelikyan> I am not sure that we will fix this during juno-1. We have only 10 days left
17:39:48 <sjmc7> we need to at least have a good idea of how to handle it
17:39:56 <slagun> This was fixed. At least partially. If unhandled exception occurs during deployment API receives notification
17:39:57 <sjmc7> i.e. through the RPC path
17:40:41 <sergmelikyan> slagun, yeah, it is mentioned in comments to the issue. We need to redesign a little bit this part of interaction between API and Engine
17:40:59 <sergmelikyan> slagun, how do you think - you can fix this during juno-1?
17:41:05 <tnurlygayanov> slagun, could you please write the comments to this bug about this fix and how we can implement this is in future?
17:41:09 <sergmelikyan> as part of debuggability initiative?
17:42:07 <slagun> What exactly is left to do in that bug?
17:42:38 <tnurlygayanov> slagun looks like we don't know
17:42:55 <sergmelikyan> Add error state for environment? And rewrite part of the code that is responsible for sending notifications in case of exception.
17:42:55 <tnurlygayanov> and we should perform some investigation on this
17:42:59 <slagun> Me either. Need to think on that
17:43:43 <ruhe> slagun: will you please take an AI to work on this bug to figure out next steps?
17:43:46 <sergmelikyan> slagun, https://github.com/stackforge/murano/blob/master/murano/common/engine.py#L73
17:44:02 <tnurlygayanov> so, ok, I will add the comments to the description of this issue
17:44:03 <slagun> ok
17:44:49 <ruhe> slagun: thank you!
17:45:21 <tnurlygayanov> slagun, I will assign this issue to you and will keep juno-1 mailstone
17:45:46 <tnurlygayanov> next https://bugs.launchpad.net/bugs/1316786
17:45:56 <tnurlygayanov> unassigned too
17:46:35 <tnurlygayanov> looks like it is problem with Murano PL
17:46:49 <slagun> there is a BP for that
17:46:58 <slagun> thats part of what I'm doing
17:47:05 <ativelkov> Yep, I would not say it is a bug
17:47:17 <ativelkov> but there is a lot of room for improvement, sure
17:47:21 <tnurlygayanov> so, can you please send the lin to bp and I will close this issue?
17:47:50 <sergmelikyan> No need to closing issue, I believe, we may track them in parallel.
17:48:02 <tnurlygayanov> https://blueprints.launchpad.net/murano/+spec/muranopl-stack-traces?
17:48:09 <sergmelikyan> Otherwise BP need to be updated with details from this issue
17:48:16 <tnurlygayanov> ok
17:48:16 <sjmc7> it's not a bug in the true sense of the term, but it makes debugging issues extremely difficult
17:48:25 <slagun> Give me a minute to find
17:48:31 <tnurlygayanov> so, I can't edit this bp
17:48:46 <slagun> https://blueprints.launchpad.net/murano/+spec/throw-correct-exception
17:48:57 <sjmc7> i cna link to it
17:49:07 <tnurlygayanov> ok, thank you!
17:49:42 <tnurlygayanov> next issue https://bugs.launchpad.net/murano/+bug/1325371
17:50:31 <ruhe> katyafervent2: that's probably yours
17:50:56 <katyafervent2> ok
17:51:02 <tnurlygayanov> assigned.
17:51:14 <tnurlygayanov> next https://bugs.launchpad.net/murano/+bug/1286085
17:51:27 <tnurlygayanov> I suggest to move it to another mailstone
17:51:45 <ruhe> katyafervent2: do you think that you can handle it in juno-1?
17:51:57 <tnurlygayanov> because we have many other critical issues
17:52:06 <ruhe> tnurlygayanov: +1
17:52:33 <katyafervent2> ruhe, not sure, but let's keep it for j-1
17:52:45 <tnurlygayanov> ok, next one https://bugs.launchpad.net/murano/+bug/1292009
17:53:13 <tnurlygayanov> katyafervent2, what about this issue?
17:53:30 <slagun> IMHO this is invalid
17:53:34 <ruhe> do we have an agreement on this one? sergmelikyan and katyafervent2 had several heated discussions about this bug :)
17:53:35 <tnurlygayanov> the importance is Low..
17:54:12 <slagun> Murano ids have nothing to do with GUID format
17:54:15 <tnurlygayanov> I want to fix it too
17:54:43 <ruhe> seems like we need more time to discuss our approach with IDs
17:54:47 <slagun> This should not be changed
17:54:51 <sergmelikyan> ruhe, I am not sure :) We need to re-discuss it again :) There should be distinctive approach to each usage of ID generation.
17:55:05 <katyafervent2> I don't know, I guess we agreed that we will not change anything
17:55:57 <katyafervent2> let's create another meeting for that discussion?)
17:56:05 <tnurlygayanov> :)
17:56:05 <ruhe> katyafervent2: +1
17:56:20 <tnurlygayanov> so, let's discuss it on the separate meeting :)
17:56:40 <tnurlygayanov> all comments were added
17:56:43 <ruhe> i don't think we need a separate meeting for this. we can take it to ML or to our weekly meeting
17:56:54 <tnurlygayanov> next one https://bugs.launchpad.net/murano/+bug/1295573
17:58:03 <tnurlygayanov> looks like a no-critical bug with API responces statuses
17:58:30 <tnurlygayanov> sergmelikyan, do you have time to fix it in juno-1?
17:59:40 <sergmelikyan> sure
18:00:09 <tnurlygayanov> hm... looks like this is the end of our meeting today... because it is 10 PM in Moscow. We can continue tomorrow
18:00:36 <ruhe> tnurlygayanov: can we? we'll have weekly meeting at the same time
18:01:37 <tnurlygayanov> what if we will continue our bug scrub meeting before the weekly meeting? at 16:00 UTC?  (comunity meeting will be at 17:00-18:00 UTC)
18:01:43 <ruhe> sjmc7: will you guys be able to join at 4PM UTC?
18:01:51 <ruhe> i guess it's very early for you
18:01:57 <tnurlygayanov> hm
18:02:00 <sjmc7> when
18:02:02 <sjmc7> tomorow
18:02:09 <sjmc7> i willtry
18:02:16 <ruhe> sjmc7: tomorrow, 4PM UTC
18:02:26 <tnurlygayanov> or we can move it to another day
18:03:14 <sergmelikyan> How many bugs are left to triage?
18:03:25 <sergmelikyan> May be we can continue today?
18:03:35 <ruhe> sergmelikyan: uh oh
18:03:50 <ruhe> sergmelikyan: what about life? :)
18:04:05 <tnurlygayanov> sergmelikyan we need to dicuss also all 'new' bugs
18:04:12 <akuznetsova_> sergmelikyan: more then a half
18:05:08 <tnurlygayanov> ok, what about the 4 June, 5:00-6:00PM UTC?
18:06:04 <tnurlygayanov> (the same time as todays meeting)
18:06:14 <sergmelikyan> +
18:06:14 <ruhe> tnurlygayanov: i'd say 4:00-6:00 PM UTC
18:06:24 <ruhe> we obviously need more time
18:06:42 <tnurlygayanov> ruhe, ok, I agree.
18:07:04 <ruhe> ah, dang it. we have internall meeting till 5-30PM UTC
18:08:15 <ruhe> ok. let's agree on 4:00 to 6:00PM
18:08:24 <tnurlygayanov> ok
18:08:29 <tnurlygayanov> Thanks for the meeting!
18:08:42 <katyafervent2> bye
18:08:58 <tnurlygayanov> #endmeeting