Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2267483.1
Update Date:2017-05-30
Keywords:

Solution Type  Problem Resolution Sure

Solution  2267483.1 :   Oracle ZFS Storage Appliance: BUI Reports 'Unanticipated System Error Occurred': task storage_add_ext does not permit goto  


Related Items
  • Sun ZFS Storage 7420
  •  
  • Oracle ZFS Storage ZS5-2
  •  
  • Oracle ZFS Storage ZS3-2
  •  
  • Oracle ZFS Storage ZS4-4
  •  
  • Oracle ZFS Storage ZS5-4
  •  
  • Oracle ZFS Storage ZS3-4
  •  
  • Sun ZFS Storage 7120
  •  
  • Oracle ZFS Storage Appliance Racked System ZS4-4
  •  
  • Sun ZFS Storage 7320
  •  
  • Oracle ZFS Storage ZS3-BA
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: ZS
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-14902354601>

Applies to:

Oracle ZFS Storage ZS5-4 - Version All Versions and later
Oracle ZFS Storage ZS5-2 - Version All Versions and later
Oracle ZFS Storage ZS4-4 - Version All Versions and later
Oracle ZFS Storage Appliance Racked System ZS4-4 - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

Problem Description:  Error message received when trying to add new storage to a pool

System:  Oracle ZFS Storage ZS5-2

Error message:

An unanticipated system error occurred:
task storage_add_ext does not permit goto
This may be due to transient failure, or a software defect. If this problem persists, contact your service provider.

 

Cause

Cause of the problem is Bug 15634464 : MAX-TORO+SAS2 : EXCEPTION WHILE GOING TO THE PREVIOUS STEP DURING    ----> duplicate of CR 6802049 (old CR)

New migrated bug:  Bug 15540044 - grey out back button on utasks that don't support goto

 

Since this has been reported in more than one place, it's beginning to become clear that this isn't a bug in the clustering code so much as it is a bug in the integration between the BUI and utasks.

It looks like we need a way for the UI to determine whether a utask supports the goto operation, and if not, we shouldn't allow the user to go backwards in utask steps where this is not allowed.

 

Solution

Solution is to retry the storage addition from BUI    (Customer confirmed that this works)

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback