vania-janet/multiturn-rag-retrieval-data huggingface dataset:
(https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-docker-latesttroubleshoot-docker-latest)

[Why do all the tags get deleted when I delete an image?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-rmtroubleshoot-image-rm)

[Why doesn't the retention command show all the images?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-list-retentiontroubleshoot-image-list-retention)

[Why do I get an error when I'm restoring an image?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-restoretroubleshoot-image-restore)

[Why aren't all the tags restored when I restore by digest?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-restore-digesttroubleshoot-image-restore-digest)

[Why do I get a manifest unknown error?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-manifest-unknowntroubleshoot-manifest-unknown)

[Why do I get a manifest type error when I tag my image?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-manifest-error-typetroubleshoot-manifest-error-type)

[Why do I get a manifest version error?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-manifest-error-versiontroubleshoot-manifest-error-version)

[Why do I get a manifest list invalid error?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-manifest-list-errortroubleshoot-manifest-list-error)





 Troubleshooting networking 

[Why can't I access the registry through a custom firewall?]
Lazy evaluation 

Lazy evaluation is an evaluation strategy that delays the evaluation of an expression until its value is needed. When combined with memoization, lazy evaluation strategy avoids repeated evaluations and can reduce the running time of certain functions by a significant factor.

The time series library uses lazy evaluation to process data. Notionally an execution graph is constructed on time series data whose evaluation is triggered only when its output is materialized. Assuming an object is moving in a one dimensional space, whose location is captured by x(t). You can determine the harsh acceleration/braking (h(t)) of this object by using its velocity (v(t)) and acceleration (a(t)) time series as follows:

 1d location timeseries
x(t) = input location timeseries

 velocity - first derivative of x(t)
v(t) = x(t) - x(t-1)

 acceleration - second derivative of x(t)
a(t) = v(t) - v(t-1)

 harsh acceleration/braking using thresholds on acceleration
h(t) = +1 if a(t) > threshold_acceleration
= -1 if a(t) < threshold_deceleration
= 0 otherwise

This results in a simple execution graph of the form:

x(t) --> v(t) --> a(t) --> h(t)

Evaluations are triggered only when an action is performed, such as compute h(5...10), i.e. compute h(5), ..., h(10). The library captures narrow temporal dependencies between time series. In this example, h(5...10) requires a(5...10), which in turn requires v(4...10), which then requires x(3...10). Only the relevant portions of a(t), v(t) and x(t) are evaluated.

h(5...10) <-- a(5...10) <-- v(4...10) <-- x(3...10)
Why is my job run not starting? 

  What’s happening 

A trigger to start a job run fails to start the job run.

  Why it’s happening 

If your job run did not start, check that the quota for your jobs and job runs is not exceeded.

  How to fix it 

Code Engine has quotas for jobs and job runs within a project.

Check that the quota limit for jobs and job runs for your project is not exceeded. You are limited to 100 jobs per project and 100 job runs per project before you need to clean up old ones. See [Limits and quotas for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limits).

Use one of the following ways to check that the quota limit for jobs and job runs is not exceeded.



*  In the CLI, run the [ibmcloud ce jobrun list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-list) command to list all your defined job runs. Run the [ibmcloud ce job list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-list) command to list all your defined jobs.
*  From the console, select your project and then go to the Code Engine Overview page. You can view the number of jobs and job runs for the project in the Summary section. For more details, select Jobs or Job runs from the Summary section or select Jobs from the navigation menu.



If the number of jobs or job runs is near the quota limit, delete job runs and then jobs as needed. See [I'm over my limit for jobs or job runs. How can I delete them?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-jobrun-deleteforquota)

For more information, see [Working with jobs and job runs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-plan) and [Debugging jobs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-job).
Why can't I change signature thresholds? 

You get an error when you try to change the signature threshold or revocation signature threshold. The error can be reported by either the TKE plug-in or the Trusted Key Entry application.

  What’s happening 

You receive an error message similar to the following one:

> FAILED Error reported by EP11 crypto module. Return code: 209 Reason code: 71 Error message: Change not allowed. You are not allowed to change a threshold value if the corresponding attribute control bit is reset.

  Why it’s happening 

The TKE plug-in through version 0.0.11 restricts the ability to set the signature threshold and revocation signature threshold to a value other than one. The restriction can be removed by zeroizing the crypto unit.

  How to fix it 

To set the signature threshold or revocation signature threshold to a value greater than one, [zeroize the crypto unit](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-delete-instancezeroize-crypto-unit-step). This removes the restriction. Then reinstall the administrators that you want to use and set the threshold values by using either the latest version of the TKE plug-in or the Trusted Key Entry application.

Zeroizing a crypto unit clears the master key registers. To fully recover the state of a crypto unit after zeroizing it, you need to reload the master key registers and the administrators. Depending on your loading method, see [Loading master keys with the TKE CLI plug-in](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsmload-master-keys) or [Initializing service instances using smart cards and the Management Utilities](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-management-utilitiesload-master-key-management-utilities) for instructions.
If the 이 character were separated from the following character by a space, it would be replaced by an X, as described in [Numeric redaction results](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-formattingnumeric-redaction-results).









 Numeric redaction results 

The following table shows examples of final transcripts both with and without numeric redaction in each supported language.



Table 5. Numeric redaction example transcripts

 Language Without redaction With redaction 

 US English my credit card number is four one four seven two my credit card number is XXXXX 
 Japanese 私 のクレジット カード 番号 は 四 一 四 七 二です 私 のクレジット カード 番号 は XXXXX です 
 Korean 내 신용 카드 번호는 사 일 사 칠 이 번입니다 내 신용 카드 번호는 XXXXX 번입니다 







 Numeric redaction example 

The following example requests numeric redaction with a recognition request by setting the redaction parameter to true. Because the request enables redaction, the service implicitly enables smart formatting with the request. The service effectively disables the other parameters of the request so that they have no effect: The service returns a single final transcript and recognizes no keywords.

IBM Cloud

curl -X POST -u "apikey:{apikey}" --header "Content-Type: audio/wav" --data-binary @{path}audio-file.wav "{url}/v1/recognize?&redaction=true&max_alternatives=3&keywords=birth%2Cbirthday&keywords_threshold=0.5"

IBM Cloud Pak for Data
For detailed instructions on installing and configuring the Management Utilities, see [Setting up smart cards and the Management Utilities](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-prepare-management-utilities) and [Initializing service instances using smart cards and the Management Utilities](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-management-utilities).





 Smart cards 

A smart card looks like a credit card with an embedded chip. The chip can perform a limited set of cryptographic operations and is loaded with custom software. In the Management Utilities, the Smart Card Utility Program loads custom software on the smart card to create two types of smart cards:



* Certificate authority smart cards - Establish a set of smart cards that can work together, called a smart card zone.
* Enterprise PKCS #11 (EP11) smart cards - Hold an administrator signature key and up to 85 master key parts. With EP11 smart cards, you can sign a command by using a private signature key that is stored on the smart card and encrypt a master key part for delivery to a crypto unit.



Smart cards are protected by a personal identification number (PIN) that must be entered on a smart card reader PIN pad before the smart card performs the operations. The EP11 smart card has a single PIN. The certificate authority smart card has two PINs and both must be entered to enable operations.

On an EP11 smart card, if an incorrect PIN is entered three times, the smart card becomes blocked and can't be used for operations that require PIN entry. An EP11 smart card can be unblocked by using the Smart Card Utility Program. You need the certificate authority smart card that is used to initialize the EP11 smart card to unblock an EP11 smart card. To unblock an EP11 smart card, select EP11 Smart Card > Unblock EP11 smart card from the menu, and follow the prompts.

A certificate authority smart card becomes blocked if an incorrect PIN is entered five times. If a certificate authority smart card becomes blocked, it can't be unblocked.





 Smart card readers
When you are finished updating the settings, click Save Integration.



If you are using Terraform or the API with the OAuth authentication method, switch to using a Personal Access Token (PAT) to provide granular access to a specific user or repo. Authorizing with a PAT is recommended when you use Terraform or the API. Otherwise, you can use the console to authorize IBM Cloud to access your GitHub account:



1. From the IBM Cloud console, click the menu icon ![hamburger icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_hamburger.svg), and select DevOps. On the Toolchains page, locate the toolchain to which you want to add the GitHub tool integration. Click the toolchain to open its Overview page.
2. On the Toolchain's Overview page, click Add.
3. On the Add tool integration page, click the GitHub tool card.
4. On the Configure GitHub page, click Authorize to go to the GitHub website. If you don't have an active GitHub session, you are prompted to log in. Click Authorize IBM-Cloud to allow IBM Cloud to access your GitHub account. You are redirected to the Configure GitHub page.
5. Close the page without taking any further action in the console, and then try to create the GitHub tool integration with Terraform or the API again.







 Why can't I use the Git Repos and Issue Tracking tool integration in my toolchain from one region in a toolchain within a different region? 

You cannot use an instance of Git Repos and Issue Tracking across multiple regions.

 What’s happening 

When I attempt to add the Git Repos and Issue Tracking tool integration to my toolchain, I receive the following error message:

Repository URL is not valid.
Or if the customer is selecting a credit card from options that show only the last four digits, you will need to use the full credit card number to access the account details or complete a transaction.

In this situation, you can write an expression to access the original properties of the selected item:



1. Create or edit a step that comes after the step in which the customer selects from the dynamic options.
2. In the Variable values section, write an expression to assign a value to a session variable. (For more information, see [Using an expression to assign a value to a session variable](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-expressionsexpression-variable).)
3. In the expression editor, type a dollar sign ($) and then select the step in which the customer selected the dynamic option.
4. Use the property name item to represent the selected item, and dot notation to access its properties. For example, the following expression accesses the id property of the item selected in a previous step:

${step_331}.item.id

You can use a complex expression to construct a value using multiple properties of the selected item. For example, you might use an expression such as ${step_123}.item.firstname + " " + ${step_123}.item.lastname to construct a person's full name. Use the expression to define the value in whatever format you need to complete any required action.
Verify that the ibmcloud-object-storage-driver is successfully upgraded. The upgrade is successful when you see daemon set "ibmcloud-object-storage-driver" successfully rolled out in your CLI output.

oc rollout status ds/ibmcloud-object-storage-driver -n ibm-object-s3fs
7. Verify that the IBM Cloud Object Storage pods are in a Running state.

oc get pods -n <namespace> -o wide | grep object-storage



If you're having trouble updating the IBM Cloud Object Storage plug-in, see [Object storage: Installing the Object storage ibmc Helm plug-in fails](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_helm_fails) and [Object storage: Installing the IBM Cloud Object Storage plug-in fails](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_fails).





 Removing the IBM Cloud Object Storage plug-in 

If you don't want to provision and use IBM Cloud Object Storage in your cluster, you can uninstall the ibm-object-storage-plugin and the ibmc Helm plug-in.

Removing the ibmc Helm plug-in or the ibm-object-storage-plugin doesn't remove existing PVCs, PVs, or data. When you remove the ibm-object-storage-plugin, all the related driver pods and daemon sets are removed from your cluster, which means you can't provision new IBM Cloud Object Storage for your cluster unless you configure your app to use the IBM Cloud Object Storage API directly. There is no impact on existing PVCs and PVs.

Before you begin:



* [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).
* Make sure that you don't have any PVCs or PVs in your cluster that use IBM Cloud Object Storage.
The upgrade is successful when you see daemon set "ibmcloud-object-storage-driver" successfully rolled out in your CLI output.

kubectl rollout status ds/ibmcloud-object-storage-driver -n ibm-object-s3fs
7. Verify that the IBM Cloud Object Storage pods are in a Running state.

kubectl get pods -n <namespace> -o wide | grep object-storage



If you're having trouble updating the IBM Cloud Object Storage plug-in, see [Object storage: Installing the Object storage ibmc Helm plug-in fails](https://cloud.ibm.com/docs/containers?topic=containers-cos_helm_fails) and [Object storage: Installing the IBM Cloud Object Storage plug-in fails](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_fails).





 Removing the IBM Cloud Object Storage plug-in 

If you don't want to provision and use IBM Cloud Object Storage in your cluster, you can uninstall the ibm-object-storage-plugin and the ibmc Helm plug-in.

Removing the ibmc Helm plug-in or the ibm-object-storage-plugin doesn't remove existing PVCs, PVs, or data. When you remove the ibm-object-storage-plugin, all the related driver pods and daemon sets are removed from your cluster, which means you can't provision new IBM Cloud Object Storage for your cluster unless you configure your app to use the IBM Cloud Object Storage API directly. There is no impact on existing PVCs and PVs.

Before you begin:



* [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)
* Make sure that you don't have any PVCs or PVs in your cluster that use IBM Cloud Object Storage.
ibmc-s3fs-flex-regional ibm.io/ibmc-s3fs 8m
ibmc-s3fs-standard-cross-region ibm.io/ibmc-s3fs 8m
ibmc-s3fs-standard-perf-cross-region ibm.io/ibmc-s3fs 8m
ibmc-s3fs-standard-perf-regional ibm.io/ibmc-s3fs 8m
ibmc-s3fs-standard-regional ibm.io/ibmc-s3fs 8m
ibmc-s3fs-vault-cross-region ibm.io/ibmc-s3fs 8m
ibmc-s3fs-vault-regional ibm.io/ibmc-s3fs 8m

If you want to set one of the IBM Cloud Object Storage storage classes as your default storage class, run oc patch storageclass <storageclass> -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'. Replace <storageclass> with the name of the IBM Cloud Object Storage storage class.
3. Follow the instructions to [add object storage to your apps](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_apps).



If you're having trouble installing the IBM Cloud Object Storage plug-in, see [Object storage: Installing the Object storage ibmc Helm plug-in fails](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_helm_fails) and [Object storage: Installing the IBM Cloud Object Storage plug-in fails](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_fails).
ibmc-s3fs-flex-regional ibm.io/ibmc-s3fs 8m
ibmc-s3fs-standard-cross-region ibm.io/ibmc-s3fs 8m
ibmc-s3fs-standard-perf-cross-region ibm.io/ibmc-s3fs 8m
ibmc-s3fs-standard-perf-regional ibm.io/ibmc-s3fs 8m
ibmc-s3fs-standard-regional ibm.io/ibmc-s3fs 8m
ibmc-s3fs-vault-cross-region ibm.io/ibmc-s3fs 8m
ibmc-s3fs-vault-regional ibm.io/ibmc-s3fs 8m

If you want to set one of the IBM Cloud Object Storage storage classes as your default storage class, run kubectl patch storageclass <storageclass> -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'. Replace <storageclass> with the name of the IBM Cloud Object Storage storage class.
3. Follow the instructions to [add object storage to your apps](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_apps).



If you're having trouble installing the IBM Cloud Object Storage plug-in, see [Object storage: Installing the Object storage ibmc Helm plug-in fails](https://cloud.ibm.com/docs/containers?topic=containers-cos_helm_fails) and [Object storage: Installing the IBM Cloud Object Storage plug-in fails](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_fails).
See also [different ways to run VMware workloads in IBM Cloud](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-v2t-migrationfaq-v2t-migration-vmware-platforms).





 If I'm using BYOL on my IBM Cloud bare metal hosts, how does it impact the upgrade? 

Upgrading vSphere software is your responsibility. However, with Bring Your Own License (BYOL) you can access VMware Support directly by using your license agreement. IBM Cloud provides support for your bare metal servers infrastructure on IBM Cloud.

For more information about upgrading, see [VMware ESXi upgrade VMware vSphere 6.7](https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-esxi-671-upgrade-guide.pdf) and [vSphere upgrade VMware vSphere 6.5](https://docs.vmware.com/en/VMware-vSphere/6.5/vsphere-esxi-vcenter-server-651-upgrade-guide.pdf). As part of the upgrade planning, consider moving to the IBM Cloud vCenter Server with NSX-T offering, this lift-and-shift upgrade approach might be more beneficial.

See also [different ways to run VMware workloads in IBM Cloud](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-v2t-migrationfaq-v2t-migration-vmware-platforms).





 If I am using BYOL on my VMware Solutions - vCenter Server hosts how does this impact the upgrade? 

Upgrading vSphere software is your responsibility. However, with Bring Your Own License (BYOL) you access VMware Support directly by using your license agreement. IBM Cloud provides support for your bare metal servers infrastructure on the IBM Cloud.
For more information, see [Forwarding Kubernetes API audit logs to an external server](https://cloud.ibm.com/docs/containers?topic=containers-health-auditaudit-api-server-external).



Am I responsible for keeping Fluentd updated?
: To change your logging or filter configurations, the Fluentd logging component must be at the latest version. By default, automatic updates to the add-on are enabled. To disable automatic updates, see [Updating cluster components: Fluentd for logging](https://cloud.ibm.com/docs/containers?topic=containers-updatelogging-up).

Can I forward some logs, but not others, from one source in my cluster?
: Yes. For example, if you have a particularly chatty pod, you might want to prevent logs from that pod from taking up log storage space, while still allowing other pods' logs to be forwarded. To prevent logs from a specific pod from being forwarded, see [Filtering logs](https://cloud.ibm.com/docs/containers?topic=containers-healthfilter-logs).





 Forwarding cluster and app logs 

Create a configuration for cluster and app logging. You can differentiate between the different logging options by using options.

The following table shows the different options that you have when you configure logging and their descriptions.



Table 1. Understanding logging configuration options

 Parameter Description 

 <cluster_name_or_ID> The name or ID of the cluster. 
 --logsource The source that you want to forward logs from. Accepted values are container, application, worker, kubernetes, ingress, and storage. This option supports a comma-separated list of log sources to apply to the configuration. If you don't provide a log source, logging configurations are created for container and ingress log sources. 
 --type syslog The value syslog forwards your logs to an external server. 
 --namespace Optional: The Kubernetes namespace that you want to forward logs from. Log forwarding is not supported for the ibm-system and kube-system Kubernetes namespaces.
Make sure to include the name of your cluster in your toolchain name so that you can easily find the toolchain that is associated with your cluster later. For more information, see [Creating toolchains](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-toolchains_getting_started).
7. Select Delivery Pipeline to review the stages of your continuous integration and continuous delivery pipeline. After you create your toolchain, your pipeline is automatically kicked off and runs through the stages that you configured. Make sure that your stages run successfully and correct any errors.
8. Modify your toolchain. You can add more tools to your toolchain or change the stages of your delivery pipeline.



1. From the [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift), select the cluster for which you want to set up a continuous delivery pipeline.
2. Select the DevOps tab.
3. Select the toolchain that you want to modify.



Having trouble finding the toolchain that you configured for your cluster? If one of the stages in your continuous delivery pipeline fails, the toolchain does not show in the DevOps tab of your cluster. Make sure to review errors in your pipeline by selecting your toolchain from the [Continuous Delivery dashboard](https://cloud.ibm.com/devops/toolchains) directly.