Don't default to yes for registration if a machine is already registered
Bug #396730 reported by
Andreas Hasenack
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
We should try to prevent a machine that is already registered from being registered again.
One suggestion would be a change to landscape-config. When it comes to the question about registering the machine with landscape, it could check if the client is already registered, and in that case issue a warning and change the default answer from "yes" to "no".
| Changed in landscape-client: | |
| importance: | Undecided → Low |
| milestone: | none → later |
| Changed in landscape-client: | |
| importance: | Low → Medium |
| tags: | added: sooner-rather-than-later |
| summary: |
- Try to prevent double registration + Don't default to yes for registration if a machine is already registered |
| Changed in landscape-client: | |
| milestone: | later → backlog |
Revision history for this message
| 🤖 Landscape Builder (landscape-builder) wrote | #1 |
| Changed in landscape-client: | |
| status: | New → Invalid |
To post a comment you must log in.
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
Landscape Team