Skip to content

Conversation

@hexfusion
Copy link
Contributor

@hexfusion hexfusion commented Oct 29, 2019

The discovery init container is a very important part of the bootstraping process. Currently, we use SRV queries to populate ENV variables consumed by other containers in the pod.

As we move to an operator managed etcd cluster additional data points and validations need to be performed. The scaling of etcd is managed by the clustermembercontroller (CMC). When a new candidate for membership is verified as Ready to join the cluster the CMC populates a ConfigMap with basic information for the scaling process. This information includes details on the current members of the cluster. From this information, we can then populate the ETCD_INITIAL_CLUSTER variable which directs etcd on who its peers are.

To manage new candidates from racing only 1 member can scale at a time. Until that member has been added and verified no other member can be added. We do this by doing a wait until we observe the data identifying the pod as scaling.

We also populate a new ENV variable ETCD_ENDPOINTS this is used later on in the process by a new init container called membership.

Pending changes: The following items will change in the near future.

  • the member-config ConfigMap will stop using annotations for scaling data instead a more traditional data: key.

depends on #1224

@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Oct 29, 2019
@alaypatel07
Copy link
Contributor

depends on #1224, needs rebase after that gets in, thanks

@hexfusion hexfusion force-pushed the 4.3-cluster-etcd-operator-v1 branch from e08c0f3 to 9865cad Compare November 2, 2019 14:59
@hexfusion hexfusion changed the title WIP setup-etcd-environment: support scaling from cluster-etcd-operator setup-etcd-environment: support scaling from cluster-etcd-operator Nov 2, 2019
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 2, 2019
@hexfusion
Copy link
Contributor Author

hexfusion commented Nov 2, 2019

cmd/setup-etcd-environment/run.go:56:1: cyclomatic complexity 34 of func runRunCmd is high (> 30) (gocyclo)
func runRunCmd(cmd *cobra.Command, args []string) error {

Is this a new test I don't think we changed this.

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1221/pull-ci-openshift-machine-config-operator-master-verify/2211#1:build-log.txt%3A18

Update: We have a fix

@hexfusion
Copy link
Contributor Author

fail [k8s.io/kubernetes/test/e2e/apimachinery/resource_quota.go:167]: Unexpected error:
    <*errors.errorString | 0xc00029c0c0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred

@hexfusion
Copy link
Contributor Author

/test e2e-aws

1 similar comment
@hexfusion
Copy link
Contributor Author

/test e2e-aws

@hexfusion
Copy link
Contributor Author

trying to understand this failure.

/test e2e-aws

@hexfusion hexfusion force-pushed the 4.3-cluster-etcd-operator-v1 branch 3 times, most recently from 92f4abc to e5e4ecd Compare November 4, 2019 11:27
@openshift-ci-robot openshift-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Nov 4, 2019
@hexfusion hexfusion force-pushed the 4.3-cluster-etcd-operator-v1 branch from ec61312 to 8f2653b Compare November 4, 2019 11:42
@openshift-ci-robot openshift-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Nov 4, 2019
@hexfusion hexfusion force-pushed the 4.3-cluster-etcd-operator-v1 branch from 6f6556a to 6bef5de Compare November 4, 2019 14:16
@hexfusion
Copy link
Contributor Author

test failures related to regression in aws tests openshift/origin#24083

@hexfusion hexfusion force-pushed the 4.3-cluster-etcd-operator-v1 branch from 6bef5de to 38c5eaf Compare November 4, 2019 14:19
@hexfusion hexfusion force-pushed the 4.3-cluster-etcd-operator-v1 branch from 38c5eaf to 032ddd5 Compare November 4, 2019 14:20
@hexfusion hexfusion force-pushed the 4.3-cluster-etcd-operator-v1 branch from 032ddd5 to 37e6851 Compare November 4, 2019 14:26
@retroflexer
Copy link

/lgtm

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

/retest

Copy link
Contributor

@kikisdeliveryservice kikisdeliveryservice left a comment

Choose a reason for hiding this comment

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

looks good

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hexfusion, kikisdeliveryservice, retroflexer

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:
  • OWNERS [kikisdeliveryservice]

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 Nov 4, 2019
@hexfusion
Copy link
Contributor Author

/skip

@hexfusion
Copy link
Contributor Author

/test e2e-aws

@hexfusion
Copy link
Contributor Author

/retest

1 similar comment
@hexfusion
Copy link
Contributor Author

/retest

@openshift-bot
Copy link
Contributor

/retest

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

2 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.

@hexfusion
Copy link
Contributor Author

e2e-gcp-op still needs manual override it has the same failure.

cc @kikisdeliveryservice @runcom

@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
Contributor

openshift-ci-robot commented Nov 5, 2019

@hexfusion: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/e2e-aws-scaleup-rhel7 37e6851 link /test e2e-aws-scaleup-rhel7

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.

@hexfusion
Copy link
Contributor Author

/retest

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/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants