Bug 1882293

Summary:	In the N-1 capsule sync, "Packet too short or invalid while reading the response record. (Maybe a UTF-8 problem?)" messages get continuously
Product:	Red Hat Satellite	Reporter:	Devendra Singh <desingh>
Component:	Foreman Proxy	Assignee:	Lukas Zapletal <lzap>
Status:	CLOSED NOTABUG	QA Contact:	Vladimír Sedmík <vsedmik>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	aruzicka, inecas
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-24 12:43:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Devendra Singh 2020-09-24 09:24:53 UTC

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:

Comment 2 Adam Ruzicka 2020-09-24 09:46:46 UTC

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.

Comment 3 Devendra Singh 2020-09-24 10:47:44 UTC

(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?

Comment 4 Lukas Zapletal 2020-09-24 12:41:30 UTC

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