[Katello 2.3] - RHEL repos aren't accessible by content host - [Errno 14] HTTPS Error 403 - Forbidde

Support
1

Hello guys,

We need your help.
We lost our Katello server and after building a new one the Red Hat repos
aren't accessible by content hosts.

failure: repodata/repomd.xml from rhel-7-server-rpms: [Errno 256] No more
mirrors to try.
https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] HTTPS Error 403 - Forbidden

  • Details:
    Foreman version: 1.9.3
    Katello version: 2.3.0-6.el7.noarch

  • Steps to reproduce:

  1. Install katello 2.3
  2. Download license manifest from redhat site (this manifest was in use by
    our old katello server)
  3. Upload manifest
  4. Select Kickstart and RPM repos
  5. Sync these repos
  6. Deploy a new RHEL 7 host
  7. Execute yum repo list or try to install a package on content host

One of the configured repositories failed (Red Hat Enterprise Linux 7
Server (RPMs)),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the

problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a

working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

 3. Disable the repository, so yum won't use it by default. Yum will

then
just ignore the repository until you permanently enable it again or
use
–enablerepo for temporary usage:

        yum-config-manager --disable rhel-7-server-rpms

 4. Configure the failing repository to be skipped, if it is

unavailable.
Note that yum will try to contact the repo. when it runs most
commands,
so will have to try and fail each time (and thus. yum will be be
much
slower). If it is a very temporary problem though, this is often a
nice
compromise:

        yum-config-manager --save

–setopt=rhel-7-server-rpms.skip_if_unavailable=true

failure: repodata/repomd.xml from rhel-7-server-rpms: [Errno 256] No more
mirrors to try.
https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] HTTPS Error 403 - Forbidden

Thank you

Regards,

Fernando

2

> Hello guys,
>
> We need your help.
> We lost our Katello server and after building a new one the Red Hat repos
> aren't accessible by content hosts.
>

After you rebuilt your server, added content and synced it down did you
also re-apply the new bootstrap RPM and register the content host to the
rebuild?

··· On Wed, Nov 18, 2015 at 8:59 PM, wrote:
  • These are the error messages when executing yum repolist on the content
    host:

https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.

failure: repodata/repomd.xml from rhel-7-server-rpms: [Errno 256] No more
mirrors to try.

https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] HTTPS Error 403 - Forbidden

  • Details:
    Foreman version: 1.9.3
    Katello version: 2.3.0-6.el7.noarch

  • Steps to reproduce:

  1. Install katello 2.3
  2. Download license manifest from redhat site (this manifest was in use by
    our old katello server)
  3. Upload manifest
  4. Select Kickstart and RPM repos
  5. Sync these repos
  6. Deploy a new RHEL 7 host
  7. Execute yum repo list or try to install a package on content host
  • Output:
    [root@testsc1 ~]# yum repolist -v
    Not loading “rhnplugin” plugin, as it is disabled
    Loading “product-id” plugin
    Loading “subscription-manager” plugin
    Updating Subscription Management repositories.
    Config time: 0.806
    Yum version: 3.4.3

https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.

One of the configured repositories failed (Red Hat Enterprise Linux 7
Server (RPMs)),
and yum doesn’t have enough cached data to continue. At this point the
only
safe thing yum can do is fail. There are a few ways to work “fix” this:

 1. Contact the upstream for the repository and get them to fix the

problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a

working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

 3. Disable the repository, so yum won't use it by default. Yum will

then
just ignore the repository until you permanently enable it again
or use
–enablerepo for temporary usage:

        yum-config-manager --disable rhel-7-server-rpms

 4. Configure the failing repository to be skipped, if it is

unavailable.
Note that yum will try to contact the repo. when it runs most
commands,
so will have to try and fail each time (and thus. yum will be be
much
slower). If it is a very temporary problem though, this is often a
nice
compromise:

        yum-config-manager --save

–setopt=rhel-7-server-rpms.skip_if_unavailable=true

failure: repodata/repomd.xml from rhel-7-server-rpms: [Errno 256] No more
mirrors to try.

