Bug 1826451 - IndexManagement cronjob creation fails if an image is not specified
Summary: IndexManagement cronjob creation fails if an image is not specified
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.5.0
Assignee: Jeff Cantrill
QA Contact: Qiaoling Tang
URL:
Whiteboard:
: 1835397 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-21 17:42 UTC by Jeff Cantrill
Modified: 2020-07-13 17:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:29:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift elasticsearch-operator pull 320 0 None closed Bug 1826451: Make indexmanagment rely on packaged es image 2020-12-10 00:43:30 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:30:10 UTC

Description Jeff Cantrill 2020-04-21 17:42:34 UTC 
Description of problem:

IndexManagement creates cronjobs to perform curation and rollover which rely on the elasticsearch CR specifying an image.  There is no need to use a specific image since the services are python based.  Creations of the cron can utilize the default image associated with the operator
Comment 3 Qiaoling Tang 2020-05-09 05:47:46 UTC 
Tested with images from 4.5.0-0.ci-2020-05-08-221527, manifests are copied from the master branch with the latest code.

There doesn't have image specified in the elasticsearch instance, the index management cronjob can be created successfully, and the image is the ELASTICSEARCH_IMAGE specified in the deployment/elasticsearch-operator.

Move this bz to verified.
Comment 4 Jeff Cantrill 2020-05-15 13:17:46 UTC 
*** Bug 1835397 has been marked as a duplicate of this bug. ***
Comment 5 errata-xmlrpc 2020-07-13 17:29:56 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/RHBA-2020:2409
Note You need to log in before you can comment on or make changes to this bug.