Project

General

Profile

Bug #35538

Obsolete foreman_docker

Added by Ian Ballou 2 months ago. Updated 1 day ago.

Status:
Closed
Priority:
Normal
Category:
RPMs
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

The foreman_docker plugin is no longer active, so we should ensure that no one has it installed. We're purging the old contents of the plugin in the DB, so it should be gone from the installed plugins as well.


Related issues

Related to Foreman - Bug #35347: After removing the foreman_docker plugin, foreman log is flooded with huge tracebacks related to "unknown class DockerRegistry, ignoring" and "unknown class Container, ignoring"Closed

Associated revisions

Revision 79e5457e (diff)
Added by Ewoud Kohl van Wijngaarden about 1 month ago

Fixes #35538 - Obsolete foreman_docker in foreman

In Foreman 3.3 foreman_docker was removed from packaging1 while Foreman
3.5 includes DB migrations to remove the plugin from the database.

[1]: c8cd0c659ff11c8366e30a2ff36e03323626be1e

History

#1 Updated by The Foreman Bot 2 months ago

  • Assignee set to Ewoud Kohl van Wijngaarden
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-packaging/pull/8517 added

#2 Updated by Evgeni Golov about 1 month ago

  • Related to Bug #35347: After removing the foreman_docker plugin, foreman log is flooded with huge tracebacks related to "unknown class DockerRegistry, ignoring" and "unknown class Container, ignoring" added

#3 Updated by The Foreman Bot about 1 month ago

  • Fixed in Releases 3.5.0 added

#4 Updated by Ewoud Kohl van Wijngaarden about 1 month ago

  • Status changed from Ready For Testing to Closed

#5 Updated by Ewoud Kohl van Wijngaarden 1 day ago

  • Triaged changed from No to Yes

Also available in: Atom PDF