Article ID: 121867, created on Jun 2, 2014, last review on Jun 2, 2014

  • Applies to:
  • Operations Automation 5.5

Symptoms

After some troubles of provisioning and after deleting the 50 GB HDD on CLM side, the hardware is still visible in the CCP with the status "creating"

Cause

POA database was not updated due to manual disk removal or manual cancellation of removal tasks.

Resolution

  1. Find the CLM logs location in POA database:

    plesk=> SELECT * FROM clm_config WHERE name='log_file_path';
         name      |      value
    ---------------+------------------
     log_file_path | /var/log/clm.log
    (1 row)
    
  2. Find the disk uid from CCP and check CLM logs. There should be information about VM status like:

    --------------------------------- Wed May  7 17:23:35 2014
    
    HTTP/1.1 200 OK
    Server: Apache-Coyote/1.1
    Content-Type: text/xml;charset=utf-8
    Transfer-Encoding: chunked
    Date: Wed, 07 May 2014 20:23:35 GMT
    Connection: close
    
    699
    <?xml version="1.0" ?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns1:executeProcessResponse xmlns:ns1="http://bmc.com/ao/xsd/2008/09/soa"><ns1:Output><ns1:Output><ns1:Parameter><ns1:Name>message</ns1:Name><ns1:Value ns1:type="xs:anyType"><ns1:XmlDoc><output xmlns="">Successfully retrieved VM information.</output></ns1:XmlDoc></ns1:Value></ns1:Parameter><ns1:Parame
    ter><ns1:Name>output</ns1:Name><ns1:Value ns1:type="xs:anyType"><ns1:XmlDoc><output xmlns=""><vm-id>6faeffb0-7774-4718-af42-7baa2debd954</vm-id><vm-name>VM</vm-name><host-name>vm</ho
    st-name><memory>1024</memory><vm-state>Running</vm-state><hardware-architecture>X86</hardware-architecture><cpus>1</cpus><owner>tenant_admin</owner><operating-system>Windows Server 2008 R2</o
    perating-system>
    
    -----------------
    # list of disks #
    ------------------
    
    <local-disk id="0f60db9b-350d-4a3e-aabc-9385b757ced9" size-in-gb="50.0">Disk1</local-disk>
    <local-disk id="bdf54b01-9397-4eb0-8635-db75a4e1841d" size-in-gb="100.0">Disk2</local-disk>
    
  3. If the disk, which stuck in "Creating" state, is not present in the list - you are free to remove it from POA database. Its ID in CCP is 6faeffb0-7774-4718-af42-7baa2debd954 in this example:

    plesk=> select * from clm_disks where status = 'Creating' and vm_id ='6faeffb0-7774-4718-af42-7baa2debd954';
     disk_id | local_disk_id |                vm_id                 | name |  status  | additional | size_in_gb | resource_id
    ---------+---------------+--------------------------------------+------+----------+------------+------------+-------------
         689 |               | 6faeffb0-7774-4718-af42-7baa2debd954 |      | Creating | y          |         50 |      204457
    (1 row)
    
    plesk=> begin; delete from clm_disks where status = 'Creating' and vm_id ='6faeffb0-7774-4718-af42-7baa2debd954'; commit;
    COMMIT
    

Search Words

Error trying to delete a hard disk in the CCP

5b048d9bddf8048a00aba7e0bdadef37 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF