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

ArgoCD 2.4.0 webUI with rootpath no longer works. #9692

Closed
3 tasks done
reefland opened this issue Jun 16, 2022 · 4 comments · Fixed by #9724
Closed
3 tasks done

ArgoCD 2.4.0 webUI with rootpath no longer works. #9692

reefland opened this issue Jun 16, 2022 · 4 comments · Fixed by #9724
Labels
bug Something isn't working

Comments

@reefland
Copy link

reefland commented Jun 16, 2022

Checklist:

  • I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
  • I've included steps to reproduce the bug.
  • I've pasted the output of argocd version.

Describe the bug

Existing 2.3.4 installation upgraded to 2.40 using a rootpath of "/argocd" now Web UI no longer renders. ArgoCD itself seems to working with the repo just fine and still processing changes. Just the Web UI is not rendering.

I also upgraded the CRDS:

$ kubectl apply -k https://github.com/argoproj/argo-cd.git/manifests/crds?ref=v2.4.0

customresourcedefinition.apiextensions.k8s.io/applications.argoproj.io unchanged
customresourcedefinition.apiextensions.k8s.io/applicationsets.argoproj.io configured
customresourcedefinition.apiextensions.k8s.io/appprojects.argoproj.io unchanged

To Reproduce

The 2.3.4 Helm values.yaml had this:

  server:
    name: server
    extraArgs:
      - --insecure
      - --rootpath=/argocd

In reviewing logs after 2.4.0 upgrade I noticed this conflict warning:

$ k logs argocd-server-66497bbc98-j8f7s -n argocd -f
time="2022-06-16T12:43:20Z" level=warning msg="--basehref and --rootpath had conflict: basehref: / rootpath: /argocd"
time="2022-06-16T12:43:20Z" level=info msg="Starting configmap/secret informers"
time="2022-06-16T12:43:21Z" level=info msg="Configmap/secret informer synced"
time="2022-06-16T12:43:21Z" level=info msg="Starting configmap/secret informers"
time="2022-06-16T12:43:21Z" level=info msg="secrets informer cancelled"
time="2022-06-16T12:43:21Z" level=info msg="Configmap/secret informer synced"
time="2022-06-16T12:43:21Z" level=info msg="configmap informer cancelled"
time="2022-06-16T12:43:21Z" level=info msg="argocd v2.4.0+91aefab serving on port 8080 (url: , tls: false, namespace: argocd, sso: false)"
time="2022-06-16T12:43:21Z" level=info msg="0xc000f7de00 subscribed to settings updates"
time="2022-06-16T12:43:21Z" level=info msg="Starting rbac config informer"
time="2022-06-16T12:43:21Z" level=info msg="RBAC ConfigMap 'argocd-rbac-cm' added"

Educated guess, I set that as well:

  server:
    name: server
    extraArgs:
      - --insecure
      - --rootpath=/argocd
      - --basehref=/argocd

Conflict warning message went away, but still Web UI does not render.

$ k logs argocd-server-b47dfccd-jxp8q -n argocd -f
time="2022-06-16T13:31:56Z" level=info msg="Starting configmap/secret informers"
time="2022-06-16T13:31:57Z" level=info msg="Configmap/secret informer synced"
time="2022-06-16T13:31:57Z" level=info msg="Starting configmap/secret informers"
time="2022-06-16T13:31:57Z" level=info msg="secrets informer cancelled"
time="2022-06-16T13:31:57Z" level=info msg="configmap informer cancelled"
time="2022-06-16T13:31:57Z" level=info msg="Configmap/secret informer synced"
time="2022-06-16T13:31:57Z" level=info msg="argocd v2.4.0+91aefab serving on port 8080 (url: , tls: false, namespace: argocd, sso: false)"
time="2022-06-16T13:31:57Z" level=info msg="0xc000f8af60 subscribed to settings updates"
time="2022-06-16T13:31:57Z" level=info msg="Starting rbac config informer"
time="2022-06-16T13:31:57Z" level=info msg="RBAC ConfigMap 'argocd-rbac-cm' added"

When I view source code of blank page, it is just this:

<!doctype html><html lang="en"><head><meta charset="UTF-8"><title>Argo CD</title><base href="/argocd/"></div></body></html>

I can't find any errors to troubleshoot.

@reefland reefland added the bug Something isn't working label Jun 16, 2022
@almynamswertakn
Copy link

I am also seeing this issue after stepping up from v2.3.3 with these values previously working:

        server:
          extraArgs:
            - --insecure
            - --rootpath
            - /argocd
            - --basehref
            - /argocd

As @reefland mentions, syncing seems to work.
I also have webhooks in my gitops repo that continue to work.

Istio-proxy sidecar shows 200s , but the page is just white.

[2022-06-18T01:03:34.422Z] "GET /argocd/ HTTP/1.1" 200 - via_upstream - "-" 0 123 0 0 "xxx.xx.xxx.229" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0" "xxxx-xx-46a1-x-xx" "dev.xxxx.com" "127.0.0.1:8080" inbound|8080|| 127.0.0.1:57358 10.42.11.195:8080 xxx.xx.xxx.229:0 - default
```

@d7volker
Copy link
Contributor

I do experience this as well

@chenfli
Copy link

chenfli commented Jun 19, 2022

I also have this on 2.4.0 First release, worked on 2.3.4
deploy argocd-server

      containers:
      - command:
        - argocd-server
        - --rootpath
        - /argocd

ingress

      http:
        paths:
        - backend:
            service:
              name: argocd-server
              port:
                number: 443
          path: /argocd
          pathType: ImplementationSpecific

Returns an empty HTML

<!doctype html><html lang="en"><head><meta charset="UTF-8"><title>Argo CD</title><base href="/argocd/"></div></body></html>

@reefland
Copy link
Author

Chart 4.9.6 brought in ArgoCD 2.4.2 and its working again. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants