Hi Rohit, Thank you for the assistance. I did find that the cache clear fixed my NFS settings view.
In regards to the management servers, my management servers don’t seem to meet the criteria in which you mentioned require manual deletion from the database tables. For example, the UI already sees the management servers as “Down”. That being said, I can attempt that and keep that as a fix should I run across this in future upgrade. * Alex [__tpx__] From: Rohit Yadav <[email protected]> Date: Tuesday, July 23, 2024 at 4:52 AM To: [email protected] <[email protected]> Subject: Re: Management Server issues post 4.19.1.0 upgrade EXTERNAL Hi Alex, On the translation - post an upgrade, some of the UI assets such as translations (a static json file) may be cached in your browser. You do a force reload (like Ctrl+Shift+R, or Cmd+Shift+R) or close/reopen browser and reload the UI. This is usually a browser issue. On duplicate or older mgmt server records (under the UI or API), currently there's no API to purge them. This happens when older mgmt server change IPs, or NIC/mac-address or have multiple nics/mac address. You may manually mark old mgmt server as 'Down' and removed=now() via MySQL client on the cloud.mshost table. Regards. ________________________________ From: Ruben Bosch <[email protected]> Sent: Tuesday, July 23, 2024 13:06 Cc: users <[email protected]> Subject: Re: Management Server issues post 4.19.1.0 upgrade Hi Alex, Clear your browser cache and cookies and report back if something's still amiss. On Mon, Jul 22, 2024 at 9:19 PM Alex Dietrich <[email protected]> wrote: > Hello All, > > After upgrading to 4.19.1.0, I noticed a few issues that came out of the > upgrade: > > > * For one of my two management servers, the NFS mount options is not > displaying correctly. It is instead displaying label.nfsmountopts. > * On both management servers, there are a duplicate set of management > servers that appear in the Infrastructure > Management Servers screen. One > set shows 4.19.0.1 (prior version), the other has the current version. The > current version management servers are considered Up in this pane. > > The upgrades were performed using the deb packages from CloudStack via apt. > > I haven’t delved too much deeper for other issues, but I am wondering if > something got hosed on the upgrade for one of my management servers. What > would be the recommended course of action to attempt to repair? > > > * Alex > >
