Project

General

Profile

Actions

Bug #31850

closed

Global Registration: Registration fails when Remote execution interface specified for non-rhel system

Added by Leos Stejskal almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Host registration
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1921522

Description of problem:

Registering a non-rhel(Ubuntu,Fedora) client with remote execution interface (ens33), failing with below error:

-----
ERROR: not_found
Interface with the 'ens33' identifier was specified as a remote execution interface, however the interface was not found on the host. If the interface exists, it needs to be created in Foreman during the registration.
-----

Same interface accepted for RHEL. I tried with Fedora and Ubuntu.

Version-Release number of selected component (if applicable):
6.9

How reproducible:
Always

Steps to Reproduce:
1. Create command with Remote Execution YES and give interface "ens33"
2. Generate command
3. Use command for registration

Actual results:

For RHEL, it registered correctly.

For Fedora: It gives error

---
ERROR: not_found
Interface with the 'ens33' identifier was specified as a remote execution interface, however the interface was not found on the host. If the interface exists, it needs to be created in Foreman during the registration.
----

For Ubuntu : Same error.

Expected results:

Subscribed properly

Additional info:

Details logs in case comment

Actions #1

Updated by Leos Stejskal almost 4 years ago

  • Category set to Host registration
Actions #2

Updated by The Foreman Bot almost 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/8320 added
Actions #3

Updated by The Foreman Bot over 3 years ago

  • Fixed in Releases 2.5.0 added
Actions #4

Updated by Leos Stejskal over 3 years ago

  • Status changed from Ready For Testing to Closed
Actions #5

Updated by Tomer Brisker over 3 years ago

  • Fixed in Releases 2.4.0 added
  • Fixed in Releases deleted (2.5.0)
Actions

Also available in: Atom PDF