vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Common issues with worker nodes 

Virtual Private Cloud

Classic infrastructure

Review common error messages and learn how to resolve them. Messages might begin with the prefix, '<provider>' infrastructure exception:, where <provider> identifies which infrastructure provider the worker node uses.



 Account prohibited from ordering 

Message:

Your account is currently prohibited from ordering 'Computing Instances'.

Description and resolution:

Your IBM Cloud infrastructure account might be restricted from ordering compute resources. Contact IBM Cloud support by opening an [IBM Cloud support case](https://cloud.ibm.com/docs/containers?topic=containers-get-help).





 Could not place order 

Message:

Could not place order.

Could not place order. There are insufficient resources behind router 'router_name' to fulfill the request for the following guests: 'worker_id'.

Description and resolution: The zone that you selected might not have enough infrastructure capacity to provision your worker nodes. Or, you might have exceeded a limit in your IBM Cloud infrastructure account.

To resolve, try one of the following options:



* Infrastructure resource availability in zones can fluctuate often. Wait a few minutes and try again.
* For a single zone cluster, create the cluster in a different zone. For a multizone cluster, add a zone to the cluster.
* Specify a different pair of public and private VLANs for your worker nodes in your IBM Cloud infrastructure account. For worker nodes that are in a worker pool, you can use the ibmcloud ks zone network-set [command](/docs/containers?topic=containers-kubernetes-service-cli
* Contact your IBM Cloud infrastructure account manager to verify that you don't exceed an account limit, such as a global quota.
* Open an [IBM Cloud infrastructure support case](https://cloud.ibm.com/docs/containers?topic=containers-get-help).







 Could not obtain network VLAN 

Message:

Could not obtain network VLAN with ID: <vlan-id>

Description and resolution:

Your worker node could not be provisioned because the selected VLAN ID could not be found for one of the following reasons:
Containerd N/A N/A N/A 
 Haproxy af5031 8398d1 [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916). 







 Change log for worker node fix pack 1.24.10_1558, released 13 March 2023 

The following table shows the changes that are in the worker node fix pack 1.24.10_1558. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.24.10_1554

 Component Previous Current Description 

 Ubuntu 20.04 packages 5.4.0-139 5.4.0-144 Worker node kernel & package updates for [CVE-2022-29154](https://nvd.nist.gov/vuln/detail/CVE-2022-29154), [CVE-2022-3545](https://nvd.nist.gov/vuln/detail/CVE-2022-3545), [CVE-2022-3821](https://nvd.nist.gov/vuln/detail/CVE-2022-3821), [CVE-2022-40898](https://nvd.nist.gov/vuln/detail/CVE-2022-40898), [CVE-2022-41218](https://nvd.nist.gov/vuln/detail/CVE-2022-41218), [CVE-2022-4139](https://nvd.nist.gov/vuln/detail/CVE-2022-4139),
Why can't I create or delete clusters or worker nodes? 

You can't perform infrastructure-related commands on your cluster, such as:



* Adding worker nodes in an existing cluster or when creating a new cluster.
* Removing worker nodes.
* Reloading or rebooting worker nodes.
* Resizing worker pools.
* Updating your cluster.
* Deleting your cluster.



Review the error messages in the following sections to troubleshoot infrastructure-related issues that are caused by [incorrect cluster permissions](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster_infra_errorscs_credentials), [orphaned clusters in other infrastructure accounts](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster_infra_errorsorphaned), or [a time-based one-time passcode (TOTP) on the account](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster_infra_errorscs_totp).



 Unable to create or delete worker nodes due to permission errors 

 What’s happening 

You can't manage worker nodes for your cluster, and you receive an error message similar to one of the following examples.

We were unable to connect to your Softlayer account.
Creating a standard cluster requires that you have either a
Pay-As-You-Go account that is linked to an IBM Cloud infrastructure
account term or that you have used the Kubernetes service
CLI to set your Infrastructure API keys.

'Item' must be ordered with permission.

The worker node instance '<ID>' can't be found. Review '<provider>' infrastructure user permissions.

The worker node instance can't be found. Review '<provider>' infrastructure user permissions.

The worker node instance can't be identified. Review '<provider>' infrastructure user permissions.

The IAM token exchange request failed with the message: <message>
IAM token exchange request failed: <message>

The cluster could not be configured with the registry.
* [Deploy_failed state](https://cloud.ibm.com/docs/containers?topic=containers-worker-node-state-referenceworker-node-deploy-failed)
* [Normal state](https://cloud.ibm.com/docs/containers?topic=containers-worker-node-state-referenceworker-node-normal)
* [Provisioned state](https://cloud.ibm.com/docs/containers?topic=containers-worker-node-state-referenceworker-node-provisioned)
* [Provisioning state](https://cloud.ibm.com/docs/containers?topic=containers-worker-node-state-referenceworker-node-provisioning)
* [Provision pending state](https://cloud.ibm.com/docs/containers?topic=containers-worker-node-state-referenceworker-node-provision-pending)
* [Provision_failed state](https://cloud.ibm.com/docs/containers?topic=containers-worker-node-state-referenceworker-node-provision-failed)
* [Reloading state](https://cloud.ibm.com/docs/containers?topic=containers-worker-node-state-referenceworker-node-reloading)
* [Reloading_failed state](https://cloud.ibm.com/docs/containers?topic=containers-worker-node-state-referenceworker-node-reloading-failed)
* [Reload_pending state](https://cloud.ibm.com/docs/containers?topic=containers-worker-node-state-referenceworker-node-reload-pending)
* [Unknown state](https://cloud.ibm.com/docs/containers?topic=containers-worker-node-state-referenceworker-node-unknown)
* [Warning state](https://cloud.ibm.com/docs/containers?topic=containers-worker-node-state-referenceworker-node-warning)
(https://cognitiveclass.ai/courses/docker-essentials)





 What is Red Hat OpenShift? 

Red Hat OpenShift is a Kubernetes container platform that provides a trusted environment to run enterprise workloads. It extends the Kubernetes platform with built-in software to enhance app lifecycle development, operations, and security. With Red Hat OpenShift, you can consistently deploy your workloads across hybrid cloud providers and environments. For more information about the differences between the community Kubernetes and Red Hat OpenShift cluster offerings, see the [comparison table](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_ovopenshift_kubernetes).





 What compute host infrastructure does the service offer? 

You can create clusters on Classic or IBM Cloud® Virtual Private Cloud infrastructure. You can also bring your own hosts by using Satellite.

For more information, see [Supported infrastructure providers](https://cloud.ibm.com/docs/openshift?topic=openshift-infrastructure_providers).





 Related resources 

Review how you can learn about Kubernetes concepts and the terminology.



* Familiarize yourself with the product by completing the [Creating clusters tutorial](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_tutorial).
* Learn how Kubernetes and Red Hat OpenShift on IBM Cloud work together by completing this [course](https://cognitiveclass.ai/courses/kubernetes-course).
With Kubernetes, you can combine various resources such as secrets, deployments, and services to securely create and manage highly available, containerized apps.

Red Hat OpenShift
: Red Hat OpenShift on IBM Cloud is a Kubernetes-based platform that is designed especially to accelerate your containerized app delivery processes that run on a Red Hat Enterprise Linux 7 operating system. You can orchestrate and scale your existing Red Hat OpenShift workloads across on-prem and off-prem clouds for a portable, hybrid solution that works the same in multicloud scenarios. To get started, try out the [Red Hat OpenShift on IBM Cloud tutorial](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_tutorial).
* Does the service come with a managed Red Hat OpenShift master and worker nodes?

Every cluster in Red Hat OpenShift on IBM Cloud is controlled by a dedicated Red Hat OpenShift master that is managed by IBM in an IBM-owned IBM Cloud infrastructure account. The Red Hat OpenShift master, including all the master components, compute, networking, and storage resources, is continuously monitored by IBM Site Reliability Engineers (SREs). The SREs apply the latest security standards, detect and remediate malicious activities, and work to ensure reliability and availability of Red Hat OpenShift on IBM Cloud.

Periodically, Red Hat OpenShift releases [major, minor, or patch updates](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsupdate_types). These updates can affect the Red Hat OpenShift API server version or other components in your Red Hat OpenShift master. IBM automatically updates the patch version, but you must update the master major and minor versions. For more information, see [Updating the master](https://cloud.ibm.com/docs/containers?topic=containers-updatemaster).

Worker nodes in standard clusters are provisioned in to your IBM Cloud infrastructure account. The worker nodes are dedicated to your account and you are responsible to request timely updates to the worker nodes to ensure that the worker node OS and Red Hat OpenShift on IBM Cloud components apply the latest security updates and patches.
To get started, try out the [Red Hat OpenShift on IBM Cloud tutorial](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_tutorial).





 Does the service come with a managed Red Hat OpenShift master and worker nodes? 

Every cluster in Red Hat OpenShift on IBM Cloud is controlled by a dedicated Red Hat OpenShift master that is managed by IBM in an IBM-owned IBM Cloud infrastructure account. The Red Hat OpenShift master, including all the master components, compute, networking, and storage resources, is continuously monitored by IBM Site Reliability Engineers (SREs). The SREs apply the latest security standards, detect and remediate malicious activities, and work to ensure reliability and availability of Red Hat OpenShift on IBM Cloud.

Periodically, Red Hat OpenShift releases [major, minor, or patch updates](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsupdate_types). These updates can affect the Red Hat OpenShift API server version or other components in your Red Hat OpenShift master. IBM automatically updates the patch version, but you must update the master major and minor versions. For more information, see [Updating the master](https://cloud.ibm.com/docs/containers?topic=containers-updatemaster).

Worker nodes in standard clusters are provisioned in to your IBM Cloud infrastructure account. The worker nodes are dedicated to your account and you are responsible to request timely updates to the worker nodes to ensure that the worker node OS and Red Hat OpenShift on IBM Cloud components apply the latest security updates and patches. Security updates and patches are made available by IBM Site Reliability Engineers (SREs) who continuously monitor the Linux image that is installed on your worker nodes to detect vulnerabilities and security compliance issues. For more information, see [Updating worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-updateworker_node).





 Are the master and worker nodes highly available? 

The Red Hat OpenShift on IBM Cloud architecture and infrastructure is designed to ensure reliability, low processing latency, and a maximum uptime of the service.
For more information, see [Comparison between Red Hat OpenShift and community Kubernetes clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_ovopenshift_kubernetes).

Kubernetes
: [Kubernetes](https://kubernetes.io/) is a production-grade, open source container orchestration platform that you can use to automate, scale, and manage your containerized apps that run on an Ubuntu operating system. With the [IBM Cloud Kubernetes Service version](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionscs_versions), you get access to community Kubernetes API features that are considered beta or higher by the community. Kubernetes alpha features, which are subject to change, are generally not enabled by default. With Kubernetes, you can combine various resources such as secrets, deployments, and services to securely create and manage highly available, containerized apps.

Red Hat OpenShift
: Red Hat OpenShift on IBM Cloud is a Kubernetes-based platform that is designed especially to accelerate your containerized app delivery processes that run on a Red Hat Enterprise Linux 7 operating system. You can orchestrate and scale your existing Red Hat OpenShift workloads across on-prem and off-prem clouds for a portable, hybrid solution that works the same in multicloud scenarios. To get started, try out the [Red Hat OpenShift on IBM Cloud tutorial](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_tutorial).





 Does the service come with a managed Red Hat OpenShift master and worker nodes? 

Every cluster in Red Hat OpenShift on IBM Cloud is controlled by a dedicated Red Hat OpenShift master that is managed by IBM in an IBM-owned IBM Cloud infrastructure account. The Red Hat OpenShift master, including all the master components, compute, networking, and storage resources, is continuously monitored by IBM Site Reliability Engineers (SREs).
[VMware Solutions and Red Hat OpenShift](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/openshift-sddc.svg)

Figure 1. VMware Solutions and OpenShift



 Red Hat OpenShift overview 

The Red Hat OpenShift platform is a platform that is designed to orchestrate containerized workloads across a cluster of nodes. The platform uses Kubernetes as the core container orchestration engine, which manages the Docker container images and their lifecycle.

The operating system of the nodes is Red Hat® Enterprise Linux® CoreOS, which is the container host version of Red Hat Enterprise Linux (RHEL) and features an RHEL kernel with SELinux enabled by default. RHEL CoreOS includes kubelet, which is the Kubernetes node agent, and the CRI-O container runtime, which is optimized for Kubernetes. In Red Hat OpenShift 4.7, you must use RHEL CoreOS for all control plane machines, but you can use Red Hat Enterprise Linux (RHEL) as the operating system for compute, or worker machines. If you choose to use RHEL workers, you must perform more system maintenance than if you use RHEL CoreOS for all of the cluster machines.

The reference architecture and this build process use RHEL CoreOS. The nodes must have direct Internet access to complete the following tasks.



* Access the Red Hat OpenShift Infrastructure Providers page to download the installation program.
* Access quay.io to obtain the packages that are required to install the cluster.
* Obtain the packages that are required to perform cluster updates.
* Access Red Hat’s software as a service page to perform subscription management.



In the reference architecture, the following components are installed and configured in the build process:



* Bastion node - This RHEL VM acts as a "jump-server" on the overlay network to enable the build process. It is accessed by using SSH through the private network. It also hosts a webserver to help the build process of the cluster.
Red Hat OpenShift for VMware configuration 

When you order the service, you must provide a Red Hat® pull secret. This pull secret is used to associate the new Red Hat OpenShift cluster with your existing Red Hat account. You can obtain a copy of your pull secret by [logging in to your Red Hat account](https://cloud.redhat.com/openshift/install/vsphere/user-provisioned) and clicking Copy Pull Secret.





 Setting up DNS to access your Red Hat OpenShift console 

Red Hat OpenShift depends on DNS to function properly. The ocp wildcard zone in your VMware environment root zone resolves all names to the IP address of the Red Hat OpenShift cluster application. This way, all applications that run within Red Hat OpenShift are routed through the Load Balancer, as needed.

Because the Red Hat OpenShift web console runs as an application within Red Hat OpenShift, your system must properly resolve DNS names before you can connect to the Red Hat OpenShift web console. You must complete the following steps before you open the Red Hat OpenShift console:



1. Ensure you are connected to your environment by using the IBM Cloud infrastructure VPN.
2. Ensure the system that you use to connect to the Red Hat OpenShift web console can properly resolve hostnames in the DNS zone for your VMware environment. For an existing DNS infrastructure, configure the DNS delegation. Therefore, the queries for hostnames within the VMware instance's root zone are handled by the AD DNS server that is running within your VMware environment.



Alternately, you can configure your local hosts file with the following entries so you can access the Red Hat OpenShift web console. Use the following details for the example.



* Replace APPLICATION_IP with the Red Hat OpenShift application IP address shown in the Red Hat OpenShift service details page.
* Replace ROOTDOMAIN with the root domain shown on the Summary page for the vCenter Server instance.
Benefits and service offerings 

[Red Hat® OpenShift® on IBM Cloud®](https://www.ibm.com/products/openshift) is an IBM Cloud service, where IBM sets up and helps you manage a cluster of worker nodes that come installed with the OpenShift Container Platform container orchestration software.

To see a list of the cluster operators that are supported by default, you can run the oc get co command.



 Benefits of using the service 

With Red Hat OpenShift on IBM Cloud, your developers have a fast and secure way to containerize and deploy enterprise workloads in Kubernetes clusters. Red Hat OpenShift clusters build on Kubernetes container orchestration that offers consistency and flexibility for your development lifecycle operations.

Your Red Hat OpenShift workloads can scale across IBM’s global footprint of data centers and multizone regions. At the same time, you’re able to uniformly monitor, log, and secure apps. Because IBM manages the service, you can focus on innovating with high-value IBM Cloud services and middleware, such as AI and analytics. You also have access to Red Hat packaged open-source tools, including your favorite app runtimes, frameworks, databases, and more.

Ready to get started? Try out the [creating a Red Hat OpenShift on IBM Cloud cluster tutorial](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_tutorial).

Choice of container platform provider
: Deploy clusters with Red Hat OpenShift or community Kubernetes installed as the container platform orchestrator.
: Choose the developer experience that fits your company, or run workloads across both Red Hat OpenShift or community Kubernetes clusters.
: Built-in integrations from the IBM Cloud console to the Kubernetes dashboard or Red Hat OpenShift web console.
: Single view and management experience of all your Red Hat OpenShift or community Kubernetes clusters from IBM Cloud.
Red Hat OpenShift on IBM Cloud version information 

Review information about the supported Red Hat OpenShift versions for Red Hat® OpenShift® on IBM Cloud® clusters.

View information of version changes for major, minor, and patch updates that are available for your Red Hat® OpenShift® on IBM Cloud® clusters. Changes include updates to Red Hat OpenShift, Kubernetes, and IBM Cloud Provider components.

Unless otherwise noted in the change logs, the IBM Cloud provider version enables Red Hat OpenShift APIs and features that are at beta. Red Hat OpenShift alpha features, which are subject to change, are disabled.

Check the [Security Bulletins on IBM Cloud Status](https://cloud.ibm.com/status?selected=security) for security vulnerabilities that affect Red Hat OpenShift on IBM Cloud. You can filter the results to view only Kubernetes Service security bulletins that are relevant to Red Hat OpenShift on IBM Cloud. Change log entries that address other security vulnerabilities but don't also refer to an IBM security bulletin are for vulnerabilities that are not known to affect Red Hat OpenShift on IBM Cloud in normal usage. If you run privileged containers, run commands on the workers, or execute untrusted code, then you might be at risk.

Master patch updates are applied automatically. Worker node patch updates can be applied by reloading or updating the worker nodes. For more information about major, minor, and patch versions and preparation actions between minor versions, see [Red Hat OpenShift versions](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions).

For more details about the Red Hat OpenShift and Kubernetes project versions, review the Red Hat OpenShift release notes.



* [Red Hat OpenShift 4.13 release notes overview](https://docs.openshift.com/container-platform/4.13/release_notes/ocp-4-13-release-notes.html)
Red Hat OpenShift on IBM Cloud is a managed Red Hat OpenShift offering that delivers powerful tools, an intuitive user experience, and built-in security for rapid delivery of apps that you can bind to cloud services that are related to IBM Watson®, AI, IoT, DevOps, security, and data analytics. As a certified Kubernetes provider, Red Hat OpenShift on IBM Cloud provides intelligent scheduling, self-healing, horizontal scaling, service discovery and load balancing, automated rollouts and rollbacks, and secret and configuration management. The service also has advanced capabilities around simplified cluster management, container security and isolation policies, the ability to design your own cluster, and integrated operational tools for consistency in deployment.

For a detailed overview of capabilities and benefits, see [Benefits of using the service](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_ovbenefits).





 What container platforms are available for my cluster? 

With IBM Cloud, you can create clusters for your containerized workloads from two different container management platforms: the IBM version of community Kubernetes and Red Hat OpenShift on IBM Cloud. The container platform that you select is installed on your cluster master and worker nodes. Later, you can [update the version](https://cloud.ibm.com/docs/containers?topic=containers-updateupdate) but can't roll back to a previous version or switch to a different container platform. If you want to use multiple container platforms, create a separate cluster for each.

For more information, see [Comparison between Red Hat OpenShift and community Kubernetes clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_ovopenshift_kubernetes).

Kubernetes
: [Kubernetes](https://kubernetes.io/) is a production-grade, open source container orchestration platform that you can use to automate, scale, and manage your containerized apps that run on an Ubuntu operating system.