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

CHANGELOG: Document changes since v0.9.0 #1064

Merged
merged 1 commit into from
Jan 16, 2019

Conversation

wking
Copy link
Member

@wking wking commented Jan 15, 2019

@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 15, 2019
@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 15, 2019
@abhinavdahiya
Copy link
Contributor

/approve

looks good.

@wking
Copy link
Member Author

wking commented Jan 15, 2019

e2e-aws:

6 error level events were detected during this test run:

Jan 15 01:30:16.732 E kube-apiserver Kube API started failing: Get https://ci-op-5979kimc-1d3f3-api.origin-ci-int-aws.dev.rhcloud.com:6443/api/v1/namespaces/kube-system?timeout=3s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Jan 15 01:34:20.521 E kube-apiserver Kube API started failing: Get https://ci-op-5979kimc-1d3f3-api.origin-ci-int-aws.dev.rhcloud.com:6443/api/v1/namespaces/kube-system?timeout=3s: context deadline exceeded
Jan 15 01:34:47.732 E kube-apiserver Kube API started failing: Get https://ci-op-5979kimc-1d3f3-api.origin-ci-int-aws.dev.rhcloud.com:6443/api/v1/namespaces/kube-system?timeout=3s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Jan 15 01:34:48.732 - 30s   E kube-apiserver Kube API is not responding to GET requests
Jan 15 01:35:17.733 E kube-apiserver Kube API started failing: Get https://ci-op-5979kimc-1d3f3-api.origin-ci-int-aws.dev.rhcloud.com:6443/api/v1/namespaces/kube-system?timeout=3s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Jan 15 01:39:19.732 E kube-apiserver Kube API started failing: Get https://ci-op-5979kimc-1d3f3-api.origin-ci-int-aws.dev.rhcloud.com:6443/api/v1/namespaces/kube-system?timeout=3s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)

/retest

@abhinavdahiya
Copy link
Contributor

/lgtm

/hold

@openshift-ci-robot openshift-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. labels Jan 15, 2019
CHANGELOG.md Outdated
cluster network.
- On OpenStack, the machine(set) templates have been updated to set
`cloudName` and some other properties.
- On libvirt, `destroy cluster` is not more robust in the face of
Copy link
Contributor

Choose a reason for hiding this comment

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

s/not/now/

Copy link
Member Author

Choose a reason for hiding this comment

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

s/not/now/

Thanks :). Fixed with 2cbe0f8 -> 997f778. Can you drop a fresh /lgtm?

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Jan 15, 2019
@crawford
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 15, 2019
Through 63bdb7f (Merge pull request openshift#1050 from
ironcladlou/trouble-doc, 2019-01-14).
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Jan 15, 2019
@wking
Copy link
Member Author

wking commented Jan 15, 2019

I've pushed 997f778 -> 68692df, bumping the release date to today. @crawford, can I get a fresh /lgtm?

@abhinavdahiya
Copy link
Contributor

/lgtm

I've pushed 997f778 -> 68692df, bumping the release date to today. @crawford, can I get a fresh /lgtm?

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, crawford, 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:
  • OWNERS [abhinavdahiya,crawford,wking]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@wking
Copy link
Member Author

wking commented Jan 15, 2019

/hold cancel

We're about to tag 0.10.0 on top of this via #1068.

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 15, 2019
@wking
Copy link
Member Author

wking commented Jan 15, 2019

e2e-aws:

fail [k8s.io/kubernetes/test/e2e/storage/pvc_protection.go:61]: Failed waiting for PVC to be bound PersistentVolumeClaim pvc-mw6ll not in phase Bound within 3m0s
Expected error:
    <*errors.errorString | 0xc4210aae80>: {
        s: "PersistentVolumeClaim pvc-mw6ll not in phase Bound within 3m0s",
    }
    PersistentVolumeClaim pvc-mw6ll not in phase Bound within 3m0s
not to have occurred

and two other volume-related errors.

/retest

@openshift-bot
Copy link
Contributor

/retest

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

@wking
Copy link
Member Author

wking commented Jan 15, 2019

e2e-aws error was:

level=error msg="Error: Error applying plan:"
level=error
level=error msg="1 error occurred:"
level=error msg="\t* module.vpc.aws_lb.api_external: 1 error occurred:"
level=error msg="\t* aws_lb.api_external: timeout while waiting for state to become 'active' (timeout: 10m0s)"

@wking
Copy link
Member Author

wking commented Jan 15, 2019

e2e-aws:

fail [github.com/openshift/origin/test/extended/deployments/deployments.go:388]: Expected
    <string>: --> pre: Running hook pod ...
    test pre hook executed
to contain substring
    <string>: deployment-test-2 up to 1

...
failed: (3m5s) 2019-01-15T20:31:02 "[Feature:DeploymentConfig] deploymentconfigs with test deployments [Conformance] should run a deployment to completion and then scale to zero [Suite:openshift/conformance/parallel/minimal]"

and more.

/retest

@wking
Copy link
Member Author

wking commented Jan 15, 2019

e2e-aws:

Failing tests:

[Area:Networking] multicast when using one of the plugins 'redhat/openshift-ovs-multitenant, redhat/openshift-ovs-networkpolicy' should allow multicast traffic in namespaces where it is enabled [Suite:openshift/conformance/parallel]
[Feature:Builds][Conformance] imagechangetriggers imagechangetriggers should trigger builds of all types [Suite:openshift/conformance/parallel/minimal]
[Feature:DeploymentConfig] deploymentconfigs when run iteratively [Conformance] should immediately start a new deployment [Suite:openshift/conformance/parallel/minimal]
[sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] should implement legacy replacement when the update strategy is OnDelete [Suite:openshift/conformance/parallel] [Suite:k8s]
[sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] should not deadlock when a pod's predecessor fails [Suite:openshift/conformance/parallel] [Suite:k8s]
[sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s]
[sig-scheduling] ResourceQuota should create a ResourceQuota and capture the life of a service. [Suite:openshift/conformance/parallel] [Suite:k8s] 

/retest

@wking
Copy link
Member Author

wking commented Jan 16, 2019

e2e-aws:

level=error
level=error msg="Error: Error applying plan:"
level=error
level=error msg="1 error occurred:"
level=error msg="\t* module.vpc.aws_lb_listener.api_internal_api: 1 error occurred:"
level=error msg="\t* aws_lb_listener.api_internal_api: Error retrieving Listener: timeout while waiting for state to become 'success' (timeout: 1m0s)"

/retest

@wking
Copy link
Member Author

wking commented Jan 16, 2019

e2e-aws:

level=error msg="Error: Error applying plan:"
level=error
level=error msg="1 error occurred:"
level=error msg="\t* module.vpc.aws_lb.api_internal: 1 error occurred:"
level=error msg="\t* aws_lb.api_internal: timeout while waiting for state to become 'active' (last state: 'provisioning', timeout: 10m0s)"

Sigh.

/retest

@wking
Copy link
Member Author

wking commented Jan 16, 2019

/retest

@openshift-merge-robot openshift-merge-robot merged commit 3af001d into openshift:master Jan 16, 2019
@wking
Copy link
Member Author

wking commented Jan 16, 2019

woo, finally

@wking wking deleted the version-0.10.0 branch January 17, 2019 00:28
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.

6 participants