Menu

#1231 delete issue with Synchronization Data Sources when using prefix on table name

2.3.0
closed
Data synchronization
Critical
2.2.0
defect
2016-06-16
2016-04-21
Bluearrow
No

If you use prefix_name on tables(ex:prefix), you create Synchronization Data Sources with Data table = prefixsynchro_data_ServerOCSng then you change your mind and want to delete synchronization Data source, we can receive error message " Error: Failed to issue SQL_query:query = DROP TABLE 'synchro_data_ServerOCSng', mysql_error = Unknown table 'synchro_data_ServerOCSng'.
It doesn' t consider name of table with prefix so can't delete it. You are forced to delete table from mysql.
You can reproduce issue with OCSng collector that creates automatically synchronization Data sources.

Discussion

  • Romain Quetiez

    Romain Quetiez - 2016-06-08
    • status: new --> accepted
    • Milestone: Unassigned --> 2.3.0
     
  • Romain Quetiez

    Romain Quetiez - 2016-06-09
    • labels: --> data synchro, delete
    • status: accepted --> more-info-needed
     
  • Romain Quetiez

    Romain Quetiez - 2016-06-09

    Not reproduced.

    I have followed the following steps:
    Install iTop 2.3.0 (trunk), with prefix PFX (all default choices, and demo data)
    Run the vSphere collector
    Amongst the created tables, all of them are correctly prefixed (e.g. pfxsynchro_data_hypervisor_7)
    Looking at the data sources, their tables are correctly set (e.g. pfxsynchro_data_hypervisor_7)
    * Delete worked fine for all of the 8 sources created by the collector

    Note: data synchro sources have an attribute 'database_table_name' which is read/only in the console and which is computed when the source is created/updated. Thus, changing the table prefixes manually requires you to "touch" the data sources in order to have this attribute be refreshed to the expected value.

     
  • Bluearrow

    Bluearrow - 2016-06-16
    • status: more-info-needed --> closed
     
  • Bluearrow

    Bluearrow - 2016-06-16

    With OCS extensions and itop 2.2 I could not manage to reproduce it.
    so sorry for it, I close issue

     

Log in to post a comment.