Bug 1128235
Summary: | node deactivate does not remove the binding of the repo to the node | ||
---|---|---|---|
Product: | [Retired] Pulp | Reporter: | Preethi Thomas <pthomas> |
Component: | nodes | Assignee: | pulp-bugs |
Status: | CLOSED UPSTREAM | QA Contact: | pulp-qe-list |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.4 Beta | CC: | jortel, mhrivnak, rbarlow, skarmark |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-02-28 22:15:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Preethi Thomas
2014-08-08 16:19:04 UTC
Given that nodes are activated by adding a special note on the consumer document, I don't believe this is a regression. Further, since the deactivation is a consumer update to the REST and manager layers, this would be hard to fix without doing a real hack. There have been discussion about making nodes a 1st class thing in the platform. I think this should be addressed properly then. Moved to https://pulp.plan.io/issues/486 |