Bug #16528

Subnet's Discovery Capsule can point to a deleted proxy

Added by Pavel Moravec 8 months ago. Updated 6 months ago.

Status:Closed
Priority:Low
Assigned To:Lukas Zapletal
Category:Discovery plugin
Target version:Foreman - Team Anurag backlog
Difficulty: Pull request:https://github.com/theforeman/foreman_discovery/pull/307
Bugzilla link:
Story points-
Velocity based estimate-

Description

In foreman db, there is a missing key constraint from subnet.discovery_id to smart_proxies.id. That means, if a subnet refers a Discovery Capsule and I delete the capsule/proxy, no warning is raised.

Add a key constraint similar to e.g. "subnet.tftp_id -> smart_proxies.id".


Related issues

Related to Discovery - Feature #8514: Add support for requests to smart proxy discovery plugin Closed 11/26/2014

Associated revisions

Revision 514576e3
Added by Amit Karsale 7 months ago

Fixes #16528 - Added foreign key dependency

History

#1 Updated by Pavel Moravec 8 months ago

  • Related to Feature #8514: Add support for requests to smart proxy discovery plugin added

#2 Updated by Lukas Zapletal 8 months ago

  • Project changed from Foreman to Discovery
  • Category set to Discovery plugin

#3 Updated by The Foreman Bot 8 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_discovery/pull/307 added

#4 Updated by Lukas Zapletal 7 months ago

  • Assigned To set to Lukas Zapletal

#5 Updated by Amit Karsale 7 months ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#6 Updated by Amit Karsale 6 months ago

  • Target version set to Team Anurag backlog

Also available in: Atom PDF