Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
In Section 2 of "RED HAT ENTERPRISE LINUX ATOMIC HOST 7 GETTING STARTED WITH CONTAINERS" (https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#get_started_orchestrating_containers_with_kubernetes), there is a step that is missing that will cause an error in the replication controller when creating the "Simple Apache Web Server" and "Simple Database Server" containers.
If following the directions from the docs, the output of kubectl describe replicationcontroller/webserver-controller and kubectl describe replicationcontroller/db-controller will show an error creating the web and db pods (see output below).
[cloud-user@rhah-0 manifests]$ kubectl describe replicationcontroller/webserver-controller
Name: webserver-controller
Namespace: default
Image(s): webwithdb
Selector: name=webserver
Labels: name=webserver,uses=db
Replicas: 0 current / 1 desired
Pods Status: 0 Running / 0 Waiting / 0 Succeeded / 0 Failed
No volumes.
Events:
FirstSeen LastSeen Count From SubobjectPath Reason Message
───────── ──────── ───── ──── ───────────── ────── ───────
35m 18m 33 {replication-controller } FailedCreate Error creating: Pod "webserver-controller-" is forbidden: no API token found for service account default/default, retry after the token is automatically created and added to the service account
17m 18s 35 {replication-controller } FailedCreate Error creating: Pod "webserver-controller-" is forbidden: no API token found for service account default/default, retry after the token is automatically created and added to the service account
To fix this, "ServiceAccount" must be removed from the KUBE_ADMISSION_CONTROL property in /etc/kubernetes/apiserver.
KUBE_ADMISSION_CONTROL="--admission-control=NamespaceLifecycle,NamespaceExists,LimitRanger,SecurityContextDeny,ResourceQuota"
This step should be added in Section 2.3.2 before or after step 3.
System:
Red Hat Enterprise Linux Atomic Host release 7.2