RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
  When adding new repo via `yum-config-manager --add URL`, the repo file should not be created and the command should return non zero return code.

Version-Release number of selected component (if applicable):
  yum-utils-1.1.31-42.el7.noarch

How reproducible:
  100%

Steps to Reproduce:
1. Try to add repo from non-existing URL:
  # yum-config-manager --add http://example.com/test.repo
2. Check the return code:
  # echo $?
3. Check /etc/yum.repos.d/ directory:
  # ll /etc/yum.repos.d/test.repo
4. Check the content of test.repo file:
  # cat /etc/yum.repos.d/test.repo 

Actual results:
# yum-config-manager --add http://example.com/test.repo
adding repo from: http://example.com/test.repo
grabbing file http://example.com/test.repo to /etc/yum.repos.d/test.repo
Could not fetch/save url http://example.com/test.repo to file /etc/yum.repos.d/test.repo: [Errno 14] HTTP Error 404 - Not Found

# echo $?
0

# ll /etc/yum.repos.d/test.repo 
-rw-r--r--. 1 root root 0 Nov 22 10:39 /etc/yum.repos.d/test.repo

# cat /etc/yum.repos.d/test.repo 

(the file is empty)

Expected results:
  When the remote repo file is not available, no local (empty) repo file should be created and the return code should not be zero.

Additional info:

*** This bug has been marked as a duplicate of bug 1493489 ***