OK closed as not a bug but how to fix it?

I get the same error message

[root@rhel7 files]# leapp upgrade

============================================================
                        ERRORS
============================================================

2019-05-07 19:53:05.275101 [ERROR] Actor: prepare_upgrade_transaction Message: Cannot find any required target repository. The list of available required repositories is empty. 

============================================================
                     END OF ERRORS
============================================================

while upgrading a default minimal install from 7.6 to 8.0 following the steps in

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/upgrading_to_rhel_8/performing-the-upgrade-from-rhel-7-to-rhel-8_upgrading-to-rhel-8

and

https://access.redhat.com/articles/3664871

It is closed as notabug as the BZ was opened for case the machine is not registered and subscribed using RHSM. AFAIK, the message you see should be found only when
 a) the system is not registered and subscribed properly
 b) correct required data files from the archive in the article (the one you sent) are not provided in /etc/leapp/files (but if I remember well, in such case you should see message about missing files earlier)
 c) the machine is subscribed using RHSM against satellite instead of CDN servers abd RHEL 8 content is not provided through the satellite server or it is provided using different repository name
 d) you changed configuration of RHSM and the redhat.repo file is not managed by RHSM (the 'manage_repos' option)

To be able to get the RHEL 8 content, it is expected that using RHSM, we are able to get a repo file containing repositories with these IDs:
 rhel-8-for-x86_64-baseos-rpms
 rhel-8-for-x86_64-appstream-rpms

Maybe I missed something yet, but I tried to write here all cases I have in my mind when this message can be printed. Of course, we will try to provide better information / guidance in future in such message. My tip is that your system had not been registered and subscribed or it is subscribed against the satellite server (meet the expectation that system is not detached completely from the network). Can you check whether your system met one of those cases I mentioned above?

In case you thing that everything is really OK, your system is subscribed,
  # rhsm list --consumed
  # rhsm status
please open a ticket on our support with included sos report, to be able to investigate better your setup and what exactly happened. But from my experience from the past, I believe it's problem (a) or (c).

Thank you for the detailed explanation. I subscribed the system without any error but checking the subscription status showed me this:

SKU:               RH00049
..
Bietet Verwaltung: Nein
Aktiv:             True
Anzahl verbraucht: 1
Servicelevel:      Premium
Servicetyp:        L1-L3
Statusdetails:     Gast wurde auf keinem Host gemeldet und benutzt eine derzeit nicht zugeordnete
                   Gast-Subskription.
Subskriptionstyp:  Standard (Temporary)
Startet:           01.01.2017
Endet:             14.05.2019
Systemtyp:         Virtuell

The guest is a VMware VM, so I'm not sure what the status "Guest has not been reported on any host and is using a currently unassigned Guest subscription." means. Anyway,aAfter removing and re-assigning the subscription the subscription status went to fully subscribed and leapp started the upgrade. Unfortunately the upgrade part after reboot failed and dropped me in an emergency shell. I will open a new ticket for this issue.

Thank you Andreas for the feedback. Any bug report is welcomed. Please, do not forget to append more information about your system in the bug report (or in customer case ticket). It's important for us to be able to improve the tooling in more ways.

Upgrade instructions should be added for Satellite users:

- Sync RHEL 8 repos on Satellite server
- Create RHEL 8 activation key
- subscription-manager register --org=<ORG NAME> --activationkey="<RHEL 8 ACTIVATION KEY>" --force
- # leapp upgrade

I have my server registered with RHCDN and the status looks good. But I could not see below error while leap upgrade. 
subscription-manager list --installed
+-------------------------------------------+
    Installed Product Status
+-------------------------------------------+
Product Name:   Red Hat Enterprise Linux Server
Product ID:     69
Version:        7.6
Arch:           x86_64
Status:         Subscribed
Status Details:
Starts:         01/01/19
Ends:           01/01/20

[ERROR] Actor: prepare_upgrade_transaction Message: Failed to get list of available RHEL repositories. A Leapp Command Error occurred.

Thank you for your report, Boopathiraj.  The error message is somewhat similar, but it's not the same and it looks to me it could be different issue.

Could you please re-report it as a new bug?

Also, we'll probably need more information; in particular, if you could also provide:
 * output from `leapp upgrade` command, ideally with `--debug` option, ie. `leapp --debug upgrade`,
 * leapp version (`rpm -qa "leapp*"`),
 * more information about your OS (/etc/os-release and `uname -a` should do it.)

I had an similar error when I had accent in repo name. I don't think it is this one because the same message is used if it can't find appstream/baseos. When it is empty it show this message (but it might deserve a dedicated error message)