Error: unrecognized command podman image mount in bootstrap node
#735
Replies: 18 comments
-
|
Release image service failed:
bootstrap node can't resolve the mirror registry |
Beta Was this translation helpful? Give feedback.
-
|
I added to /etc/hosts after can't resolve the mirror registry log and it passed after that instance then I see podman mount error |
Beta Was this translation helpful? Give feedback.
-
|
Registry address must be resolvable on bootstrap/masters/workers with no /etc/hosts hacks, as it won't be passed to the container |
Beta Was this translation helpful? Give feedback.
-
|
Oh I see, I'll try to build registry with IP address and will see how it goes. |
Beta Was this translation helpful? Give feedback.
-
|
I see same error even after dns name resolved within vpc by aws private hosted zone. I have destroyed old bootstrap node and created a new one. Here is the log bundle. |
Beta Was this translation helpful? Give feedback.
-
|
Are you using RHCOS as a start image? You need to use FCOS (see #566 (comment)) |
Beta Was this translation helpful? Give feedback.
-
|
Nope. I'm using https://docs.okd.io/latest/installing/installing_aws/installing-restricted-networks-aws.html#installation-aws-user-infra-rhcos-ami_installing-restricted-networks-aws document says this is FCOS image AMI ID: ami-0b421328859954025. |
Beta Was this translation helpful? Give feedback.
-
|
Oh wait I see in AWS it says rhcos ami. Shall I use this ISO https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210217.3.0/x86_64/fedora-coreos-33.20210217.3.0-live.x86_64.iso and build AMI from ISO and use it for all the bootstrap, master and worker nodes? |
Beta Was this translation helpful? Give feedback.
-
No, use official Fedora CoreOS AMIs, see https://github.com/vrutkovs/installer/blob/fcos-release-4.7/data/data/fcos-amd64.json |
Beta Was this translation helpful? Give feedback.
-
|
I'm using fcos AMI ami-021238084bf8c95ff as per feedback and tried to intiliaze bootstrap node. I got error $ sudo /opt/registry/downloads/tools/openshift-install wait-for bootstrap-complete --dir=/home/centos/okdago/ $ journalctl -b -f -u bootkube.service $journalctl -b -f -u kubelet.service -u crio.service tail -f /var/log/containers/* $tail -f -n 200 .openshift_install.log |
Beta Was this translation helpful? Give feedback.
-
|
After creating manifests files I have removed below files and created ignition-config files |
Beta Was this translation helpful? Give feedback.
-
see docs for other methods |
Beta Was this translation helpful? Give feedback.
-
|
Yes I have used other method(Manually gathering logs with SSH access to your host) to get those logs. I tried to direct journal logs to file but file contains only recent logs. In manual method we can only see logs and there is no way to bundle it as per the above doc |
Beta Was this translation helpful? Give feedback.
-
No, the real problem is
|
Beta Was this translation helpful? Give feedback.
-
|
Anyway I destroyed bootstrap node and created again to gather log bundle even though gather bootstrap command is unresponsive. But now I see different error in bootstrap node logs look like x509: certificate has expired. But If I see cert details, it has valid upto 2nd may 2026 I attached cert details here. do I need to rebuild registry again or do i need to deal with configuration
|
Beta Was this translation helpful? Give feedback.
-
|
You need to recreate Ignition files to have it updated |
Beta Was this translation helpful? Give feedback.
-
Cert issue solved by re created ignition files. Now I can see syncing pod issue. How can I solve this? Is there an way to solve this problem?
|
Beta Was this translation helpful? Give feedback.
-
|
Could you please suggest me here anything |
Beta Was this translation helpful? Give feedback.
-
Hi, I'm installing latest okd stable 4.7.0-0.okd-2021-04-24-103438 on AWS restricted https://docs.okd.io/latest/installing/installing_aws/installing-restricted-networks-aws.html and I had setup mirror registry and provisioned vpc, dns and load balancers, security groups and Iam policies.
When I created bootstrap node and looked into journalctl -b -f -u release-image.service -u bootkube.service and I see error Error: unrecognized command
podman image mountimages were able to pulled from registry but mount point is failed. I collected logs after wait-for bootstrap-complete command and I attached log bundle here and also I added small log snippet herelog-bundle-20210504085215-okdago.tar.gz
.
Beta Was this translation helpful? Give feedback.
All reactions