Removing a relation from a double-related client stops and disables the client
Bug #1348237 reported by
Free Ekanayaka
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Charm |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
Steps to reproduce:
- Register an environment with Landscape
- Deploy landscape-client
- Deploy a service A
- Add a relation between the client and service A
- Deploy a service B, co-locating it with service A
- Add a relation between the client and service B
- Check that a new computer is there in Landscape
- Remove the relation between service B and landscape-client
Now the client will be stopped and disabled by the charm, and you'll be left with a non-contacting computer that eventually will trigger an alert, even if the relation with service A is still there.
| description: | updated |
Revision history for this message
| 🤖 Landscape Builder (landscape-builder) wrote | #1 |
| Changed in landscape-charm: | |
| 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