Bug #477

Incorrect error message

Added by Maciej Kruk about 10 years ago. Updated over 9 years ago.

Status:ClosedStart date:01/31/2011
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

0%

Category:Core & System
Target version:Release 3.0
Resolution:fixed Pull request:
Affected Versions:

Description

On creation of new virtual machine, whenever using other user's private vnet, error message says:

Error: [VirtualMachineAllocate] User [1] not authorized to perform CREATE on VM Pool

This is really confusing and gives no hint whatsoever to what the real cause of the problem is.

Message like that would be much more useful:

Error: [VirtualMachineAllocate] User [1] not authorized to use the Virtual Network [0].

Associated revisions

Revision a97f0c40
Added by Carlos Martín over 9 years ago

Bug #477: Let the authorization errors reach the user

Revision 78247256
Added by Carlos Martín over 9 years ago

Bug #477: Small change in error string generation

Revision 7d0ac75b
Added by Carlos Martín over 9 years ago

Bug #477: Fix AuthManagerTest, now the authorization errors are more vebose

Revision fa37092a
Added by Carlos Martín over 9 years ago

Bug #477: Fix AuthManagerTest, now the authorization errors are more vebose
(cherry picked from commit 7d0ac75b0f873e17088c5aa3fd23e8e3cb6e7c0d)

Revision da0ca8d6
Added by Abel Coronado over 3 years ago

B #5370: Solved bug when import vCenter template (#477)

Revision 07277db7
Added by Abel Coronado over 3 years ago

B #5370: Solved bug when import vCenter template (#477)

(cherry picked from commit da0ca8d6d01148ef3236240252aa7fadcfe7c9d2)

History

#1 Updated by Carlos Martín over 9 years ago

  • Category changed from CLI to Core & System
  • Status changed from New to Closed
  • Assignee changed from Javi Fontan to Carlos Martín
  • Target version set to Release 3.0
  • Resolution set to fixed

Also available in: Atom PDF