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

upi-gcp-install: enable 'master' name for control plane #9490

Merged

Conversation

jstuever
Copy link
Contributor

@jstuever jstuever commented Jun 4, 2020

This change updates the upi-gcp-install step to be able to use the full
word 'master' in the name of control plane nodes. It maintains
compatiblity with the the older 'm' naming convention by looking at
which one was used in the 05_control_plane.py template.

openshift/installer#3713

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 4, 2020
MASTER0_IP=$(gcloud compute instances describe ${INFRA_ID}-m-0 --zone ${ZONE_0} --format json | jq -r .networkInterfaces[0].networkIP)
MASTER1_IP=$(gcloud compute instances describe ${INFRA_ID}-m-1 --zone ${ZONE_1} --format json | jq -r .networkInterfaces[0].networkIP)
MASTER2_IP=$(gcloud compute instances describe ${INFRA_ID}-m-2 --zone ${ZONE_2} --format json | jq -r .networkInterfaces[0].networkIP)
MASTER0_IP=$(gcloud compute instances describe ${INFRA_ID}-${MASTER}-0 --zone ${ZONE_0} --format json | jq -r .networkInterfaces[0].networkIP)
Copy link
Contributor

Choose a reason for hiding this comment

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

qq: is there no way to request the information from the deploymentmanager template that was deployed. i.e all the resources it created?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There likely is, but that's not what is in our documentation. I'd like to make sure we are sticking to documentation as much as possible, since that's the point.

This change updates the upi-gcp-install step to be able to use the full
word 'master' in the name of control plane nodes. It maintains
compatiblity with the the older 'm' naming convention by looking at
which one was used in the 05_control_plane.py template.

openshift/installer#3713
@jstuever
Copy link
Contributor Author

jstuever commented Jun 5, 2020

/test pj-rehearse

@openshift-ci-robot
Copy link
Contributor

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

Test name Commit Details Rerun command
ci/rehearse/openshift/installer/master/e2e-gcp-upi 2695133 link /test pj-rehearse
ci/prow/pj-rehearse 2695133 link /test pj-rehearse

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.

@jstuever
Copy link
Contributor Author

jstuever commented Jun 5, 2020

Running into the following bug https://bugzilla.redhat.com/show_bug.cgi?id=1844613:

Jun 05 16:56:35 ci-op-w41w3lff-42368-qqkxn-m-0.c.openshift-gce-devel-ci.internal hyperkube[1532]: E0605 16:56:35.306854    1532 kubelet_node_status.go:92] Unable to register node "ci-op-w41w3lff-42368-qqkxn-m-0.c.openshift-gce-devel-ci.internal" with API server: Node "ci-op-w41w3lff-42368-qqkxn-m-0.c.openshift-gce-devel-ci.internal" is invalid: metadata.labels: Invalid value: "ci-op-w41w3lff-42368-qqkxn-m-0.c.openshift-gce-devel-ci.internal": must be no more than 63 characters

PR openshift/installer#3713 is designed to work around this bug, but it requires this PR to merge first.

@abhinavdahiya
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 8, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, jstuever

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-merge-robot openshift-merge-robot merged commit cf9f3eb into openshift:master Jun 8, 2020
@openshift-ci-robot
Copy link
Contributor

@jstuever: Updated the following 2 configmaps:

  • step-registry configmap in namespace ci at cluster api.ci using the following files:
    • key upi-install-gcp-commands.sh using file ci-operator/step-registry/upi/install/gcp/upi-install-gcp-commands.sh
  • step-registry configmap in namespace ci at cluster app.ci using the following files:
    • key upi-install-gcp-commands.sh using file ci-operator/step-registry/upi/install/gcp/upi-install-gcp-commands.sh

In response to this:

This change updates the upi-gcp-install step to be able to use the full
word 'master' in the name of control plane nodes. It maintains
compatiblity with the the older 'm' naming convention by looking at
which one was used in the 05_control_plane.py template.

openshift/installer#3713

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.

@jstuever jstuever deleted the gcp_relax_clustername branch June 8, 2020 16:55
jstuever added a commit to jstuever/release that referenced this pull request Jun 8, 2020
This change updates the upi-gcp-install step to be able to use the full
word 'worker' in the name of compute nodes. It maintains
compatiblity with the the older 'w' naming convention by looking at
if 'm' or 'master' is used in control_plane.py per openshift#9490.

openshift/installer#3713
openshift#9490
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
4 participants