Error when upgrade via cluster.yaml

[hatsnal]

What happened?

When i run cluster.yaml for upgrade i've got error
'kubeadm_images_raw' is undefined"

What did you expect to happen?

node upgrade

How can we reproduce it (as minimally and precisely as possible)?

run cluster.yaml for upgrade per node

OS

Linux 5.15.0-92-generic x86_64
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

Version of Ansible

ansible [core 2.15.6]
config file = /home/sysadm/dev/ansible-kubespray/kubespray/ansible.cfg
configured module search path = ['/home/sysadm/dev/ansible-kubespray/kubespray/library']
ansible python module location = /home/sysadm/dev/ansible-kubespray/lib/python3.10/site-packages/ansible
ansible collection location = /home/sysadm/.ansible/collections:/usr/share/ansible/collections
executable location = /home/sysadm/dev/ansible-kubespray/bin/ansible
python version = 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (/home/sysadm/dev/ansible-kubespray/bin/python3)
jinja version = 3.1.2
libyaml = True

Version of Python

3.10.12

Version of Kubespray (commit)

ffda365

Network plugin used

calico

Full inventory with variables

Command used to invoke ansible

ansible-playbook cluster.yml -b -i inventory/ansible-kubespray-inventory/mts-k8s-01-test/hosts.yaml -e ansible_user=girdyuk_a --limit "mts-k8s-01-w0[1-4]-test.ga.loc"

Output of ansible run

Anything else we need to know

No response

[VannTen]

run cluster.yaml for upgrade per node

Do you mean that you upgrade first the control plane ? I see the problem, (#10899) but it should have happened before if you upgrade only the nodes and not the control plane first.

[VannTen]

/assign

[VannTen]

/reopen

[k8s-ci-robot]

@VannTen: Reopened this issue.

In response to this:

/reopen

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.