Project

General

Profile

Bug #26434

Add descriptive error to API when VM fails to start

Added by D C over 1 year ago. Updated 11 months ago.

Status:
Done
Priority:
No priority
Assignee:
William Grzybowski
Category:
Middleware
Target version:
Seen in:
Severity:
Med High
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Description: No output on VM start when starting a VM in FreeNAS-11.X and the VM fails to start.

The GUI should return an output with the failed error or requirements.

VM-Device-Disk-2018-07-20.png (14.2 KB) VM-Device-Disk-2018-07-20.png Michael Reynolds, 07/20/2018 08:53 AM
VM-DescriptiveError-2018-07-20.png (78.8 KB) VM-DescriptiveError-2018-07-20.png Michael Reynolds, 07/20/2018 09:55 AM
22147
22163

Related issues

Related to FreeNAS - Bug #26315: Raise error if VM fails to start for any reasonClosed
Related to FreeNAS - Bug #39103: Raise descriptive error in new UI when VM fails to startDone
Has duplicate FreeNAS - Bug #34330: VM crashes and then fails to start due to insufficient memory.Closed
Has duplicate FreeNAS - Bug #34825: Add UI error message for VM memory usageClosed
Has duplicate FreeNAS - Bug #30127: VM start from GUI not workingClosed

Associated revisions

Revision 0759c1e9 (diff)
Added by Brandon Schneider 12 months ago

fix(vm/start): Raise an error if the vm fails to start

Requires rewriting a large portion to get this to properly report status, so for now we wait 10 seconds and if it didn't die, it's a success. Otherwise, it should raise an exception properly.

Ticket: #26434

Revision 8fd48840 (diff)
Added by William Grzybowski 11 months ago

fix(middlewared/vm): raise errors when VM fails to start

Ticket: #26434

Revision 223eeb68 (diff)
Added by William Grzybowski 11 months ago

fix(middlewared/vm): raise errors when VM fails to start

Ticket: #26434

History

#1 Updated by Dru Lavigne over 1 year ago

  • Status changed from Unscreened to 15

D C: is this in the old UI or the new UI?

#2 Updated by D C over 1 year ago

Dru Lavigne wrote:

D C: is this in the old UI or the new UI?

Both.

#3 Updated by Dru Lavigne over 1 year ago

  • Category changed from GUI (new) to 2
  • Status changed from 15 to Unscreened
  • Assignee changed from Release Council to Marcelo Araujo

#4 Updated by D C over 1 year ago

Made a quick demo of it
https://youtu.be/goowaQFSI18

#5 Updated by Marcelo Araujo over 1 year ago

  • Status changed from Unscreened to Screened
  • Target version set to 11.2-BETA1

#6 Avatar?id=14398&size=24x24 Updated by Kris Moore over 1 year ago

  • Target version changed from 11.2-BETA1 to 11.3

#7 Avatar?id=14398&size=24x24 Updated by Kris Moore over 1 year ago

  • Status changed from Screened to Not Started

#8 Avatar?id=13649&size=24x24 Updated by Ben Gadd about 1 year ago

  • Target version changed from 11.3 to Backlog

#9 Updated by Marcelo Araujo about 1 year ago

  • Severity set to Medium

#10 Updated by Marcelo Araujo about 1 year ago

  • Status changed from Not Started to Screened
  • Target version changed from Backlog to 11.4

Bump it to 11.4.

#11 Updated by Marcelo Araujo about 1 year ago

  • Category changed from GUI (new) to Middleware
  • Status changed from Screened to Unscreened
  • Assignee changed from Marcelo Araujo to William Grzybowski
  • Target version changed from 11.4 to N/A

Forward to middleware team.

#12 Updated by William Grzybowski about 1 year ago

  • Assignee changed from William Grzybowski to Brandon Schneider
  • Target version changed from N/A to Backlog
  • Severity changed from Medium to Med High

#13 Updated by Brandon Schneider about 1 year ago

  • Status changed from Unscreened to Not Started

#14 Updated by Brandon Schneider 12 months ago

  • Status changed from Not Started to In Progress

#15 Updated by Brandon Schneider 12 months ago

PR: https://github.com/freenas/freenas/pull/1458

DESC: This will wait 10 seconds and if an exception hasn't occured, the VM is good to go
RISK: Low
ACCEPTANCE: Start a VM and it shows running after 10 seconds, destroy the zvol and try starting it again.

#16 Updated by Brandon Schneider 12 months ago

  • Related to Bug #26315: Raise error if VM fails to start for any reason added

#17 Updated by Brandon Schneider 12 months ago

  • Related to Bug #34330: VM crashes and then fails to start due to insufficient memory. added

#18 Updated by Dru Lavigne 12 months ago

  • Related to deleted (Bug #34330: VM crashes and then fails to start due to insufficient memory.)

#19 Updated by Dru Lavigne 12 months ago

  • Has duplicate Bug #34330: VM crashes and then fails to start due to insufficient memory. added

#20 Updated by Dru Lavigne 12 months ago

  • Assignee changed from Brandon Schneider to William Grzybowski
  • Target version changed from Backlog to 11.2-BETA2

#21 Updated by William Grzybowski 12 months ago

  • Assignee changed from William Grzybowski to Brandon Schneider

#22 Updated by William Grzybowski 12 months ago

  • Has duplicate Bug #34825: Add UI error message for VM memory usage added

#23 Updated by William Grzybowski 12 months ago

  • Has duplicate Bug #30127: VM start from GUI not working added

#25 Updated by William Grzybowski 11 months ago

  • Status changed from In Progress to Not Started
  • Assignee changed from Brandon Schneider to William Grzybowski

Brandon is out sick this week, I will handle this.

#26 Updated by Bug Clerk 11 months ago

  • Status changed from Not Started to In Progress

#27 Updated by Bug Clerk 11 months ago

  • Status changed from In Progress to Ready for Testing

#28 Updated by Dru Lavigne 11 months ago

  • Subject changed from FreeNAS-11.X does not display any output on fail VM start to Raise descriptive error when VM fails to start
  • Needs QA changed from No to Yes
  • Needs Merging changed from Yes to No

#29 Updated by Michael Reynolds 11 months ago

22147

#34 Updated by Michael Reynolds 11 months ago

  • Status changed from Ready for Testing to Passed Testing
  • Needs QA changed from Yes to No

Created a zvol
Used that zvol as the disk for a new VM
started the VM
Stopped the VM then deleted the zvol
started the VM
got the error seen in VM-DescriptiveError-2018-07-20.png

#35 Updated by Dru Lavigne 11 months ago

  • Subject changed from Raise descriptive error when VM fails to start to Add descriptive error to API when VM fails to start
  • Status changed from Passed Testing to Done
  • Needs Doc changed from Yes to No

#36 Updated by Dru Lavigne 11 months ago

  • Related to Bug #39103: Raise descriptive error in new UI when VM fails to start added

Also available in: Atom PDF