Description of problem:

Even after successfully restoring a capsule server from backup, Visiting Satellite UI --> Infrastructure --> Capsules shows the external capsule in an error state and logs are filled with errors like

SSL_connect returned=1 errno=0 state=error: certificate verify failed (self signed certificate in certificate chain)

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

satellite-capsule-6.13.0-6.el8sat.noarch
rubygem-foreman_maintain-1.2.4-1.el8sat.noarch
satellite-maintain-0.0.1-1.el8sat.noarch

How reproducible:

Always

Steps to Reproduce:
1. Install a Satellite 6.13 and Capsule 6.13 and sync some stuff in both
2. Take offline backup ( without pulp ) of both and save them in a network storage
3. Rebuild the OS for both of the VMs with same hostname\IP\Networking as the old OS
4. Follow "14.1. Restoring from a Full Backup" from https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/administering_red_hat_satellite/restoring-satellite-server-or-capsule-from-a-backup_admin  to restore the backups on satellite and then capsule

Actual results:

--> Satellite successfully restored without any errors and operating fine
--> Capsule successfully restored without any errors but

• • Visiting Sat UI --> Infrastructure --> Capsules page shows the capsule in an Error state.
  • If we click open the capsule entry we get to see multiple errors like "SSL_connect returned=1 errno=0 state=error: certificate verify failed (self signed certificate in certificate chain)"

Expected results:

No such errors.

It's either a flaw in the restore process or we are missing some intermediate steps in the documentation for the capsule part of the restoration.

Additional info:

NOTE: I tested with the both online and offline backups of capsules and the result remains the same.

And I cannot immediately confirm if it's a regression or not as I had last tested this process on 6.9 and it had worked but never had tested it afterwards ( until now ).