https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] HTTPS Error 403 - Forbidden

Thank you

Regards,

Fernando

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

3

Hi Eric, thank you for your reply.

Here the steps we've followed:

  1. Deploy new RHEL 7 vm

rpm -ivh

http://qxpgsv20.corp.shq.local/pub/katello-ca-consumer-latest.noarch.rpm

subscription-manager register --org="Default_Organization"

–name="test1.test.shq.local" --activationkey="RHEL_7"

The system has been registered with ID: 81bc245a-3ce6-43e4-9bda-bc71a4490830

Installed Product Current Status:
Product Name: Red Hat Enterprise Linux Server
Status: Subscribed

subscription-manager identity

system identity: 81bc245a-3ce6-43e4-9bda-bc71a4490830
name: test1.test.shq.local
org name: Default Organization
org ID: Default_Organization
environment name: SHQ/RHEL_7

··· On Thu, Nov 19, 2015 at 7:47 AM, Eric D Helms wrote:

On Wed, Nov 18, 2015 at 8:59 PM, ffrodrigues2011@gmail.com wrote:

Hello guys,

We need your help.
We lost our Katello server and after building a new one the Red Hat repos
aren’t accessible by content hosts.

After you rebuilt your server, added content and synced it down did you
also re-apply the new bootstrap RPM and register the content host to the
rebuild?

  • These are the error messages when executing yum repolist on the content
    host:

https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.

failure: repodata/repomd.xml from rhel-7-server-rpms: [Errno 256] No more
mirrors to try.

https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] HTTPS Error 403 - Forbidden

  • Details:
    Foreman version: 1.9.3
    Katello version: 2.3.0-6.el7.noarch

  • Steps to reproduce:

  1. Install katello 2.3
  2. Download license manifest from redhat site (this manifest was in use
    by our old katello server)
  3. Upload manifest
  4. Select Kickstart and RPM repos
  5. Sync these repos
  6. Deploy a new RHEL 7 host
  7. Execute yum repo list or try to install a package on content host
  • Output:
    [root@testsc1 ~]# yum repolist -v
    Not loading “rhnplugin” plugin, as it is disabled
    Loading “product-id” plugin
    Loading “subscription-manager” plugin
    Updating Subscription Management repositories.
    Config time: 0.806
    Yum version: 3.4.3

https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.

One of the configured repositories failed (Red Hat Enterprise Linux 7
Server (RPMs)),
and yum doesn’t have enough cached data to continue. At this point the
only
safe thing yum can do is fail. There are a few ways to work “fix” this:

 1. Contact the upstream for the repository and get them to fix the

problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a

working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

 3. Disable the repository, so yum won't use it by default. Yum will

then
just ignore the repository until you permanently enable it again
or use
–enablerepo for temporary usage:

        yum-config-manager --disable rhel-7-server-rpms

 4. Configure the failing repository to be skipped, if it is

unavailable.
Note that yum will try to contact the repo. when it runs most
commands,
so will have to try and fail each time (and thus. yum will be be
much
slower). If it is a very temporary problem though, this is often
a nice
compromise:

        yum-config-manager --save

–setopt=rhel-7-server-rpms.skip_if_unavailable=true

failure: repodata/repomd.xml from rhel-7-server-rpms: [Errno 256] No more
mirrors to try.

https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] HTTPS Error 403 - Forbidden

Thank you

Regards,

Fernando

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/QBXOsSBHXDw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

4

Hi Eric,

Even with subscription-manager showing the correct information, the repos
aren't available:

  1. Deploy new RHEL 7 vm

rpm -ivh

http://qxpgsv20.corp.shq.local/pub/katello-ca-consumer-latest.noarch.rpm

subscription-manager register --org="Default_Organization"

–name="test1.test.shq.local" --activationkey="RHEL_7"

The system has been registered with ID: 81bc245a-3ce6-43e4-9bda-bc71a4490830

Installed Product Current Status:
Product Name: Red Hat Enterprise Linux Server
Status: Subscribed

subscription-manager identity

