Skip to content

microk8s does not starting after host server reboot #3967

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

Closed
javad87 opened this issue May 14, 2023 · 2 comments
Closed

microk8s does not starting after host server reboot #3967

javad87 opened this issue May 14, 2023 · 2 comments
Labels

Comments

@javad87
Copy link

javad87 commented May 14, 2023

Summary

After host rebooted, microk8s does not start on CentOs7

What Should Happen Instead?

micrk8s start should make kube running

Reproduction Steps

Not exactly I know after restart of host server it happened...

  1. ...
  2. ...

Introspection Report

inspection-report-20230514_092437.tar.gz

Can you suggest a fix?

Are you interested in contributing with a fix?

@ktsakalozos
Copy link
Member

Hi @javad87

Would it be possible to use the latest 1.27 release? There have been a few updates for better support of CentOS in the latest release.

Also, could you please not name the nodes "localhost.localdomain".

Finally, I see there are some issues in pulling the images:

May 14 09:23:47 kousha.ifb.ir microk8s.daemon-containerd[1425]: time="2023-05-14T09:23:47.605612820+03:30" level=info msg="PullImage \"library/pyodbcsqlimage:1.0.0\""
May 14 09:23:55 kousha.ifb.ir microk8s.daemon-containerd[1425]: time="2023-05-14T09:23:55.101644621+03:30" level=info msg="trying next host" error="pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed" host=registry-1.docker.io

Could you please check that the node kousha.ifb.ir can actually pull images?

Copy link

stale bot commented Apr 9, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the inactive label Apr 9, 2024
@stale stale bot closed this as completed May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants