Add a job to promote MCD from fcos-master branch

[vrutkovs]

Not entirely sure about tag_specification

/cc @smarterclayton

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vrutkovs
To complete the pull request process, please assign ashcrow
You can assign the PR to them by writing /assign @ashcrow in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/machine-config-operator/OWNERS
• ci-operator/jobs/openshift/machine-config-operator/OWNERS

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

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/rehearse/openshift/machine-config-operator/fcos-master/e2e-gcp-upgrade	64772758ace9efc0c16ded286743100617dcaf86	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/fcos-master/e2e-gcp-op	64772758ace9efc0c16ded286743100617dcaf86	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/fcos-master/e2e-aws-scaleup-rhel7	64772758ace9efc0c16ded286743100617dcaf86	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/fcos-master/e2e-aws-disruptive	64772758ace9efc0c16ded286743100617dcaf86	link	/test pj-rehearse
ci/prow/correctly-sharded-config	efb1d29	link	/test correctly-sharded-config
ci/prow/generated-config	efb1d29	link	/test generated-config
ci/rehearse/openshift/machine-config-operator/fcos-master/images	efb1d29	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/fcos-master/verify	efb1d29	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/fcos-master/unit	efb1d29	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/fcos-master/e2e-aws	efb1d29	link	/test pj-rehearse
ci/prow/pj-rehearse	efb1d29	link	/test pj-rehearse

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.

Details

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]

/cc @LorbusChris @smarterclayton

[smarterclayton]

If we're going to have a dedicated branch that is not using CI, it needs to be called "fcos" for now (master in the branch name will just confuse various things).

…

On Thu, Oct 24, 2019 at 4:19 PM Vadim Rutkovsky ***@***.***> wrote: /cc @LorbusChris <https://github.com/LorbusChris> @smarterclayton <https://github.com/smarterclayton> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5557?email_source=notifications&email_token=AAI37J5NLIXBQOHVB7TOCCLQQH7O3A5CNFSM4JEBKOZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECGJYHI#issuecomment-546085917>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAI37J47SOHUZJXJSEPXY5DQQH7O3ANCNFSM4JEBKOZQ> .

[smarterclayton]

you need to define the explicit base images here you want from fcos, i.e.:

base_images:
  ...
  machine-os-content:
     namespace: fcos
     name: 4.3
     tag: machine-os-content
  // any other images that differ, like installer

[smarterclayton]

this is probably fine as a promotion target. I think we'll want a separate job that takes over from the okd promotion flow that combines the three custom images here (machine-os-content, machine-config-operator, and installer) tests them with the latest okd images, and promotes them.

Once we have these publishing to fcos I will update the release controller so that it stops publishing the three images from ocp to okd, and instead we'll side load them via the job I mentioned.