You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2021/02/02 08:04:47 UTC

[GitHub] [cloudstack] slavkap commented on pull request #4631: fix: create template with Marvin

slavkap commented on pull request #4631:
URL: https://github.com/apache/cloudstack/pull/4631#issuecomment-771447883


   Hi @DaanHoogland 
   I have checked the logs but nowhere is used the change. Unfortunately  don't have access to Xen or VMware to debug it further 
   
   for Xen it fails because of this:
   
   test_01_scale_vm
   > com.cloud.utils.exception.CloudRuntimeException: Unable to scale vm due to Catch exception com.xensource.xenapi.Types$LicenceRestriction when scaling VM:i-167-193-VM due to This operation is not allowed under your license.  Please contact your support representative.
   
   for VMware:
   
   test_03_deploy_and_upgrade_kubernetes_cluster
   
   > 2021-02-01 12:26:30,643 INFO  [c.c.h.v.m.VirtualMachineMO] (VM-Question-Monitor-4:null) (logid:b9341113) Found that VM has a pending question that we need to answer programmatically, question id: msg.cdromdisconnect.locked, for safe operation we will automatically decline it
   2021-02-01 12:26:30,837 INFO  [c.c.h.v.u.VmwareHelper] (DirectAgent-1:ctx-ea9a902a 10.10.4.160, job-695, cmd: DettachCommand) (logid:b9341113) [ignored]failed to get message for exception: Connection control operation failed for disk 'ide0:0'.
   2021-02-01 12:26:30,837 WARN  [c.c.s.r.VmwareStorageProcessor] (DirectAgent-1:ctx-ea9a902a 10.10.4.160, job-695, cmd: DettachCommand) (logid:b9341113) AttachIsoCommand(detach) failed due to Exception: java.lang.RuntimeException
   Message: Connection control operation failed for disk 'ide0:0'.
    Also check if your guest os is a supported version
   java.lang.RuntimeException: Connection control operation failed for disk 'ide0:0'.
   
   > [upgrade/apply] FATAL: fatal error when trying to upgrade the etcd cluster, rolled the state back to pre-upgrade state: couldn't upgrade control plane. kubeadm has tried to recover everything into the earlier state. Errors faced: timed out waiting for the condition
   To see the stack trace of this error execute with --v=5 or higher
   [upgrade/config] FATAL: failed to get config map: Get https://10.1.1.163:6443/api/v1/namespaces/kube-system/configmaps/kubeadm-config: dial tcp 10.1.1.163:6443: connect: connection refused
   To see the stack trace of this error execute with --v=5 or higher
   
   test_04_change_offering_small and test_change_service_offering_for_vm_with_snapshots have failed with the same error:
   
   > VM current state is : PowerOn. But VM should be in PowerOff state
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org