fix: reset role for cri-o

[turbosnail]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug

/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
fix:
Remove cri-o apt repo job has state present but need absent
Uninstall CRI-O packages job has undefined variable crio_packages. Replaced by list of packages

Which issue(s) this PR fixes:

Fixes #10048

Special notes for your reviewer:

Does this PR introduce a user-facing change?: NONE

[k8s-ci-robot]

Hi @turbosnail. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[turbosnail]

/retest

[k8s-ci-robot]

@turbosnail: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[MrFreezeex]

Hi actually I think this is actually a bad copy paste from cleanup.yaml. Could you rather remove everything related to packages/repos and import the cleanup playbook? Or maybe even remove it entirely, there is a TODO note in cleanup.yaml by @cristicalin about it, WDYT @cristicalin?

[turbosnail]

as i see cleanup.yaml must be deleted but reset.yaml must be present. i just copied packages names from cleanup.yaml and paste to reset.yaml because the reset.yaml and delete of packages used in other container engeene

[MrFreezeex]

Well if we are going this way there is no reasons to keep these in reset.yml as well actually

[turbosnail]

IMHO deleting all code from reset.yaml not good idea because it's going outside of this PR and issue.
reset.yaml exists in all container-engine roles and it's need new PR

[MrFreezeex]

It doesn't make much sense to me to remove the cleanup.yml without removing the same tasks in the reset.yml though. I would either remove cleanup and the same tasks in reset.yml or import the cleanup.yml from the reset.yml if this need to be postponed further.

[turbosnail]

ok. i restore deleted file and left edits that only fix cleaning errors. any others edits must be resolved by other issue

[oomichi]

/cc @oomichi

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: turbosnail
Once this PR has been reviewed and has the lgtm label, please assign mattymo 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

[turbosnail]

Moved all changes to #10197