portainer: Portainer-CE 2.0 is missing Stacks

Bug description After upgrade to CE 2.0.0, Portainer is no longer displaying all existing stacks. Also counts of Stacks are displayed incorrectly in multiple places. - however that’s repro with 1.24.1 too.

Expected behavior All stacks should be listed properly.

Steps to reproduce the issue: Our setup:

  • Swarm with 1 manager and 1 worker
  • 5 stacks with active services (incl Portainer stack)
  • 2 stacks without services (placeholders created in Portainer but with services deleted)

Steps:

  1. Have Portainer 1.24.1 on Docker Swarm with the aforementioned stack setup.
  2. Upgrade to Portainer-CE 2.0.0
  3. Log in and observe Home page - “primary” endpoint is listing 5 stacks: portainer-home
  4. Select the primary endpoint and observe the Dashboard - 7 stacks: portainer-dash
  5. Select Stacks list - only 2 stacks are shown (Portainer stack and one of the empty placeholders): Portainer-200-stacks
  6. Downgrade to Portainer 1.24.1 and go to Stacks - all 7 are visible now: Portainer-1241-stacks

Technical details:

  • Portainer version:
  • Docker version (managed by Portainer): 19.03.13
  • Platform (windows/linux): Linux, CentOS 7
  • Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): docker stack deploy -c portainer-agent-stack.yml portainer
  • 2 Compose stacks (for 1.24.1 and 2.0.0): portainer-compose.zip
  • Browser: Firefox

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 2
  • Comments: 35 (11 by maintainers)

Most upvoted comments

Hi Jean,

Can you try to start the missing stack using API on the docker host using httpie http POST :9000/api/auth Username="admin" Password="<admin password"

Copy the token http GET :9000/api/stacks "Authorization: Bearer <JWT Token>"

Copy the ID of the missing stack http POST :9000/api/stacks/<stack id>/start "Authorization: Bearer <JWT Token>"

This should set the Status of the stack to 1 and should show up in the GUI.

Let me know how you get on.

Ah I thought these were Swarm stacks as I was looking at the bug report context, sorry about that.