| 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: | |
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 |
Description of problem: If you deactivate a repo that has has bound repo, seems like node deactivate does not remove the binding. So if you activate it again the repo stays bound. So node sync, syncs up the repo. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: [root@cloud-qe-15 ~]# pulp-admin node deactivate --node-id node1 Child node deactivated. [root@cloud-qe-15 ~]# [root@cloud-qe-15 ~]# [root@cloud-qe-15 ~]# pulp-admin node activate --node-id node1 Command: activate Description: activate a consumer as a child node Available Arguments: --consumer-id - (required) unique identifier; only alphanumeric, ., -, and _ allowed --strategy - synchronization strategy (mirror|additive) default is additive The following options were specified but do not exist on the command: --node-id [root@cloud-qe-15 ~]# pulp-admin node activate --consumer-id node1 Consumer activated as child node. [root@cloud-qe-15 ~]# pulp-admin node sync run --node-id node1 This command may be exited via ctrl+c without affecting the request. (1/2) Repository: copy [==================================================] 100% (2/2) Repository: upload [==================================================] 100% Synchronization succeeded +----------------------------------------------------------------------+ Child Node Synchronization +----------------------------------------------------------------------+ Repository: Action: Merged Content Sources: Downloads: Total Passes: 0 Total Sources: 0 Id: copy Units: Added: 0 Removed: 0 Updated: 0 Repository: Action: Merged Content Sources: Downloads: Total Passes: 0 Total Sources: 0 Id: upload Units: Added: 0 Removed: 0 Updated: 0 Repository: Action: Removed Content Sources: Downloads: Id: zoo Units: Added: 0 Removed: 0 Updated: 0 Actual results: Expected results: Additional info: