-
Notifications
You must be signed in to change notification settings - Fork 189
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
[BUG] the server doesn't have a resource type "route" #658
Comments
I also tried to delete all microshift pods but that did not worked as expected. |
More logs
|
@oglok per our email conversation. This seem to be a big blocker. As a microshift user ,i would first stup the cluster , install apps i need. Later if we want to stop the cluster, i would expect when we bring it back (start) it should have all my apps running and i can access them as i was doing it prior reboot the microshift instance. Any help on this would be appretiated. |
@ksingh7 new image has been built. Could you please test it? Thanks! https://quay.io/repository/microshift/microshift-aio?tab=tags |
@ksingh7 have you tried with |
@oglok thanks a lot for new image, which i have not tested yet, i will test it soon and share feedback. Also i have not tried |
I'm having a similar issue and
Notably, the ingress and service-ca are both stuck at
And, as mentioned, the route resource is not available:
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
The team has decided to drop support for running MicroShift in a container and focus on running via systemd. If you're still having trouble with this issue using that configuration, please create a new issue with the details of that configuration. |
What happened:
I encountered a reproducible issue. Microshift AIO in container (podman) works fine , however whenever i reboot the host machine, then start microshift container
podman start microshift
and dooc get routes
after a while , i get an errorerror: the server doesn't have a resource type "route"
, and i get healthcheck failure errors in router-default container logsWhat you expected to happen:
oc get routes
should not throw error about resource type does not existsHow to reproduce it (as minimally and precisely as possible):
oc get route
to verify its workingoc get route
<--- This throws errorAnything else we need to know?:
Here are the logs of
router-default
podEnvironment:
microshift version
):Microshift-AIO:latest
cat /etc/os-release
): Fedorauname -a
):Linux fedora 5.14.10-300.fc35.x86_64 #1 SMP Thu Oct 7 20:48:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Relevant Logs
The text was updated successfully, but these errors were encountered: