Chandrakala M Subramanyam
Chandrakala M Subramanyam
Invalid label fails with autotune 0.0.5 ``` *******----------- Running test for invalid-label ----------******* log_length_before_test 134 extract_lines 135 autotune object invalid-label got created Expected message is : com.autotune.analyzer.exceptions.InvalidValueException: label: not supported...
@msvinaykumar - I have deployed latest autotune from mvp_demo ( docker.io/msvinaykumar/autotune_operator:th) and applied the A/B json from PR #486, I get a NPE in autotune log, could you please check....
@bharathappali - Can you please update the API design doc with latest changes for listTrialStatus API
Applying blank layer presence label name results in NPE as seen below and applying valid yaml after that fails with io.fabric8.kubernetes.client.dsl.internal.RawWatchConnectionManager - Current reconnect backoff is 1000 milliseconds (T0) ```...
Yes, you can pick this up. We can discuss the priority of this during our scrum call. This should be run regularly as part of PR check.
Output for no-sloclass, null-sloclass, no-sloclass-value, blank-sloclass with autotune 0.0.5 ``` >>cat blank-sloclass-autotune.log com.autotune.analyzer.exceptions.InvalidValueException: slo_class: not supported at com.autotune.analyzer.k8sObjects.SloInfo.(SloInfo.java:58) at com.autotune.analyzer.deployment.AutotuneDeployment.getAutotuneObject(AutotuneDeployment.java:311) at com.autotune.analyzer.deployment.AutotuneDeployment$1.eventReceived(AutotuneDeployment.java:94) at com.autotune.analyzer.deployment.AutotuneDeployment$1.eventReceived(AutotuneDeployment.java:87) at io.fabric8.kubernetes.client.dsl.internal.RawWatchConnectionManager$1.onMessage(RawWatchConnectionManager.java:133) at okhttp3.internal.ws.RealWebSocket.onReadMessage(RealWebSocket.java:323) at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:219)...
@ShishirH - Issue is still seen ``` { "application_name": "petclinic-sample-0-75884c5549-2gld5", "objective_function": "transaction_response_time", "tunables": [ { "value_type": "double", "lower_bound": "150M", "name": "memoryRequest", "upper_bound": "300M" }, { "value_type": "double", "lower_bound": "1.0", "name":...
@ShishirH - I don't see this fixed with latest build too
@ShishirH - Is this different from issue #276 or is it a sub-issue required for this issue #276? If it is a sub-issue link it to #276, if it is...
Global Datasource related yaml tests too fail due to this error