Ability to upgrade stopped stack for catalog

[deniseschannon]

v0.44.0

Steps to Reproduce:

1. Create an older version of a catalog entry.
2. Click on upgrade button in UI

Result: Unable to upgrade the services.

[alena1108]

We should also support upgrade for stack having mix of active/inactive services

[deniseschannon]

Some better steps written by @tfiduccia

Steps;

1. Add Elasticsearch Stack with older version of rancher
2. Click on upgrade before you start any services
3. Try to finish upgrade

Results:
It gets stuck trying to upgrade.

Expected:
Should not get stuck.

[alena1108]

@sangeethah you can test this fix using the UI only. Could you file a separate bug to enable rancher-compose support?

[sangeethah]

Tested with build from master - dec 3

1. Add Elasticsearch Stack with older version of rancher. Choose not to start the service.
2. Click on upgrade before you start any services

kpof service tries to get upgraded but gets stuck in "activating" state since the containers get constantly restarted . All other services in the stack continue to remain in "Inactive" state.

Following exception seen in kpof container logs:

12/3/2015 7:29:51 PM2015/12/04 03:29:51 [emerg] 1#1: host not found in upstream "es-clients:9200" in /etc/nginx/nginx.conf:25
12/3/2015 7:29:51 PMnginx: [emerg] host not found in upstream "es-clients:9200" in /etc/nginx/nginx.conf:25
12/3/2015 7:30:19 PM2015/12/04 03:30:19 [emerg] 1#1: host not found in upstream "es-clients:9200" in /etc/nginx/nginx.conf:25
12/3/2015 7:30:19 PMnginx: [emerg] host not found in upstream "es-clients:9200" in /etc/nginx/nginx.conf:25

[asciifaceman]

Would it be related if I am unable to stop a "Finish upgrade" when there is a port conflict that can only be stopped by deleting the service in the stack

[deniseschannon]

@asciifaceman What state is your service in? Is it still trying to Uprgrade? This issue is specifically about having inactive stack and trying to upgrade the stack.

[asciifaceman]

Ah, it's not a match then. My situation was clicking "Finish upgrade" on an
active service with a port conflict puts it in an infinite loop that can
only be stopped by deleting it entirely.

On Tue, Mar 22, 2016 at 3:38 PM, Denise notifications@github.com wrote:

@asciifaceman https://github.com/asciifaceman What state is your
service in? Is it still trying to Uprgrade? This issue is specifically
about having inactive stack and trying to upgrade the stack.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#2650 (comment)

Charles P. Corbett

[ibuildthecloud]

Tested on 1.0.0-rc5 and can't reproduce.

[deniseschannon]

Verified with v1.0.0-rc6.