FusionAccess-ITA Portal associated VM keep status of “attaching”

Publication Date:  2015-03-05 Views:  366 Downloads:  0
Issue Description
Applicable version:
R002C00
Symptom
FusionAccess admin engineer re-associate a VM to user: Before associate VM, unassign VM first, the VNC login VM to exit domain. Then use this domain account and computer name re-assign a new VM to user.
In ITA Portal, setup name method, import VM assign template, set user group DG, then click OK to start assign VM. Then found VM keep the status of “attaching”, check VM information found “User” and “VM Type” is already updated, DDC related DG got the domain account too. Only “VM name” not changed.
In this case, name method show: use sht-gkhjzxzx630 as computer name
Alarm Information
 Check VM status in ITA portal.
ITA log
Handling Process
Handling process
1. Log in to AD server, manually delete the computer name which for the VM you want to delete. Contact domain administrator if AD belong to ISP.
2. VNC log in VM, change computer name, add domain account and password as prompted, then restart VM.
3. Log in VDS SQL database, find ITA database, open tbl_InstanceInfo table. (see screenshot attached)

4. Find VM ID and its row, press tab to “instanceName” column to modify the value. Continue press tab to find “attachState” column, modify value to ATTACHED.  (refer screenshots)


5. Save all in database.

6. Restart ITA server tomcat process.
Root Cause
Rootcause
1、 Analyze ITA log, found after restart VM, every 3 minutes there is error log of “invalid instanceName”:
2012-01-07 10:54:38.294  DEBUG  PROC  pool-1-thread-6  ComputerNameGenarator.java  513  checkIsExistInAD():PowerShell:invalid instanceName
2012-01-07 10:54:38.294  ERROR  PROC  pool-1-thread-6  ComputerNameGenarator.java  517  checkIsExistInAD():PowerShell:invalid instanceName
……
2012-01-07 10:57:27.487  DEBUG  PROC  pool-1-thread-6  ComputerNameGenarator.java  513  checkIsExistInAD():PowerShell:invalid instanceName
2012-01-07 10:57:27.487  ERROR  PROC  pool-1-thread-6  ComputerNameGenarator.java  517  checkIsExistInAD():PowerShell:invalid instanceName
……
2012-01-07 11:00:16.570  DEBUG  PROC  pool-1-thread-6  ComputerNameGenarator.java  513  checkIsExistInAD():PowerShell:invalid instanceName
2012-01-07 11:00:16.570  ERROR  PROC  pool-1-thread-6  ComputerNameGenarator.java  517  checkIsExistInAD():PowerShell:invalid instanceName
2、 According name method, can only generate 1 valid computer name sht-gkhjzxzx630, but when ITA check it in AD sht-gkhjzxzx630 already exist, so because Number of Numerals is 0, increase failed. This software code bug let ITA fall in above dead circle. This issue will be fixed on R002C00SPC205 patch.
3、 VNC log in VM, find computer name not changed as expected.
4、 We found when VM exit domain, in AD the computer name only marked “x”, but not be deleted really, need delete computer name manually.  So ITA got invalid name in AD which generate by name method.
Suggestions
On R002C01 version, in AD server ITA have authority to make VM exit domain when unassign VM, and will let ITA auto log in AD to clear the unused computer name (NETBIOS NAME)

END