Bug 1315503
Summary: | NewPkg: Add python-elasticsearch | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Rich Megginson <rmeggins> |
Component: | Logging | Assignee: | Luke Meyer <lmeyer> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Junqi Zhao <juzhao> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 3.2.0 | CC: | aos-bugs, rmeggins, tdawson, xiazhao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-22 16:12:01 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1315504 |
Description
Rich Megginson
2016-03-07 23:06:59 UTC
Thanks to tdawson I am able to build and install python-elasticsearch and elastic-curator using mock with rhaos-3.2-rhel-7-candidate. So can this bug be closed or do we need it to track something? (In reply to Luke Meyer from comment #2) > So can this bug be closed or do we need it to track something? I don't know. I think QE has to verify that the package can be installed from the official RH AOS 3.2.x channel. This packages is available in the official openshift enterprise / openshift container platform 3.2 and 3.3 channels. Marking it on qe so it can be tested. Will mark it as Closed / Current Release if it passes QE @juzhao Could you please update status here for this issue? Do you still have issue on deleting indices for 3.2.0 level logging stacks? @xiazhao, Tested on OCP 3.3.1 + Logging 3.3.1, python-elasticsearch version is 2.3.0, all the three cases passed testing https://tcms.engineering.redhat.com/case/509062/?from_plan=14587 https://tcms.engineering.redhat.com/case/536618/?from_plan=14587 https://tcms.engineering.redhat.com/case/531500/?from_plan=14587 But when tested on OCP 3.3.1 + Logging 3.2.1, it seems curator could not process more than one project with same time and time unit. Will confirm this issue tomorrow. Verified with 3.2.1 images on ops registry, curator worked fine on process more than one project with same time and time unit, set to verified: openshift3/logging-elasticsearch 15fb42270514 openshift3/logging-kibana b420c7b0f4e6 openshift3/logging-curator 2c60445c0b6e openshift3/logging-fluentd 77a64b668f70 openshift3/logging-deployment d7efd0e669f7 |