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

Argo server should start without configmap #2285

Closed
sarabala1979 opened this issue Feb 21, 2020 · 1 comment · Fixed by #2562
Closed

Argo server should start without configmap #2285

sarabala1979 opened this issue Feb 21, 2020 · 1 comment · Fixed by #2562
Assignees
Labels
type/bug type/regression Regression from previous behavior (a specific type of bug)
Milestone

Comments

@sarabala1979
Copy link
Member

What happened:
If the workflow-controller is running in a cluster scope, the user can submit the workflow from their namespace. The user wants to run the argo server in hosted/local mode for their namespace. They don't enable persistence and they don't have permission for Argo namespace. Argo server is throwing below error.

error: “FATA[0000] configmaps “workflow-controller-configmap” not found”

What you expected to happen:
Argo server can start without workflow-controller-configmap
How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Argo version:
$ argo version
  • Kubernetes version :
$ kubectl version -o yaml

Other debugging information (if applicable):

  • workflow result:
argo get <workflowname>
  • executor logs:
kubectl logs <failedpodname> -c init
kubectl logs <failedpodname> -c wait
  • workflow-controller logs:
kubectl logs -n argo $(kubectl get pods -l app=workflow-controller -n argo -o name)

Logs

argo get <workflowname>
kubectl logs <failedpodname> -c init
kubectl logs <failedpodname> -c wait
kubectl logs -n argo $(kubectl get pods -l app=workflow-controller -n argo -o name)

Message from the maintainers:

If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

@sarabala1979 sarabala1979 self-assigned this Feb 21, 2020
@sarabala1979 sarabala1979 added this to the v2.6 milestone Feb 21, 2020
sarabala1979 added a commit to sarabala1979/argo that referenced this issue Feb 21, 2020
@alexec alexec closed this as completed Feb 24, 2020
@heavytail
Copy link

Saw this bug again in 2.7.0

level=fatal msg="configmaps \"workflow-controller-configmap\" not found"
argo version
argo: v2.7.0
  BuildDate: 2020-03-31T23:35:53Z
  GitCommit: 4d1175eb68f6578ed5d599f877be9b4855d33ce9
  GitTreeState: clean
  GitTag: v2.7.0
  GoVersion: go1.13.4
  Compiler: gc
  Platform: windows/amd64
kubectl version -o yaml
clientVersion:
  buildDate: "2019-12-07T21:20:10Z"
  compiler: gc
  gitCommit: 70132b0f130acc0bed193d9ba59dd186f0e634cf
  gitTreeState: clean
  gitVersion: v1.17.0
  goVersion: go1.13.4
  major: "1"
  minor: "17"
  platform: windows/amd64
serverVersion:
  buildDate: "2020-02-21T10:47:45Z"
  compiler: gc
  gitCommit: 20c697423de11d4d5d08c6832a513217ca11a6aa
  gitTreeState: clean
  gitVersion: v1.16.7
  goVersion: go1.13.6
  major: "1"
  minor: "16"
  platform: linux/amd64

@alexec alexec reopened this Apr 1, 2020
@alexec alexec added the type/regression Regression from previous behavior (a specific type of bug) label Apr 1, 2020
alexec added a commit to alexec/argo-workflows that referenced this issue Apr 1, 2020
@alexec alexec linked a pull request Apr 1, 2020 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug type/regression Regression from previous behavior (a specific type of bug)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants