The expected result after a `pro detach` is two things:
1. The machine stops being counted as an active machine according to the Pro
backend (and reflected on the Pro dashboard for users)
2. The machine stops receiving Pro services
If `pro` fails to do either of these things, then we can't really say
the machine was detached.
In this case, livepatch was in an odd state, but if you fixed the state
of livepatch, it would likely still be configured to receive patches,
authenticated with your Pro account. So if `pro detach` had succeeded,
you would have continued receiving a Pro service despite the detached
state. That is undesirable.
`pro` is reflecting the underlying error here and I'm not sure there is
anything `pro` could do to automatically recover from this, so I don't
think there is anything `pro` can do better in this situation.
Marking "invalid", but feel free to provide counterarguments.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Invalid
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076188
Title:
pro detach fails if /snap/bin/canonical-livepatch disable fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2076188/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