system identity: 81bc245a-3ce6-43e4-9bda-bc71a4490830
name: test1.test.shq.local
org name: Default Organization
org ID: Default_Organization
environment name: SHQ/RHEL_7

  1. We get the same error:

yum repolist

https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.

failure: repodata/repomd.xml from rhel-7-server-rpms: [Errno 256] No more
mirrors to try.
https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] HTTPS Error 403 - Forbidden

··· On Thursday, November 19, 2015 at 7:47:22 AM UTC-5, Eric Helms wrote: > > > > On Wed, Nov 18, 2015 at 8:59 PM, <ffrodri...@gmail.com > > wrote: > >> Hello guys, >> >> We need your help. >> We lost our Katello server and after building a new one the Red Hat repos >> aren't accessible by content hosts. >> > > After you rebuilt your server, added content and synced it down did you > also re-apply the new bootstrap RPM and register the content host to the > rebuild? > > >> >> * These are the error messages when executing yum repolist on the content >> host: >> >> https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml: >> [Errno 14] HTTPS Error 403 - Forbidden >> Trying other mirror. >> >> failure: repodata/repomd.xml from rhel-7-server-rpms: [Errno 256] No more >> mirrors to try. >> >> https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml: >> [Errno 14] HTTPS Error 403 - Forbidden >> >> * Details: >> Foreman version: 1.9.3 >> Katello version: 2.3.0-6.el7.noarch >> >> * Steps to reproduce: >> 1) Install katello 2.3 >> 2) Download license manifest from redhat site (this manifest was in use >> by our old katello server) >> 3) Upload manifest >> 4) Select Kickstart and RPM repos >> 5) Sync these repos >> 6) Deploy a new RHEL 7 host >> 7) Execute yum repo list or try to install a package on content host >> >> * Output: >> [root@testsc1 ~]# yum repolist -v >> Not loading "rhnplugin" plugin, as it is disabled >> Loading "product-id" plugin >> Loading "subscription-manager" plugin >> Updating Subscription Management repositories. >> Config time: 0.806 >> Yum version: 3.4.3 >> >> https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml: >> [Errno 14] HTTPS Error 403 - Forbidden >> Trying other mirror. >> >> >> One of the configured repositories failed (Red Hat Enterprise Linux 7 >> Server (RPMs)), >> and yum doesn't have enough cached data to continue. At this point the >> only >> safe thing yum can do is fail. There are a few ways to work "fix" this: >> >> 1. Contact the upstream for the repository and get them to fix the >> problem. >> >> 2. Reconfigure the baseurl/etc. for the repository, to point to a >> working >> upstream. This is most often useful if you are using a newer >> distribution release than is supported by the repository (and the >> packages for the previous distribution release still work). >> >> 3. Disable the repository, so yum won't use it by default. Yum will >> then >> just ignore the repository until you permanently enable it again >> or use >> --enablerepo for temporary usage: >> >> yum-config-manager --disable rhel-7-server-rpms >> >> 4. Configure the failing repository to be skipped, if it is >> unavailable. >> Note that yum will try to contact the repo. when it runs most >> commands, >> so will have to try and fail each time (and thus. yum will be be >> much >> slower). If it is a very temporary problem though, this is often >> a nice >> compromise: >> >> yum-config-manager --save >> --setopt=rhel-7-server-rpms.skip_if_unavailable=true >> >> failure: repodata/repomd.xml from rhel-7-server-rpms: [Errno 256] No more >> mirrors to try. >> >> https://qxpgsv20.corp.shq.local/pulp/repos/Default_Organization/SHQ/RHEL_7_OS/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml: >> [Errno 14] HTTPS Error 403 - Forbidden >> >> Thank you >> >> Regards, >> >> Fernando >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Eric D. Helms > Red Hat Engineering > Ph.D. Student - North Carolina State University >
5

@Fernando_F_Rodrigues

When you build a new server did you choose custom SSL? I think I had 403 too when I configured the foreman using custom SSL and reinstalling with the foreman generated SSL fixed my issue for now.

Thanks,
Pawan

1 Like