Project

General

Profile

Bug #16528

Subnet's Discovery Capsule can point to a deleted proxy

Added by Pavel Moravec over 6 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Low
Assignee:
Lukas Zapletal
Category:
Discovery plugin
Target version:
1.15.6
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman_discovery/pull/307
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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 pluginClosed2014-11-26

Associated revisions

Revision 514576e3 (diff)
Added by Amit Karsale over 6 years ago

Fixes #16528 - Added foreign key dependency

History

#1 Updated by Pavel Moravec over 6 years ago

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

#2 Updated by Lukas Zapletal over 6 years ago

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

#3 Updated by The Foreman Bot over 6 years 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 over 6 years ago

  • Assignee set to Lukas Zapletal

#5 Updated by Amit Karsale over 6 years ago

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

#6 Updated by Amit Karsale over 6 years ago

  • Target version set to 1.15.6

Also available in: Atom PDF