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

[CVP-1588] Set default baseDomain variable inside for ipi stage in step-registry #15135

Merged
merged 1 commit into from Jan 21, 2021

Conversation

samvarankashyap
Copy link
Contributor

$subject,
These changes help up overriding the baseDomain variable inside the config template of ipi stage.

@samvarankashyap
Copy link
Contributor Author

@dirgim PTAL

- name: BASE_DOMAIN
default: "origin-ci-int-aws.dev.rhcloud.com"
documentation: |-
Base domain is used for setting baseDomain variable in Config template used in ipi-conf-aws-commands.sh
Copy link
Contributor

@dirgim dirgim Jan 21, 2021

Choose a reason for hiding this comment

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

Maybe changing this to something like A fully-qualified domain or subdomain name. The base domain of the cloud provider is used for setting baseDomain variable of the install configuration of the cluster.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@dirgim
Copy link
Contributor

dirgim commented Jan 21, 2021

/cc @petr-muller @stevekuznetsov

@wking
Copy link
Member

wking commented Jan 21, 2021

/retitle [CVP-1588] Set default baseDomain variable inside for ipi stage in step-registry

@openshift-ci-robot openshift-ci-robot changed the title [CVP-1588 ]Set default baseDomain variable inside for ipi stage in step-registry [CVP-1588] Set default baseDomain variable inside for ipi stage in step-registry Jan 21, 2021
@wking
Copy link
Member

wking commented Jan 21, 2021

Looks reasonable to me, but I'd like to see at least a few green rehearsals.

@wking
Copy link
Member

wking commented Jan 21, 2021

Has some green now.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 21, 2021
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: samvarankashyap, wking

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 Jan 21, 2021
@openshift-bot
Copy link
Contributor

/retest

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 21, 2021

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

Test name Commit Details Rerun command
ci/rehearse/openshift/installer/master/e2e-aws-proxy b5d5eb1 link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-ovn-step-registry b5d5eb1 link /test pj-rehearse
ci/rehearse/openshift/cluster-logging-operator/master/e2e-operator b5d5eb1 link /test pj-rehearse
ci/rehearse/openshift/aws-ebs-csi-driver/master/e2e-aws-csi b5d5eb1 link /test pj-rehearse
ci/rehearse/openshift/cluster-samples-operator/master/e2e-aws-jenkins b5d5eb1 link /test pj-rehearse
ci/rehearse/openshift/oc/release-4.2/e2e-cmd b5d5eb1 link /test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/master/e2e-agnostic b5d5eb1 link /test pj-rehearse
ci/rehearse/cri-o/cri-o/master/e2e-agnostic b5d5eb1 link /test pj-rehearse
ci/prow/pj-rehearse b5d5eb1 link /test pj-rehearse
ci/rehearse/openshift/insights-operator/release-4.2/insights-operator-e2e-tests b5d5eb1 link /test pj-rehearse

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

@openshift-merge-robot openshift-merge-robot merged commit 0385584 into openshift:master Jan 21, 2021
@openshift-ci-robot
Copy link
Contributor

@samvarankashyap: Updated the following 2 configmaps:

  • step-registry configmap in namespace ci at cluster api.ci using the following files:
    • key ipi-conf-aws-commands.sh using file ci-operator/step-registry/ipi/conf/aws/ipi-conf-aws-commands.sh
    • key ipi-conf-aws-ref.yaml using file ci-operator/step-registry/ipi/conf/aws/ipi-conf-aws-ref.yaml
  • step-registry configmap in namespace ci at cluster app.ci using the following files:
    • key ipi-conf-aws-commands.sh using file ci-operator/step-registry/ipi/conf/aws/ipi-conf-aws-commands.sh
    • key ipi-conf-aws-ref.yaml using file ci-operator/step-registry/ipi/conf/aws/ipi-conf-aws-ref.yaml

In response to this:

$subject,
These changes help up overriding the baseDomain variable inside the config template of ipi stage.

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.

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.
Projects
None yet
6 participants