Why Is the "dnf update" Command Failing on the Private Automation Hub Node Running on RHEL 8.4 or 8.5?

Issue

• Why is the "dnf update" command failing on the private Automation Hub node running on RHEL 8.4 or 8.5?

  # dnf update
  Updating Subscription Management repositories.
  Last metadata expiration check: 2:15:38 ago on Sun May 22 16:19:35 2022.
  Error: 
   Problem 1: package ansible-core-2.12.2-3.1.el8.x86_64 conflicts with ansible < 2.10.0 provided by ansible-core-2.12.0-2.el8ap.x86_64
    - cannot install both ansible-core-2.12.2-3.1.el8.x86_64 and ansible-core-2.12.0-2.el8ap.x86_64
    - package ansible-lint-5.0.8-2.el8pc.noarch requires ansible >= 2.9, but none of the providers can be installed
    - cannot install the best update candidate for package ansible-core-2.12.0-2.el8ap.x86_64
    - problem with installed package ansible-lint-5.0.8-2.el8pc.noarch
   Problem 2: package ansible-core-2.12.2-3.1.el8.x86_64 conflicts with ansible < 2.10.0 provided by ansible-core-2.12.0-2.el8ap.x86_64
    - cannot install both ansible-core-2.12.2-3.1.el8.x86_64 and ansible-core-2.12.0-2.el8ap.x86_64
    - package ansible-test-2.12.2-3.1.el8.x86_64 requires ansible-core = 2.12.2-3.1.el8, but none of the providers can be installed
    - package python38-galaxy-importer-0.4.0-2.el8pc.noarch requires ansible, but none of the providers can be installed
    - cannot install the best update candidate for package ansible-test-2.12.0-2.el8ap.x86_64
    - problem with installed package python38-galaxy-importer-0.4.0-2.el8pc.noarch
  (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)