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.

Description of problem: In the N-1 capsule sync, "Packet too short or invalid while reading the response record. (Maybe a UTF-8 problem?)" messages get continuously


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

How reproducible:
always

Steps to Reproduce:
1. Install staellite & Capsule with the latest 6.7 GA version
2. Upgrade satellite frm 6.7 to 6.8.
3. Keep capsule on the 6.7 version.
4. Perform Optimized capsule sync.

Actual results:
During sync a lot of message were seen like "avahi-daemon[801]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)"

Expected results:
These messages should not come.

Additional info:

As far as I know no part of satellite is actively using avahi, I don't even have it installed at all on any of my satellites. Either it is a misconfiguration on your machine or a bug in avahi, but it is definitely not something we should try to address in satellite.

(In reply to Adam Ruzicka from comment #2)
> As far as I know no part of satellite is actively using avahi, I don't even
> have it installed at all on any of my satellites. Either it is a
> misconfiguration on your machine or a bug in avahi, but it is definitely not
> something we should try to address in satellite.

yes, you are right, this is not related to satellite, Can we close it as not a bug?

Yes this can be closed, feel free to report on the avahi component if you like.