-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shutdown order for services must go in opposite direction of starting for the deb package #133
Comments
e-grigorov
added
bug
Something isn't working
and removed
task
Single unit of work
labels
Sep 20, 2022
I'll have a look at this. |
daniel-milchev
added a commit
to bosch-io/kanto
that referenced
this issue
Sep 20, 2022
…irection of starting for the deb package Reordered the services Signed-off-by: Daniel Milchev <[email protected]>
e-grigorov
pushed a commit
that referenced
this issue
Sep 20, 2022
… for the deb package (#136) [#133] Shutdown order for services must go in opposite direction of starting for the deb package Reordered the services Signed-off-by: Daniel Milchev <[email protected]>
Repository owner
moved this from In Review
to Done
in Eclipse Kanto
Sep 20, 2022
konstantina-gramatova
added a commit
to bosch-io/kanto
that referenced
this issue
Sep 20, 2022
…irection of starting for the deb package Fixed ordering of stopping and purging of the connectivity components. Fixed start attempts for the connectivity components. Added unmasking and state update for the disabled components on installation. Signed-off-by: Konstantina Gramatova <[email protected]>
konstantina-gramatova
added a commit
to bosch-io/kanto
that referenced
this issue
Sep 20, 2022
…irection of starting for the deb package Fixed ordering of stopping and purging of the connectivity components. Fixed start attempts for the connectivity components. Added unmasking and state update for the disabled components on installation. Signed-off-by: Konstantina Gramatova <[email protected]>
konstantina-gramatova
added a commit
that referenced
this issue
Sep 20, 2022
… for the deb package (#139) [#133] Shutdown order for services must go in opposite direction of starting for the deb package Fixed ordering of stopping and purging of the connectivity components. Fixed start attempts order for the connectivity components. Added unmasking and state update for the disabled components on installation. Signed-off-by: Konstantina Gramatova <[email protected]>
Repository owner
moved this from Ready for Review
to Done
in Eclipse Kanto
Sep 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the files build/prerm and build/postrm, the order of services should be:
system-metrics.service
file-backup.service
software-update.service
file-upload.service
container-management.service
suite-connector.service
local-digital-twins.service
suite-bootstrapping.service
This is the opposite order of us starting the services. We don't start local-digital-twins and suite-bootstrapping by default, but if we do, suite-bootstrapping must be started first, followed by local-digital-twins, so this deactivation order keeps being opposite of that.
The text was updated successfully, but these errors were encountered: