Yiping,
if you are sure you can reproduce the issue, it would be good to raise a
GitHub issue and provide as much detail as possible.
Andrija
On Wed, 5 Jun 2019 at 05:29, Yiping Zhang
wrote:
> Hi, Sergey:
>
> Thanks for the tip. After setting vmware.create.full.clone=false, I was
> able to cr
Hello,
I am having an issue on a new test system, cloudstack version 4.11.00
(shapeblue) with KVM (Ubuntu 16.04), In production and in the past I have used
these settings in the agent.properties
guest.cpu.model=SandyBridge
guest.cpu.mode=custom
As this was needed to allow windows 2016 to boot
It might be because I'm using a Westmere CPU?
Doh
Adam
-Original Message-
From: Adam Witwicki
Sent: 05 June 2019 13:08
To: [email protected]
Subject: CPU compatibility issue
** This mail originated from OUTSIDE the Oakford corporate network. Treat
hyperlinks and attachments
All,
The 4.11.3.0 milestone (https://github.com/apache/cloudstack/milestone/7),
currently only has one outstanding PR.
You may go through the list of open issues and pull requests and share any
blocker or critical bug that should be fixed towards 4.11.3.0. The list of
already closed pull req
Well, I can always reproduce it in this particular vSphere set up, but in a
different ACS+vSphere environment, I don't see this problem.
Yiping
On 6/5/19, 1:00 AM, "Andrija Panic" wrote:
Yiping,
if you are sure you can reproduce the issue, it would be good to raise a
GitHu
All,
Bases on some conversation on a Github issue on moving to Python3 today, I
would like to propose a PR after 4.13 is cut on deprecation of following
hypervisors in the next major 4.14 release:
- XenServer 6.2, 6.5 and older
- VMware 5.x
- KVM/CentOS6/RHEL6 (though we've already voted and ag
OVM ?
On Wed, Jun 5, 2019, 19:56 Rohit Yadav wrote:
> All,
>
> Bases on some conversation on a Github issue on moving to Python3 today, I
> would like to propose a PR after 4.13 is cut on deprecation of following
> hypervisors in the next major 4.14 release:
>
> - XenServer 6.2, 6.5 and older
>
This must be specific to that environment. For a full clone mode ACS simply
calls cloneVMTask of vSphere API so basically until cloning of that template
succeeds when attmepted in vSphere client it would keep failing in ACS. Can
you post vmkernel.log from your ESX host esx-0001-a-001?
On 6/
Hi, Sergey:
During the time period when I had problem cloning template, there are only a
few unique entries in vmkernel.log, and they were repeated hundreds/thousands
of times by all the cpu cores:
2019-06-02T16:47:00.633Z cpu9:8491061)FSS: 6751: Failed to open file
'hpilo-d0ccb15'; Requested
How do I remove abandined templates?
While trying to clean up after couple failed attempts of importing a vm
template status is "UploadAbandoned"
When I try to delete file I get an error , "Failed to delete template"
Looking at management.log
2019-06-05 14:43:17,508 WARN [c.c.t.HypervisorTemplate
Some operations log get transferred to vCenter log vpxd.log. It is not
straightforward to trace I but Vmware will be able to help should you open case
with them.
On 6/5/19, 11:39 AM, "Yiping Zhang" wrote:
Hi, Sergey:
During the time period when I had problem cloning template,
Hi Jesse,
As the upload was abandoned, it has never started, so the workaround will be
just deleting the entry from CloudStack as there will be no files on secondary
storage. To do this, please first execute this query on database:
update template_store_ref set destroyed = 1 where template_id =
Hi, Sergey:
I found more logs in vpxa.log ( the esxi hosts are using UTC time zone, so I
was looking at wrong time periods earlier). I have uploaded more logs into
pastebin.
From these log entries, it appears that when copying template to VM, it tried
to open destination VMDK file and got
Hi Adam,
This PR seems to fix your issue: https://github.com/apache/cloudstack/pull/3335
and it has been merged into master but not on 4.11.x, which means it will be
available on the next 4.13 release.
Regards,
Nicolas Vazquez
From: Adam Witwicki
Sent: Wednesda
Hi Haijiao,
We cannot accept or back port completely new features on 4.11 branch, we should
ideally only accept bugfixes but sometimes small infra/operational enhancements
do make it in minor releases.
Once 4.11.3.0 is out, we will work towards 4.13.0.0 and users can get all new
features with
Hi Yiping,
do you have snapshots enabled on the NetApp filer? (it used to be seen as a
".snapshot" subdirectory in each directory)
If so try disabling snapshots - there used to be a bug where the .snapshot
directory would confuse CloudStack.
[email protected]
www.shapeblue.com
Amade
16 matches
Mail list logo
