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

Ensure the test deployment invariant is maintained #9839

Merged
merged 1 commit into from
Jul 14, 2016

Conversation

smarterclayton
Copy link
Contributor

Update scale for deployment while also setting next phase.

Fixes #9195 [test]

if deployment.Spec.Replicas != 0 {
switch nextStatus {
case deployapi.DeploymentStatusComplete, deployapi.DeploymentStatusFailed:
if config, err := deployutil.DecodeDeploymentConfig(deployment, c.codec); err == nil && config.Spec.Test {
Copy link
Contributor

Choose a reason for hiding this comment

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

This is getting annoying. Can't we just add a test annotation in the deployment when it's created? Then you wouldn't need to deserialize at all... and it's all over the place in this controller.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Update scale for deployment while also setting next phase.
@smarterclayton
Copy link
Contributor Author

Comment addressed, [merge]

@0xmichalis
Copy link
Contributor

Back to the first one

• Failure [20.435 seconds]
deploymentconfigs
/data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:554
  with test deployments
  /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:255
    should run a deployment to completion and then scale to zero [Conformance] [It]
    /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:254

    Expected
        <string>: --> pre: Running hook pod ...
        test pre hook executed
        --> pre: Success
        --> Scaling deployment-test-1 to 2
        --> Waiting up to 10m0s for pods in deployment deployment-test-1 to become ready
    to contain substring
        <string>: --> Success

    /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:211
------------------------------

We may want to use the failure trap for this test.

@smarterclayton
Copy link
Contributor Author

Extended.deploymentconfigs with test deployments should run a deployment to completion and then scale to zero [Conformance] (from (conformance_parallel_01.xml))

/data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:254
Expected
    <string>: --> pre: Running hook pod ...
    test pre hook executed
    --> pre: Success
    --> Scaling deployment-test-1 to 2
    --> Waiting up to 10m0s for pods in deployment deployment-test-1 to become ready
to contain substring
    <string>: --> Success

I think this is #9775

@smarterclayton
Copy link
Contributor Author

[test]

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to 74a5893

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/6293/)

@smarterclayton
Copy link
Contributor Author

[merge] and will switch to failure trap later

@openshift-bot
Copy link
Contributor

openshift-bot commented Jul 14, 2016

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/6293/) (Image: devenv-rhel7_4594)

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to 74a5893

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants