Project

General

Custom queries

Profile

Actions
Copy link

Bug #16528

closed

Subnet's Discovery Capsule can point to a deleted proxy

Added by Pavel Moravec over 8 years ago. Updated almost 7 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 1 (0 open — 1 closed)

Related to Discovery - Feature #8514: Add support for requests to smart proxy discovery pluginClosedOri Rabin11/26/2014Actions
Actions
Copy link
 #1

Updated by Pavel Moravec over 8 years ago

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

Updated by Lukas Zapletal over 8 years ago

  • Project changed from Foreman to Discovery
  • Category set to Discovery plugin
Actions
Copy link
 #3

Updated by The Foreman Bot over 8 years ago

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

Updated by Lukas Zapletal over 8 years ago

  • Assignee set to Lukas Zapletal
Actions
Copy link
 #5

Updated by Amit Karsale over 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #6

Updated by Amit Karsale over 8 years ago

  • Target version set to 1.15.6
Actions
Copy link

Also available in: Atom PDF