Bug 1822685
| Summary: | Binary builds executed by 'oc start-build' take much longer to complete when dynatrace-oneagent-operator is enabled | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Tony Garcia <antgarci> | ||||
| Component: | Build | Assignee: | Adam Kaplan <adam.kaplan> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | wewang <wewang> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.2.z | CC: | aos-bugs, malonso, oarribas, wzheng | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-04-09 18:52:25 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: | |||||||
| Attachments: |
|
||||||
This is not a bug in OpenShift builds. Based on the description and work-around, the performance degradation is due to the behavior of the Dynatrace agents. *** Bug 1952467 has been marked as a duplicate of this bug. *** |
Created attachment 1677573 [details] dynatrace-disabled-settings Description of problem:Enabling dynatrace-oneagent-operator cause builds using 'oc start-build' command to take much longer than expected Version-Release number of selected component (if applicable): OCP 4.2.z and 4.3.z How reproducible: Install and enable the dynatrace-oneagent-operator Steps to Reproduce: 1.Install dynatrace operator. 2.Enable dynatrace-oneagent-operator via dynatrace console. 3.Run build via 'oc start-build' Actual results: Builds will take 10+ minutes to complete Expected results: Builds take 1+ minute to complete Additional info: An original workaround was to remove the agent and operator, scale down the machinesets to 0 and then scale them back up. However, the customer discovered that if they disable the "Automatically monitor processes" and "Automatically inject real user monitoring JavaScript tag" in the "Process Group" of the Dynatrace settings dashboard, the builds complete within an expected time frame and this workaround does not require removal of the Dynatrace agents or Operator. I've attached a screenshot of the settings in the dashboard the customer disabled.