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

Make software update non-disruptive #1188

Closed
schakrava opened this Issue Feb 25, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@schakrava
Member

schakrava commented Feb 25, 2016

Currently, whenever an update is run, rockstor service stopped. This may not be necessary.

Even more worrisome is the fact that services like samba and rock-ons are turned off and user must manually turn them back on after the update. This shouldn't be the case.

@schakrava schakrava self-assigned this Feb 25, 2016

@schakrava schakrava added this to the Looney Bean milestone Feb 25, 2016

@schakrava

This comment has been minimized.

Show comment
Hide comment
@schakrava

schakrava Nov 27, 2016

Member

Samba no longer has dependency on rockstor service, one less thing to worry about.

Member

schakrava commented Nov 27, 2016

Samba no longer has dependency on rockstor service, one less thing to worry about.

@schakrava schakrava modified the milestones: Pinnacles, Looney Bean Nov 27, 2016

@schakrava schakrava closed this in 3825b2b Mar 8, 2017

schakrava added a commit that referenced this issue Mar 8, 2017

Merge pull request #1670 from schakrava/1188_docker_service_indp
docker service shouldn't require rockstor-bootstrap. Fixes #1188
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment