redhat containers uses old repositories

Bug #1648745 reported by Eduardo Gonzalez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Expired
Undecided
Unassigned

Bug Description

In base image Dockerfile, there is a step to enable RedHat OpenStack repository [0].

RUN yum-config-manager --enable rhel-7-server-rpms \
    && yum-config-manager --enable rhel-7-server-openstack-7.0-rpms

*RedHat OpenStack 7 is the equivalent to Kilo version.

Some months ago, RedHat released their commercial version 8 (Liberty) and 9 (Mitaka).

Kolla Liberty and Mitaka have wrong repository enabled by default.
Any installation is made with the wrong packages and users may think they are using Newton or Mitaka but really are using Kilo.

IMHO Newton and master should be using RDO Community repositories because RedHat repositories have not been released yet.

[0] https://github.com/openstack/kolla/blob/master/docker/base/Dockerfile.j2#L75

Changed in kolla:
status: New → Confirmed
Changed in kolla:
milestone: none → ocata-3
Changed in kolla:
importance: Undecided → High
Revision history for this message
Martin André (mandre) wrote :

I personally don't know of anyone using this code to build RHEL-based images, and I'd be happy with simply removing it.

To give a bit more of context, Red Hat is using a different method to build container images that doesn't involve setting up repositories. The code linked above create confusion because it produces images that cannot be in any way be supported by Red Hat. People who want a Red Hat family distro should build using a CentOS base instead or get RHEL-base container images through official channels.

Changed in kolla:
assignee: nobody → Martin André (mandre)
Changed in kolla:
milestone: ocata-3 → ocata-rc1
Changed in kolla:
milestone: ocata-rc1 → pike-1
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

@mandre mind give more info about the image build in RHEL?

Changed in kolla:
milestone: pike-2 → pike-3
Changed in kolla:
milestone: pike-3 → pike-rc1
Revision history for this message
Martin André (mandre) wrote :

@Jeffrey: the containers are built using the koji build system. We generate Dockerfiles for each of the images using the "kolla-build --template-only" command. We also pass it with a number of overrides to disable the external repos and registration, see for example the file we're using upstream for centos [1], our downstream override is consuming the same file plus some other stuff specifically for rhel. Finally we build all the containers in isolation. So it's important for us to keep the 'rhel' base distro so if needed we can have:

{% if base_distro in ['rhel'] %}
  Do RHEL specific stuff
{% endif %}

But the rhos repos and subscription management are not used. We're removing it all with:

{% block base_rhos_repo_enablement %}
{% endblock %}
{% block base_rhel_package_installation %}
{% endblock %}

[1] https://github.com/openstack/tripleo-common/blob/master/container-images/tripleo_kolla_template_overrides.j2

Changed in kolla:
milestone: pike-rc1 → queens-1
Changed in kolla:
milestone: queens-2 → queens-3
Changed in kolla:
milestone: queens-3 → queens-rc1
Changed in kolla:
milestone: queens-rc1 → queens-rc2
Changed in kolla:
milestone: queens-rc2 → rocky-1
Changed in kolla:
milestone: rocky-2 → rocky-3
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA

Changed in kolla:
assignee: Martin André (mandre) → nobody
importance: High → Undecided
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.