Re: Upgrade to Cloudstack 4.11.2 fails *AGAIN*

Hi, There is no need to get rid of qemu-ev packages. Just downgrade them to 2.10 and it works fine. On Wed, May 22, 2019 at 10:52 PM Andrija Panic wrote: > > Important to see you happy with 4.11.2 - the rest (HW) will follow ;) > > On Wed, 22 May 2019 at 21:49, Eric Lee Green > wrote: > > > EXC

Apache-Cloudstack 4.11.2.0, Maven Error: java.lang.UnsatisfiedLinkError (com/sun/jna/linux-aarch64/libjnidispatch.so not found)

I'm attempting to build/install Cloudstack 4.11.2.0 on a Pine64 Rock64 running Armbian 5.75 - *This time* Ubuntu-18.04 [Bionic Beaver]... root@rock64:/usr/local/src/apache-cloudstack-4.11.2.0-src# lsb_release -a Distributor ID: Ubuntu Descriptio

Re: Upgrade to Cloudstack 4.11.2 fails *AGAIN*

Important to see you happy with 4.11.2 - the rest (HW) will follow ;) On Wed, 22 May 2019 at 21:49, Eric Lee Green wrote: > EXCELLENT! > > That did it. I downgraded to the libvirt and openssh rpms from Centos > 7.5, which was the latest DVD I had hanging around (likely the one I > used to instal

Re: Upgrade to Cloudstack 4.11.2 fails *AGAIN*

EXCELLENT! That did it. I downgraded to the libvirt and openssh rpms from Centos 7.5, which was the latest DVD I had hanging around (likely the one I used to install the systems with in the first place). Turns out it was the Red Hat updates that came in when I did 'rpm update' that broke thin

Re: questions on cloudstack and VMware hypervisors

Correct Yiping - at the time we initially wrote Trillian a couple of years ago we didn't have all the modules required, but since we could do everything with a CloudMonkey script we simply templated this and triggered a bash script run from Ansible. We could possibly rewrite now with the availab

Re: Upgrade to Cloudstack 4.11.2 fails *AGAIN*

+1 on what Nux said - simply downgrade the packages and check if that works - no need to reinstall everything ! As for the $ from github (CentOS 7.6 issue) - simple new line at the end of id_rsa file and/or downgrading the ssh-keygen will work. Don't want to annoy you, but if the company is so

Re: questions on cloudstack and VMware hypervisors

Hi, Dag: Thanks for the quick reply. Yea, that is it!. The custom attribute "cloud.zone" was set to true for the datacenter in vCenter. Once I delete that attribute, or change its value to "false", I could re-associate the datacenter with new CloudStack zone. If I delete the VMware datacent

Re: Upgrade to Cloudstack 4.11.2 fails *AGAIN*

Eric, I think you can get away with just downgrading to stock qemu-kvm packages (or patch your cloudstack installation). BTW qemu-kvm-ev is not part of stock CentOS for a reason, SIG packages don't get the same level of testing and QA. -- Sent from the Delta quadrant using Borg technology! Nux

Re: Upgrade to Cloudstack 4.11.2 fails *AGAIN*

I don't have spare hardware. I work for a small business, i.e., poor, which is why the hardware is the antiques I listed, it's all basically other company's garbage sourced from eBay. I tested it on a small cluster used by QA to test software deployments on various versions of Windows and Ubunt

Re: Upgrade to Cloudstack 4.11.2 fails *AGAIN*

Eric, did you actually test this in production? Andrija On Wed, 22 May 2019 at 16:33, Eric Lee Green wrote: > Okay. This makes sense. > > And people wonder why Amazon decided to make their own Linux rather than > use Centos and why Ubuntu has seized huge market share from Red Hat in > the past

Re: Upgrade to Cloudstack 4.11.2 fails *AGAIN*

Okay. This makes sense. And people wonder why Amazon decided to make their own Linux rather than use Centos and why Ubuntu has seized huge market share from Red Hat in the past few years. SIGH. Downgrading my CentOS is not going to be easy. There were security patches in the latest CentOS th

Re: Upgrade to Cloudstack 4.11.2 fails *AGAIN*

While the VR does not use cloud-init (afaik!), it's worth mentioning that in recent tests with CentOS 7 VMs and cloud-init there were problems when using too low RAM offerings. In my particular case 512MB turned out to not be enough for cloud-init to execute properly, upgrading the offering "fix

Re: Upgrade to Cloudstack 4.11.2 fails *AGAIN*

Hi Eric, Based on your shared version details, the specific issue and why it does not work for you has to do with usage of qemu-ev 2.12, which was only recently supported: https://github.com/apache/cloudstack/pull/3278 The issue has to do with how systemvms are patched by cloudstack-agent us

Re: questions on cloudstack and VMware hypervisors

Hi Yiping, See https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-EC0F7308-96AE-4089-9DD4-B42AF50AABDC.html You should find a custom attribute to your virtual DC called something like "cloud.zone" which I believe you have to wipe before you can re-add it to a

Re: Upgrade to Cloudstack 4.11.2 fails *AGAIN*

Hi Eric, all, I believe you might be hitting this one - issues on latest CentOS 7.6: https://github.com/apache/cloudstack/pull/ due to changes in the OS itself... If you believe that is the case, please try with CentOS 7.4 (can confirm works fine) and/or CentOS 7.5. Best, Andrija On Wed,

Re: Upgrade to Cloudstack 4.11.2 fails *AGAIN*

On 5/21/2019 11:10 PM, Thomas Joseph wrote: Hello Eric, If the router version is displayed as UNKNOWN in the portal, it would be a connectivity issue. Check your connections related to firewall rules between the ACP management hosts, hypervisor and VR. Is your VR management network setup