Bug 1785692 - Ceph deployments (even those without dashboard) fail due to wrong container URLs
Summary: Ceph deployments (even those without dashboard) fail due to wrong container URLs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ga
: 16.0 (Train on RHEL 8.1)
Assignee: Francesco Pantano
QA Contact: Nathan Weinberg
URL:
Whiteboard:
: 1792377 (view as bug list)
Depends On:
Blocks: 1626260 1790754 1793986
TreeView+ depends on / blocked
 
Reported: 2019-12-20 17:14 UTC by Francesco Pantano
Modified: 2020-02-06 14:44 UTC (History)
10 users (show)

Fixed In Version: openstack-tripleo-common-11.3.3-0.20200121231250.3c68b48.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-06 14:44:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:0283 0 None None None 2020-02-06 14:44:39 UTC

Description Francesco Pantano 2019-12-20 17:14:33 UTC
Description of problem:
We should have the right default values to properly pull the grafana/prometheus/alertmanager/node-exporter containers from the right location.
By default these containers are pulled from docker.io, but we should trigger ceph-ansible using the ocp4 containers [1].

Here an example of a wrong containers-prepare-parameter.yaml:


parameter_defaults:
  ContainerImagePrepare:
  - push_destination: true
    set:
      ceph_alertmanager_image: alertmanager
      ceph_alertmanager_namespace: docker.io/prom
      ceph_alertmanager_tag: v0.16.2
      ceph_grafana_image: grafana
      ceph_grafana_namespace: docker.io/grafana
      ceph_grafana_tag: 5.2.4
      ceph_image: rhceph-4.0-rhel8
      ceph_namespace: docker-registry.upshift.redhat.com/ceph
      ceph_node_exporter_image: node-exporter
      ceph_node_exporter_namespace: docker.io/prom
      ceph_node_exporter_tag: v0.17.0
      ceph_prometheus_image: prometheus
      ceph_prometheus_namespace: docker.io/prom
      ceph_prometheus_tag: v2.7.2
      ceph_tag: latest
      name_prefix: rhosp16-openstack-
      name_suffix: ''
      namespace: rhos-qe-mirror-rdu2.usersys.redhat.com:5002/rh-osbs
      neutron_driver: ovn
      rhel_containers: false
      tag: 20191213.1


and here the right parameters we should use:

Registry is: registry.access.redhat.com
Namespace is the same we’re using for openshift 4: openshift4
Grafana container: ose-grafana: v4.1
Prometheus container: ose-prometheus: v4.1
Alertmanager Container: ose-prometheus-alertmanager: v4.1
Node exporter container: ose-prometheus-node-exporter: v4.1



[1] https://github.com/ceph/ceph-ansible/pull/4424/files


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 John Fulton 2019-12-20 17:23:52 UTC
(In reply to fpantano from comment #0)
> and here the right parameters we should use:
> 
> Registry is: registry.access.redhat.com

As per the doc [1] shouldn't it be registry.redhat.io ?

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0-beta/html/transitioning_to_containerized_services/obtaining-container-images#container-image-preparation-parameters


> Namespace is the same we’re using for openshift 4: openshift4
> Grafana container: ose-grafana: v4.1
> Prometheus container: ose-prometheus: v4.1
> Alertmanager Container: ose-prometheus-alertmanager: v4.1
> Node exporter container: ose-prometheus-node-exporter: v4.1

Comment 2 Francesco Pantano 2019-12-20 17:36:20 UTC
Yes, right, the registry is "registry.redhat.io" and ceph-ansible contains the correct info [1].

[1] https://github.com/ceph/ceph-ansible/blob/master/group_vars/rhcs.yml.sample#L572

Comment 3 shreshtha joshi 2020-01-17 12:42:29 UTC
The fix is in the compose, can we get blocker ack to add it to errata.

Comment 6 Giulio Fidente 2020-01-21 13:04:24 UTC
*** Bug 1792377 has been marked as a duplicate of this bug. ***

Comment 15 errata-xmlrpc 2020-02-06 14:44:12 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:0283


Note You need to log in before you can comment on or make changes to this bug.