Skip to content

Conversation

@jstuever
Copy link
Contributor

Prior to this change, the aws upi template set the compute replicas to
zero but did not set masterScheduable to false. This caused the master
nodes to be schedulable.

This change sets masterScheduable to false to maintain the same
configuration we are asking of our customers in our documentation.

Prior to this change, the aws upi template set the compute replicas to
zero but did not set masterScheduable to false. This caused the master
nodes to be schedulable.

This change sets masterScheduable to false to maintain the same
configuration we are asking of our customers in our documentation.
@jstuever
Copy link
Contributor Author

/cc @wking

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 16, 2020
@jstuever
Copy link
Contributor Author

/test pj-rehearse

@patrickdillon
Copy link
Contributor

/lgtm

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

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Jan 17, 2020
@jstuever
Copy link
Contributor Author

/lgtm cancel
isn't masterScheduleable already false? https://github.com/openshift/installer/blob/master/pkg/asset/manifests/scheduler.go#L52

No... because https://github.com/openshift/installer/blob/master/pkg/asset/manifests/scheduler.go#L73

@patrickdillon
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 17, 2020
@wking
Copy link
Member

wking commented Jan 18, 2020

Not loading from disk is a bug. Can we fix this, e.g. like openshift/installer#1211? I'm fine landing this as a temporary hack if folks want.

@jstuever
Copy link
Contributor Author

Not loading from disk is a bug. Can we fix this, e.g. like openshift/installer#1211? I'm fine landing this as a temporary hack if folks want.

I see how that bug is related. However, here we are fixing the discrepancy between CI and the customer facing docs. Step 4 is not listed as optional:

https://docs.openshift.com/container-platform/4.2/installing/installing_aws/installing-aws-user-infra.html#installation-user-infra-generate-k8s-manifest-ignition_installing-aws-user-infra

@wking
Copy link
Member

wking commented Jan 21, 2020

However, here we are fixing the discrepancy between CI and the customer facing docs.

Fair. And again, I'm fine with this PR as a short-term hack. But I think "haha, we just clobbered the manifest you supplied before calling the installer" is a gotcha that I'd rather avoid. Can we at least get a ticket for accepting those early manifests instead of requreing folks to supply it at just the right time to get slurped in?

@sdodson
Copy link
Member

sdodson commented Jan 22, 2020

/test pj-rehearse

@sdodson
Copy link
Member

sdodson commented Jan 22, 2020

/approve

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jstuever, patrickdillon, sdodson

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

The pull request process is described here

Details 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 22, 2020
@openshift-merge-robot openshift-merge-robot merged commit 0be34fe into openshift:master Jan 22, 2020
@openshift-ci-robot
Copy link
Contributor

@jstuever: Updated the following 3 configmaps:

  • prow-job-cluster-launch-installer-upi-e2e configmap in namespace ci at cluster ci/api-build01-ci-devcluster-openshift-com:6443 using the following files:
    • key cluster-launch-installer-upi-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml
  • prow-job-cluster-launch-installer-upi-e2e configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-installer-upi-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml
  • prow-job-cluster-launch-installer-upi-e2e configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-installer-upi-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml
Details

In response to this:

Prior to this change, the aws upi template set the compute replicas to
zero but did not set masterScheduable to false. This caused the master
nodes to be schedulable.

This change sets masterScheduable to false to maintain the same
configuration we are asking of our customers in our documentation.

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.

@sdodson
Copy link
Member

sdodson commented Jan 22, 2020

@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/fcos/e2e-vsphere a390790 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-gcp-upi a390790 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-proxy a390790 link /test pj-rehearse
ci/prow/pj-rehearse a390790 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.

Details

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 jstuever deleted the awsupi_master_unschedulable branch February 11, 2022 17:27
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/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants