Back to bug 1017350
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RHEL Program Management | 2013-10-09 17:30:15 UTC | Keywords | FutureFeature | |
| Red Hat Bugzilla | 2013-10-09 17:30:15 UTC | Doc Type | Bug Fix | Enhancement |
| Og Maciel | 2013-10-10 18:44:55 UTC | CC | omaciel | |
| Mike McCune | 2013-10-22 04:15:41 UTC | CC | mmccune | |
| Todd Sanders | 2014-01-27 14:22:25 UTC | Component | pulp | Content Management |
| Brad Buckingham | 2014-06-26 16:39:10 UTC | CC | bbuckingham | |
| Brad Buckingham | 2014-08-19 21:33:37 UTC | Blocks | 950743 | 950746 |
| Brian Bouterse | 2015-03-03 19:26:00 UTC | Keywords | Triaged | |
| CC | bbouters | |||
| Component | Content Management | Pulp | ||
| Link ID | Pulp Redmine 199 | |||
| Assignee | katello-bugs | satellite6-bugs | ||
| Bryan Kearney | 2016-10-06 15:32:11 UTC | CC | bkearney | |
| Summary | RFE: need a way to tell if a content node's repo is out of sync. | [RFE] need a way to tell if a content node's repo is out of sync. | ||
| Brad Buckingham | 2016-11-21 16:58:33 UTC | Link ID | Foreman Issue Tracker 17419 | |
| David Davis | 2016-12-09 19:12:06 UTC | CC | daviddavis | |
| Summary | [RFE] need a way to tell if a content node's repo is out of sync. | [RFE] need a way to tell if a Pulp server's repo is out of sync. | ||
| Michael Hrivnak | 2017-02-20 02:51:33 UTC | Status | NEW | CLOSED |
| Resolution | --- | WORKSFORME | ||
| Last Closed | 2017-02-19 21:51:33 UTC | |||
| pulp-infra | 2017-06-05 18:42:57 UTC | CC | pcreech | |
| pulp-infra | 2017-06-05 18:43:00 UTC | CC | ttereshc | |
| Brian Bouterse | 2017-07-26 19:46:56 UTC | CC | bbouters | |
| pulp-infra | 2018-05-25 15:39:33 UTC | CC | rchan | |
| pulp-infra | 2018-05-25 15:39:35 UTC | CC | dkliban | |
| pulp-infra | 2020-10-05 14:54:14 UTC | CC | bmbouter | |
| pulp-infra | 2020-10-05 14:54:15 UTC | CC | ipanova | |
| pulp-infra | 2021-04-06 18:04:40 UTC | CC | ggainey | |
| Red Hat One Jira (issues.redhat.com) | 2021-04-06 18:27:50 UTC | Link ID | Red Hat Issue Tracker SAT-2193 |
Back to bug 1017350