PiotrBerent's Posts

So, we have this marvelous 6-node vSAN stretched cluster, elegantly divided into 2 availability zones - each zone flaunts 3 ESXi hosts with the exact same exquisite hardware configuration. Our humble... See more...
So, we have this marvelous 6-node vSAN stretched cluster, elegantly divided into 2 availability zones - each zone flaunts 3 ESXi hosts with the exact same exquisite hardware configuration. Our humble desire was to extend this masterpiece by adding just 1 host to each of these breathtaking availability zones. With enthusiasm, we attempted both methods: via an API call garnished with a JSON payload, and through the ever-charming GUI. Lo and behold, from the JSON payload, we were graced with an error: "VDS(s) specified in the input spec ([w01-cl01-vds02]) and in the existing cluster ([w01-cl01-vds02, w01-cl01-vds01]) do not match." How intriguing! And, as if the universe had a sense of humor, in the SDDC GUI, the option to add a host to the cluster was greyed out, accompanied by this delightful comment: "Add Host feature is disabled for Stretched Clusters." Ah, the irony! Oh, how could I forget to mention that the hosts we so dearly wished to add are, in fact, blessed with the exact same hardware specifications as the already existing nodes? Indeed, this divine harmony of hardware was meant to ensure a seamless expansion of our glorious vSAN stretched cluster. And yet, despite our meticulous planning and the uniformity of our hardware, we were faced with these perplexing obstacles, both in the JSON payload and the SDDC GUI. It seems that our quest to expand this magnificent creation has been met with an ironic twist of fate. So, with great sarcasm and a heavy heart, we must ask again: Is this a bug, or is it a feature?
I can only say that the issue still exist on 7.0.3i - build 20842708. When I'm trying to migrate out VM that have 10TB disks (with thin provisioning and with policy for vSAN that "utilize" 4x spac... See more...
I can only say that the issue still exist on 7.0.3i - build 20842708. When I'm trying to migrate out VM that have 10TB disks (with thin provisioning and with policy for vSAN that "utilize" 4x space - site mirroring stretched cluster + FTT 1 - RAID-1 (Mirroring)), so if on the VM on all disk total used space is 5TB - on vSAN it reflect to 20TB used space - because of that policy).  So now when I'm trying to move that VM to LUN on SAN datastore with 15TB capacity - migration will not even start since it shows that 15TB is less than required, and it need to be 20TB+ LUN on SAN. However, after migration - VM will utilize 5TB (while keeping thin provisioning). So - is there any other solution to avoid that problem than change VM policy to not redundancy at all? 
Yes, In fact it turns that only 3 packets were missing: audit, bash and bindutils But the copying procedure require just a PERFECT timing.
I need to dig that post out. How to set with powercli this toogle switch from GUI "Configure per disk" - since setting both (for VM Home, and Disks) is ok, but newly added disk will not have this ... See more...
I need to dig that post out. How to set with powercli this toogle switch from GUI "Configure per disk" - since setting both (for VM Home, and Disks) is ok, but newly added disk will not have this policy.
Yup, I've already tried that. My situation is described here (kb adviced by VMWare Support): https://kb.vmware.com/s/article/89606 It is a step in right direction however… I’ve copied first ... See more...
Yup, I've already tried that. My situation is described here (kb adviced by VMWare Support): https://kb.vmware.com/s/article/89606 It is a step in right direction however… I’ve copied first package which was missing: Stat file, file missing. filename=/opt/vmware/var/lib/vami/update/data/package-pool/package-pool/audit-2.8.5-19.ph3.x86_64.rpm   So i’ve revert snapshot, copied file to location from KB article, but next run was failed with another missing file: Stat file, file missing. filename=/opt/vmware/var/lib/vami/update/data/package-pool/package-pool/bash-4.4.18-3.ph3.x86_64.rpm   So, I’ve just check how mnay files are on cd, and how many are in /opt…. Update folder, but here it seems all files are there – and they are, I’ve checked root@vrslcm [ ~ ]# ls /opt/vmware/var/lib/vami/update/data/package-pool/package-pool/ | wc -l 56 But I did check if the file is really missing, and it is not, file is there. root@vrslcm [ ~ ]# ls -al /opt/vmware/var/lib/vami/update/data/package-pool/package-pool/bash-4.4.18-3.ph3.x86_64.rpm -r-------- 1 root root 1038794 Oct 23 22:04 /opt/vmware/var/lib/vami/update/data/package-pool/package-pool/bash-4.4.18-3.ph3.x86_64.rpm But I didn’t give up yet, and I was able to copy  those two packages (audit, and bash), and.. it turns out, that it doesnt help at all, since surpisingly, there was another missing package: 23/10/2022 22:34:14 [INFO] Using update pre-install script 23/10/2022 22:34:14 [DEBUG] Writing to file: pre_install 23/10/2022 22:34:14 [DEBUG] Running CheckPackageSet 23/10/2022 22:34:14 [DEBUG] Stat file, file exists. filename=/opt/vmware/var/lib/vami/update/data/package-pool/package-pool/audit-2.8.5-19.ph3.x86_64.rpm 23/10/2022 22:34:14 [DEBUG] Stat file, file exists. filename=/opt/vmware/var/lib/vami/update/data/package-pool/package-pool/bash-4.4.18-3.ph3.x86_64.rpm 23/10/2022 22:34:14 [DEBUG] Stat file, file missing. filename=/opt/vmware/var/lib/vami/update/data/package-pool/package-pool/bindutils-9.16.33-1.ph3.x86_64.rpm 23/10/2022 22:34:14 [DEBUG] Download Cache Miss: /package-pool/bindutils-9.16.33-1.ph3.x86_64.rpm 23/10/2022 22:34:14 [ERROR] Unable to install updates because package files are missing. It is a bit of madness here since earlier in the log I can find following: 23/10/2022 22:34:08 [DEBUG] Downloading file. name=audit 23/10/2022 22:34:08 [DEBUG] Opening local file named: /tmp/update_agent_cdrom_ZlJ788/update/package-pool/audit-2.8.5-19.ph3.x86_64.rpm 23/10/2022 22:34:08 [DEBUG] DownloadPackage success 23/10/2022 22:34:08 [DEBUG] Import file. [location,name]:  [/opt/vmware/var/lib/vami/update/data,/package-pool/package-pool/audit-2.8.5-19.ph3.x86_64.rpm] 23/10/2022 22:34:08 [DEBUG] Import successful. filename=/opt/vmware/var/lib/vami/update/data/package-pool/package-pool/audit-2.8.5-19.ph3.x86_64.rpm 23/10/2022 22:34:08 [INFO] Updating package audit status in /opt/vmware/var/lib/vami/update/data/update_progress.json 23/10/2022 22:34:08 [INFO] Downloaded file. url=/package-pool/audit-2.8.5-19.ph3.x86_64.rpm 23/10/2022 22:34:08 [DEBUG] Downloading file. name=bash 23/10/2022 22:34:08 [DEBUG] Opening local file named: /tmp/update_agent_cdrom_ZlJ788/update/package-pool/bash-4.4.18-3.ph3.x86_64.rpm 23/10/2022 22:34:08 [DEBUG] DownloadPackage success 23/10/2022 22:34:08 [DEBUG] Import file. [location,name]:  [/opt/vmware/var/lib/vami/update/data,/package-pool/package-pool/bash-4.4.18-3.ph3.x86_64.rpm] 23/10/2022 22:34:08 [DEBUG] Import successful. filename=/opt/vmware/var/lib/vami/update/data/package-pool/package-pool/bash-4.4.18-3.ph3.x86_64.rpm 23/10/2022 22:34:08 [INFO] Updating package bash status in /opt/vmware/var/lib/vami/update/data/update_progress.json 23/10/2022 22:34:08 [INFO] Downloaded file. url=/package-pool/bash-4.4.18-3.ph3.x86_64.rpm 23/10/2022 22:34:08 [DEBUG] Downloading file. name=bindutils 23/10/2022 22:34:08 [DEBUG] Opening local file named: /tmp/update_agent_cdrom_ZlJ788/update/package-pool/bindutils-9.16.33-1.ph3.x86_64.rpm 23/10/2022 22:34:08 [DEBUG] DownloadPackage success 23/10/2022 22:34:08 [DEBUG] Import file. [location,name]:  [/opt/vmware/var/lib/vami/update/data,/package-pool/package-pool/bindutils-9.16.33-1.ph3.x86_64.rpm] 23/10/2022 22:34:08 [DEBUG] Import successful. filename=/opt/vmware/var/lib/vami/update/data/package-pool/package-pool/bindutils-9.16.33-1.ph3.x86_64.rpm 23/10/2022 22:34:08 [INFO] Updating package bindutils status in /opt/vmware/var/lib/vami/update/data/update_progress.json 23/10/2022 22:34:08 [INFO] Downloaded file. url=/package-pool/bindutils-9.16.33-1.ph3.x86_64.rpm   Anyway – I’ve tried to copy all packages (marked in log file – total 56 packages) to copy at once – but seems that it require just a perfect timing since during copy all files at once I’ve ended up with following error:   23/10/2022 23:16:23 [DEBUG] Import file. [location,name]:  [/opt/vmware/var/lib/vami/update/data,/package-pool/package-pool/linux-4.19.256-2.ph3.x86_64.rpm] 23/10/2022 23:16:23 [ERROR] Exception while saving file /opt/vmware/var/lib/vami/update/data/package-pool/package-pool/linux-4.19.256-2.ph3.x86_64.rpm: boost::filesystem::copy_file: File exists: "/tmp/vmware_update_download_ANfMqY", "/opt/vmware/var/lib/vami/update/data/package-pool/package-pool/linux-4.19.256-2.ph3.x86_64.rpm" 23/10/2022 23:16:23 [ERROR] Failed to import file. filename=/opt/vmware/var/lib/vami/update/data/package-pool/package-pool/linux-4.19.256-2.ph3.x86_64.rpm 23/10/2022 23:16:23 [ERROR] Failed to write file. url=/package-pool/linux-4.19.256-2.ph3.x86_64.rpm And here I’ve just give up. So, what is wrong there? Since for me it looks like the update script is poorly writen, or it has some bugs and errors. Is there any command line tool to force that update? From the logs it looks like i have 2 seconds to fit in and copy all missing packages, which is just crazy. There is no way to copy all those packeges BEFORE upgrade process will start – because it thorws an error also.
Hello, I'm in process of upgradeing VCF up to 4.5 from 4.4.1.1 - besides plenty of issues with NSX update and vCenter as well, now I'm stuck with updating lifecycle manager from 8.8.2.3 up to 8.10. I... See more...
Hello, I'm in process of upgradeing VCF up to 4.5 from 4.4.1.1 - besides plenty of issues with NSX update and vCenter as well, now I'm stuck with updating lifecycle manager from 8.8.2.3 up to 8.10. It just stuck at installation stage, just throwing every 4 seconds to the logs following info: 2022-10-21 16:37:27.391 INFO [http-nio-8080-exec-1] c.v.v.l.u.ShellExecutor - -- Executing shell command: /opt/vmware/bin/vamicli update --progress --detail 2022-10-21 16:37:27.391 INFO [http-nio-8080-exec-1] c.v.v.l.u.ProcessUtil - -- Execute /opt/vmware/bin/vamicli 2022-10-21 16:37:27.423 INFO [http-nio-8080-exec-1] c.v.v.l.u.ShellExecutor - -- Result: [56 packages have been downloaded. Installing...]. 2022-10-21 16:37:31.394 INFO [http-nio-8080-exec-9] c.v.v.l.u.ShellExecutor - -- Executing shell command: /opt/vmware/bin/vamicli update --progress --detail 2022-10-21 16:37:31.395 INFO [http-nio-8080-exec-9] c.v.v.l.u.ProcessUtil - -- Execute /opt/vmware/bin/vamicli 2022-10-21 16:37:31.427 INFO [http-nio-8080-exec-9] c.v.v.l.u.ShellExecutor - -- Result: [56 packages have been downloaded. Installing...]. I've raised ticket to support, but I need to wait until Monday. I've already tried the trick with removing /etc/upgradeprogress file, restarted installation and stuck (now it is stuck for arround 8 hours) exactly at the same stage.
Hello all, We have similiar issue as described here: https://communities.vmware.com/t5/VMware-vCenter-Discussions/Port-902-not-listening-on-TCP/m-p/1380610 We have 9 nodes cluster - with on... See more...
Hello all, We have similiar issue as described here: https://communities.vmware.com/t5/VMware-vCenter-Discussions/Port-902-not-listening-on-TCP/m-p/1380610 We have 9 nodes cluster - with one node added recently - and on that node when commvault trying to reach VMs located on that new node, we're getting error: Error opening the virtual machine disks. Verify that the correct transport mode is selected. Access node [commvault01] is unable to communicate with port 902 on host [esxi09] for nbd access But, on that node - 902 port is open, since we're able to get access via telnet from plenty of other places. The only thing is Commvault servers - can't do it, while they are able to connect on port 902 other hosts from that vmware cluster.