Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Stack trace in server log when deleting all the platforms from UI"integrity constraint (NIPUNA.FKEEEB4C1162B21414) violated - child record found"

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.4
  • Fix Version/s: None
  • Component/s: Core Monitoring
  • Environment:
    Release 4.4.0-EE-1475,Platform:Linux,DB:Oracle
  • Case Links:
    none
  • Regression:
    No
  • Tags:

Description

Steps to Reproduce

Go to Browse Resources
select all the Platforms (Linux,win32 ,ESX-Host)
Click Delete

Actual Results:

All the resources are deleted successfully,but server log displays error.

Server log error:

2010-06-23 13:12:15,776 INFO [ControlEventListener1] [org.hyperic.hq.control.server.session.ControlEventListener@55] Removing scheduled jobs for 2:10188
2010-06-23 13:12:15,936 WARN [AppdefBoss.removeDeletedResources1] [org.hibernate.util.JDBCExceptionReporter@77]

SQL Error: 2292, SQLState: 23000
2010-06-23 13:12:15,937 ERROR [AppdefBoss.removeDeletedResources1] [org.hibernate.util.JDBCExceptionReporter@78] ORA-02292: integrity constraint (NIPUNA.FKEEEB4C1162B21414) violated - child record found

2010-06-23 13:12:15,938 WARN [AppdefBoss.removeDeletedResources1] [org.hibernate.util.JDBCExceptionReporter@77] SQL Error: 2292, SQLState: 23000
2010-06-23 13:12:15,938 ERROR [AppdefBoss.removeDeletedResources1] [org.hibernate.util.JDBCExceptionReporter@78] ORA-02292: integrity constraint (NIPUNA.FKEEEB4C1162B21414) violated - child record found

For more details please see the attached server log

Activity

Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    42 weeks ago