process extensions before file updates

[yuvalk]

so that files/ systemd units can rely on extensions in the same MC

Closes: OCPBUGS-17826

- What I did
I changed the order by which update is applied, so that extensions are processed before files (systemd, file content, etc)

- How to verify it
try with the following mc spec:

  config:
    ignition:
      version: 3.2.0
  extensions:
    - ipsec
  systemd:
    units:
    - name: ipsec.service
      enabled: true

- Description for the changelog
change update apply order so that extensions can be specified with systemd units that relate to extension content

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yuvalk
Once this PR has been reviewed and has the lgtm label, please assign sinnykumari for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[yuvalk]

/test verify

[yuvalk]

/test unit

[yuvalk]

/test e2e-hypershift

[yuvalk]

/test e2e-aws-ovn-upgrade

[sinnykumari]

Unfortunately this is not going to help for this usecase. Extensions and OSUpdates are applied using rpm-ostree and this results into a new deployment. They don't get reflected to current OS deployment to which it has been booted. While, any writing file/ systemd service and any processing to it happen to booted deployment on RHCOS node.

[yuvalk]

Unfortunately this is not going to help for this usecase. Extensions and OSUpdates are applied using rpm-ostree and this results into a new deployment. They don't get reflected to current OS deployment to which it has been booted. While, any writing file/ systemd service and any processing to it happen to booted deployment on RHCOS node.

right, that would be too easy ;-)

[openshift-ci]

@yuvalk: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-hypershift	f3a459a	link	true	/test e2e-hypershift

Full PR test history. Your PR dashboard.

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.

[cgwalters]

This relates to #1190 which is going to be fixed by the in-cluster build and layering because we consistently and transactionally update the OS and configuration as one unit in this approach.