Persisting clone state on registration.
Bug #1739825 reported by
Simon Poirier
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
Fix Released
|
Medium
|
Kevin Nasto | ||
| Landscape Server |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
When the client is not restarted, the "clone state" persists.
Steps to reproduce:
* create a computer
* re-register to get a clone.
* remove initial computer; there should be no clone.
* the client still thinks it is a clone as it has set the "clone" suffix as its in-memory name.
Expected:
client re-checking for clone and not sticking to the "clone" suffix when re-registering.
| Changed in landscape-client: | |
| assignee: | nobody → Kevin Nasto (silverdrake11) |
Revision history for this message
| Kevin Nasto (silverdrake11) wrote | #1 |
| Changed in landscape-client: | |
| status: | New → Fix Committed |
| Changed in landscape: | |
| milestone: | none → 19.10.8 |
| status: | New → Fix Committed |
| Changed in landscape: | |
| status: | Fix Committed → Fix Released |
| Changed in landscape-client: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The landscape client changes are here https:/