vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Currently the cloud host migration is not mandatory and there is not an exact date about when the old domain will be out of support, but once this is settled, the customer who are still using the old domain name will be notified.

For gateway authentication endpoint, currently bluemix.net has been deprecated, if you are using REST API or SDK, please ensure you are connecting to [new endpoints](https://cloud.ibm.com/apidocs/secure-gatewayintro) instead of bluemix.net. For Secure Gateway Client, please ensure your Secure Gateway Client does not fall more than 3 versions behind.
* Where can I receive Secure Gateway notifications, especially for disruptive maintenance?

You can get notifications via our [status page](https://cloud.ibm.com/status?selected=maintenance).



* To get the notifications about completed disruptive maintenance, please search Secure Gateway in the tab [History](https://cloud.ibm.com/status?query=Secure+Gateway&selected=history).
* To get the notifications about on going or planned disruptive maintenance, please search Secure Gateway in the tab [Planned maintenance](https://cloud.ibm.com/status?query=Secure+Gateway&selected=maintenance).



When the Secure Gateway client disconnected unexpectedly, please go to the status page to check whether there is disruptive maintenance at that time.
* How can we avoid manually restart after the disruptive maintenance?

If the maintenance needs to have disruption over 10 minutes, then you might need to manually restart the Secure Gateway client to reconnect to the Secure Gateway server after the maintenance. In this case, you can use the [startup options](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-client-interactingstartup-args)--service when starting up the Secure Gateway client, such that the parent process of the Secure Gateway client will restart within 60s if all child clients are terminated. Beside that, you can also use the startup options --reconnect to define the reconnect attempts after the connection between Secure Gateway client and Secure Gateway server drop, --reconnect='-1' means retry forever.
There was a request to delete a subnet, but the subnet still has resources in it. Subnets may have instances, VPNs, load balancers, or public gateways in them. You must delete your resources in the subnet before you can delete the subnet.

In some situations, this error can occur even when the console shows 0 VSIs and 0 load balancers. Deletion is asynchronous, and it may take a few minutes for the internal status to change. Try your subnet deletion again in a few minutes.

If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 subnet_not_empty_pgway_exists 

Message: Cannot delete the subnet while it is attached to a public gateway. Detach the public gateway and retry.

There was a request to delete a subnet, but the subnet still has a public gateway attached to it. You must delete or detach the public gateway before you can delete the subnet.

If using the CLI, you can run ibmcloud is public-gateways to list the public gateways and ibmcloud is subnet-public-gateway-detach to detach a public gateway from a subnet.

If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 subnet_not_empty_iks_worker_node_exists 

Message: Cannot delete the subnet while it is in use by IBM Cloud Kubernetes Service. Please remove Kubernetes worker nodes from the subnet and retry.

There was a request to delete a subnet, but the subnet still has some IKS worker nodes on it. You must delete the IKS worker nodes before you can delete the subnet.

The value field inside the error message should contain the ID list of IKS clusters that are on the subnet.
The HTTP 400 Bad Request response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

The client should not repeat this request without modification.





 Context 

The create instance policy request fails because the same policy was specified more than once.

You may specify multiple policies in the request as long as each policy is unique. For example, you could create instance policies for dualAuthDelete and allowedIP in the same request.



 Example 

This request fails because more than one instance policy was provided.

 this request fails because the dualAuthDelete policy was specified more than once
$ curl -X PUT "https://us-south.kms.cloud.ibm.com/api/v2/instance/policies?policy=dualAuthDelete" -H "authorization: Bearer $ACCESS_TOKEN" -H "bluemix-instance: $KP_INSTANCE_ID" -H "content-type: application/vnd.ibm.kms.policy+json" -d '{
"metadata": {
"collectionType": "application/vnd.ibm.kms.policy+json",
"collectionTotal": 2
},
"resources": [
{
"policy_type": "dualAuthDelete",
"policy_data": {
"enabled": false
}
},
{
"policy_type": "dualAuthDelete",
"policy_data": {
"enabled": false
}
}
]
}'
Show more



 JSON response 

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.error+json",
"collectionTotal": 1
},
"resources": [
{
"errorMsg": "Bad Request: Instance policy could not be created. Please see reasons for more details.",
"reasons":
{
Why does the host registration script fail? 

 What’s happening 

When you SSH into your own infrastructure machine that you want to attach as a Satellite host and run the host registration script, you see a message similar to the following example.

No package rh-python36 available.
Error: Nothing to do

 Why it’s happening 

Your machine does not meet the minimum requirements to become a Satellite host. In particular, you must have the following packages installed on your RHEL 7 or 8 machine.

For RHEL 7

Repository 'rhel-server-rhscl-7-rpms' is enabled for this system.
Repository 'rhel-7-server-optional-rpms' is enabled for this system.
Repository 'rhel-7-server-rh-common-rpms' is enabled for this system.
Repository 'rhel-7-server-supplementary-rpms' is enabled for this system.
Repository 'rhel-7-server-extras-rpms' is enabled for this system.

For RHEL 8

Repository 'rhel-8-for-x86_64-appstream-rpms' is enabled for this system.
Repository 'rhel-8-for-x86_64-baseos-rpms' is enabled for this system.

 How to fix it 

To resolve this issue, follow these steps.



1. Add the required packages to your machine. For example, in IBM Cloud infrastructure you can run the following commands to add the required packages. For cloud provider-specific configurations, see [Cloud infrastructure providers](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-plan).



1. Refresh the Red Hat packages on your machine.

subscription-manager refresh

If you see an error such as Network error, unable to connect to server. Please see /var/log/rhsm/rhsm.log for more information., check the security group and other network settings for your machine to make sure that you have connectivity to the internet.
2. Enable the package repositories on your machine. For example, enable RHEL 8 package requirements.
disable the instance dual authorization policy
$ ibmcloud kp instance policy-update dual-auth-delete --disable

Updating instance policy...
OK

 attempt to delete the key - this fails because the key policy
 does not change when the instance policy is updated
$ ibmcloud kp key delete 6a8a129b-0cd4-4667-ba57-b355a125a7ca

Deleting key: 6a8a129b-0cd4-4667-ba57-b355a125a7ca, from instance: a192d603-0b8d-452f-aac3-f9e1f95e7411...
FAILED
kp.Error:
correlation_id='cbc0d18b-a816-45ab-af6a-b8e18dc3e628',
msg='Conflict: 1 prior authorization(s) are required for deletion: Key could not be deleted. Please see "reasons" for more details.',
reasons='[AUTHORIZATIONS_NOT_MET: Number of authorizations required to delete is not met -
FOR_MORE_INFO_REFER: https://cloud.ibm.com/apidocs/key-protect]'







 Required parameters 



* -d, --disable
* -e, --enable

Disable or enable the dual authorization policy. One option is required.
* -i, --instance-ID

The IBM Cloud instance ID that identifies your Key Protect instance.

You can set an environment variable instead of specifying -i with the following command: $ export KP_INSTANCE_ID=<INSTANCE_ID>.









 kp key alias-create 

Creates an alias for a key and displays the output in JSON format. Aliases can be used as reference in methods that accept a key ID. Each alias is unique only within the given instance and is not reserved across the Key Protect service. Each key can have up to five aliases. There is no limit to the number of aliases per instance.
Using Kubernetes with Code Engine 

IBM Cloud® Code Engine is designed so that you do not need to interact with the underlying technology it is built upon. However, if you have existing tools that are based on Kubernetes or Knative, you can still use it with Code Engine. Code Engine supports the Kubernetes (and Knative) APIs and their CLI commands. For more information about Knative, see [Using Knative with Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-knative).

If you decide to use Kubernetes with Code Engine, consider the following:



* Most containers or pods that run on Kubernetes also run on Code Engine.
* Kubernetes constructs, such as deployments, run on Code Engine if they do not use cluster-wide capabilities, such as security policies. Code Engine is scoped to what can run in a Kubernetes namespace.



Code Engine does not support OpenShift-specific resources or other container orchestration platforms, such as Docker Swarm or Compose Swarm.



 Installing the Kubernetes command-line interface 

To install the Kubernetes CLI, download and install the [kubectl CLI](https://kubernetes.io/docs/tasks/tools/install-kubectl/).

Be sure to add the kubectl binary to your system's PATH environment variable.





 Interacting with Kubernetes API 

To interact with your project from the Kubernetes command-line interface, kubectl, or with Knative, kn you must set up your environment to interact with the Kubernetes API of Code Engine.

Before you begin



* You must [create your project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-projectcreate-a-project) and the project must be in active status.
4. Add the following information to the description: Please set up the network to allow capacity aggregation on the public and private VLANs associated with my account. This is related to https://cloud.ibm.com/docs/containers?topic=containers-loadbalancer-v2ipvs_provision, and is needed so I can configure NLB v2.0 LoadBalancers in my Classic Kubernetes Cluster.. Note that if you want to allow capacity aggregation on specific VLANs, such as the public VLANs for one cluster only, you can specify those VLAN IDs in the description.
5. Click Submit.



2. Enable a [Virtual Router Function (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) for your IBM Cloud infrastructure account. To enable VRF, see [Enabling VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf). To check whether a VRF is already enabled, use the ibmcloud account show command. If you can't or don't want to enable VRF, enable [VLAN spanning](https://cloud.ibm.com/docs/vlans?topic=vlans-vlan-spanningvlan-spanning). When a VRF or VLAN spanning is enabled, the NLB 2.0 can route packets to various subnets in the account.
3. If you use [Calico pre-DNAT network policies](https://cloud.ibm.com/docs/containers?topic=containers-network_policiesblock_ingress) to manage traffic to an NLB 2.0, you must add the applyOnForward: true and doNotTrack: true fields to and remove the preDNAT: true from the spec section in the policies. applyOnForward: true ensures that the Calico policy is applied to the traffic as it is encapsulated and forwarded.
Unsupported: Beta version of Lease API Migrate manifests and API clients to use the coordination.k8s.io/v1 API version, available since Kubernetes version 1.14. For more information, see [Kubernetes API and Feature Removals In 1.22: Here’s What You Need To Know](https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/). 
 Unsupported: Beta versions of Ingress API Migrate manifests and API clients to use the networking.k8s.io/v1 API version, available since Kubernetes version 1.19. For more information, see [Kubernetes API and Feature Removals In 1.22: Here’s What You Need To Know](https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/). 
 Unsupported: IBM Cloud Kubernetes Ingress Controller As of 1 Jun 2021, the IBM Cloud Kubernetes Ingress Controller is no longer supported on IBM Cloud Kubernetes Service. Migrate your IBM Cloud Kubernetes Ingress Controller based ALBs to the Kubernetes Ingress Controller. 
 Ingress Kubernetes 1.22 supports Ingress and IngressClass resources with networking.k8s.io/v1 version, which is only available on Kubernetes Ingress Controller version 1.0.0 and newer. Kubernetes Ingress Controller version 1.0.0 is supported on IBM Cloud Kubernetes Service cluster versions 1.19 or newer.<br><br><br><br> * Cluster versions 1.19, 1.20, and 1.21: Ingress and IngressClass resources that were created on clusters that run on Kubernetes versions 1.19, 1.20 or 1.21 and Ingress Controller version 1.0.0 are automatically updated during the cluster update to 1.22.
Administering your console 

ATTENTION!! IBM Blockchain Platform SaaS Edition is being replaced by IBM Support for Hyperledger Fabric!! IBM Blockchain Platform SaaS Edition will no longer be supported after July 31, 2023. Customers have been directed to migrate their networks by July 31, 2023. After this date, IBM Blockchain Platform SaaS networks that are not migrated to IBM Support for Hyperledger Fabric will be at risk for potential security vulnerabilities. A migration tool is provided from your console, and the disruption to your network is minimal. See [Migrating to IBM Support for Hyperledger Fabric](https://cloud.ibm.com/docs/blockchain?topic=blockchain-migrating-to-hlf-support) for details.

There are various actions that you can take to manage your console behavior. This topic describes actions outside of the blockchain node operations that aid you in your day-to-day usage of the console.

Target audience: This topic is designed for network operators who are responsible for creating, monitoring, and managing the blockchain network.



 Refreshing your console 

If you are having trouble connecting to your console after you click Launch the IBM Blockchain Platform on the Welcome back panel, or recently upgraded your OpenShift Container platform 3.11 to 4.x, the Refresh cluster button is a useful mechanism to renew the connection between your console and your Kubernetes cluster on IBM Cloud. It can also be used to upgrade to a newer release of the console, if one is available.

To access this button:



1. Log in to IBM Cloud and open [IBM Cloud Resource list](https://cloud.ibm.com/resources). Ensure that you log in with your IBM ID.
2. Your IBM Blockchain Platform service instance is visible under the Services twistie. Locate and click the IBM Blockchain Platform service instance that you deployed.
3. On the Welcome Back panel, click Refresh cluster. The operation could take a few minutes while it re-establishes connectivity to your Kubernetes cluster and refreshes the management console.
4. Click Launch IBM Blockchain Platform again.
To obtain access to the Client Communication Center, follow the steps in the following link to submit an Access Request: [How to Request CCC Access](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-ssphow-to-request-ccc-access)

Please note an an IBMid and password is required to access the Client Communication Center. If you do not have an IBMid, please sign up for one at:

[https://www.ibm.com/account/us-en/signup/register.html](https://www.ibm.com/account/us-en/signup/register.html)

Once the IBMid is activated you will receive an email confirmation.

If you have any questions or concerns regarding this process please open a [Support Case](https://www.ibm.com/mysupport).





 Notifications 

Once you are able to login to the CCC portal, you can sign up to receive notifications directly via or email or RSS Feed. Further information is provided below.

Email Subscription Important Notes:



* Users who are granted access to the Client Communication Center portal are automatically subscribed to all notifications.
* Select the E-Mail Subscription button (in the upper right hand corner) to subscribe to notification emails (announcements).
* Enter the email address for the user(s) who should receive email notifications. This option is provided to enable other members of your organization to still receive email announcements although they may not require access to the Client Communication Center portal.
* All emails referenced must be associated with an [IBMid](https://www.ibm.com/account/us-en/signup/register.html)
* Multiple email addresses can be specified, separated by comma.
* All announcement categories (Alert, Announcement, Incident, Maintenance, Security) are selected by default. Click the down arrow on the Subscribe to field to uncheck any announcement types you do not wish to receive. For a description of the announcement categories, see the table below. All recipients entered in the Email field will receive the selected types.
* Read the Privacy Policy terms
* Select the Subscribe button
Service Description 

Below is the link to the current Service Description for TRIRIGA Application Suite Managed Service.

[TAS MS Service Description](https://www.ibm.com/support/customer/csol/terms/?ref=i126-9227-01-10-2021-zz-en)

If you have previously downloaded this, please check regularly as it is updated periodically and the current service description takes precedent.
The target Kubernetes cluster is configured during the toolchain setup by using your IBM Cloud API key and your Kubernetes cluster name. You can change these settings later by updating the Delivery Pipeline configuration. Any code that is merged into the target Git repo branch is automatically built, validated, and deployed into the Kubernetes cluster.

To create a Deploy your application to multiple clusters toolchain, click

[![Create toolchain](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/create_toolchain_button.png)](https://cloud.ibm.com/devops/setup/deploy?repository=https%3A%2F%2Fus-south.git.cloud.ibm.com%2Fopen-toolchain%2Fsatellite-cd-toolchain&env_id=ibm:yp:us-south)

Alternatively, 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, click Create a Toolchain. On the Create a Toolchain page, click Deploy your application to multiple clusters.



 Review the Welcome page 

Before you start to set up your toolchain, review the prerequisites to discover what items you must first provision and configure. In the Description section, you can access an overview of the toolchain.

Zoom

!
* [osa](https://cloud.ibm.com/docs/containers?topic=containers-classic-flavorsosa)
* [par](https://cloud.ibm.com/docs/containers?topic=containers-classic-flavorspar)
* [sao](https://cloud.ibm.com/docs/containers?topic=containers-classic-flavorssao)
* [sjc](https://cloud.ibm.com/docs/containers?topic=containers-classic-flavorssjc)
* [sng](https://cloud.ibm.com/docs/containers?topic=containers-classic-flavorssng)
* [syd](https://cloud.ibm.com/docs/containers?topic=containers-classic-flavorssyd)
* [tok](https://cloud.ibm.com/docs/containers?topic=containers-classic-flavorstok)
* [tor](https://cloud.ibm.com/docs/containers?topic=containers-classic-flavorstor)
* [wdc](https://cloud.ibm.com/docs/containers?topic=containers-classic-flavorswdc)







 FAQs 

[FAQs](https://cloud.ibm.com/docs/containers?topic=containers-faqsfaqs)



* [What is Kubernetes?](https://cloud.ibm.com/docs/containers?topic=containers-faqskubernetes)
* [How does IBM Cloud Kubernetes Service work?](https://cloud.ibm.com/docs/containers?topic=containers-faqskubernetes_service)
* [Why should I use IBM Cloud Kubernetes Service?](https://cloud.ibm.com/docs/containers?topic=containers-faqsfaq_benefits)
* [Can I get a free cluster?](https://cloud.ibm.com/docs/containers?topic=containers-faqsfaq_free)
Why do I see wrong credentials or access denied messages when I create a PVC? 

Virtual Private Cloud

Classic infrastructure

  What’s happening 

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

SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. For more information, see REST Authentication and SOAP Authentication for details.

AccessDenied: Access Denied status code: 403

CredentialsEndpointError: failed to load credentials

InvalidAccessKeyId: The AWS Access Key ID you provided does not exist in our records

can't access bucket <bucket_name>: Forbidden: Forbidden

  Why it’s happening 

The IBM Cloud Object Storage service credentials that you use to access the service instance might be wrong, or allow only read access to your bucket.

  How to fix it 

Create a new secret.



1.  In the navigation on the service details page, click Service Credentials.
2.  Find your credentials, then click View credentials.
3.  In the iam_role_crn section, verify that you have the Writer or Manager role. If you don't have the correct role, you must create new IBM Cloud Object Storage service credentials with the correct permission.
4.  If the role is correct, verify that you use the correct access_key_id and secret_access_key in your Kubernetes secret.
5.  [Create a new secret with the updated access_key_id and secret_access_key](https://cloud.ibm.com/docs/containers?topic=containers-storage-cos-understandcreate_cos_secret).
Why do I see wrong credentials or access denied messages when I create a PVC? 

Virtual Private Cloud

Classic infrastructure

This troubleshooting topic applies only to Red Hat OpenShift clusters that run version 3.11.

  What’s happening 

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

SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. For more information, see REST Authentication and SOAP Authentication for details.

AccessDenied: Access Denied status code: 403

CredentialsEndpointError: failed to load credentials

InvalidAccessKeyId: The AWS Access Key ID you provided does not exist in our records

can't access bucket <bucket_name>: Forbidden: Forbidden

  Why it’s happening 

The IBM Cloud Object Storage service credentials that you use to access the service instance might be wrong, or allow only read access to your bucket.

  How to fix it 

Create a new secret.



1.  In the navigation on the service details page, click Service Credentials.
2.  Find your credentials, then click View credentials.
3.  In the iam_role_crn section, verify that you have the Writer or Manager role. If you don't have the correct role, you must create new IBM Cloud Object Storage service credentials with the correct permission.
4.  If the role is correct, verify that you use the correct access_key_id and secret_access_key in your Kubernetes secret.
5.  [Create a new secret with the updated access_key_id and secret_access_key](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-cos-understandcreate_cos_secret).