Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

check ServiceCatalog basic usages in OCP 4.x #23352

Merged

Conversation

jianzhangbjz
Copy link
Contributor

This PR will cover ServiceCatalog test cases: OCP-24062, OCP-24049, OCP-15600. @jmrodri @shawn-hurley @bparees Could you help have a review? Thanks! cc: @bandrade @scolange @cuipinghuo @chengzhang1016 @zihantang-rh @emmajiafan

@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 10, 2019
@jianzhangbjz
Copy link
Contributor Author

/assign @jmrodri @bparees

@jmrodri
Copy link
Contributor

jmrodri commented Jul 10, 2019

@jianzhangbjz I'll review it tomorrow (July 11th)

@jianzhangbjz jianzhangbjz force-pushed the service-catalog branch 2 times, most recently from 6e44e5a to b6ca3c2 Compare July 12, 2019 10:09
@openshift-ci-robot openshift-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jul 12, 2019
@jianzhangbjz
Copy link
Contributor Author

/retest

@jianzhangbjz
Copy link
Contributor Author

@jmrodri Thanks! I'm looking forward to your comments.

@jianzhangbjz
Copy link
Contributor Author

/test e2e-aws

Copy link
Contributor

@jmrodri jmrodri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine to me. Nothing stands out.

@jianzhangbjz
Copy link
Contributor Author

@bparees Could you help take a look below errors? I have no idea why it uses ci-op-v9kp4jjx namespace. :(

fail [github.com/openshift/origin/test/extended/operators/service_catalog.go:94]: Unexpected error:
    <*util.ExitError | 0xc003fea660>: {
        Cmd: "oc --config=/tmp/admin.kubeconfig process -f /tmp/fixture-testdata-dir654606588/test/extended/testdata/service_catalog/ups-deployment.yaml -p NAMESPACE=e2e-test-service-catalog-97jk7",
        StdErr: "error: unable to process template\n  namespaces \"ci-op-v9kp4jjx\" not found",

@shawn-hurley
Copy link

/retest

@bparees
Copy link
Contributor

bparees commented Jul 15, 2019

@bparees Could you help take a look below errors? I have no idea why it uses ci-op-v9kp4jjx namespace. :(

i don't either, it looks right to me.

/retest

heritage: Tiller
release: ups-broker
name: ups-broker
namespace: "${NAMESPACE}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just in case, can you use a different name for this parameter in case somehow things are being tripped by NAMESPACE being a special value?

i don't think it's the issue but it's an easy thing to try.

@bparees
Copy link
Contributor

bparees commented Jul 15, 2019

The implication of the error you're getting is that the oc binary is using a namespace that doesn't exist (namely it looks like it's using the namespace that the CI job pod is running under, which doesn't make much sense to me):

oc process -f /tmp/template.yaml -p NAMESPACE=test -n nonexistent
error: unable to process template
  namespaces "nonexistent" not found

var _ = g.Describe("[Feature:Platform] Service Catalog should", func() {
defer g.GinkgoRecover()

var oc = exutil.NewCLI("service-catalog", exutil.KubeConfigPath()).WithoutNamespace()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's possible this is your issue. Why are you choosing "withoutnamespace"? This means your oc invocations will not have a -n arg added to them for the namespace your e2e test is running in.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought I have to add --namespace value for each oc command if I don't use WithoutNamespace(). So, I used it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think you have that backwards.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove the WithoutNamespace() func and it works now, thanks!

@jianzhangbjz
Copy link
Contributor Author

Seems like Service Catalog Operator doesn't support change status to Removed from Unmanaged. That also means if the user wants to disable Service Catalog, they have to change the status to Managed first. Is it as expected? @jmrodri @shawn-hurley

fail [github.com/openshift/origin/test/extended/operators/service_catalog.go:72]: Expected
    <string>: [map[lastTransitionTime:2019-07-16T06:24:10Z message:the apiserver is in the desired state (Removed). reason:Removed status:True type:Available] map[lastTransitionTime:2019-07-16T06:17:15Z reason:Removed status:False type:Progressing] map[lastTransitionTime:2019-07-16T05:41:53Z reason:Removed status:False type:Degraded] map[lastTransitionTime:2019-07-16T06:17:06Z reason:NoUnsupportedConfigOverrides status:True type:UnsupportedConfigOverridesUpgradeable] map[lastTransitionTime:2019-07-16T06:17:06Z status:False type:ResourceSyncControllerDegraded] map[lastTransitionTime:2019-07-16T06:17:12Z status:False type:WorkloadDegraded]]
to contain substring
    <string>: RemovalRequestIgnored

@shawn-hurley
Copy link

shawn-hurley commented Jul 16, 2019

Yes, that is correct and by design we are working on a fix for it, you can see this bug for more info: https://bugzilla.redhat.com/show_bug.cgi?id=1710937

@jianzhangbjz
Copy link
Contributor Author

@shawn-hurley Yes, thanks! But bug 1710937, it related to removing Service Catalog. And the current issue is that Service Catalog Operator doesn't support change Unmanaged to Removed. Is it as expected? If yes, why add this restriction?

@jianzhangbjz
Copy link
Contributor Author

/test e2e-aws

4 similar comments
@jianzhangbjz
Copy link
Contributor Author

/test e2e-aws

@jianzhangbjz
Copy link
Contributor Author

/test e2e-aws

@jianzhangbjz
Copy link
Contributor Author

/test e2e-aws

@jianzhangbjz
Copy link
Contributor Author

/test e2e-aws

@jianzhangbjz
Copy link
Contributor Author

/retest

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 3, 2019
@jianzhangbjz
Copy link
Contributor Author

Anyone can help fix this account problem for GCP: your Red Hat account is not enabled for remote support or your token has expired? Or am I missing something? Thanks! @bparees @smarterclayton

level=info msg="Cluster operator support Disabled is True with NotAuthorized: Reporting was not allowed: your Red Hat account is not enabled for remote support or your token has expired"
level=fatal msg="failed to initialize the cluster: Cluster operator console has not yet reported success"

@bparees
Copy link
Contributor

bparees commented Dec 4, 2019

@jianzhangbjz try pinging the @dpp-team in #forum-dp-platform or if you think our GCP account is fundamentally broken you can escalate to @dptp-triage in #4-dev-triage

but i'm not seeing evidence this is consistently failing across PRs:
https://prow.svc.ci.openshift.org/job-history/origin-ci-test/pr-logs/directory/pull-ci-openshift-origin-master-e2e-gcp

@jianzhangbjz
Copy link
Contributor Author

/test e2e-gcp

@jianzhangbjz
Copy link
Contributor Author

/retest

@jianzhangbjz
Copy link
Contributor Author

/test e2e-gcp

1 similar comment
@jianzhangbjz
Copy link
Contributor Author

/test e2e-gcp

@jianzhangbjz
Copy link
Contributor Author

/retest

@jianzhangbjz
Copy link
Contributor Author

/test e2e-gcp

@jianzhangbjz
Copy link
Contributor Author

@shawn-hurley Could you help add the /approve label? Thanks! I think @jmrodri and I only have the lgtm permission.

@shawn-hurley
Copy link

/approve

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jianzhangbjz, jmrodri, shawn-hurley

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 13, 2019
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

5 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 13, 2019

@jianzhangbjz: The following tests failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/e2e-aws-upgrade 48a591c link /test e2e-aws-upgrade
ci/prow/artifacts 48a591c link /test artifacts
ci/prow/e2e-aws 05d04c8 link /test e2e-aws

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 68b9a89 into openshift:master Dec 13, 2019
@jianzhangbjz jianzhangbjz deleted the service-catalog branch December 15, 2019 02:17
name: ups-deployment-template
objects:
- apiVersion: extensions/v1beta1
kind: Deployment
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extensions/v1beta1 are deprecated for a long time and removed in kube already, followed by removal in 4.4, correct is apps/v1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants