vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 vpn_gateway_missing_subnet_id 

Message: Could not find a subnet identifier for the given VPN gateway template.

The Subnet ID is a required field. Provide a subnet ID with your command.





 vpn_gateway_missing_name 

Message: Could not find a name for the given VPN gateway template.

The name is a required field. Provide a name with your command.





 vpn_gateway_not_created 

Message: The VPN gateway <vpn_gateway_id> could not be created.

Try 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).





 vpn_gateway_not_deleted 

Message: The VPN gateway <vpn_gateway_id> could not be deleted.

Try 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).





 vpn_gateway_not_found 

Message: The VPN gateway <vpn_gateway_id> could not be found.

Check whether the VPN gateway ID is correct. Try 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).





 vpn_gateway_not_updated 

Message: The VPN gateway <vpn_gateway_id> could not be updated.

Try again in a few minutes.
* UI
* CLI
* API







 Updating trusted profiles 

You can update the permissions or redefine trust relationships for trusted profiles at any time by using either the console or the [IAM Identity Services](https://cloud.ibm.com/apidocs/iam-identity-token-apicreate-claim-rule-request) API.

To update trusted profiles, you must be assigned the administrator, operator, or editor role within the account, or on the IAM Identity Service.

You can use Activity Tracker to monitor which federated users and compute resources apply a trusted profile. For more information, see [Monitoring login sessions for trusted profiles](https://cloud.ibm.com/docs/account?topic=account-trusted-profile-monitor).



 Updating trusted profiles in the console 

To update trusted profiles, go to Manage > Access (IAM) in the IBM Cloud console, and select Trusted profiles. Then, select the name of the trusted profile that you want to update.



 Updating the description of your profile 

Click the name of the trusted profile that you want to update, and select Actions > Edit. Enter the new name and description, and click Apply.





 Redefining the trust relationship 

After the trusted profile is created, you can build trust with both federated users and compute resources in the same trusted profile.



1. Click the name of the trusted profile that you want to update.
2. Click Add to add a condition to the existing trust relationship. To edit an existing condition, click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/secure-enterprise/includes/account/includes/icons/action-menu-icon.svg) > Edit next to the trust relationship you want to update.



* Click Add a condition and repeat as needed to add more conditions.
* To remove a condition, click the Remove icon !
"id": "9c6d20ad-779e-27c5-3842-2a20b19abfcf",
"name": "my-secret-group",
"type": "application/vnd.ibm.secrets-manager.secret.group+json",
"updated_at": ""
},
"warnings": null
}







 Update a secret group 

Use this command to update a secret group.

vault write [-format=FORMAT] auth/ibmcloud/manage/groups/SECRET_GROUP_ID name=NAME [description="DESCRIPTION"]



 Prerequisites 

You need the [Manager service role](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-iam) to update secret groups.





 Command options 

name
: The human-readable alias that you want to assign to the secret group. Required.

description
: An extended description of the secret group.

-format
: Prints the output in the format that you specify. Valid formats are table, json, and yaml. The default is table. You can also set the output format by using the VAULT_FORMAT environment variable.





 Examples 

Update the name and description of a secret group.

vault write auth/ibmcloud/manage/groups/9c6d20ad-779e-27c5-3842-2a20b19abfcf name="my-updated-secret-group" description="An updated group of secrets."





 Output 

The command returns the following output:

Key Value
--- -----
created_at 2020-10-05T17:43:49Z
description An updated group of secrets.
id 9c6d20ad-779e-27c5-3842-2a20b19abfcf
name my-updated-secret-group
type application/vnd.ibm.secrets-manager.secret.group+json
updated_at 2020-10-05T17:56:56Z







 Delete a secret group
