tiup dm doesn't have a config to "enable" a system service, so can't handle reboot #1110
Labels
type/bug
Categorizes issue as related to a bug.
Comments
|
cc @lichunzhu |
|
It's been fixed in #1114 Please have another try |
|
/close |
|
@9547: You can't close an active issue/PR unless you authored it or you are a collaborator. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Please answer these questions before submitting your issue. Thanks!
use tiup deploy DM, then reboot a node
What did you expect to see?
dm-worker on that node autostarts after reboot
What did you see instead?
not start
What version of TiUP are you using (
tiup --version)?1.3.1
tiup dm --version: 1.3.2
The text was updated successfully, but these errors were encountered: