VC-7.0u2c breaks network config

[loungehostmaste]

are you kidding me?

after apply the update and restart the application it got a danymic ip and hostname
never seen something trivial like a static ip messed up in 20 years with Linux
especially not in a virtual machine

[root@z-dynamic-238:~]$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0c:29:6d:de:a1
         inet addr:10.0.0.238  Bcast:10.0.0.255  Mask:255.255.255.0
         inet6 addr: fe80::20c:29ff:fe6d:dea1/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:956 errors:0 dropped:0 overruns:0 frame:0
         TX packets:479 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:99118 (99.1 KB)  TX bytes:42809 (42.8 KB)

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:65536  Metric:1
         RX packets:20242 errors:0 dropped:0 overruns:0 frame:0
         TX packets:20242 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:23160430 (23.1 MB)  TX bytes:23160430 (23.1 MB)

[root@z-dynamic-238:~]$ hostname
z-dynamic-238.thelounge.net

[loungehostmaste]

ok, now i really get tired of Vmware

i cloned the vcenter yesterday to a NFS storage and edited the MAC in the VMX file to be the same as on the live
that was my last-resort strategy to have always a bootable vcenter whatever happens
now i can't power on the VM directly in ESXi

https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.troubleshooting.doc/GUID-7F723748-E...

[loungehostmaste]

ok and the proposed dynamic URL for the webinterface to probably restore the last daily vcenter config over sftp says "no healthy upstream" - i wish Proxmox would have existed in 2008

[loungehostmaste]

you need to deploy a new appliance to restore a config backup of the vCenter appliance?
what a kindergarten

[loungehostmaste]

this also shows the incompetence of VMware like tons of other errors you face after reboot vCenter when you look in the logs - maybe the guys developing this *bad word* should look there too *before* throwing software at paying customers

2021-08-30T12:00:01.446635+00:00 vcenter logrotate: error: destination /var/log/vmware/procstate-20210830.gz already exists, skipping rotation
2021-08-30T14:00:01.722128+00:00 vcenter logrotate: error: destination /var/log/vmware/procstate-20210830.gz already exists, skipping rotation
2021-08-30T16:00:01.389319+00:00 vcenter logrotate: error: destination /var/log/vmware/procstate-20210830.gz already exists, skipping rotation
2021-08-30T18:00:01.155598+00:00 vcenter logrotate: error: destination /var/log/vmware/procstate-20210830.gz already exists, skipping rotation
2021-08-30T20:00:01.795632+00:00 vcenter logrotate: error: destination /var/log/vmware/procstate-20210830.gz already exists, skipping rotation
2021-08-30T22:00:01.628898+00:00 vcenter logrotate: error: destination /var/log/vmware/procstate-20210830.gz already exists, skipping rotation
2021-08-31T01:00:01.710804+00:00 vcenter logrotate: error: destination /var/log/vmware/procstate-20210831.gz already exists, skipping rotation
2021-08-31T02:00:01.436213+00:00 vcenter logrotate: error: destination /var/log/vmware/procstate-20210831.gz already exists, skipping rotation
2021-08-31T04:00:01.118140+00:00 vcenter logrotate: error: destination /var/log/vmware/procstate-20210831.gz already exists, skipping rotation