What were you trying to do that didn't work?

Make sure opentelemetry-collector works as expected after upgrading from RHEL-9.6 to RHEL-10.0 during CUT (ticket related: RHELMISC-8922)

What is the impact of this issue to you?

Customers already having opentelemetry-collector installed, if they upgrade their AWS cloud instances from 9 to 10, they won't receive any logs into their AWS Account due to the service failing and entering in a start loop.

Please provide the package NVR for which the bug is seen:

• opentelemetry-collector-0.107.0-1.el9_5.x86_64
• opentelemetry-collector-0.107.0-1.el9_5.aarch64

How reproducible is this bug?:

100%

Steps to reproduce

1. Spawn a RHEL-9.6 AWS instance that contains opentelemetry-collector (AMI built from latest compose, using osbuild-composer)
2. Make sure opentelemetry-collector package works as expected before upgrade
3. Set the subscription-manager config values:
   1. subscription-manager config --rhsmcertd.auto_registration=1
   2. subscription-manager config --rhsm.manage_repos=1
4. Register the machine with subscription-manager or insights-client
5. Perform a major upgrade by following this guide (link pending)
6. Reboot
7. Check opentelemetry-collector.service status and is-active
8. Checl journalctl -u opentelemetry-collector.service

Expected results

• systemctl is-active opentelemetry-collector.service returns "active"
• systemctl status opentelemetry-collector.service shows as  "active (running)"
• jurnalctl -u opentelemetry-collector.service doesn't show any errors

Actual results

• systemctl is-active opentelemetry-collector.service returns "activating (auto-restart)" all the time
• systemctl status opentelemetry-collector.service shows Main PID: (code=exited, status=217/USER)
• jurnalctl -u opentelemetry-collector.service shows errors: