Description of problem:
Deploying OCS rolls out a NooBaa operator that creates the following HPA:
This HPA results in the below alert:
May 6, 8:56 am
HPA openshift-storage/noobaa-endpoint has been running at max replicas for longer than 15 minutes.
Since the maxReplicas and minReplicas are 1, it will always be at max replicas, and any attempt to disable the HPA or expand max replicas is overwritten, so it seems like a potential defect.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy OCS on top of 4.3.
2. Wait for NooBaa operator to deploy.
3. Observe the HPA alerts.
I assume that the HPA is there for some reason, but if there's no ability to change it without editing the operator and there is no scaleable range, it could just be removed from the operator.
I can provide must-gather logs on request, if they are needed.
Moving to OCS (and guessing OCS version an component name).
@raz I guess we can push out of 4.5 since auto scale won't be in ?
*** Bug 1800599 has been marked as a duplicate of this bug. ***
*** Bug 1840102 has been marked as a duplicate of this bug. ***
@Bipin & @Nimrod,
Is this the epic for the auto-scale of noobaa-endpoint?
As mentioned before, as well as another investigation on a similar bug (See https://bugzilla.redhat.com/show_bug.cgi?id=1788126#c23)
These alerts cannot be suppressed.
Pushing to 4.6 when autoscaling might be delivered and then those alerts would stop.
(In reply to Nimrod Becker from comment #21)
> As mentioned before, as well as another investigation on a similar bug (See
> These alerts cannot be suppressed.
BZ 1788126 could be fixed via inhibition rules, as noted in comment
If you want to claim that this can't be fixed, I expect mcg dev team to
find someone from openshift team to validate such opinion.
This can't be fixed, we need to change the scale of HPA to 1-2 which will happen in 4.6
As part of the endpoint HPA TP in 4.6, the default was set to 1 - 2, the alerts won't fire.
It seems that the fix was not complete.
I don't see alert mentioned in bug description:
"HPA openshift-storage/noobaa-endpoint has been running at max replicas for longer than 15 minutes."
but I still see the following alert after installation:
"KubeHpaReplicasMismatch: HPA openshift-storage/noobaa-endpoint has not matched the desired number of replicas for longer than 15 minutes."
$ oc get deployment noobaa-endpoint -n openshift-storage -o yaml
$ oc get HorizontalPodAutoscaler noobaa-endpoint -n openshift-storage -o yaml
@Filip, I can tell from the last message that this is not the same issue.
Can we please close this one and open a new one for the "desiredReplicas: 0" problem?
Ok, based on comments 28 and 29 I VERIFY that the original HPA alert is gone. For remaining HPA problems were reported BZ 1885313 and BZ 1885320.