Some of the new things to expect.
- Tightened up the look and feel
- New Application Manager
- Numerous updates and minor fixes
How this should work is each location must have 1 and only 1 caching agent. If you select an agent and then select to set as caching agent it will take ownership on that role relieving the previous agent of that roll.dbitters wrote: ↑Tue Oct 12, 2021 3:48 am The new version looks great, and I like the new name. I have a small suggestion initially.
In the applications manager UI at the customer level, can you either change the "Set as caching agent" to an enable/disable, or can you add a disable button below the set? I only say this because the interface wasn't behaving as expected with the right-click menu, and when I was setting the caching agent on a server, it actually set it on a workstation, a few below it causing two systems to show the icon of caching agent. Maybe there is a disable button to remove it from the incorrect system, but having it around the same place would be helpful to fix any missteps such as that. Much appreciated. The following day, I checked, and the incorrect system no longer showed as having the duplicate caching agent icon. Maybe your script detects the most recent selection and removes the prior selection after the next maintenance run.
I have a suggestion for an unrelated topic on the Habitat Powershell client console. The Dot.NET Versions tab, doesn't sort the Systems list as the other two tabs do. I don't suppose that can be auto sorted so it's not like trying to find a needle in a haystack on larger customers . Much appreciated.
This would make since if your not able to reach local cache. The Caching agent is getting repo data but either can not access the cache location or the agents trying to get cache can not access cache.We are still getting this log statement on each of our systems when the Application Manager Service runs:
"The agents location does not have a configured "Location Drive" or credentials to access drive, exiting script without agent changes."
Do you have any suggestions for this? I set the agent caching agent last week, and I still get this.
I should also note that also even after a week, the Installed Version column has been blank on all of our systems. The repo version collum is populating though. I know it's a work in progress, but in case it helps, I wanted to provide that info as well.