Disallow Atomic Host installs on 4.0

[vrutkovs]

Atomic Host install has been deprecated in 3.11 and cannot be used in master

TODO:

• Read OS family and disallow Atomic

[vrutkovs]

/test gcp-major-upgrade

[vrutkovs]

CSR approval flake during 3.11 setup

/test gcp-major-upgrade

[vrutkovs]

/test gcp-major-upgrade

[vrutkovs]

Flakes
/retest

[vrutkovs]

/test install

[vrutkovs]

/test install

[vrutkovs]

/test install

[vrutkovs]

/test install

[michaelgugino]

/lgtm

[vrutkovs]

/test e2e-gcp-major-upgrade-master
/test e2e-aws

[vrutkovs]

/retest

[vrutkovs]

/refresh

[vrutkovs]

/retest

[vrutkovs]

/refresh
/skip
/retest

[sdodson]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: michaelgugino, sdodson, vrutkovs

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 [michaelgugino,sdodson,vrutkovs]

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

[vrutkovs]

/retest

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/openshift-jenkins/install	6b0e156	link	/test install
ci/prow/e2e-gcp-major-upgrade-master	d373d1b	link	/test e2e-gcp-major-upgrade-master
ci/prow/e2e-gcp-logging	d373d1b	link	/test e2e-gcp-logging
ci/prow/e2e-gcp-major-upgrade	c64ab8f	link	/test e2e-gcp-major-upgrade

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.

[vrutkovs]

/test e2e-gcp

[smarterclayton]

Shortly after this pull merged, the openshift extended_install job started failing and blocking merges to origin:

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install/16436/consoleFull#181091684258b6e51eb7608a5981914356

TASK [openshift_cli : Install clients] *****************************************
task path: /usr/share/ansible/openshift-ansible/roles/openshift_cli/tasks/main.yml:2
ok: [localhost] => {
    "attempts": 1, 
    "changed": false, 
    "generated_timestamp": "2018-10-25 13:23:31.669277", 
    "msg": "", 
    "rc": 0, 
    "results": [
        "origin-clients-4.0.0-0.alpha.0.409.853d900.x86_64 providing origin-clients-4.0.0-0.alpha.0.409.853d900 is already installed"
    ]
}

TASK [openshift_cli : Pull CLI Image] ******************************************
task path: /usr/share/ansible/openshift-ansible/roles/openshift_cli/tasks/main.yml:10
fatal: [localhost]: FAILED! => {
    "changed": false, 
    "generated_timestamp": "2018-10-25 13:23:32.405818", 
    "msg": "Error pulling docker.io/openshift/origin-node - code: None message: manifest for docker.io/openshift/origin-node:853d900 not found"
}

PLAY RECAP *********************************************************************
 [WARNING]: Could not create retry file '/usr/share/ansible/openshift-
ansible/playbooks/deploy_cluster.retry'.         [Errno 13] Permission denied:
u'/usr/share/ansible/openshift-ansible/playbooks/deploy_cluster.retry'
localhost                  : ok=228  changed=93   unreachable=0    failed=1   

That seems like too much of a coincidence. Did the default change so that this block was getting called?

[smarterclayton]

I guess we've already removed that job, so we can simply turn it off.