blocker: fixing recursed accumulation of path for managed clair resources (PROJQUAY-7993)

[deshpandevlab]

The scale-down component was never rendered because of the incorrect path.
The clair-postgres and clair-app needed to scale back after the postgres upgrade.

This change ensures following flow in the case where clair is managed:

• Scale down clair-app
• Scale down clair-postgres
• Upgrade clair-postgres
• Scale up clair-postgres
• Scale up clair-app

Testing

• e2e tests
• tested by deploying to the OC
• tested for managed and unmanaged clair and postgres component

managed clair component for registry

shudeshp@shudeshp-mac ~ % oc get pods
NAME                                                  READY   STATUS              RESTARTS      AGE
shubhra-registry-clair-app-776c664cc7-8x54b           1/1     Running             0             14m
shubhra-registry-clair-app-776c664cc7-bmm8d           1/1     Running             0             15m
shubhra-registry-clair-postgres-5d6bb5bd9d-h87wp      1/1     Running             0             14m
shubhra-registry-clair-postgres-5d6bb5bd9d-nrf2m      0/1     ContainerCreating   0             14m
shubhra-registry-clair-postgres-old-85c795ddc-zst2j   1/1     Running             1 (14m ago)   15m
shubhra-registry-clair-postgres-upgrade-q9qws         0/1     ContainerCreating   0             15m
shubhra-registry-quay-app-754b596f7b-4pwrp            1/1     Running             2 (14m ago)   15m
shubhra-registry-quay-app-754b596f7b-4szrf            1/1     Running             3 (14m ago)   15m
shubhra-registry-quay-app-upgrade-vb2dh               0/1     Completed           0             16m
shubhra-registry-quay-database-6c6d5bc96f-2lb6p       1/1     Running             0             15m
shubhra-registry-quay-redis-d6d98bbfc-q7rbg           1/1     Running             0             15m

unmanaged clair component for registry

NAME                                                    READY   STATUS      RESTARTS      AGE
shubhra-registry-quay-app-fb9c7bfbd-mh9kl              1/1     Running     0             4m16s
shubhra-registry-quay-app-fb9c7bfbd-xw6xr              1/1     Running     0             4m16s
shubhra-registry-quay-app-upgrade-f57rt                0/1     Completed   0             5m5s
shubhra-registry-quay-config-editor-76444d4499-sklfl   1/1     Running     0             5m4s
shubhra-registry-quay-database-f5767b98-mkmg6          1/1     Running     0             5m4s
shubhra-registry-quay-redis-6bdf77fc56-7wvxm           1/1     Running     0             5m4s

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[deshpandevlab]

/test ocp-latest-e2e

[openshift-ci]

@deshpandevlab: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/ocp-latest-e2e	c75c72f	link	true	/test ocp-latest-e2e

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[jonathankingfc]

LGTM

[deshpandevlab]

/cherrypick redhat-3.13

[bcaton85]

/cherry-pick redhat-3.13

[openshift-cherrypick-robot]

@bcaton85: new pull request created: #970

In response to this:

/cherry-pick redhat-3.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.