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.

Sign up for GitHub

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

Jump to bottom

Create master upgrade tests #3135

Closed
roberthbailey opened this issue Dec 23, 2014 · 10 comments
Closed

Create master upgrade tests #3135

roberthbailey opened this issue Dec 23, 2014 · 10 comments
Assignees
@zmerlynn
Labels
area/reliability area/test area/test-infra area/upgrade priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Milestone
v1.0

Comments

@roberthbailey
Copy link
Contributor

We need to get a good handle on upgrade/release policy, versions we're going to keep around, versions we're going to allow upgrade between, etc.
@roberthbailey roberthbailey added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/reliability labels Dec 23, 2014
@roberthbailey roberthbailey added the sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. label Feb 6, 2015
@roberthbailey roberthbailey added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Mar 4, 2015
@roberthbailey roberthbailey added this to the v1.0 milestone Mar 4, 2015
@mbforbes
Copy link
Contributor

mbforbes commented Apr 2, 2015

This is a pretty packed issue. Will decompose when I start working on this. For reference, node upgrade rollup: #6079

@mbforbes
Copy link
Contributor

mbforbes commented Apr 2, 2015

Changing to P1 because I don't believe we can claim upgrades work reliably without a test that exercises them. The other pieces of this issue—a thorough policy for retention, allowance, and testing—are very important, though we can debate their priority when this is broken down.

@mbforbes mbforbes added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. labels Apr 2, 2015
@alex-mohr
Copy link
Contributor

For v1, we only need new binary rollouts via upgrade but not necessarily functionality -- that can land shortly afterwards.

@mbforbes
Copy link
Contributor

I've got the binary rollout test plans in #7256—comments (esp. prioritization for 1.0) welcome!

@roberthbailey
Copy link
Contributor Author

This issue is quite vague. @mbforbes - I saw that you created issues for various node upgrade test scenarios; is there an issue for testing master upgrades?

@mbforbes
Copy link
Contributor

mbforbes commented May 6, 2015

@roberthbailey No issue for master upgrade tests yet; was leaving that to @zmerlynn given our node/master split, though happy to hash out a draft when I've got a few cycles.

@roberthbailey
Copy link
Contributor Author

Since you have the node upgrade issues sufficiently sussed out elsewhere, I'm going to repurpose this for master upgrade tests and re-assign to @zmerlynn.

@roberthbailey roberthbailey changed the title Create upgrade tests Create master upgrade tests May 7, 2015
@roberthbailey roberthbailey assigned zmerlynn and unassigned mbforbes May 7, 2015
@roberthbailey
Copy link
Contributor Author

/cc @satnam6502 (after our discussion today)

@davidopp
Copy link
Member

@roberthbailey and @zmerlynn will file more detailed issues for this (and mark them as 1.0).

This was referenced May 11, 2015
Closed
Closed
@roberthbailey
Copy link
Contributor Author

Split into #80801 and #8082.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zmerlynn zmerlynn

Labels
area/reliability area/test area/test-infra area/upgrade priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
5 participants
@mbforbes @zmerlynn @roberthbailey @davidopp @alex-mohr