vania-janet/multiturn-rag-retrieval-data huggingface dataset:
In the spec.selector section of the LoadBalancer service, ensure that the <selector_key> and <selector_value> is the same as the key/value pair that you used in the spec.template.metadata.labels section of your deployment YAML. If labels don't match, the Endpoints section in your LoadBalancer service displays none and your app is not accessible from the internet.
3. Check that you used the port that your app listens on.





4. Check your NLB service and review the Events section to find potential errors.

kubectl describe service <myservice>

Look for the following error messages.

Clusters with one node must use services of type NodePort
: To use the NLB service, you must have a standard cluster with at least two worker nodes.

No cloud provider IPs are available to fulfill the NLB service request. Add a portable subnet to the cluster and try again.
: This error message indicates that no portable public IP addresses remaining to be allocated to your NLB service. Refer to [Adding subnets to clusters](https://cloud.ibm.com/docs/containers?topic=containers-subnetssubnets) to find information about how to request portable public IP addresses for your cluster. After portable public IP addresses are available to the cluster, the NLB service is automatically created.

Requested cloud provider IP <cloud-provider-ip> is not available. The following cloud provider IPs are available: <available-cloud-provider-ips>
: You defined a portable public IP address for your load balancer YAML by using the loadBalancerIP section, but this portable public IP address is not available in your portable public subnet. In the loadBalancerIP section your configuration script, remove the existing IP address and add one of the available portable public IP addresses. You can also remove the loadBalancerIP section from your script so that an available portable public IP address can be allocated automatically.

No available nodes for NLB services
: You don't have enough worker nodes to deploy an NLB service. One reason might be that you deployed a standard cluster with more than one worker node, but the provisioning of the worker nodes failed.



1.
* [Step 2: Run Ingress tests in the Diagnostics and Debug Tool](https://cloud.ibm.com/docs/containers?topic=containers-ingress-debugdebug-tool-ingress)
* [Step 3: Check for error messages in your Ingress deployment and the ALB pod logs](https://cloud.ibm.com/docs/containers?topic=containers-ingress-debugerrors)
* [Step 4: Ping the ALB subdomain and public IP addresses](https://cloud.ibm.com/docs/containers?topic=containers-ingress-debugping)
* [Step 5: Check your domain mappings and Ingress resource configuration](https://cloud.ibm.com/docs/containers?topic=containers-ingress-debugts_ingress_config)
* [Removing an ALB from DNS for debugging](https://cloud.ibm.com/docs/containers?topic=containers-ingress-debugone_alb)



[Gathering Ingress logs](https://cloud.ibm.com/docs/containers?topic=containers-ingress-must-gatheringress-must-gather)

[Classic clusters: Why can't my app connect via Ingress?](https://cloud.ibm.com/docs/containers?topic=containers-cs_ingress_failscs_ingress_fails)

[VPC clusters: Why can't my app connect via Ingress?](https://cloud.ibm.com/docs/containers?topic=containers-vpc_ts_albvpc_ts_alb)

[Why does no Ingress subdomain exist after cluster creation?](https://cloud.ibm.com/docs/containers?topic=containers-ingress_subdomainingress_subdomain)



* [Classic clusters](https://cloud.ibm.com/docs/containers?topic=containers-ingress_subdomainno-ingress-subdomain-classic)
journalctl -u ibm-host-attach --no-pager
4. Review the logs for errors. See the following sections for more details.





 First boot did not complete successfully 

You receive output similar to the following messages.

export HOME=/root
HOME=/root
'[!' '' -f /var/log/firstboot.flag ']'


The first boot did not complete successfully. Check the /tmp/bootstrap/bootstrap_base.log file and continue looking for errors.





 Host registration script fails 

You receive output similar to the following messages. Note that the package name might be replaced with another package name.

No package matching '''container-selinux''' found available, installed or updated
No package rh-python36 available. Error: Nothing to do

For more information about these messages, see [Host registration script fails](https://cloud.ibm.com/docs/satellite?topic=satellite-host-registration-script-fails).





 Machine cannot be reached on the network 

You receive output similar to the following messages.

curl: (6) Could not resolve host: <URL>.com; Unknown error
tar -xvf bootstrap.tar
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
[ -n ‘’ ]]
echo ‘Failed to untar bootstrap.tar’
Failed to untar bootstrap.tar n + rm -rf /tmp/bootstrap

The machine cannot be reached on the network.
* [Increasing the log level for the calico-node components](https://cloud.ibm.com/docs/openshift?topic=openshift-calico_log_levelcalico-increase-logging-node)
* [Increasing the log level for the calico-kube-controllers components](https://cloud.ibm.com/docs/openshift?topic=openshift-calico_log_levelcalico-increase-logging-kube-controllers)
* [Gathering Calico logs](https://cloud.ibm.com/docs/openshift?topic=openshift-calico_log_levelcalico-log-gather)



[Why can't I use the Red Hat annotations to restrict access to the Red Hat OpenShift Console?](https://cloud.ibm.com/docs/openshift?topic=openshift-ip_whitelistip_whitelist)

[Why does my pod with long running TCP connections get disconnected?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-keepalive-sysctlts-keepalive-sysctl)

[Why are DNS lookups from certain pods so slow?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-slow-dns-lookupts-slow-dns-lookup)





 Apps and services 

[Debugging app deployments](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_appsdebug_apps)

[Why does my build error due to image pull authentication?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-app-build-img-pullts-app-build-img-pull)

[Why can't I push or pull images from my local machine to the Docker registry?]
"$eq": "Lars von Trier"
}
}

In the following example that uses subfields, the field imdb in a matching document must also have a subfield rating, and the subfield must have a value equal to 8.

See the following example of implicit operator that is applied to a subfield test:

{
"imdb": {
"rating": 8
}
}

You can make the equality operator explicit.

See the following example of an explicit equality operator:

{
"selector": {
"imdb": {
"rating": { "$eq": 8 }
}
}
}

See the following example of a $eq operator that is used with full text indexing:

{
"selector": {
"year": {
"$eq": 2001
}
},
"sort": [
"title:string"
],
"fields": [
"title"
]
}

See the following example of an $eq operator that is used with a database that is indexed on the field year:

{
"selector": {
"year": {
"$eq": 2001
}
},
"sort": [
"year"
],
"fields": [
"year"
]
}

In the following example, the field director must be present and contain the value Lars von Trierand the field year must exist and have the value 2003.

See the following example of an implicit $and operator:

{
"director": "Lars von Trier",
"year": 2003
}

You can make both the $and operator and the equality operator explicit.

See the following example that uses explicit $and and $eq operators:

{
"$and": [
{
"director": {
"$eq": "Lars von Trier"
}
},
{
"year": {
"$eq": 2003
Review the FAQs in the [Red Hat OpenShift docs](https://docs.openshift.com/container-platform/4.9/storage/persistent_storage/persistent-storage-local.html).
2. Review the [troubleshooting documentation](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-must-gather) to troubleshoot and resolve common issues.
3. Check the status of the IBM Cloud platform and resources by going to the [Status page](https://cloud.ibm.com/status).
4. Review [Stack Overflow](https://stackoverflow.com/questions/tagged/ibm-cloud) to see whether other users experienced the same problem. Tag any questions with ibm-cloud, so that it's seen by the IBM Cloud development teams.
5. If you run into an issue with the Local File Storage Operator, you can open an issue in the [Red Hat Customer Portal](https://access.redhat.com/).
ibmcloud sat location ls
2. Confirm that your host meets the [minimum requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs) and verify that the hostname contains only lowercase alphanumeric characters, -, or ..
3. Check your host for connectivity issues.



1. Log in to your host machine, such as via SSH.
2. Check your [host network settings](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network) to ensure that your host can access the required ports and IP addresses, which might be blocked by a security group or firewall.
3. Check access to the required [IBM Cloud multizone metro endpoints](https://cloud.ibm.com/docs/satellite?topic=satellite-assign-failsendpoints-to-verify).
4. For hosts that are assigned to clusters, get the details of the cluster master endpoint.

ibmcloud ks cluster get -c <cluster_name_or_ID> | grep "Master URL"
5. Check connectivity to the cluster master. If the curl request fails, your host might not have access to the endpoint, such as blocked by a security group, firewall, or private network.

curl -k <master_URL>
6. If you think you might have a webhook in the cluster that block access to the API server, see [Cluster cannot update because of broken webhook](https://cloud.ibm.com/docs/openshift?topic=openshift-webhooks_update). Webhooks are often components for additional capabilities in your cluster, such as Cloud Paks, Istio, or container image security enforcement.



4. After you resolve any connectivity issues, [check the health of your host](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-hosts-debug) for further information.
5. Reassign your hosts if you continue to have issues.



1.
Collections.singletonMap("$in", Arrays.asList(1978, 2009)));

PostExplainOptions explainOptions =
new PostExplainOptions.Builder()
.db("my-movies")
.selector(selector)
.build();

ExplainResult response =
service.postExplain(explainOptions).execute()
.getResult();

System.out.println(response);

import { CloudantV1 } from '@ibm-cloud/cloudant';

const service = CloudantV1.newInstance({});

let selector: CloudantV1.JsonObject = {
Person_name: 'Robert De Niro',
Movie_year: {'$in': [1978, 2009]}
};

service.postFind({
db: 'my-movies',
selector: selector,
}).then(response => {
console.log(response.result);
});

from ibmcloudant.cloudant_v1 import CloudantV1

service = CloudantV1.new_instance()

response = service.post_find(
db='my-movies',
selector={'Person_name': 'Robert De Niro',
'Movie_year': {'$in': (1978, 2009)}}
).get_result()

print(response)

postFindOptions := service.NewPostFindOptions(
"my-movies",
map[string]interface{}{
"Person_name": "Robert De Niro",
"Movie_year": map[string][]interface{}{
"$in": []interface{}{1978, 2009},
},
},
)

findResult, _, err := service.PostFind(postFindOptions)
if err != nil {
panic(err)
}
* [Ingress statuses](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-statusingress_status)
* [Ingress messages](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-statusingress_message)



[Debugging Ingress](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-debug-roks4ingress-debug-roks4)



* [Step 1: Check your app deployment and Ingress resource configuration](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-debug-roks4app-debug-ingress-43)
* [Step 2: Run Ingress tests in the Diagnostics and Debug Tool](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-debug-roks4debug-tool-43)
* [Step 3: Check the health of the Ingress controller](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-debug-roks4errors-43)
* [Step 4: Ping the Ingress subdomain and Ingress controller public IP address](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-debug-roks4ping-43)



[Gathering Ingress logs](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-must-gatheringress-must-gather)

[Classic clusters: Why can't my app connect via Ingress?](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_ingress_failscs_ingress_fails)

[VPC clusters: Why can't my app connect via Ingress?]
* [Logging in to a RHCOS host machine to debug](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-hosts-login-rhcos)
* [Why can't I SSH into my host machines?](https://cloud.ibm.com/docs/satellite?topic=satellite-ssh-login-denied)
* [Why aren't my hosts attaching to my location?](https://cloud.ibm.com/docs/satellite?topic=satellite-host-not-attaching)
* [Why does the host registration script fail?](https://cloud.ibm.com/docs/satellite?topic=satellite-host-registration-script-fails)
* [Why can't I assign hosts to a cluster?](https://cloud.ibm.com/docs/satellite?topic=satellite-assign-fails)
* [Why does host assign fail with a CRI-O error? ](https://cloud.ibm.com/docs/satellite?topic=satellite-host-assign-file-system)
* [Why can't I reuse a host in a different Satellite location?](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-host-reattach-fail)
* [Why can't my HTTP proxy connect to the Red Hat servers?](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-http-proxy)
* [Why do my unassigned hosts have an Unresponsive status?](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-host-unassigned-unknown)
* [Why is my host attach script triggering a state change in Terraform?](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-host-terraform)



* Connectors
The $allMatch operator matches and returns all documents that contain an array field, where all the elements in the array field match the supplied query criteria.

See the following example that uses the $allMatch operator:

{
"genre": {
"$allMatch": {
"$eq": "Horror"
}
}
}





 The $and operator 

The $and operator matches if all the selectors in the array match.

See the following example that uses the $and operator:

{
"selector": {
"$and": [
{
"year": {
"$in": 2014, 2015]
}
},
{
"genre": {
"$all": "Comedy","Short"]
}
}
]
},
"fields": [
"year",
"_id",
"title"
],
"limit": 10
}
Show more





 The $elemMatch operator 

The $elemMatch operator matches and returns all documents that contain an array field with at least one element that matches the supplied query criteria.

See the following example that uses the $elemMatch operator:

{
"selector": {
"genre": {
"$elemMatch": {
"$eq": "Horror"
}
}
},
"fields": [
"title",
"genre"
],
"limit": 10
}





 The $nor operator 

The $nor operator matches if the selector does not match.

See the following example that uses the $nor operator:

{
"selector": {
"year": {
"$gte": 1900,
"$lte": 1910
},
"$nor": [
{ "year": 1901 },
{ "year": 1905 },
{ "year": 1907 }
]
},
"fields": [
Classic: canary traffic originates from the public IP address of one of the worker nodes and arrives to the public IP address of your classic load balancers. Configure your network policies to allow this communication. For more information, see [Controlling traffic with network policies on classic clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-network_policies).







 Next steps 



1. Wait 30 minutes, then run the oc get clusteroperator ingress command and check the MESSAGE column again.
2. If you see a different error message repeat the troubleshooting steps.
3. If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In the case details, be sure to include any relevant log files, error messages, or command outputs.
Warning AnnotationError 2s router-dal10-y2d4359tf4-g4ar7 Failed to apply ingress.bluemix.net/custom-port annotation.
3. Check the Ingress resource configuration file.

oc get ingress -o yaml



1. Ensure that you define a host in only one Ingress resource. If one host is defined in multiple Ingress resources, the Ingress controller might not forward traffic properly and you might experience errors.
2. Check that the subdomain and TLS certificate are correct. To find the IBM provided Ingress subdomain and TLS certificate, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.
3. Make sure that your app listens on the same path that is configured in the path section of your Ingress.
4. Edit your resource configuration YAML as needed. When you close the editor, your changes are saved and automatically applied.

oc edit ingress <myingressresource>



4. Check to see if you reached the maximum number of VPC load balancers permitted per account. Check the [VPC quotas documentation](https://cloud.ibm.com/docs/vpc?topic=vpc-quotas) for VPC resource quotas across all your VPC clusters in your VPC.







 Step 2: Run Ingress tests in the Diagnostics and Debug Tool 

Use the IBM Cloud Kubernetes Service Diagnostics and Debug Tool to run Ingress tests and gather pertinent Ingress information from your cluster. To use the debug tool, you can enable the add-on in your cluster.



1. In the [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift), click the name of the cluster where you want to install the debug tool add-on.
2. On the Diagnostics and Debug Tool card, click Install.
3. In the dialog box, click Install.
5. Review contents of the MESSAGE column and complete the following steps based on your cluster type and error message.



* If you see errors regarding your API key, you can try resetting the API key with the ibmcloud oc api-key reset[command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_api_key_reset).
* Classic: If you see errors regarding your load balancer deployment, ensure your cluster has at least two healthy workers. For more information, see [Adding worker nodes and zones to clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workers).
* Classic: If you see errors saying that no IPs are available, add new portable subnets to the cluster with the ibmcloud oc cluster subnet create[command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_subnet_create).
* VPC: If you see permission issues, review your IAM permissions. For more information, see [Setting up an Application Load Balancer for VPC](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-lbaassetup_vpc_ks_vpc_lb).
* VPC: Ensure that you did not reach your LBaaS instance quota. For more information, see [Quotas and service limits](https://cloud.ibm.com/docs/vpc?topic=vpc-quotasalb-quotas) and ibmcloud is load-balancers[command](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencelb-anchor).



6. Wait 10 to 15 minutes, then check if the load balancer got an address assigned. If not, check the events again.
7. If you see a different error, repeat the troubleshooting steps. If the issue persists, contact support.
* [Target the regional endpoint](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-location-missing-locationts-location-missing-location-target)
* [Ask the location owner to update your permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-location-missing-locationts-location-missing-location-perms)







 Hosts 

[Debugging host health](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-hosts-debugts-hosts-debug)

[Logging in to a RHEL host machine to debug](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-hosts-logints-hosts-login)



* [First boot did not complete successfully](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-hosts-logints-hosts-login-first-boot)
* [Host registration script fails](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-hosts-logints-hosts-login-host-script)
* [Machine cannot be reached on the network](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-hosts-logints-hosts-login-cannot-reach)
* [Host is attempting to register with the location](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-hosts-logints-hosts-login-host-register)



[Logging in to a RHCOS host machine to debug](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-hosts-login-rhcosts-hosts-login-rhcos)



* [Machine cannot be reached on the network](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-hosts-login-rhcosts-hosts-login-cannot-reach-rhcos)
* [Get the details of your persistent volume claims](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-must-gatherstorage-gather-pvc-details)
* [Get the pod logs for your app](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-must-gatherstorage-get-pod-logs)
* [Review the details](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-must-gatherstorage-review-details)
* [Contact Support](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-must-gathercontact-ibm-support)



[Storage error messages](https://cloud.ibm.com/docs/satellite?topic=satellite-debug-storagedebug-storage)



* [Reviewing error messages and logs](https://cloud.ibm.com/docs/satellite?topic=satellite-debug-storagereview-messages-logs-storage)



* [ST0001 error message](https://cloud.ibm.com/docs/satellite?topic=satellite-debug-storagest0001)
* [ST0002 error message](https://cloud.ibm.com/docs/satellite?topic=satellite-debug-storagest0002)
* [ST0003 error message](https://cloud.ibm.com/docs/satellite?topic=satellite-debug-storagest0003)
* [ST0004 error message](https://cloud.ibm.com/docs/satellite?topic=satellite-debug-storagest0004)
* [ST0005 error message](https://cloud.ibm.com/docs/satellite?topic=satellite-debug-storagest0005)
* [ST0006 error message](https://cloud.ibm.com/docs/satellite?topic=satellite-debug-storagest0006)
* Cause: The wrong image pull secret is being used.
* Solution: Complete the following steps during the installation:



* Start installing Watson Discovery.
* After watson-discovery-operator module completes, check if a WatsonDiscovery custom resource is created by running the following command:

oc get WatsonDiscovery wd
* After the custom resource is created, run the following commands to point the correct image pull secret to pull images from the external registry:

pull_secret=$(oc get secrets | grep 'docker-pull-.-watson-discovery-registry-registry' | cut -d ' ' -f 1)
cat << EOS > discovery-patch.yaml
spec:
shared:
imagePullSecret: $pull_secret
EOS
oc patch wd wd --type=merge --patch "$(cat discovery-patch.yaml)"
* If the RabbitMQ pods are still in ImagePullBackoff state, remove the RabbitMQ CR to enable the rabbitmq-operator to re-create the RabbitMQ clusters. You can use the following command:

oc delete IbmRabbitmq wd-rabbitmq





* In IBM Watson® Discovery, the Content Mining project only supports one collection per project. If you create more than one Content Mining collection, you might experience errors. If you experience errors, delete additional Content Mining collections so that each Content Mining project has only one associated collection.
* If you are preparing your Discovery for Cloud Pak for Data clusters for an in-place upgrade of your instance from 2.2.0 to 2.2.1, occasionally, the cpd-cli adm command fails, showing the following error message: Error from server (UnsupportedMediaType): error when applying patch. If you receive this error message, enter oc delete scc cpd-zensys-scc cpd-user-scc cpd-noperm-scc edb-operator-scc admin-discovery-scc to delete the related resources, and re-enter the cpd-cli adm command.