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
check ServiceCatalog basic usages in OCP 4.x #23352
Conversation
@jianzhangbjz I'll review it tomorrow (July 11th) |
6e44e5a
to
b6ca3c2
Compare
/retest |
@jmrodri Thanks! I'm looking forward to your comments. |
/test e2e-aws |
There was a problem hiding this 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.
@bparees Could you help take a look below errors? I have no idea why it uses
|
/retest |
i don't either, it looks right to me. /retest |
heritage: Tiller | ||
release: ups-broker | ||
name: ups-broker | ||
namespace: "${NAMESPACE}" |
There was a problem hiding this comment.
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.
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):
|
var _ = g.Describe("[Feature:Platform] Service Catalog should", func() { | ||
defer g.GinkgoRecover() | ||
|
||
var oc = exutil.NewCLI("service-catalog", exutil.KubeConfigPath()).WithoutNamespace() |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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!
Seems like Service Catalog Operator doesn't support change status to
|
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 |
@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 |
/test e2e-aws |
4 similar comments
/test e2e-aws |
/test e2e-aws |
/test e2e-aws |
/test e2e-aws |
/retest |
Anyone can help fix this account problem for GCP: 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" |
@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: |
/test e2e-gcp |
/retest |
/test e2e-gcp |
1 similar comment
/test e2e-gcp |
/retest |
/test e2e-gcp |
@shawn-hurley Could you help add the |
/approve |
[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 |
/retest Please review the full test history for this PR and help us cut down flakes. |
5 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@jianzhangbjz: The following tests failed, say
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. |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
name: ups-deployment-template | ||
objects: | ||
- apiVersion: extensions/v1beta1 | ||
kind: Deployment |
There was a problem hiding this comment.
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
check ServiceCatalog basic usages in OCP 4.1
check ServiceCatalog basic usages in OCP 4.2
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