Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Zentyal-virt-report error #1924

Closed
dudumao520 opened this issue Dec 2, 2019 · 4 comments
Closed

Zentyal-virt-report error #1924

dudumao520 opened this issue Dec 2, 2019 · 4 comments
Labels
Reason: Cannot reproduce Indicates that an issue couldn't been reproduced Status: Nothing to do Indicates that work won't continue on an issue or pull request Type: Bug Indicates an unexpected problem or unintended behavior

Comments

@dudumao520
Copy link

Describe the bug
Failed to start the virtual machine. After the configuration is completed, the error "error > sudo. PM: 240 ebox:: sudo:: ﹣ rooterror - root command / var / lib / zentyal / machines / test001 / manage. Sh start failed."

All screenshots
001
002
003
004
005
@dudumao520 dudumao520 added the Type: Bug Indicates an unexpected problem or unintended behavior label Dec 2, 2019
@dudumao520
Copy link
Author

zentyal 6.1 DEV Edition

@dudumao520
Copy link
Author

Describe the bug
Failed to start the virtual machine. After the configuration is completed, the error "error > sudo. PM: 240 ebox:: sudo:: ﹣ rooterror - root command / var / lib / zentyal / machines / test001 / manage. Sh start failed."

All screenshots
001
002
003
004
005

Zentyal Dev Edition 6.1 UBU18.04 LTS

@brunolorente brunolorente added Reason: Cannot reproduce Indicates that an issue couldn't been reproduced Status: Nothing to do Indicates that work won't continue on an issue or pull request labels Dec 13, 2019
@brunolorente
Copy link
Member

We couldn't reproduce this issue, and this is the first time that we have been notified about this...

Additionally you can check your zentyal.log and libvirt/* in order to find more info.

Anyway, many thanks for your report @dudumao520 !

@Neustradamus
Copy link

@dudumao520: It is solved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Reason: Cannot reproduce Indicates that an issue couldn't been reproduced Status: Nothing to do Indicates that work won't continue on an issue or pull request Type: Bug Indicates an unexpected problem or unintended behavior
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Neustradamus @dudumao520 @brunolorente