-
Bug
-
Resolution: Done
-
Undefined
-
None
Description of problem:
Creation of a new host on OCP-V compute resource fails with an underlying error VMI does not exist
How reproducible:
Always
Is this issue a regression from an earlier version:
Steps to Reproduce:
1. Create an OCP-V compute resource
2. Provision a new host
3.
Actual behavior:
The creation times out with a message in the log:
The specified wait_for timeout (600 seconds) was exceeded' error (Fog::Errors::TimeoutError): The specified wait_for timeout (600 seconds) was exceeded 04:35:24 rails.1 | 352dc941 | /home/vagrant/foreman/.vendor/ruby/3.0.0/gems/fog-core-2.6.0/lib/fog/core/wait_for.rb:9:in `block in wait_for' 04:35:24 rails.1 | 352dc941 | /home/vagrant/foreman/.vendor/ruby/3.0.0/gems/fog-core-2.6.0/lib/fog/core/wait_for.rb:6:in `loop' 04:35:24 rails.1 | 352dc941 | /home/vagrant/foreman/.vendor/ruby/3.0.0/gems/fog-core-2.6.0/lib/fog/core/wait_for.rb:6:in `wait_for' 04:35:24 rails.1 | 352dc941 | /home/vagrant/foreman/.vendor/ruby/3.0.0/gems/fog-core-2.6.0/lib/fog/core/model.rb:103:in `wait_for' 04:35:24 rails.1 | 352dc941 | /home/vagrant/foreman/app/models/compute_resource.rb:368:in `vm_ready' 04:35:24 rails.1 | 352dc941 | /home/vagrant/foreman/app/models/concerns/orchestration/compute.rb:191:in `setComputeIP' 04:35:24 rails.1 | 352dc941 | /home/vagrant/foreman/app/models/concerns/orchestration.rb:227:in `execute'
Expected behavior:
The host should be created.
Business Impact / Additional info:
When looking in the OCP-V UI, you can see a{{VMI does not exist}} error on the diagnostics tab.
The internal reason for that is that we add an image parameter:
volumes:
- containerDisk:
image: rhel7-server-small
name: my-machine-example-com-disk-00
Which is not needed when not using image based provisioning.
- relates to
-
-
- Release Pending
-