vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* openapi-3.0
* openapi-3.1
* openid-2.0
* openidConnectClient-1.0
* openidConnectServer-1.0
* opentracing-1.0
* osgi.jpa-1.0
* osgiAppIntegration-1.0
* osgiBundle-1.0
* osgiConsole-1.0







 P 



* passwordUtilities-1.0







 R 



* requestTiming-1.0
* restConnector-1.0
* restConnector-2.0
* rtcomm-1.0
* rtcommGateway-1.0







 S 



* samlWeb-2.0
* scim-1.0
* servlet-3.0
* servlet-3.1
* servlet-4.0
* sessionDatabase-1.0
* sipServlet-1.1
* socialLogin-1.0
* spnego-1.0
* springBoot-1.5
* springBoot-2.0
* ssl-1.0







 T 



* timedOperations-1.0
* transportSecurity-1.0







 W 



* wab-1.0
* wasJmsClient-1.1
* wasJmsClient-2.0
* wasJmsSecurity-1.0
* wasJmsServer-1.0
* webCache-1.0
* webProfile-6.0
* webProfile-7.0
* webProfile-8.0
* websocket-1.0
* websocket-1.1
* wmqJmsClient-1.1
* wmqJmsClient-2.0
* wsAtomicTransaction-1.2
* wsSecurity-1.1
From the [IBM Cloud resource list](https://cloud.ibm.com/resources), find the Portworx service that you created.
4. Review the Status column to see if the installation succeeded or failed. The status might take a few minutes to update.
5. If the Status changes to Provision failure, follow the [instructions](https://cloud.ibm.com/docs/openshift?topic=openshift-debug-portworx) to start troubleshooting why your installation failed.
6. If the Status changes to Provisioned, verify that your Portworx installation completed successfully and that all your local disks were recognized and added to the Portworx storage layer.



1. List the Portworx pods in the kube-system project. The installation is successful when you see one or more portworx, stork, and stork-scheduler pods. The number of pods equals the number of worker nodes that are in your Portworx cluster. All pods must be in a Running state.

oc get pods -n kube-system | grep 'portworx|stork'

Example output

portworx-594rw 1/1 Running 0 20h
portworx-rn6wk 1/1 Running 0 20h
portworx-rx9vf 1/1 Running 0 20h
stork-6b99cf5579-5q6x4 1/1 Running 0 20h
stork-6b99cf5579-slqlr 1/1 Running 0 20h
stork-6b99cf5579-vz9j4 1/1 Running 0 20h
stork-scheduler-7dd8799cc-bl75b 1/1 Running 0 20h
stork-scheduler-7dd8799cc-j4rc9 1/1 Running 0 20h
stork-scheduler-7dd8799cc-knjwt 1/1 Running 0 20h
2.
Why do cluster master operations fail due to a broken webhook? 

Virtual Private Cloud

Classic infrastructure

This troubleshooting topic is not for general webhook troubleshooting. See [Debugging webhooks](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-webhook-debug) for webhook problems not related to updating the cluster master.

 What’s happening 

During a master operation such as updating your cluster version, the cluster had a broken webhook application.

Now, master operations can't complete. You see an error similar to the following:

Cannot complete cluster master operations because the cluster has a broken webhook application. For more information, see the troubleshooting docs: 'https://ibm.biz/master_webhook'

 Why it’s happening 

Your cluster has configurable Kubernetes webhook resources, validating or mutating admission webhooks, that can intercept and modify requests from various services in the cluster to the API server in the cluster master.

Because webhooks can change or reject requests, broken webhooks can impact the functionality of the cluster in various ways, such as preventing you from updating the master version or other maintenance operations. For more information, see the [Dynamic Admission Control](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/) in the Kubernetes documentation.

Potential causes for broken webhooks include:



* The underlying resource that issues the request is missing or unhealthy, such as a Kubernetes service, endpoint, or pod.
* The webhook is part of an add-on or other plug-in application that did not install correctly or is unhealthy.
* Your cluster might have a networking connectivity issue that prevents the webhook from communicating with the Kubernetes API server in the cluster master.



 How to fix it 

Identify and restore the resource that causes the broken webhook.



1.
Do not attempt to use Kubernetes commands to remove the node. Instead, it is extremely important that you use the IBM Blockchain Platform console or the APIs to remove the failed node to ensure that the associated metadata and storage are also cleaned up.





 How can I view my smart contract container logs? 

 What’s happening 

You may need to view your smart contract, or chaincode, container logs to debug a smart contract issue.

 How to fix it 

Follow these instructions to view your smart contract container logs on [IBM Cloud](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-manage-consoleibp-console-manage-console-container-logs).





 Why is my CA, peer, or ordering node that is configured to use HSM not working? 

 What’s happening 

This problem can happen when you try to deploy a CA, peer, or ordering node that is configured with HSM and the deployment fails. Or it can surface when a node that is configured for HSM stops working. The node, client, or SDK logs contain the following error:

{"code":1000,"message":"Private key not found [pkcs11: 0x30: CKR_DEVICE_ERROR]"}"

or

{"code":1000,"message":"Private key not found [pkcs11: 0xB3: CKR_SESSION_HANDLE_INVALID]"}"

 Why it’s happening 

This problem happens when the PKCS #11 proxy that is associated with the HSM is unreachable due to a network problem or if the proxy restarts after the node has connected to it.

 How to fix it 

To re-establish communications between the node and the proxy, restart the failing node by deleting the pod associated with the node. A new pod will be created and the connection with the PKCS #11 proxy is restored. Use the following steps to restart the failing node:



* List the pods: kubectl get pods -n <NAMESPACE>
* Delete the pod: kubectl delete pod -n <NAMESPACE> <PODNAME>



Replace:
pods/attach <br><br> * <br><br><br> create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 pods/exec <br><br> * <br><br><br> create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 pods/log get, list, watch get, list, watch get, list, watch 
 pods/portforward <br><br> * <br><br><br> create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 pods/proxy <br><br> * <br><br><br> create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 pods/status get, list, watch get, list, watch get, list, watch 
 replicasets.apps get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 replicasets.apps/scale get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 replicasets.extensions get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 replicasets.extensions/scale get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch
./uninstall.sh --mode uninstallEverything --kubeconfigPath /.kube/config --cloudpakNamespace <project_name>

5. Verify that IBM Cloud Pak for Multicloud Management is uninstalled by accessing the OpenShift web console and verifying that the IBM Cloud Pak for Multicloud Management components such as the pods and resources are no longer available.

 Troubleshooting

 Take action page is not displaying data.

To solve this issue, complete the instructions in [Take Action pages show no data](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.3.0/mcm/troubleshoot/troubleshoot_takeactions.html).
Why am I seeing egress connection failures from pods? 

Virtual Private Cloud Gen 2

Egress connections from pods in your IBM Cloud Kubernetes Service version 1.24 are failing.

If you have a LoadBalancer in your cluster of type NLB with the annotation service.kubernetes.io/ibm-load-balancer-cloud-provider-enable-features: "nlb" and are running IBM Cloud Kubernetes Service version 1.24 earlier, then your pod-network pod egress connections might infrequently chose one of the NodePorts that your NLB is using, which creates a conflict and causes that egress connection to fail.

Update the pod natPortRange in Calico to 32768 - 65535 so it doesn't conflict with the NodePort range of 30000 - 32767.

Run the following command to patch the Calico natPortRange. This change takes effect immediately.

calicoctl patch felixconfiguration default --patch '{"spec":{"natPortRange": "32768:65535"}}'

Check whether the egress connections for pods are successful. 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.
You can learn more about data type [encoding and decoding for compatibility with external representations such as JSON](https://developer.apple.com/documentation/foundation/archives_and_serialization/encoding_and_decoding_custom_types).

Example

struct Input: Codable {
let name: String?
}
struct Output: Codable {
let greeting: String
}
func main(param: Input, completion: (Output?, Error?) -> Void) -> Void {
let result = Output(greeting: "Hello (param.name ?? "stranger")!")
print("Log greeting:(result.greeting)")
completion(result, nil)
}

This example takes an input parameter as Codable Input with field name, and returns a Codable output with a field greetings.



 Handling errors in Swift 

By using the Codable completion handler, you can pass an error to indicate a failure in your action. [Error handling in Swift](https://docs.swift.org/swift-book/LanguageGuide/ErrorHandling.html) resembles exception handling in other languages, with the use of the try, catch, and throw keywords.

The following snippet shows an example of handling an error.

enum VendingMachineError: Error {
case invalidSelection
case insufficientFunds(coinsNeeded: Int)
case outOfStock
}
func main(param: Input, completion: (Output?, Error?) -> Void) -> Void {
// Return real error
do{
throw VendingMachineError.insufficientFunds(coinsNeeded: 5)
} catch {
completion(nil, error)
}
}







 Packaging a Swift 4.2 file 

Compile a single source file that doesn't depend on external libraries. Use the flag -compile with the name of the main method.

Before you begin



* [Install Docker](https://hub.docker.com/search/?offering=community&type=edition).
Change log for master fix pack 1.25.2_1517 and worker node fix pack 1.25.2_1516, released 6 October 2022 



Changes since version 1.24.6_1538 master and 1.24.6_1539 worker node.

 Component Previous Current Description 

 Calico v3.23.3 v3.24.1 See the [Calico release notes](https://docs.tigera.io/archive/v3.24/release-notes/). In addition, a defaultFelixConfiguration resource is created if it doesn't exist. The resource has natPortRange set to 32768:65535. For more information, see [Why am I seeing SNAT port issues and egress connection failures?](https://cloud.ibm.com/docs/containers?topic=containers-ts-network-snat-125) 
 CoreDNS 1.9.3 1.10.0 See the [CoreDNS release notes](https://github.com/coredns/coredns/blob/v1.10.0/notes/coredns-1.10.0.md). 
 IBM Cloud Controller Manager v1.24.5-1 v1.25.2-2 Updated to support the Kubernetes 1.25.2 release and Go version 1.19.1. 
 Kubernetes v1.24.6 v1.25.2 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.25.2). 
 Kubernetes admission controllers configuration N/A N/A Enabled the PodSecurity and removed the PodSecurityPolicy admission controllers. [Pod Security Policies](https://kubernetes.io/docs/concepts/security/pod-security-policy/) were removed in Kubernetes version 1.25.
* type: describes the current status of the component



* Deploying: component pod(s) spinning up but not yet running and ready
* Deployed: component pod(s) are running
* Precreated: (specific to the Orderer) Orderer is waiting for the genesis block to be created
* Error: component hit an error during reconcile, or a certificate has expired
* Warning: one or more of the component's certificate will be expiring within 30 days (by default)
* Initializing: component is being reconciled again due to spec updates in the pre-reconcile checks









 Do you support using certificates from non-IBM Certificate Authorities? 

Yes, you can bring your own certificates if they are issued by a CA that is X.509 compliant. The CA should sign by using ECDSA and the defaults should be set to use P256 curve. See this topic about [Using certificates from an external CA with your peer or ordering node](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-third-party-ca).





 What is the recommended way to manage private keys? 

Because private keys are not stored by the platform, users are responsible for downloading and securing their private key. Therefore, when a higher level of security is required for private keys, an HSM is recommended. An HSM is a hardware appliance that performs cryptographic operations and provides the capability to ensure that the cryptographic keys never leave the HSM. Hyperledger Fabric supports HSM devices that implement the PKCS #11 standard. PKCS #11 is a cryptographic standard for secure operations, generation, and storage of keys. See [Configuring a node to use a Hardware Security Module (HSM)](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-cfg-hsm) to learn more.





 Can I integrate my corporate LDAP server with the Certificate Authority (CA) in the IBM Blockchain Platform?
./uninstall.sh --mode uninstallEverything --kubeconfigPath /.kube/config --cloudpakNamespace <project_name>

5. Verify that IBM Cloud Pak for Multicloud Management is uninstalled by accessing the OpenShift web console and verifying that the IBM Cloud Pak for Multicloud Management components such as the pods and resources are no longer available.

 Troubleshooting

 Take action page is not displaying data.

To solve this issue, complete the instructions in [Take Action pages show no data](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.1.0/mcm/troubleshoot/troubleshoot_takeactions.html).
Why does my app pod fail with an Operation not permitted error? 

Virtual Private Cloud

Classic infrastructure

  What’s happening 

When you create a PVC, you see an error message similar to the following:

EPERM: operation not permitted

  Why it’s happening 

IAM has introduced a refresh_token_expiration key which causes an issue with the IAM credential response parser, where the parser was not able to differentiate between expiration and refresh_token_expiration.

This issue is resolved in the [community repo](https://github.com/s3fs-fuse/s3fs-fuse/pull/1421) and in the IBM Cloud Object Storage plug-in.

  How to fix it 

Complete the steps to [update your IBM Cloud Object Storage plug-in to the latest version](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_installupdate_cos_plugin).
* The webhook is part of an add-on or other plug-in application that did not install correctly or is unhealthy.
* Your cluster might have a networking connectivity issue that prevents the webhook from communicating with the Kubernetes API server in the cluster master.



 How to fix it 

Identify and restore the resource that causes the broken webhook.



1. Create a test pod to get an error that identifies the broken webhook. The error message might have the name of the broken webhook. If the webhook test passes, then the failure may have been temporary and can be retried.

kubectl run webhook-test --image registry.ng.bluemix.net/armada-master/pause:3.2 -n ibm-system

In the following example, the webhook is trust.hooks.securityenforcement.admission.cloud.ibm.com.

Error from server (InternalError): Internal error occurred: failed calling webhook "trust.hooks.securityenforcementadmission.cloud.ibm.com": Post https://ibmcloud-image-enforcement.ibm-system.svc:443/mutating-pods?timeout=30s: dialtcp 172.21.xxx.xxx:443: connect: connection timed out
2. Get the name of the broken webhook.



* If the error message has a broken webhook, replace trust.hooks.securityenforcement.admission.cloud.ibm.com with the broken webhook that you previously identified.

kubectl get mutatingwebhookconfigurations,validatingwebhookconfigurations -o jsonpath='{.items[?(@.webhooks].name=="trust.hooks.securityenforcement.admission.cloud.ibm.com")].metadata.name}{"n"}'

Example output

image-admission-config
* If the error does not have a broken webhook, list all the webhooks in your cluster and check their configurations in the following steps.
if err != nil {
panic(err)
}
b, _ := json.MarshalIndent(scanResult, "", " ")
fmt.Println(string(b))

const params = {
query: 'GST-sdk-',
fields: [''],
searchCursor: searchCursor,
};

globalSearchService.search(params)
.then(res => {
console.log(JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});
For more information, see [Using audio formats](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-audio-formats).

HTTP and WebSocket interfaces can now return warnings
: The HTTP and WebSocket /v1/synthesize methods can return a warnings response that includes messages about invalid query parameters or JSON fields that are included with a request. The format of the warnings changed. The following example shows the previous format:

"warnings": "Unknown arguments: [u'{invalid_arg_1}', u'{invalid_arg_2}']."

The same warning now has the following format:

"warnings": "Unknown arguments: {invalid_arg_1}, {invalid_arg_2}."





 10 March 2016 

Synthesis methods can now return warnings
: The GET and POST /v1/synthesize methods can now return a Warnings response header that includes a list of warning messages about invalid query parameters or JSON fields that are included with the request. Each element of the list includes a string that describes the nature of the warning followed by an array of invalid argument strings; for example, Unknown arguments: [u'{invalid_arg_1}', u'{invalid_arg_2}']. For more information, see the [API & SDK reference](https://cloud.ibm.com/apidocs/text-to-speech).

Beta Apple iOS SDK is deprecated
: The beta Watson Speech Software Development Kit (SDK) for the Apple® iOS operating system is deprecated and replaced by the Watson Swift SDK. The new SDK is available from the [swift-sdk repository](https://github.com/watson-developer-cloud/swift-sdk) in the watson-developer-cloud namespace on GitHub.





 22 February 2016 

New expressive SSML feature
: The service was updated with a new expressive SSML feature. The service extends SSML with an <express-as> element that you can use to indicate expressiveness in one of three speaking styles: GoodNews, Apology, or Uncertainty.
So, make sure that the cache file created by the SDK is always stored in persistent volume by providing the correct absolute path of the persistent directory.





 Offline options 

The SDK is also designed to serve configurations, perform feature flag and property evaluations without being connected to App Configuration service.

appConfigClient.setContext(collectionId, environmentId, {
bootstrapFile: 'saflights/flights.json',
liveConfigUpdateEnabled: false
})

Where:



* bootstrapFile: Absolute path of the JSON file, which contains configuration details. Make sure to provide a proper JSON file. You can generate this file by using ibmcloud ac config command of the IBM Cloud App Configuration CLI.
* liveConfigUpdateEnabled: Live configuration update from the server. Set this value to false if the new configuration values are not to be fetched from the server.







 Examples for using feature and property-related APIs 

See the following examples for using the feature-related APIs.



 Get single feature 

const feature = appConfigClient.getFeature('feature_id'); // feature can be null incase of an invalid feature id

if (feature !== null) {
console.log(Feature Name ${feature.getFeatureName()} );
console.log(Feature Id ${feature.getFeatureId()} );
console.log(Feature Type ${feature.getFeatureDataType()} );
if (feature.isEnabled()) {
// feature flag is enabled
} else {
// feature flag is disabled
}
}





 Get all features 

const features = appConfigClient.getFeatures();
const feature = features['feature_id'];

if (feature !== null) {
console.log(Feature Name ${feature.getFeatureName()} );
console.log(Feature Id ${feature.getFeatureId()} );
2022-09-08 07:13:19.719 [WARNING] startup/utils.go 228: Failed to set NetworkUnavailable; will retry error=Patch "https://172.21.0.1:443/api/v1/nodes/10.242.64.17/status?timeout=2s": net/http: request canceled (Client.Timeout exceeded while awaiting headers)



 Workarounds for calico-node 

You can use one of the following methods to work around the issue and get the calico-node pod running again.



1. Remove the sysdig-admission-controller-webhook from the system.
2. Modify the sysdig-admission-controller-webhook and change the timeout to be less than 2 seconds.
3. Modify the sysdig-admission-controller-webhook to scope it to the appropriate namespaces, and avoid system-critical namespaces such as calico-system.
4. Cordon the new node but don't drain it. Delete the VPN pod and wait for it to start on another worker. Uncordon the node.



After performing any of the previous workarounds, the calico-node pod can start successfully.
For example, where user@email.com is your GnuPG email address, bluebird:build1 is your repository and tag, and us.icr.io/birds/bluebird:build1 is the name of your image.

skopeo --insecure-policy copy --sign-by user@email.com docker-daemon:bluebird:build1 docker://us.icr.io/birds/bluebird:build1

On macOS, if you get the error Error copying image to the remote destination: Error writing signatures: mkdir /var/lib/containers/sigstore: permission denied, override the internal default for registry configuration so that the correct signature storage is used by running the command with the --registries.d option.

skopeo --registries.d . --insecure-policy copy --sign-by user@email.com docker-daemon:us.icr.io/birds/bluebird:build1 docker://us.icr.io/birds/bluebird:build1



On Linux® and macOS, the default configuration for the tools is to store the signatures locally. Storing signatures locally can lead to signature verification failure because the signature is not in the registry. To fix this problem, you can modify or delete the configuration file. On Linux®, the configuration is saved in /etc/containers/registries.d/default.yaml. On macOS, the configuration file is saved in /usr/local/etc/containers/registries.d/default.yaml. On macOS, when Skopeo is installed by using the [Homebrew](https://brew.sh/) package manager, the configuration file might be at /opt/homebrew/Cellar/etc/containers/registries.d/default.yaml for Apple silicon, or /usr/local/Cellar/etc/containers/registries.d/default.yaml for Intel.





 Using Podman to sign images 

You can use Podman to sign images. For more information, see [Podman](https://podman.io/).





 Signing images by using the Red Hat OpenShift CLI