14:36:00 <dkliban> #startmeeting Pulp Triage 2016-04-29
14:36:00 <dkliban> #info dkliban has joined triage
14:36:01 <pulpbot> Meeting started Fri Apr 29 14:36:00 2016 UTC and is due to finish in 60 minutes.  The chair is dkliban. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:36:01 <pulpbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:36:01 <pulpbot> The meeting name has been set to 'pulp_triage_2016_04_29'
14:36:01 <pulpbot> dkliban has joined triage
14:36:16 <ttereshc> !pulptriage join
14:36:16 <pulpbot> Error: The "PulpTriage" plugin is loaded, but there is no command named "join" in it.  Try "list PulpTriage" to see the commands in the "PulpTriage" plugin.
14:36:16 <smyers> The basic workflow is !start, then users need to !here, then you !next to the next issue til we're done, and you !end
14:36:18 <smyers> !here
14:36:18 <smyers> #info smyers has joined triage
14:36:18 <asmacdo> i have a lot id like to get done today, so im going to skip triage, but ill be pingable
14:36:18 <pulpbot> smyers has joined triage
14:36:33 <jortel> #info jortel has joined triage
14:36:33 <jortel> !here
14:36:33 <pulpbot> jortel has joined triage
14:36:34 <asmacdo> (unless i am needed for quorum)
14:36:36 <mhrivnak> !here
14:36:36 <mhrivnak> #info mhrivnak has joined triage
14:36:37 <pulpbot> mhrivnak has joined triage
14:36:39 <ttereshc> !here
14:36:39 <ttereshc> #info ttereshc has joined triage
14:36:40 <pulpbot> ttereshc has joined triage
14:36:41 <preethi> !here
14:36:41 <preethi> #info preethi has joined triage
14:36:42 <pulpbot> preethi has joined triage
14:36:43 <smyers> asmacdo, we have a quorum
14:36:47 <smyers> by far
14:37:06 <dkliban> great! let's begin ...
14:37:06 <asmacdo> woot
14:37:07 <pcreech> !here
14:37:07 <pcreech> #info pcreech has joined triage
14:37:08 <pulpbot> pcreech has joined triage
14:37:09 <dkliban> !next
14:37:09 <pulpbot> 14 issues left to triage.
14:37:10 <dkliban> #topic Unit copy performance regression in 2.8. - http://pulp.plan.io/issues/1714
14:37:10 <pulpbot> Pulp Issue #1714 [ASSIGNED] (mhrivnak) - Priority: High | Severity: Medium
14:37:10 <pulpbot> Unit copy performance regression in 2.8. - http://pulp.plan.io/issues/1714
14:37:55 <smyers> Oh, this guy. I'm actually looking at the Django side of things to see if we'll experience similar problems (so far so good on that)
14:38:03 <mhrivnak> We've identified with this one that no stakeholder is currently asking us to address it in the short term.
14:38:22 <mhrivnak> And we're hopeful that the switch to django's ORM will "fix" it.
14:38:23 <smyers> I think the question here was basically "Do we deal with this in mongo or switch to postgres?", right mhrivnak?
14:38:30 <mhrivnak> yes.
14:38:55 <bmbouter> I believe we're going w/ the second but leaving this open in case some community member wants to investigate with mongo
14:39:02 <mhrivnak> I suggest lowering the priority and leaving it open for additional feedback and/or for a community member to pick it up.
14:39:04 <bmbouter> the second being (postgres will fix this)
14:39:26 <bmbouter> +1 to mhrivnak's plan
14:39:28 <bmbouter> #info bmbouter has joined triage
14:39:28 <bmbouter> !here
14:39:28 <pulpbot> bmbouter has joined triage
14:39:40 <jortel> +1
14:39:42 <dkliban> Medium / Normal ?
14:39:43 <pcreech> +1 to lowering priority and leaving it open
14:39:57 <mhrivnak> I'd go for low severity.
14:40:18 <smyers> Yeah, I think that works for me. I think it's reasonable to also open issues case-by-case where there's acute pain, and expect that this one will never get done on mongo.
14:40:21 <mhrivnak> Nothing is behaving incorrectly, and we don't yet know that the regression is bad enough to have a meaningful impact on most users.
14:40:24 <smyers> (So +1 low sev)
14:40:39 <dkliban> Low / norma .... going once ...
14:40:44 <dkliban> any objections?
14:40:49 <smyers> low sev, normal prio?
14:40:54 <dkliban> yes
14:40:59 <mhrivnak> +1
14:41:01 <jalbertson> +1
14:41:25 <dkliban> done!
14:41:27 <dkliban> !next
14:41:27 <pulpbot> 13 issues left to triage.
14:41:28 <dkliban> #topic No "unprotected/http" option available for ostree repos - http://pulp.plan.io/issues/1773
14:41:28 <pulpbot> OSTree Support Issue #1773 [NEW] (unassigned) - Priority: Normal | Severity: Medium
14:41:28 <pulpbot> No "unprotected/http" option available for ostree repos - http://pulp.plan.io/issues/1773
14:41:42 <mhrivnak> dkliban, FWIW I think we've normally used $PRIO / $SEV in our shorthand, probably for no reason than that's the ordering in the issue tracker.
14:42:01 <jortel> still no decision from katello on this ..
14:42:04 <dkliban> mhrivnak: thanks for the reminder ... will do that
14:42:16 <smyers> "might need http based ostree stuff in the future" sounds like not at all severe to me
14:42:35 <smyers> Ah, just got to comment #4
14:42:39 <jortel> oh, wait, looks like a new comment added.  disregard
14:42:54 <pcreech> based on the last comment though, it appears there some 'fedora' related implications
14:43:22 <jortel> seems like this should be a story
14:43:29 <mhrivnak> jortel, I wonder if we should turn this into a task for this sprint, to make sure the use cases are covered.
14:43:30 <jsherrill> there has been some more discussion recently about provisioning and the ostree guys wanting to use published ostree repos during the installation process
14:43:51 <mhrivnak> If there's enough info to just make it a story, I'm in favor of that too.
14:44:10 <dkliban> i would like this to be a story ... and we should discuss it on monday for sprint planning
14:44:12 <jalbertson> jsherrill, what is the current impact of not having this, though? affecting 6.2 users?
14:44:22 <jalbertson> or for future work?
14:45:20 <jsherrill> jalbertson: so the ostree provisioning story has been quite frustrating, it could mean that we can't properly provision rhel atomic, or it could mean that rel-eng/ostree peoples will be forced to include the squashfs within the ISO
14:45:26 <jsherrill> err within the kickstart tree
14:45:38 <jsherrill> which they've been waffeling on i think
14:46:26 <jsherrill> i think if we went to them and said, that this wasn't an option we could force it
14:46:37 <jalbertson> jsherrill, ack
14:47:01 <mhrivnak> perhaps we can give jortel an action item, to turn this into either a story, or a task if more investigation is required?
14:47:20 <mhrivnak> jortel, would that work for you?
14:47:27 <jortel> mhrivnak: yes
14:47:35 <dkliban> so leaving this untriaged?
14:47:45 <mhrivnak> yes.
14:47:52 <smyers> !action jortel turn number #1773 into a story or task if more investigation is needed
14:47:52 <pulpbot> (action Record an action item in the meeting log. Any nicks seen in the line will be recorded) -- along with the action item in the meeting log.
14:48:00 <smyers> Well that worked super well :(
14:48:15 <smyers> !suggest jortel turn number #1773 into a story or task if more investigation is needed
14:48:16 <pulpbot> suggest Suggest an idea, which will be recorded into the triage meeting minutes.
14:48:19 <smyers> ugh
14:48:24 <dkliban> !next
14:48:25 <dkliban> #topic publishing kickstart repo fails on EL6 - http://pulp.plan.io/issues/1856
14:48:26 <pulpbot> 12 issues left to triage.
14:48:26 <pulpbot> RPM Support Issue #1856 [ON_QA] (dkliban@redhat.com) - Priority: Normal | Severity: Medium | Target Release: 2.8.3
14:48:26 <smyers> I broke that stuff apparently
14:48:26 <pulpbot> publishing kickstart repo fails on EL6 - http://pulp.plan.io/issues/1856
14:48:34 <smyers> ON_QA?
14:49:06 <dkliban> yeah ... we already fixed this
14:49:17 <mhrivnak> indeed. Let's just mark it triaged and move on.
14:49:21 <dkliban> agreed
14:49:25 <mhrivnak> Adding high priority would be fine, since it obviously was. :)
14:49:30 <smyers> URGENT :D
14:49:34 <dkliban> !next
14:49:34 <pulpbot> 11 issues left to triage.
14:49:35 <dkliban> #topic CVE-2016-3704: Unsafe use of bash $RANDOM for NSS DB password and seed - http://pulp.plan.io/issues/1858
14:49:35 <pulpbot> Pulp Issue #1858 [POST] (rbarlow) - Priority: Normal | Severity: High | Target Release: 2.8.4
14:49:35 <pulpbot> CVE-2016-3704: Unsafe use of bash $RANDOM for NSS DB password and seed - http://pulp.plan.io/issues/1858
14:49:39 <smyers> (justr kidding)
14:50:01 <smyers> This is also already done, so
14:50:02 <smyers> ...
14:50:14 <dkliban> !next
14:50:15 <dkliban> #topic As a user, I want to create scheduled sync - http://pulp.plan.io/issues/1859
14:50:15 <pulpbot> 10 issues left to triage.
14:50:15 <pulpbot> Puppet Support Issue #1859 [NEW] (unassigned) - Priority: Normal | Severity: Medium
14:50:16 <pulpbot> As a user, I want to create scheduled sync - http://pulp.plan.io/issues/1859
14:50:39 <dkliban> not a bug
14:50:59 <dkliban> i am guessing the user did not find the documentation that he was looking for
14:50:59 <mhrivnak> should be a story.
14:51:12 <mhrivnak> It's possible pulp_puppet doesn't expose it in the CLI
14:51:18 <dkliban> oh
14:51:19 <smyers> Does puppet actually not support scheduling?
14:51:33 <smyers> It's written as a story, so it's definitely in the wrong tracker
14:51:34 <mhrivnak> oh it does support it, and it is in pulp-admin
14:51:50 <bmbouter> we should add a comment and/or link to the docs and close it NOTABIUG
14:51:52 <bmbouter> NOTABUG
14:51:54 <smyers> back to NOTABUG then
14:51:57 <dkliban> can someone add a comment with a link to docs?
14:52:13 <mhrivnak> I'll do that.
14:52:18 <dkliban> mhrivnak: thanks
14:52:27 <dkliban> !next
14:52:28 <dkliban> #topic Exception using regex in filters against associate endpoint - http://pulp.plan.io/issues/1863
14:52:28 <pulpbot> 9 issues left to triage.
14:52:28 <pulpbot> Pulp Issue #1863 [NEW] (unassigned) - Priority: Normal | Severity: Medium
14:52:29 <pulpbot> Exception using regex in filters against associate endpoint - http://pulp.plan.io/issues/1863
14:53:17 <dkliban> asmacdo: are you familiar with ^
14:53:28 * asmacdo lookuing
14:53:51 <dkliban> it seems severe to me
14:54:26 <asmacdo> dkliban, i spent a few minutes looking into it
14:54:38 <asmacdo> i did confirm that it is a real bug
14:54:39 <smyers> Might be something to fix in translate, or potentially in a custom json encoder that I don't remember if we use or not...
14:54:51 <smyers> I'm not sure about severe, but would definitely agree with "pretty darn high"
14:54:58 <mhrivnak> agreed
14:55:13 <dkliban> is this normal priority though?
14:55:21 <smyers> And high prio, probably tageted to 2.8.next
14:55:21 <mhrivnak> I'm not sure there's a clear workaround.
14:55:22 <asmacdo> one thing to check is whether that only occurs when it is deeply nested like that query
14:55:24 <asmacdo> i suspect it is
14:56:09 <asmacdo> but yes, i agree its high priority
14:56:11 <mhrivnak> I suggest high/medium
14:56:30 <dkliban> I suggest High/High
14:56:40 <mhrivnak> I'm also fine with that.
14:56:51 <dkliban> i am setting the target release to 2.8.4
14:56:51 <mhrivnak> and 2.8.4
14:56:54 <mhrivnak> heh
14:57:03 <asmacdo> +1
14:57:04 <smyers> +1
14:57:09 <bmbouter> +1
14:57:14 <dkliban> !next
14:57:15 <dkliban> #topic Error searching rpm repositories by fields using dot notation - http://pulp.plan.io/issues/1865
14:57:15 <pulpbot> 8 issues left to triage.
14:57:15 <pulpbot> Pulp Issue #1865 [NEW] (unassigned) - Priority: Normal | Severity: Medium
14:57:16 <pulpbot> Error searching rpm repositories by fields using dot notation - http://pulp.plan.io/issues/1865
14:57:48 <alanoe> I created this one
14:58:08 <bmbouter> I looked into this one some and was going to comment on it
14:58:20 <mhrivnak> alanoe, thanks for joining us!
14:58:26 <smyers> Is this a regression? Really looks like it to me.
14:58:31 <alanoe> mhrivnak, you're welcome =)
14:58:37 <mhrivnak> Sure does look like a regression.
14:58:57 <bmbouter> I will comment on it today, but I recommend to triage as norm/med
14:59:24 <bmbouter> alanoe: I'm going to try to reproduce and probably ask you some questions based on what I find
14:59:32 <dkliban> is everyone good with Normal/Medium?
14:59:52 <alanoe> smyers, I am sure it does not happen in 2.5.3, the other pulp env I have setup. not sure about newer versions
14:59:55 <smyers> That's surprising to me, is it worth leaving this untriaged and we can revisit it after bmbouter can comment?
15:00:13 <smyers> That prio/sev combo was surprising to me, to be clear.
15:00:27 <dkliban> smyers: i am in favor of that actually
15:00:29 <bmbouter> smyers: I'm ok w/ that
15:00:31 <mhrivnak> agreed, I'd like more info.
15:00:35 <pcreech> +1
15:00:36 <smyers> It sounds like we need info to grok it as a group
15:00:45 <smyers> cool
15:00:49 <dkliban> !next
15:00:49 <pulpbot> 7 issues left to triage.
15:00:51 <dkliban> #topic The Pulp Python bindings don't use requests and fail to retry - http://pulp.plan.io/issues/1866
15:00:51 <pulpbot> Pulp Issue #1866 [NEW] (unassigned) - Priority: Normal | Severity: Medium
15:00:52 <pulpbot> The Pulp Python bindings don't use requests and fail to retry - http://pulp.plan.io/issues/1866
15:00:52 <bmbouter> ok I'll take a next step to comment on it today and alanoe and I will get more info
15:01:00 <mhrivnak> group grokking FTW
15:01:14 <alanoe> this one is a blocker to me. bmbouter , if I can help fixing, tell me
15:01:57 <alanoe> "this one" is 1865
15:02:15 <bmbouter> alanoe: I'll ping you with more info soon (today)
15:02:19 <alanoe> ty
15:02:21 <smyers> alanoe, untriaged bugs don't equal unworked bugs, and you're in good hands with bmbouter :)
15:02:38 <alanoe> good to know =)
15:03:15 <smyers> This (#1866) bug is a headscratcher for me...
15:03:18 <mhrivnak> I think the scope of this one should be refined.
15:03:19 <dkliban> i propose we skip this one till we can get some input from jcline ...
15:03:26 <smyers> cool, not just me
15:03:26 <pcreech> +1
15:03:29 <smyers> needinfo :)
15:03:31 <jortel> +1
15:03:35 <bmbouter> 1866 is really a task not a bug maybe?
15:03:35 <ttereshc> +1
15:03:41 <mhrivnak> switching to "requests" is a good idea, but not itself a bug.
15:04:11 <jortel> agreed
15:04:12 <mhrivnak> Failing to retry when there's a connection error is maaaaybe a bug? More likely an enhancement to add retry.
15:04:24 <bmbouter> mhrivnak: yes, let's change it's type to a story
15:04:39 <dkliban> i left a comment asking jcline to change it into a story
15:04:46 <smyers> Yeah, I like that. Switching to requests is an rfe :)
15:05:21 <dkliban> are we ready for the next one?
15:05:23 <bmbouter> can we just make it a story?
15:05:23 <mhrivnak> yes.
15:05:26 <jortel> y
15:05:31 <bmbouter> I'm also ok to move on
15:05:33 <mhrivnak> I think it's 2 stories.
15:05:38 <mhrivnak> I'll also comment.
15:05:38 <dkliban> !next
15:05:38 <pulpbot> 6 issues left to triage.
15:05:39 <dkliban> #topic pulp-admin fails silently to publish all files of a repo - http://pulp.plan.io/issues/1867
15:05:39 <pulpbot> Pulp Issue #1867 [NEW] (unassigned) - Priority: Normal | Severity: Medium
15:05:39 <pulpbot> pulp-admin fails silently to publish all files of a repo - http://pulp.plan.io/issues/1867
15:06:49 <smyers> this sounds really familiar to me
15:07:01 <smyers> can't remember specifics though
15:07:40 <mhrivnak> seems like someone needs to try reproducing.
15:07:58 <smyers> I can pick it up
15:08:17 <mhrivnak> We could triage at high/high so it'll get investigated soon, and adjust accordingly depending on what is discovered.
15:08:19 <dkliban> smyers: want me to mark it as triaged or should we wait till you reproduce?
15:08:25 <mhrivnak> Or we can just skip and let smyers look into it.
15:08:26 <dkliban> cool
15:08:34 <jortel> what are RRPMs?
15:08:36 <smyers> Well...
15:08:40 <smyers> I think we should triage it
15:08:44 <jortel> n/m
15:08:54 <dkliban> high/high is good with me
15:08:57 <bmbouter> +1
15:08:59 <jortel> +1
15:09:21 <dkliban> !next
15:09:22 <pulpbot> 5 issues left to triage.
15:09:22 <smyers> +1
15:09:32 <pulpbot> An error occured when trying to query Redmine: socket.error: ('The read operation timed out',)
15:09:36 <smyers> Oof
15:09:43 * mhrivnak kicks pulpbot
15:09:46 <smyers> You should be able to just keep !nexting
15:09:51 <dkliban> !next
15:09:52 <pulpbot> 4 issues left to triage.
15:09:56 <smyers> heh
15:09:56 <mhrivnak> uh oh
15:10:00 <dkliban> #topic Resynchronizing rhel repos seems to be failing after upgrade - http://pulp.plan.io/issues/1869
15:10:00 <pulpbot> RPM Support Issue #1869 [NEW] (unassigned) - Priority: Normal | Severity: Medium
15:10:00 <pulpbot> Resynchronizing rhel repos seems to be failing after upgrade - http://pulp.plan.io/issues/1869
15:10:24 <smyers> I'll go find which one we just skipped, and open an issue to add an issue to the "seen" list only after it's actually seen. :D
15:10:41 <dkliban> i am working on this one actually
15:10:44 <dkliban> it's high/high
15:10:51 <dkliban> i reproduced it this morning
15:11:12 <jortel> +1 high/high
15:11:13 <mhrivnak> high/high and probably 2.8.3?
15:11:32 <smyers> ooh, a blocker
15:11:34 <mhrivnak> dkliban, do we still think it's a regression in the 2.8.3 beta?
15:11:35 <dkliban> +1
15:11:54 <dkliban> dkliban: i did not try 2.8.2 but i can easily do that
15:12:06 <dkliban> mhrivnak: ^
15:12:10 <mhrivnak> dkliban, are you talking to yourself again?
15:12:36 <dkliban> for now lets treat it as regression adn i'll check after we are done with triage
15:12:42 <mhrivnak> +1
15:12:56 <smyers> Definitely 2.8.3 then?
15:13:03 <dkliban> for now
15:13:08 <smyers> +1
15:13:09 <mhrivnak> 2.8.3 for now, and dkliban can adjust if it's not a regression.
15:13:24 <dkliban> !next
15:13:24 <pulpbot> 3 issues left to triage.
15:13:25 <dkliban> #topic The default password setting in /etc/pulp/server.conf is confusing for users - http://pulp.plan.io/issues/1870
15:13:25 <pulpbot> Pulp Issue #1870 [NEW] (unassigned) - Priority: Normal | Severity: Medium
15:13:26 <pulpbot> The default password setting in /etc/pulp/server.conf is confusing for users - http://pulp.plan.io/issues/1870
15:14:26 <dkliban> normal/medium?
15:14:33 <smyers> That number's actually correct, we have to triage the current issue and left two untriaged.
15:15:14 <smyers> I like normal prio, but I think it's low severity
15:15:32 <mhrivnak> +1
15:15:52 <dkliban> +1
15:15:59 <bmbouter> +1
15:15:59 <dkliban> !next
15:15:59 <pulpbot> 2 issues left to triage.
15:15:59 <dkliban> #topic /etc/pulp/server/plugins.conf.d/docker_importer.json is not provided by the pulp-docker-plugins package - http://pulp.plan.io/issues/1871
15:16:00 <pulpbot> Docker Support Issue #1871 [NEW] (unassigned) - Priority: Normal | Severity: Medium
15:16:00 <pulpbot> /etc/pulp/server/plugins.conf.d/docker_importer.json is not provided by the pulp-docker-plugins package - http://pulp.plan.io/issues/1871
15:16:00 * smyers is curious what happens !next
15:16:21 <jortel> 1870 should be a 3.0 story?
15:16:54 <dkliban> jortel: perhaps ... mind leaving some comments about that on the issue?
15:17:02 <jortel> will do
15:18:52 <dkliban> do we want more input from randy?
15:20:04 <bmbouter> I think this is ready to go
15:20:34 <smyers> I agree. I think it's fine to leave it as a bug, based on that note about "editing" rather than "creating"
15:20:41 <mhrivnak> agreed.
15:20:48 <jortel> +1
15:20:56 <bmbouter> +1 to adding 3.0 target release
15:21:15 <smyers> crap wrong bug
15:21:23 <smyers> no right bug I'm insane
15:21:38 <dkliban> Normal/Medium 3.0.0 ?
15:21:41 <smyers> bmbouter, you're saying 3.0 for #1871?
15:21:41 <bmbouter> yes
15:22:00 <dkliban> any objections?
15:22:00 <smyers> It seems fine to me for 2.8.4, and a pretty easy fix. What am I missing?
15:22:06 <bmbouter> oh no 1870
15:22:12 * bmbouter is on the wrong bug
15:22:45 <smyers> Cool. For #1871 I think normal/medium is fine, and it's appropriate for 2.8.4.
15:22:49 <jalbertson> +1
15:23:08 <smyers> We can revisit issues if you'd like, the command would be !issue 1870
15:23:49 <alanoe> cool issue triage feature in the bot
15:24:07 <smyers> That reminds me, the issue we accidentally skipped when redmine timed out was #1868, and I think we'll need to manually switch to it.
15:24:18 <dkliban> !issue 1868
15:24:19 <dkliban> #topic Pulp on RHEL 6 serves wrong files - http://pulp.plan.io/issues/1868
15:24:20 <pulpbot> Docker Support Issue #1868 [NEW] (unassigned) - Priority: Normal | Severity: Medium
15:24:20 <pulpbot> Pulp on RHEL 6 serves wrong files - http://pulp.plan.io/issues/1868
15:24:38 <bmbouter> smyers: we can continue, 1870 is good as is
15:24:48 <smyers> I think this is a dupe
15:25:05 <smyers> mhrivnak, remember the issue with the content-type/content-encoding discussion?
15:25:12 <mhrivnak> smyers, yes.
15:25:13 <smyers> Granted, this one is a lot more detailed...
15:25:35 <mhrivnak> I think you're right, they're the same issue.
15:25:38 <smyers> If not a dupe, probably related and can inform that other bug
15:25:48 <mhrivnak> And the solution is probably documentation.
15:26:47 <mhrivnak> this one: https://pulp.plan.io/issues/1781
15:26:49 <pulpbot> Title: Issue #1781: Files ending in .gz are delivered with incorrect content headers - Pulp (at pulp.plan.io)
15:27:07 <mhrivnak> definitely a dup
15:27:17 <dkliban> mhrivnak: marking it as such
15:27:22 <smyers> +1
15:27:27 <dkliban> mhrivnak: should  i close it though?
15:28:10 <bmbouter> yes cloes it as closed - DUPLICATE
15:28:11 <mhrivnak> yes, unless there are any additional issues described in this one.
15:28:20 <jortel> +1
15:28:38 <smyers> I think they should be related, but I'll add a comment to #1781 about it
15:28:57 <dkliban> smyers: i added the relationship on there
15:29:04 <dkliban> !next
15:29:05 <dkliban> #topic /etc/pulp/server/plugins.conf.d/docker_importer.json is not provided by the pulp-docker-plugins package - http://pulp.plan.io/issues/1871
15:29:05 <pulpbot> 2 issues left to triage.
15:29:05 <pulpbot> Docker Support Issue #1871 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Target Release: 2.8.4
15:29:06 <pulpbot> /etc/pulp/server/plugins.conf.d/docker_importer.json is not provided by the pulp-docker-plugins package - http://pulp.plan.io/issues/1871
15:29:10 <smyers> dkliban, thanks
15:29:48 <dkliban> looks like we already triaged this one
15:29:53 <jalbertson> yes
15:29:54 <dkliban> !next
15:29:54 <dkliban> #topic Add example on how to generate PULP_MANIFEST file  - http://pulp.plan.io/issues/1876
15:29:55 <pulpbot> 1 issues left to triage.
15:29:55 <pulpbot> RPM Support Issue #1876 [NEW] (unassigned) - Priority: Normal | Severity: Medium
15:29:56 <pulpbot> Add example on how to generate PULP_MANIFEST file  - http://pulp.plan.io/issues/1876
15:30:18 <mhrivnak> normal / low ?
15:31:09 <ttereshc> https://github.com/pulp/pulp_rpm/pull/855
15:31:10 <pulpbot> Title: 1876 - Add in a sample program to generate the file by bkearney · Pull Request #855 · pulp/pulp_rpm · GitHub (at github.com)
15:31:32 <bmbouter> niiiice
15:31:56 <smyers> Oh cool. Move it to Story, set it POST?
15:31:57 <dkliban> i am going to add this PR to the issue
15:31:58 <mhrivnak> ttereshc++
15:31:58 <pulpbot> ttereshc's karma is now 1
15:32:08 <smyers> ^ yeah he does karma now too
15:32:35 <dkliban> !next
15:32:35 <pulpbot> 0 issues left to triage.
15:32:36 <pulpbot> No issues left to triage.
15:32:44 <smyers> ^ flawless logic
15:32:50 <dkliban> !end
15:32:50 <dkliban> #endmeeting