CHANGELOG: Document changes since 0.11.0

[wking]

Through da6d45b (#890).

Background for the networking.type validation entry is in this thread.

There's still a FIXME for documenting #1185, which I don't understand.

/hold

[wking]

@abhinavdahiya, thoughts on landing openshift/release#2772 before we cut 0.12.0, so we can drop our nominal v1beta1 support here (and avoid acting like it's supported even though we've dropped two properties)?

[wking]

Updated with 9330f0a -> 3c581f5 to document #1185.

/hold cancel

[wking]

Hmm, do we want to pick up #1182? Just into the merge queue, an it will make it easier to test upgrades.

[wking]

I've pushed 2e5acd0 -> 6a97a58 to bump the day to today, since this didn't go out yesterday. We can't actually advance beyond da6d45b (#890) without backports, because the next master commit is d1e59b3 (#1149), and that's incompatible with the pinned update payload.

[crawford]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

[openshift-bot]

/retest

[wking]

e2e-aws:

level=error msg="\t* aws_vpc.new_vpc: Error creating VPC: VpcLimitExceeded: The maximum number of VPCs has been reached."

But now we're back down to 86 VPCs (vs. our cap at 100), so...

/retest

[crawford]

aws_iam_role.bootstrap: Error creating IAM Role ci-op-vhs20b34-1d3f3-bootstrap-role: EntityAlreadyExists: Role with name ci-op-vhs20b34-1d3f3-bootstrap-role already exists.

Pretty sure this won't work...
/retest

[openshift-bot]

/retest

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

[wking]

e2e-aws:

level=error msg="\t* module.bootstrap.aws_iam_role.bootstrap: 1 error occurred:"
level=error msg="\t* aws_iam_role.bootstrap: Error creating IAM Role ci-op-z866h59b-1d3f3-bootstrap-role: EntityAlreadyExists: Role with name ci-op-z866h59b-1d3f3-bootstrap-role already exists."
level=error msg="\tstatus code: 409, request id: f4f923c1-2a27-11e9-9f0e-8f9d99bb602e"

But with #1199 out for a while I've made some progress on the orphan backlog, so we should be clear here now. On the other hand, we're not so far in the clear that I think we should be dropping /retests on all our /lgtmed PRs. I'll kick them one at a time as things land.

/retest

[wking]

e2e-aws:

level=error msg="2 errors occurred:"
level=error msg="\t* module.bootstrap.aws_s3_bucket.ignition: 1 error occurred:"
level=error msg="\t* aws_s3_bucket.ignition: Error creating S3 bucket: TooManyBuckets: You have attempted to create more buckets than allowed"

But we're down to 127 (of 150?) buckets now, so...

/retest

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/prow/e2e-openstack	2e5acd0	link	/test e2e-openstack
ci/prow/e2e-libvirt	2e5acd0	link	/test e2e-libvirt

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.

[wking]

e2e-aws:

level=error msg="4 errors occurred:"
level=error msg="\t* module.vpc.aws_route_table_association.route_net[0]: 1 error occurred:"
level=error msg="\t* aws_route_table_association.route_net.0: timeout while waiting for state to become 'success' (timeout: 5m0s)"

So now we're just hitting rate limits :p. I'll just wait and kick this again tonight.

[wking]

/retest