Project

General

Profile

Bug #26315

Raise error if VM fails to start for any reason

Added by Vaibhav Chauhan over 1 year ago. Updated 11 months ago.

Status:
Closed
Priority:
Nice to have
Assignee:
Brandon Schneider
Category:
Middleware
Target version:
Seen in:
Severity:
Medium
Reason for Closing:
Duplicate Issue
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Currently if a VM fails to start no error is presented other than "NO".

We need to expose the error to the user via a middleware CallError.

Risk
The risk is low since the UI should be ready to show raised errors.

Acceptance Criteria
When this is done if the VM fails to start for any reason the UI should present the message error stating the reason.


Related issues

Related to FreeNAS - Bug #26434: Add descriptive error to API when VM fails to startDone

History

#1 Updated by Marcelo Araujo over 1 year ago

  • Status changed from Unscreened to Screened

#2 Updated by Dru Lavigne over 1 year ago

  • Target version changed from Master - FreeNAS Nightlies to 11.2-BETA1

#3 Updated by Dru Lavigne over 1 year ago

  • Status changed from Screened to Not Started

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

  • Due date set to 03/09/2018

#5 Updated by Dru Lavigne about 1 year ago

  • Target version changed from 11.2-BETA1 to 11.2-RC2

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

  • Category changed from Middleware to OS

#7 Updated by Marcelo Araujo about 1 year ago

  • Severity set to Low Medium

#8 Updated by Marcelo Araujo 11 months ago

  • Status changed from Not Started to Screened
  • Target version changed from 11.2-RC2 to 11.2-U3
  • Reason for Blocked set to Waiting for feedback

Is it still needed?

#9 Updated by Dru Lavigne 11 months ago

  • Status changed from Screened to Blocked
  • Reason for Blocked changed from Waiting for feedback to Need additional information from Author

#10 Updated by Vaibhav Chauhan 11 months ago

I think this is needed as end users currently have no idea WHY does VM does not want to start. A message like

ErrorCode: ENODEV

"Virtual Machine failed to start! due to missing {hdd|vnc|raw|network} device"

maybe a traceback would also be beneficial.

#11 Updated by Dru Lavigne 11 months ago

  • Status changed from Blocked to Screened
  • Reason for Blocked deleted (Need additional information from Author)

#12 Updated by Marcelo Araujo 11 months ago

  • Category changed from OS to Middleware
  • Status changed from Screened to Unscreened
  • Assignee changed from Marcelo Araujo to William Grzybowski
  • Target version changed from 11.2-U3 to N/A

Forward to middleware team. More info on bhyve(8).

#13 Updated by William Grzybowski 11 months ago

  • Assignee changed from William Grzybowski to Brandon Schneider
  • Target version changed from N/A to Backlog
  • Severity changed from Low Medium to Medium
  • Seen in changed from Master - FreeNAS Nightlies to 11.2-BETA1

#14 Updated by Brandon Schneider 11 months ago

  • Status changed from Unscreened to Not Started

#15 Updated by William Grzybowski 11 months ago

  • Target version changed from Backlog to Backlog

#16 Updated by William Grzybowski 11 months ago

  • Subject changed from please return vm cannot be started if NO zdev present to Raise error if VM fails to start for any reason
  • Description updated (diff)
  • Target version changed from Backlog to 11.3

#17 Updated by Brandon Schneider 11 months ago

  • Status changed from Not Started to Closed
  • Reason for Closing set to Duplicate Issue

Dupe

#18 Updated by Brandon Schneider 11 months ago

  • Related to Bug #26434: Add descriptive error to API when VM fails to start added

#19 Updated by Dru Lavigne 11 months ago

  • Target version changed from 11.3 to N/A

Also available in: Atom PDF