portainer: SWARM: Can not edit any service after deployment .> Showstopper
Before you start please confirm the following.
- Yes, I’ve searched similar issues on GitHub.
- Yes, I’ve checked whether this issue is covered in the Portainer documentation or knowledge base.
Problem Description
I am running a Docker Swarm on 5 nodes of Oracle Linux 8.
Using Portainer EE 2.19.2 everytime i try to edit a parameter of one of my services i see a popup in the right upper corner telling me:
invalid CredentialSpec: must either provide "file", "registry", or "config" for credential spec
So defacto i can not edit my services from Portainer any more.
Expected Behavior
Let me please edit my services again.
Actual Behavior
Can not alter a parameter of a running service on my Docker Swarm on Linux.
Steps to Reproduce
- goto any service
- open for editing
- eg go to environment vars and try to add a test veriable
- -> when saving the popup appears
Portainer logs or screenshots
No response
Portainer version
2.19.2
Portainer Edition
Business Edition (BE/EE) with 5NF / 3NF license
Platform and Version
Docker Swarm 24.0.7, build afdd53b
OS and Architecture
Oracle Linux 8 on arm64
Browser
Chrome latest
What command did you use to deploy Portainer?
deploy and updating
docker pull portainer/portainer-ee:latest
docker service update --image portainer/portainer-ee:latest --publish-add 9443:9443 --force portainer_portainer
Additional Information
No response
About this issue
- Original URL
- State: closed
- Created 8 months ago
- Reactions: 19
- Comments: 30 (3 by maintainers)
Tested. Fix confirmed. TY!
Hi all - as noted above we have a fix in testing for release as part of 2.19.4 - I don’t have an ETA on release of this patch as of yet but we’re working to get this out as soon as possible as we know this bug has been disruptive for a number of you.
Finally, I found a solution to roll back. In your volume /data/backups/EE, there is a database backup. You can copy that to /data/ and replace portainer.db. Restart and change the image to 2.19.1, and it works for me~
Same for our prod environment 😞 Is there a mechanism to migrate down the database ?
Update
It workes well with the v2.19.0 (No need to downgrade the agents)
docker service update --image portainer/portainer-ce:2.19.0 [SERVICE_NAME]Good news, 2.19.4 is now out, and fixes this issue. We have noticed on occasion the error might still show up immediately after updating, but this appears to be a caching issue so make sure you clear your browser cache if this happens.
Workaround I found that doesn’t involve downgrading, assuming you’re using Chrome and you have access to a terminal with the
curlcommand. The process should be similar for Firefox/etc as long as your browser has a DevTools equivalent.Copy > Copy as cURL--data-rawargument at the end, find the text"Privileges":{"CredentialSpec":{},and remove the part"CredentialSpec": {},curlcommand{"Warnings":null}I upgraded from 2.19.1-CE to 2.19.3-CE and started to receive the :invalid CredentialSpec: must either provide “file”, “registry”, or “config” for credential spec"
While waiting for version 2.19.4, I fixed it this way. Downgrading from 2.19.3 to version 2.19.0 (not to version 2.19.1)
Also wonder why there ist no hotfix for this, its quite a major showstopping bug…
Same here:
Tried downgrading with the same error:
In the meantime a new patch version got released 2 days ago: 2.19.3
Hoped it fixes the bug, but nooope.
🤔