Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1502201 - Foreman discovery fails to report to Satellite "nmcli connection down primary"
Summary: Foreman discovery fails to report to Satellite "nmcli connection down primary"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Image
Version: 6.2.12
Hardware: All
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Daniel Lobato Garcia
QA Contact:
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On: 1426067
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-15 07:19 UTC by Deepannagaraj Nagarathinam
Modified: 2021-09-09 12:42 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 19950 0 None None None 2017-10-15 08:00:48 UTC

Description Deepannagaraj Nagarathinam 2017-10-15 07:19:51 UTC
Description of problem:

- foreman-discovery image fails with the error.
~~~~~~
nmcli connection down primary
~~~~~~

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

- Red Hat Satellite 6.2.12
- foreman-discovery-image-3.1.1-22

How reproducible:

- Always

Steps to Reproduce:

1. Enable the discovery on Satellite server.
2. Try to discover the VM with the foreman discovery image version 3.1.1-22

Actual results:

- Should report to Satellite server.

Expected results:

- Failed with the mentioned error.

Additional info:

- Issue fixed upstream.
- As a workaround use the latest discovery image from upstream.

Comment 1 Satellite Program 2017-10-15 10:24:08 UTC
Upstream bug assigned to dlobatog

Comment 2 Satellite Program 2017-10-15 10:24:11 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19950 has been resolved.

Comment 4 Lukas Zapletal 2017-10-27 09:51:32 UTC
Yes the RM linked was fixed in 6.3.

Can you ask the customer to use FDI upstream image? It is known to work with 6.2: http://downloads.theforeman.org/discovery/releases/3.4/

Comment 7 Lukas Zapletal 2017-10-31 08:52:11 UTC
Hello,

we are tracking a request to rebase FDI in 6.2.14.

Comment 8 Lukas Zapletal 2018-01-01 11:12:37 UTC
This bug is supposed to be fixed in 3.4.1 FDI in Satellite 6.3 beta.

We are tracking one bug around DHCP up pxe-less but this one should be fixed.

Comment 9 Satellite Program 2018-02-21 16:54:37 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> > 
> > For information on the advisory, and where to find the updated files, follow the link below.
> > 
> > If the solution does not work for you, open a new bug report.
> > 
> > https://access.redhat.com/errata/RHSA-2018:0336


Note You need to log in before you can comment on or make changes to this bug.