-
Notifications
You must be signed in to change notification settings - Fork 36
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
Application stuck on refresh and sync never begins #242
Comments
Adding a screenshot in case it helps! This is from Argo CD running on OpenShift on openshift-gitops-server-openshift-gitops.crc-lgph7-master-0.crc.jkvinvysksfj.instruqt.io around 1pm EDT (UTC-4) on 10 Apr 2023. The Application Controller can't start. ("Aha! THERE's yer problem!") But I'd think the platform would have resources to support it, no? Maybe something else is amiss that's indirectly related.
|
I faced the same problem. (Japanese track) The machine type used in that track is the following type. After changing to a machine type with 8 CPUs, they started up fine. 'Working with Helm' track do not start properly for the same reason. |
Hi! Unfortunately our team is no longer maintaining the Kustomize or Helm labs, just these https://developers.redhat.com/learn/openshift/devops-openshift |
Thank you @cedricclyburn! Is there a different team or others managing this lab now or is it now unmoored, as it were? |
Unmoored/unmaintained for now, would be happy if someone wanted to pick it back up though :D @jdandrea |
In which track did this bug occur?
Working with Kustomize
what is the url for the track?
https://developers.redhat.com/courses/gitops/working-kustomize
At what step of the track did this happen?
Deploying Kustomized Applicaton
Describe the bug
oc apply -f components/applications/bgd-app.yaml
is stuck on refresh and sync never starts.Logs or error messages
n/a
Expected behavior
bgd-app
syncs.Screenshots
n/a
Desktop (please complete the following information):
Additional context
n/a
The text was updated successfully, but these errors were encountered: