search

ManageIQ / manageiq-providers-kubevirt

ManageIQ plugin for the Kubevirt provider.
https://kubevirt.io/
Apache License 2.0
4 stars 29 forks source link

CrashLoopBackOff on kubevirt-infra-refresh pod - keeping restarting #169

Closed bsogithub closed 1 year ago

bsogithub commented 4 years ago

On cloudforms infrastructure provider provider, I put in the kubeadmin creds and the validation is successful. However, the vm template that I have is not listed. Checking the kubevirt-infra-resfresh pods and they are in CrashLoopBackOff status. Here are a portion of the entries of the log:

{"@timestamp":"2020-09-18T18:20:11.070781 ","hostname":"1-kubevirt-infra-refresh-8-79b58f46d6-jnm7s","pid":7,"tid":"2b101062d964","level":"info","message":"MIQ(ManageIQ::Providers::Kubevirt::InfraManager::RefreshWorker::Runner#sync_config) ID [88], PID [7], GUID [3f6a0b93-8897-44b0-9430-c459ea515ede], Zone [default], Active Roles [automate,database_operations,ems_inventory,ems_metrics_collector,ems_metrics_coordinator,ems_metrics_processor,ems_operations,event,remote_console,reporting,scheduler,smartproxy,smartstate,user_interface,web_services], Assigned Roles [automate,database_operations,database_owner,ems_inventory,ems_metrics_collector,ems_metrics_coordinator,ems_metrics_processor,ems_operations,event,remote_console,reporting,scheduler,smartproxy,smartstate,user_interface,web_services], Configuration:"}
{"@timestamp":"2020-09-18T18:20:11.071360 ","hostname":"1-kubevirt-infra-refresh-8-79b58f46d6-jnm7s","pid":7,"tid":"2b101062d964","level":"info","message":"\n---\n:count: 1\n:cpu_threshold_percent: 50\n:gc_interval: 900\n:heartbeat_freq: 10\n:heartbeat_timeout: 120\n:memory_threshold: 2147483648\n:nice_delta: 7\n:parent_time_threshold: 180\n:poll: 10\n:poll_escalate_max: 30\n:poll_method: :normal\n:starting_timeout: 600\n:stopping_timeout: 600\n:systemd_enabled: false\n:dequeue_method: :sql\n:queue_timeout: 7200"}
{"@timestamp":"2020-09-18T18:20:11.071465 ","hostname":"1-kubevirt-infra-refresh-8-79b58f46d6-jnm7s","pid":7,"tid":"2b101062d964","level":"info","message":"---"}
{"@timestamp":"2020-09-18T18:20:11.071792 ","hostname":"1-kubevirt-infra-refresh-8-79b58f46d6-jnm7s","pid":7,"tid":"2b101062d964","level":"info","message":"\n---\n:ems_id: '8'\n:guid: 3f6a0b93-8897-44b0-9430-c459ea515ede"}
{"@timestamp":"2020-09-18T18:20:15.162093 ","hostname":"1-kubevirt-infra-refresh-8-79b58f46d6-jnm7s","pid":7,"tid":"2b101062d964","level":"info","message":"MIQ(ManageIQ::Providers::Kubernetes::ContainerManager#with_provider_connection) Connecting through ManageIQ::Providers::Kubernetes::ContainerManager: [b-ocp-plus-7w-3.cp.fyre.ibm.com kubernetes provider]"}
/opt/IBM/infrastructure-management-gemset/gems/fog-kubevirt-1.3.4/lib/fog/kubevirt/compute/compute.rb:419:in `rescue in detect_version': 404 Not Found (Fog::Kubevirt::Errors::ClientError)
        from /opt/IBM/infrastructure-management-gemset/gems/fog-kubevirt-1.3.4/lib/fog/kubevirt/compute/compute.rb:416:in `detect_version'
        from /opt/IBM/infrastructure-management-gemset/gems/fog-kubevirt-1.3.4/lib/fog/kubevirt/compute/compute.rb:360:in `create_client_from_token'
        from /opt/IBM/infrastructure-management-gemset/gems/fog-kubevirt-1.3.4/lib/fog/kubevirt/compute/compute.rb:345:in `create_client'
        from /opt/IBM/infrastructure-management-gemset/gems/fog-kubevirt-1.3.4/lib/fog/kubevirt/compute/compute.rb:435:in `openshift_client'
        from /opt/IBM/infrastructure-management-gemset/gems/fog-kubevirt-1.3.4/lib/fog/kubevirt/compute/compute.rb:288:in `watch_templates'
        from /opt/IBM/infrastructure-management-gemset/bundler/gems/bluecf-providers-kubevirt-45d4b13928e9/app/models/manageiq/providers/kubevirt/infra_manager/connection.rb:108:in `watch_templates'
        from /opt/IBM/infrastructure-management-gemset/bundler/gems/bluecf-providers-kubevirt-45d4b13928e9/app/models/manageiq/providers/kubevirt/infra_manager/refresh_worker/runner.rb:208:in `block in start_watches'
        from /var/www/miq/vmdb/app/models/ext_management_system.rb:524:in `with_provider_connection'
        from /opt/IBM/infrastructure-management-gemset/bundler/gems/bluecf-providers-kubevirt-45d4b13928e9/app/models/manageiq/providers/kubevirt/infra_manager/refresh_worker/runner.rb:204:in `start_watches'
        from /opt/IBM/infrastructure-management-gemset/bundler/gems/bluecf-providers-kubevirt-45d4b13928e9/app/models/manageiq/providers/kubevirt/infra_manager/refresh_worker/runner.rb:56:in `do_before_work_loop'
        from /var/www/miq/vmdb/app/models/miq_worker/runner.rb:108:in `prepare'
        from /var/www/miq/vmdb/app/models/miq_worker/runner.rb:94:in `start'
        from /var/www/miq/vmdb/lib/workers/bin/run_single_worker.rb:113:in `<main>'
/opt/IBM/infrastructure-management-gemset/gems/rest-client-2.0.2/lib/restclient/abstract_response.rb:223:in `exception_with_response': 404 Not Found (RestClient::NotFound)
        from /opt/IBM/infrastructure-management-gemset/gems/rest-client-2.0.2/lib/restclient/abstract_response.rb:103:in `return!'
        from /opt/IBM/infrastructure-management-gemset/gems/rest-client-2.0.2/lib/restclient/request.rb:809:in `process_result'
        from /opt/IBM/infrastructure-management-gemset/gems/rest-client-2.0.2/lib/restclient/request.rb:725:in `block in transmit'
        from /usr/share/ruby/net/http.rb:920:in `start'
        from /opt/IBM/infrastructure-management-gemset/gems/rest-client-2.0.2/lib/restclient/request.rb:715:in `transmit'
        from /opt/IBM/infrastructure-management-gemset/gems/rest-client-2.0.2/lib/restclient/request.rb:145:in `execute'
        from /opt/IBM/infrastructure-management-gemset/gems/rest-client-2.0.2/lib/restclient/request.rb:52:in `execute'
        from /opt/IBM/infrastructure-management-gemset/gems/rest-client-2.0.2/lib/restclient/resource.rb:51:in `get'
        from /opt/IBM/infrastructure-management-gemset/gems/fog-kubevirt-1.3.4/lib/fog/kubevirt/compute/compute.rb:417:in `detect_version'
        from /opt/IBM/infrastructure-management-gemset/gems/fog-kubevirt-1.3.4/lib/fog/kubevirt/compute/compute.rb:360:in `create_client_from_token'
        from /opt/IBM/infrastructure-management-gemset/gems/fog-kubevirt-1.3.4/lib/fog/kubevirt/compute/compute.rb:345:in `create_client'
        from /opt/IBM/infrastructure-management-gemset/gems/fog-kubevirt-1.3.4/lib/fog/kubevirt/compute/compute.rb:435:in `openshift_client'
        from /opt/IBM/infrastructure-management-gemset/gems/fog-kubevirt-1.3.4/lib/fog/kubevirt/compute/compute.rb:288:in `watch_templates'
        from /opt/IBM/infrastructure-management-gemset/bundler/gems/bluecf-providers-kubevirt-45d4b13928e9/app/models/manageiq/providers/kubevirt/infra_manager/connection.rb:108:in `watch_templates'
        from /opt/IBM/infrastructure-management-gemset/bundler/gems/bluecf-providers-kubevirt-45d4b13928e9/app/models/manageiq/providers/kubevirt/infra_manager/refresh_worker/runner.rb:208:in `block in start_watches'
        from /var/www/miq/vmdb/app/models/ext_management_system.rb:524:in `with_provider_connection'
        from /opt/IBM/infrastructure-management-gemset/bundler/gems/bluecf-providers-kubevirt-45d4b13928e9/app/models/manageiq/providers/kubevirt/infra_manager/refresh_worker/runner.rb:204:in `start_watches'
        from /opt/IBM/infrastructure-management-gemset/bundler/gems/bluecf-providers-kubevirt-45d4b13928e9/app/models/manageiq/providers/kubevirt/infra_manager/refresh_worker/runner.rb:56:in `do_before_work_loop'
        from /var/www/miq/vmdb/app/models/miq_worker/runner.rb:108:in `prepare'
        from /var/www/miq/vmdb/app/models/miq_worker/runner.rb:94:in `start'
        from /var/www/miq/vmdb/lib/workers/bin/run_single_worker.rb:113:in `<main>'
{"@timestamp":"2020-09-18T18:20:15.766110 ","hostname":"1-kubevirt-infra-refresh-8-79b58f46d6-jnm7s","pid":7,"tid":"2b101062d964","level":"info","message":"MIQ(AuthToken#validation_successful) [ExtManagementSystem] [5], previously valid/invalid on: [2020-09-18 18:13:19 UTC]/[], previous status: [Valid]"}

Using the management-admin creds does not work either.

OCP version is 4.5.6.

miq-bot commented 1 year ago

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

miq-bot commented 1 year ago

This issue has been automatically closed because it has not been updated for at least 3 months.

Feel free to reopen this issue if this issue is still valid.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.