search

openshift / installer

Install an OpenShift 4.x cluster
https://try.openshift.com
Apache License 2.0
1.42k stars 1.38k forks source link

OCP V4.10 create-templates-and-vms.yml Ansible playbook for oVirt on UPI fails #5978

Closed pdfruth closed 1 year ago

pdfruth commented 2 years ago

Version

4.10

$ openshift-install version
./openshift-install 4.10.15
built from commit 629c3e0aadf8825dd8a3bc4c8a75d41f625140ba
release image quay.io/openshift-release-dev/ocp-release@sha256:ddcb70ce04a01ce487c0f4ad769e9e36a10c8c832a34307c1b1eb8e03a5b7ddb
release architecture amd64

Platform:

oVirt 4.15 UPI on x86_64

What happened?

As per the documentation here; https://docs.openshift.com/container-platform/4.10/installing/installing_rhv/installing-rhv-user-infra.html#installation-rhv-creating-templates-virtual-machines_installing-rhv-user-infra

Running the create-templates-and-vms.yml Ansible playbook on the oVirt engine server with this command;

ansible-playbook -i inventory.yml create-templates-and-vms.yml

Results in an error message, and the playbook fails;

.
.
Template with name 'worker_rhcos_tpl' and version 'None' in data center 'Default' was not found
.
.
PLAY RECAP *********************************************************************
localhost                  : ok=54   changed=5    unreachable=0    failed=1    skipped=44   rescued=0    ignored=0

What you expected to happen?

Ansible playbook should complete with no failures

Anything else we need to know?

The create-templates-and-vms.yml Ansible playbook has a small bug, which is easily fixed by changing one line of code.

In the create-templates-and-vms.yml file here; https://github.com/openshift/installer/blob/release-4.10/upi/ovirt/create-templates-and-vms.yml

change line 59 from; template_name: "{{ item.disks.0.name }}" to; template_name: "{{ item.template }}"

barbacbd commented 2 years ago

@pdfruth I believe that this issue should be migrated over to openshift ansible.

Can you provide the version of ansible that you were using when you encountered this error?

openshift-bot commented 1 year ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 1 year ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 1 year ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci[bot] commented 1 year ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/installer/issues/5978#issuecomment-1382968265): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.