Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stacks stop updating with GitOps polling if their author is deleted #11015

Open
2 tasks done
wpf500 opened this issue Jan 25, 2024 · 2 comments
Open
2 tasks done

Stacks stop updating with GitOps polling if their author is deleted #11015

wpf500 opened this issue Jan 25, 2024 · 2 comments
Assignees

Comments

@wpf500
Copy link

wpf500 commented Jan 25, 2024

Before you start please confirm the following.

Problem Description

My stacks are no longer automatically updating since I deleted the user who created them. It is still possible to update them manually. They are configured to update using the GitOps polling mechanism.

Expected Behavior

Stacks continue to update automatically

Actual Behavior

Stacks don't update and there are errors in the logs.

Steps to Reproduce

  1. Create a stack, enable GitOps
  2. Delete the user who created the stack
  3. Trigger an update
  4. The update won't happen

Portainer logs or screenshots

2024/01/25 11:59AM WRN github.com/portainer/portainer/api/stacks/deployments/deploy.go:68 > cannot auto update a stack, stack author user is missing | author=myauthorname endpoint_id=2 stack=mystackname stack_id=24
2024/01/25 11:59AM ERR github.com/portainer/portainer/api/scheduler/scheduler.go:113 > job returned an error, it will be rescheduled | error="stack's 24 author myauthorname is missing"

Portainer version

2.19.4

Portainer Edition

Community Edition (CE)

Platform and Version

Docker version 24.0.6, build ed223bc

OS and Architecture

Linux host-1 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux

Browser

n/a

What command did you use to deploy Portainer?

version: '3.8'

services:
  portainer:
    image: portainer/portainer-ce:latest
    restart: always
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - portainer_data:/data:rw
    environment:
      - TZ=Europe/Berlin
    labels:
      - traefik.enable=true
      - traefik.docker.network=traefik-ingress
      - traefik.http.routers.portainer.rule=Host(`xxx`)
      - traefik.http.routers.portainer.entrypoints=https
      - traefik.http.routers.portainer.tls=true
      - traefik.http.services.portainer.loadbalancer.server.port=9000
      - traefik.http.routers.portainer.tls.certresolver=letsencrypt
      - traefik.http.routers.portainer.middlewares=secHeaders@file
    networks:
      - traefik-ingress

volumes:
  portainer_data:

networks:
  traefik-ingress:
    external: true

Additional Information

No response

@jamescarppe jamescarppe self-assigned this Jan 30, 2024
@jamescarppe
Copy link
Member

Thanks for flagging this, I've been able to reproduce this here.

Internal Ref: PCT-339

@cn-ml
Copy link

cn-ml commented Nov 20, 2024

This just happened to me too, i migrated some user accounts from internal authentication to OIDC and all my stacks have owners that do not exist anymore. I cannot use any of the webhooks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants