Possible Bug: Environment did not prompt to upgrade

Automated deployment for web applications and databases

Possible Bug: Environment did not prompt to upgrade

Postby lee5i3 » Tue Jul 23, 2013 10:59 pm

I just got a warning that my version of Deployment Manager can be upgraded.

So I upgraded to newest version, and it installed successfully.
So I went to upgrade my environments and it did not say it can be upgraded, tried refreshing page, leaving back and coming back. It still didn't ask to upgrade the environment.

However, after doing a health check did it ask to upgrade, not sure if this is because it doesn't know the version on the environments until you do a health check.
Posts: 38
Joined: Fri Jul 16, 2010 8:26 pm

Postby Mike Upton » Wed Jul 24, 2013 10:25 am


You've guessed right; the Deployment Manager server checks the version of the agents when it does a health check, so won't notice that they need an upgrade until the health check is run. However, DM does run an automatic health check every 30 minutes, so would have noticed within half an hour of the upgrade.

We keep the server->agent protocol compatible across versions, so it doesn't normally matter if the agent is out of date. The only time it might be important is when we add a new feature on the agent side of things, in which case the feature won't be available until the agents are upgraded.
Mike Upton

Technical Lead - SQL Source Control | DLM Automation
Mike Upton
Posts: 222
Joined: Wed May 11, 2011 7:04 am
Location: Redgate

Return to Deployment Manager

Who is online

Users browsing this forum: No registered users and 0 guests