Use [this method](https://cloud.ibm.com/apidocs/activity-trackerpatch-v1-config-stream-exclusions-rule-id) to update an existing streaming exclusion rule.

curl --request PATCH https://api.eu-gb.logging.cloud.ibm.com/v1/config/stream/exclusions/{ruleId}
-H "content-type: application/json"
-H "servicekey: <SERVICE_KEY>"
-d '{"title": "Exclude Example Update", "query": "example", "active": false}'

{"hosts":[],"apps":[],"title":"Exclude Example Update","query":"example","active":false,"id":"xxxxxxxxxx"}
Bucket creation through these tools will fail. If a PUT bucket request fails with an unsupported ACL error, first use the console as shown in the [getting started with IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage) to create the bucket, then configure the tool to read and write objects to that bucket. Tools that set ACLs on object writes are not currently supported.
Error occurred while processing the {{.Method}} request.
* Action ID is correct.
* The requested action cannot be located. Check that the action ID is correct and try your request again.







 Resolve 

You should read the error message carefully to rectify. You can check out the required parameter is unique, has rightly provided in the payload, and you need to follow the maximum and minimum character limit to process your parameter value.







 Service error 

The Schematics Actions instance and resources are overloaded or down for maintenance.



 Message 



* Internal Service Error occurred during {{.Method}} request, wait a minute and try again. If you still encounter this problem contact the [IBM Cloud® support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).







 Resolve 



* Check the user jobs and all jobs logs. For more information, see [log commands](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-logs-job)
* Wait for a minute and check your configuration and execute the action again.
* Check you have the required permissions such as [IAM access or key](https://cloud.ibm.com/docs/schematics?topic=schematics-action-working).
* Check the firewall IP are enabled.
* Check if your [IBM Cloud environment notification](https://cloud.ibm.com/docs/get-support?topic=get-support-viewing-notifications) is in maintenance.









 State error 

While processing the create, delete, update action, the Schematics will run the Jobs are sent to pending state. The state flow and error message depends based on the template administrator. Following are the messages you can get in the process flow.



 Message 



* Action is ready, Job cannot be executed. Check the Job status.
* Action is in queue. Wait until the action completes.
* Action is in queue. Wait until the action completes update.
* Action failed to complete.
Are you getting a "region_not_allowed" error when creating a target? 

When creating a target, a message similar to Your request has failed due to the region requested not being permitted. Requested: us-east, Permitted: [eu-gb us-south] is returned with the code region_not_allowed.

  What’s happening 

Your request fails with an error message and a code of region_not_allowed.

  Why it’s happening 

You are trying to configure a target and the region you requested the target be created in is not a region that has been permitted in the configuration settings.

  How to fix it 

[Configure the --permitted-target-regions in the configuration settings](https://cloud.ibm.com/docs/atracker?topic=atracker-settings&interface=cli) to include the the region where you want to configure a target, or specify a target region (-r) on your create request in one of the existing permitted target regions.
[SSP-AM-Approve-Reject-Access-2](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Approve-Reject-Access-2.png)
4. Open the details on the request you want to process by choosing the twistie (>) to the left of the user.

![SSP-AM-Approve-Reject-Access-3](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Approve-Reject-Access-3.png)
5. Select the Disposition for the request (APPROVED, REJECTED). If the Disposition is REJECTED comments are required for reason why request was denied.
6. Once you have processed all the requests you intend to, select the "Save" icon near the upper left part of the console to start the back end processing of the requests. The requestors will be notified by email if their request has been rejected or when the processing is complete and they have been granted the requested access.

![SSP-AM-Approve-Reject-Access-4](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Approve-Reject-Access-4.png)







 Access Re-Validation 

Continued business need (CBN) for accesses provided through the Self-Service portal access management tool must be validated annually.

The re-validation process is run on an annual basis for all users, so it is possible that you will be notified of the need to re-validate less than a year after access is granted. You will receive an email when validation is required.
Error: [ERROR] Error fetching Keys An error occurred while performing the 'authenticate' step: {"errorCode":"BXNIM0415E","errorMessage":"Provided API key could not be found","context":{"requestId":"aDJwNTQ-fec49a18af674b77a356764b2c633520","requestType":"incoming.Identity_Token","userAgent":"Go-http-client/1.1","url":"https://iam.cloud.ibm.com","instanceId":"iamid-7.7-13974-e612b1c-84749569f-h2p54","threadId":"37adb","host":"iamid-7.7-13974-e612b1c-84749569f-h2p54","startTime":"12.07.2022 14:47:03:629 UTC","endTime":"12.07.2022 14:47:03:699 UTC","elapsedTime":"70","locale":"en_US","clusterName":"iam-id-prod-eu-gb-lon05"}}
│ {
│ "StatusCode": 400,
│ "Headers": {
│ "Akamai-Grn": [
│ "0.be277368.1657637223.3e442e1"
│ ],
│ "Cache-Control": [
│ "no-cache, no-store, must-revalidate"
│ ],
│ "Content-Language": [
│ "en-US"
│ ],
│ "Content-Length": [
│ "534"
│ ],
│ "Content-Type": [
│ "application/json"
│ ],
│ "Date": [
If none of the ordering nodes that were consenters on the channel are still up, any peer attempting to join the channel will try and fail to connect to the nodes listed in the genesis block and be unable to proceed past that point.

In these cases, it is necessary to edit the configuration of the peer itself with a code snippet provided by the console. This code snippet will point the peer to one of the ordering nodes servicing the channel and allow the ledger of the channel to be pulled from that node.





 Editing the peer configuration 

If your channel is in the state described above, in which none of the original ordering nodes are still servicing the channel, when attempting to join a peer to the channel the Join a peer to the channel screen will show a message similar to the following advising you that the configuration of the peer must include an "orderer override":

Zoom

![Orderer override code snippet](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/orderer_override.png)

Figure 7. Orderer override code snippet

When you see this screen, copy the code snippet. Note the addressOverrides section. It should contain the address of one of the original ordering nodes as well as the address of one of the nodes now servicing the channel.

Then, paste the code snippet into the configuration of the peer. To do this:



1. Navigate to the peer from the Nodes panel.
2. Click on the Settings button inside the peer.
3. Under Actions, click on Edit configuration JSON (Advanced).
4. In the box under Configuration updates, paste the code snipped you copied on the Join a peer to the channel page.
5. When you're ready, click Update peer.



The peer will automatically restart. When it is back up, you should be able to join the channel.

Zoom

!
Contact [IBM Cloud support](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help) to verify that you account is set up correctly.





 Permissions error 

Message:

The user does not have the necessary classic infrastructure permissions to add servers

'Item' must be ordered with permission.

The credentials could not be validated.

'<Provider>' infrastructure request not authorized

Description and resolution:

You might not have the required permissions to perform the action in your IBM Cloud infrastructure portfolio, or you are using the wrong infrastructure credentials. See [Setting up the API key to enable access to the infrastructure portfolio](https://cloud.ibm.com/docs/openshift?topic=openshift-access-creds).





 Firewall error 

Message:

Worker unable to talk to IBM Cloud Kubernetes Service servers. Please verify your firewall setup is allowing traffic from this worker.

Description and resolution:

If you have a firewall, [configure your firewall settings to allow outgoing traffic to the appropriate ports and IP addresses](https://cloud.ibm.com/docs/openshift?topic=openshift-firewallfirewall_outbound).





 Hard reboot 

Message:

The worker did not respond to the soft reboot request. A hard reboot might be necessary.

Description and resolution:

Although you issued a reboot on your worker node, the worker node is unresponsive. You can rerun the [reboot command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_worker_reboot) with the --hard option to power off the worker node, or run the worker reload[command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_worker_reload).





 Instance can't be found 

Message:

can't create IMS portal token, as no IMS account is linked to the selected BSS account
For information about how to do that, see [Adding an ordering node to the consenter set](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-add-remove-ordereribp-console-add-remove-orderer-update-channel1) of a channel.





 Console 1: add the Ordering Service_2 node to your console 

This step should be completed by every channel member.

To do this, click on the tile representing the ordering service, which in this tutorial is called Ordering Service. Then click on the Ordering nodes tab and then the Add another node tab.

Then click Import an existing node. After clicking Add file, find the JSON representing the Ordering Service_2 node that was sent to you by the operator of Console 2. After you have added the Ordering Service_2 node, you should see it on the Ordering nodes page.

Zoom

![Add the Ordering Service_2 node to your console](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/addremove_addnode_console1.png)

Figure 6. Add the Ordering Service_2 node to your console





 Update channel1 to add the Ordering Service2 MSP and the Ordering Service_2 node 

This step can be completed by any channel member.

Because this tutorial presumes that a user is adding a node to a channel that was created as part of the [Build a network tutorial](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-network), the channel the Ordering Service_2 node is being added to, channel1, does not yet have the newly created ordering service organization, Ordering Service2 MSP, as one of the administrators of the channel. While a new ordering node can be added to a channel even if the organization that owns the node is not an administrator of the ordering service, it is a best practice to add the organization that owns the node when you add the node.
$e->getMessage());
}

Show more





 Example code to place an order 

This API call is identical to the previous code example, except it calls placeOrder, rather than verifyOrder. More information about placeOrder can be found in the [SoftLayer API documentation](https://softlayer.github.io/reference/services/SoftLayer_Product_Order/placeOrder/).

$client = SoftLayerSoapClient::getClient('SoftLayer_Product_Package', null, $apiUsername, $apiKey);

try {
$filter = new stdClass();
$filter->keyName = new stdClass();
$filter->keyName->operation = 'CONTENT_DELIVERY_NETWORK_SERVICE';

$client->setObjectFilter($filter);
$client->setObjectMask(
"mask[
itemPrices.item
attributes.attributeType,
bundleItems.activeUsagePrices
priceType,
pricingLocationGroup.locations
]
]
]"
);

$package = $client->getAllObjects()[0];

$orderData = new stdClass();
$orderData->packageId = $package->id;
$orderData->prices = $package->itemPrices;

$orderObject = new SoapVar(
$orderData,
SOAP_ENC_OBJECT,
'SoftLayer_Container_Product_Order_Network_ContentDelivery_Service',
'http://api.service.softlayer.com/soap/v3/'
);

$productOrderClient = SoftLayerSoapClient::getClient('SoftLayer_Product_Order', null, $apiUsername, $apiKey);

$result = $productOrderClient->placeOrder($orderObject);
print_r($result);
print_r("n");
kp.Error:
correlation_id='59c343a7-c20f-43ea-9e50-da45cecbc8a6',
msg='Conflict:
Key could not be enabled.
Please see reasons for more details.',
reasons='[REQ_TOO_EARLY_ERR:
The key was updated recently.
Please wait and try again. -
FOR_MORE_INFO_REFER: https://cloud.ibm.com/apidocs/key-protect]'

 this request succeeds because the key was disabled at least 30 seconds ago
$ ibmcloud kp key enable $KEY_ID -i $KP_INSTANCE_ID

Enabling key: '54f53384-b563-4466-860a-c42ce42f7ac9', in instance: 'a192d603-0b8d-452f-aac3-f9e1f95e7411'...
OK
Show more







 27 - The provided ciphertext is invalid or... 



 Message 

The provided ciphertext is invalid or corrupted

Reason code: UNPROCESSABLE_CIPHERTEXT_ERR





 HTTP status code 

422 - Unprocessable Entity

The HTTP 422 Unprocessable Entity response status code indicates that the server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions.

The client should not repeat this request without modification.





 Context 

This typically means the hardware security module (HSM) could not process the data because the input was invalid.

This error is returned when there is an internal error.

If you get this error please contact [IBM support](https://cloud.ibm.com/unifiedsupport/supportcenter)







 28 - The provided encrypted nonce was not... 



 Message 

The provided encrypted nonce was not encrypted with the key material given OR the provided IV does not match the encrypted nonce

Reason code: INCORRECT_NONCE_IV_ERR
Add a new ordering node in Region 2.
3. Add two new ordering nodes in Region 3.
4. Update the ordering service in Region 1, Region 2, and Region 3.





 Before you begin 

This tutorial assumes that you have three Kubernetes clusters that are deployed across three different regions and that you have linked a blockchain service instance to each of those clusters.

Choose the regions of your Kubernetes clusters carefully. While it is fine for the ordering nodes to span regions, transaction latency can occur when the cluster regions are geographically far apart. For example, it is not recommended to deploy some ordering nodes in Tokyo, some in Australia, and some in the United States.



* [Create an IBM Blockchain Platform service instance in IBM Cloud](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-deploy-iks-icibp-v2-deploy-iks-create-service-instance).

Deploy an instance of the IBM Blockchain Platform in each cluster and verify that you can log in to the console.
* [Build a network tutorial](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-network)

We assume that you are already familiar with the console and using it to deploy a CA, register users, enroll identities, create a Membership Service Provider (MSP), and create an ordering service. If you have not used the console before, you should review the Build a Network tutorial because a similar process is used in throughout the following instructions.







 Step 1: Deploy the ordering service in Region 1 

In this section, we create a single-node ordering service and then add a second ordering node as highlighted in yellow in the diagram below:

Zoom

![Region 1 ordering service](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/mr-ha-os-region1.png)

Figure 2.
: If you rely on 500 replies for your application, you might have issues. To fix the problem, update your application to rely on 400 responses.
: If you don't take care of reduce overflow errors as part of a row in the response body, issues occur. To fix this problem, change the application to handle the errors from view requests.







 August 2017 



 17 August 2017 

The following changes were made in build 6365:

New! X-Frame-Options
: Add the X-Frame-Options header settings. The X-Frame-Options setting is a response header that controls whether an HTTP response can be embedded in a <frame>, <iframe>, or <object>. This security feature helps prevent click jacking.

You can configure this option based on your CORS settings. If CORS is enabled, X-Frame-Options are automatically enabled and send the response header, X-Frame-Options: DENY, by default. If a request HOST header matches the URL listed in the origins section of CORS, an X-Frame-Options: ALLOW-FROM URL response header is returned.

This change might impact customers who are accessing the database directly from the browser. If you see the error message, "X-Frame-Options: DENY", and it's breaking your service, you must enable CORS by [modifying the CORS configuration](https://cloud.ibm.com/apidocs/cloudantputcorsconfiguration). After you enable CORS, add the value of the HOST header that you send in the request to the list of allowed origins.

New! Replication scheduler
: Add the replication scheduler. Learn more about [replication scheduler](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-advanced-replicationthe-replication-scheduler).

_revs-diff endpoint
: POST requests to the _revs_diff endpoint require either the _reader or _replicator role.







 July 2017 



 24 July 2017 

Retire Shared plan
If you still see an authorization error message, repeat Steps 1-5 with the new image pull secrets. If you still can't log in, [open an IBM Cloud Support case](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help).



6. If the login succeeds, pull an image locally. If the command fails with an access denied error, the registry account is in a different IBM Cloud account than the one your cluster is in. [Create an image pull secret to access images in the other account](https://cloud.ibm.com/docs/openshift?topic=openshift-registryother_registry_accounts). If you can pull an image to your local machine, then your API key has correct permissions, but the API setup in your cluster is not correct.

docker pull <region>icr.io/<namespace>/<image>:<tag>
7. Check that the pull secret is either referenced directly from the deployment or from the service account that the deployment uses. If you still can't resolve the issue, [contact support](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help).