vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Similarly, you will not see potential capability updates if your nodes in the channel are not at a sufficient Fabric level to process the capability. Note that in orderers that use a system channel the default orderer capability shown is inherited from the system channel. Orderers that do not use a system channel will default to using v2_0 capabilities. While the default application capability is set to a reasonable level that will ensure that peers who attempt to join the channel will not crash. The application capability can always be updated later.

To ensure that you will always be able to see and propose updates to get a channel to the latest capability levels, it is a best practice to upgrade your peers and ordering nodes to the latest Fabric version as soon as it is available in the console. From a channel management perspective, it is also a best practice to discuss capability updates with other organizations before proposing a change. This will allow organizations to update nodes, as necessary, before the channel update request is submitted.





 Capabilities in the system channel 

Because the ordering service is involved in the validation of the orderer and channel capabilities, these capability levels exist in the system channel (if applicable). By default, any channel that is created on an ordering cluster that uses a system channel will inherit these capability levels. Because only the orderer capability (and not the channel capability) is apparent when creating a channel, it is important to communicate the channel capability level to consortium members so they can ensure that the level of their peers is at the Fabric version of the capability level or higher.

In order to edit the orderer or channel capabilities in the system channel, your organization must be an ordering service administrator.

To edit these capabilities, click on the Settings button inside the ordering service. Then click Capabilities. Note that the channel and orderer capabilities, as well as the application capabilities, can also be edited through a channel configuration update. However, an ordering service admin will have to sign any configuration update that edits the orderer or channel capabilities. Note that capability versions can only advance. You cannot go back to a previous capability or downgrade from a default capability level to a lower version.

It is not possible to update the orderer or channel capabilities to a level that will crash your ordering nodes.
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. Create the ordering service and second ordering node

Before we can deploy the ordering service, we create the ordering organization CA, register the ordering organization admin users and the ordering node user, and create the organization Membership Service Provider (MSP). The bulk of the work to set up an ordering service is performed in this section, making it simple in later steps to add ordering nodes from other regions.



 Create the ordering service CA 

For simplicity, we create an ordering service where all the ordering nodes belong to the same organization. Therefore, we create a single CA and register and enroll the identities for each ordering node with the CA. After you have logged in to the console in Region 1 complete the following steps:



1. Navigate to the Nodes tab and click Add Certificate Authority.
2. In this step, we're creating a CA, as opposed to importing one, so make sure that the option to Create a Certificate Authority is selected. Then click Next
3. Give this CA a unique display name, Multiregion OS CA.
4. Provide the CA administrator enroll ID and corresponding secret. For purposes of this tutorial, we use admin and adminpw.
5. You can ignore the Advanced deployment options, they are not relevant to this tutorial.
6. Review the Summary page, then click Add Certificate Authority.



Depending on your cluster type, deployment of the CA can take up to ten minutes. When the CA is first deployed, the status indicator box in the CA tile is a flashing gray box. When the CA is successfully deployed and is running, this box turns green, indicating that it is "Running" and can be operated from the console.
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 

This error occurs when you try to restore a key that was deleted more than 30 days ago.







 12 - KeyCreateImportAccess instance policy... 



 Message 

KeyCreateImportAccess instance policy does not allow this action

Reason code: KEY_CREATE_IMPORT_ACCESS_ERR





 HTTP status code 

409 - Conflict

The HTTP 409 Conflict response status code indicates a request conflict with current state of the server.

Conflicts are most likely to occur in response to a PUT request. For example, you may get a 409 response when uploading a file which is older than the one already on the server resulting in a version control conflict.





 Context 

The KeyCreateImportAccess instance policy was enabled and a request to create or import a key was not allowed.

For example, the instance policy does not allow creating a standard key and a request to create a standard key was rejected.



 Example 

The following steps return this error.



1. Enable the instance policy and prevent creating standard keys
2. Attempt to create a standard key, which fails
3. Remove (disable) the instance policy, which allows creating standard keys
4. Create a standard key, which succeeds



 step 1 - enable an instance policy, which prevents creating standard keys
$ curl -X PUT "https://us-south.kms.cloud.ibm.com/api/v2/instance/policies?policy=keyCreateImportAccess" -H "accept: application/vnd.ibm.kms.policy+json" -H "authorization: Bearer $ACCESS_TOKEN" -H "bluemix-instance: $KP_INSTANCE_ID" -H "content-type: application/vnd.ibm.kms.policy+json" -d '{
"metadata": {
Why didn’t I receive the confirmation email for creating my account? 

I didn't receive a confirmation email for successful account creation.

  What’s happening 

You didn't receive the confirmation email to activate your account.

  Why it’s happening 

Your email client or email server might be blocking the email.

  How to fix it 

Check your inbox and your spam folder for the email. The confirmation email is sent from the ibmacct@iam.ibm.com email address, and the subject begins with "Action Required!"



*  Check for filters or settings in your email program that delete email or route email to a location other than your inbox.
*  Make sure that your spam filter or security software is allowing emails with links through to your email address.
*  Contact your email provider or administrator to ask them to check for any configuration that blocks email from ibmacct@iam.ibm.com.



After you unblock the confirmation email, go to the [IBM Cloud console](https://cloud.ibm.com/) and log in. Click Resend to send another confirmation email to the email address that is associated with your IBMid.

If you still can't activate your account, contact [IBM Cloud Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).
Then click create the MSP definition. You should see the Ordering Service MSP. And if you look in your wallet you should now see the Ordering Service MSP Admin identity we just created.

Now that we have the msp and the identities that we need we can go back and create our ordering service. Click the add orderer tile and specify that you’re creating an ordering service. On the next panel, give this ordering service the name Ordering Service. If you intend your network to be used for testing and development, you can choose one node here. Keep in mind however that a single node ordering service is not crash fault tolerant, which means that during a maintenance cycle or upgrade, you will not be able to commit transactions on a channel hosted on that ordering service. If your network is meant for production, choose the five node option, which uses the Raft protocol, as this ordering service is both crash fault tolerant and able to handle the loss of two nodes and not lose function.

As we have done for our CAs and our peer, we will use the default resource allocation. In the summary screen, we will be able to inspect the resources this ordering service needs to be deployed and check it against the resources available in our cluster.

On the next screen, make sure that you specify the ordering service ca, not the Org1 ca, and that you give the enroll id of your ordering service node, OS1 and OS1pw. Then, select the Ordering Service MSP from the MSP drop down and ignore the TLS CSR hostname.

Now let’s give the ordering node identity that we registered, os1 and the secret, os1pw. Then select the Ordering Service MSP. As we did with the peer, we can ignore the CSR Hostname. Next, select which Fabric version image you want to use to deploy this ordering service. As we did with the peer, I will select the highest version here, as it contains the latest fixes and improvements. It will also set me up well when we enable v2 capabilities, which are currently not available.

On the next panel, review the summary to make sure these values are what you expect.
Otherwise, leave it unchecked and let the system choose for you. Click Next.
8. On the Add ordering service page



* Select Multiregion OS CA as your CA.
* Then, select os1 as the enroll ID for the node identity.
* Enter the associated secret, os1pw.
* Select your MSP, Multiregion OS MSP from the drop-down list.
* For purposes of this tutorial you can skip the TLS CSR hostname option.
* Select the latest available Fabric version from the drop-down list, as it will contain the latest bug fixes and click Next.



9. Review the Summary page and click Add another node. Don't worry about adding OS4-Region3 to the system channel yet. We'll do that after adding the last ordering node.





 Task: Add fourth ordering node 



Table 9. Create fourth ordering node

 Display name MSP Enroll ID Secret 

 Create ordering node OS4-Region3 Multiregion OS MSP 
 CA Multiregion OS CA 
 Ordering Service Identity os1 os1pw 



Repeat this exact same set of steps for the fifth ordering node, but give it the name OS5-Region3.





 Task: Add fifth ordering node 



Table 10. Create fifth ordering node

 Display name MSP Enroll ID Secret 

 Create ordering node OS5-Region3 Multiregion OS MSP 
 CA Multiregion OS CA 
 Ordering Service Identity os1 os1pw 









 Add the ordering nodes to the orderer system channel 

If your cluster does not use a system channel, skip this step. To verify if a cluster uses a system channel, click the cluster tile and check the Orderer Type.

Add both ordering nodes to the consenter set of the system channel. Click each new ordering node, then Add node to ordering service. After the nodes have been added to the ordering service, the nodes are now part of the system channel.





 Export the ordering nodes 

After these two ordering nodes have started successfully as indicated by the green status indicator on its tile, we need to export the node so that they can be imported into the ordering service in the Region 1 and Region 3 consoles.
* Unauthorized: The user does not have access to the specified resource - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-unauthorized-err)







 HTTP 403 - Forbidden 



* Requested change is not compliant with configuration rules - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-config_rule_conflict_err)
* The resource(s) queried does not belong to the service - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-resource-owner-err)
* This action can only be done by a service (service to service) - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-service-only-err)
* This action is not permitted on this resource: Please contact IBM Key Protect or open a service ticket to enable this feature - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-feature-restricted-err)







 HTTP 409 - Conflict 



* Key is not in a valid state - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-action-invalid-state-err)
* Key is protecting one or more cloud resources - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-protected-resource-err)
* KeyCreateImportAccess instance policy does not allow this action - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-create-import-access-err)
"endpoint": "s3.direct.us-south.cloud-object-storage.appdomain.cloud",
"guid": "902xxxx-xxxx-xxxx-xxxx-4127da8xxxx",
"hmac_access_key": "xxxxxxxxx",
"hmac_secret_key": "xxxxxxxx",
"provider": "ibm-cos",
"region": "us-south",
"type": "objectstore"
},
"service-endpoints": "public"
},
"allow_cleanup": false,
"crn": "crn:v1:staging:public:ibmanalyticsengine:us-south:a/d628eae2ccxxxx3bb0c9dxxxx:da82xxxx-xxxx-xxxx-xxxx-d0faf90exxxx::",
"state": "active",
"type": "service_instance",
"resource_id": "18dexxxx-xxxx-xxxx-xxxx-0ed2f9xxxx",
"dashboard_url": null,
"last_operation": {
"type": "delete",
"state": "failed",
"async": false,
"description": "500, Internal Server Error] The request could not be processed. Try again later."
},
"resource_aliases_url": "/v2/resource_instances/da82xxxx-xxxx-xxxx-xxxx-d0faf90exxxx/resource_aliases",
"resource_bindings_url": "/v2/resource_instances/da82xxxx-xxxx-xxxx-xxxx-d0faf90exxxx/resource_bindings",
Close to the end of the log file is either a:<-- <ul> --> * 1603 error * ResourceLocationId error<-- </ul> -->If the error is 1603, contact Citrix support.If the error is ResourceLocationId, an invalid resource location was used during provisioning, for example, the Resource location might have been removed or a limit was reached. To resolve this error, try one of the following actions:<-- <ol> -->1. Use Schematics to destroy the resources and rerun the Apply from the Settings page.2. Use Schematics to destroy the resources and rerun the Apply from the Settings page and remove the workspace. Reprovision the Citrix DaaS solution with a valid resource location.3. Contact IBM support.<-- </ol> --><-- </section "id="section-troubleshooting-vpc-cc-not-registered" "> --><-- <section "id="section-troubleshooting-vpc-permissions" "> --> Authentication error During the Apply, you get an authentication error. Check to make sure you have the right permissions for using Schematics. For more information about the permission needed, see Getting Started]] ! ! ! ! <-- </section "id="section-troubleshooting-vpc-permissions" "> --><-- <section "id="section-troubleshooting-snapshot" "> --> Machine Catalog Snapshot error When you are creating the Machine Catalog and you receive an error that mentions snapshots. Re-create the Machine Catalog.<-- </section "id="section-troubleshooting-snapshot" "> --><-- <section "id="section-troubleshooting-functions" "> --> After multiple apply attempts for Volume Worker, Schematics shows an IBM Cloud Functions error After selecting Apply Plan more than once, you get an error similar to this: 2022/07/19 14:23:30 Terraform apply | Error: ERROR] Error creating IBM Cloud Function Action: The request content was malformed:
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. Please wait for a minute and try again.
* Action is ready for execution.
* Action is ready for execution. The configuration and settings cannot be edited.
* Action is in draft. Please add a Git repository.
* Action is ready, Job cannot be executed. Check the Job status.
* Action state is {{.State}} and could not process the request
* The requested object cannot be located. Check that the ID is correct and try your request again.
* Playbook not selected to create a Job. Please select a playbook name.
* Unable to delete the action. Action current status: {{.Status}}.







 Resolve 



* Check the logs. For more information, see [log commands](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-logs-job)









 Job error 

The Schematics jobs displays a list of jobs and their state as successful, or failed, or active (running) job.



 Message 



* Job processing error.
* Unable to delete the job. Job current status: {{.Status}}
* The Job was temporarily locked by {{.User}} at {{.Time}}. Please wait until any current Job execution have completed.
* Playbook not selected to create a Job. Please select a playbook name.







 Resolve 



* Check the input configuration and settings.
* Check the job configuration timeout, if the job timeout is reached 60 minutes, the status is updated and error is returned.
{"error":"No active archiving configuration exists","code":"NotFound","status":"error"}

When archiving is not enabled, the following is returned when running the [PUT method](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-archiving-manage-apiarchivingapi-update-conf):

{"error":"Active archiving configuration does not exist for this account. Try creating one instead.","code":"ServerError","status":"error"}
* [Ordering Block Storage through the Console](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-orderingthroughConsole)
* [Ordering File Storage through the Console](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-getting-started)







 Creating the Network Interface 



1. Select an Uplink Port Speed.
2. Enter values the VLAN and Subnet fields



If you have decided on a public/private setup for your environment and plan to * Install multiple SAP systems that need to communicate with each other or * Choose a three-tier SAP setup (database and application instances on different hardware) Make sure that your name resolution reflects the internal and external addresses. The external address matches the hostname of the server resolved by its fully-qualified domain name (FQDN). The internal addresses will not appear in the domain name system (DNS). Since internal IPs should be used for communication between the servers, make sure you extend your /etc/hosts or Microsoft Windows "host" file accordingly. This information might also apply to the guest operating system of you VMware ESXi-based deployments.



3. Leave the default values for all other fields.
4. Review your Order Summary.
5. Select I read and agree to the following Third-Party Service Agreements.

You can create your server, save the order as a quote to provision at a later time, or add the order an estimate, which may include multiple services.
6. Click Create to be redirected to the Checkout page after your order has been verified.



You are redirected to a page with your order number. You can print the page, because it's your receipt. A confirmation email with the subject Your IBM Cloud Order ## has been approved is be sent to the email address in your profile. This email is notice that your server has been approved and is in the process of being deployed. After it is deployed, another notice is sent notifying you that the server is available and can be managed through the [IBM Cloud console](https://cloud.ibm.com/).
For example, you can use the following cURL request to create a route that defines how global and US-South location-based events are collected and routed in the account:

curl -X POST https://private.us-south.atracker.cloud.ibm.com/api/v2/routes -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json" -d '{
"name": "my-route",
"rules": [
{
"locations": "us-south", "global"],
"target_ids": "22222222-2222-2222-2222-222222222222"]
}
]
}'

In the response, you get information about the route such as the id, that indicates the GUID of the route, and the crn, that indicates the CRN of the route.





 Updating a route using the API 

When you update a route, you must include the route information in the data section of the request.



* You must pass all fields.
* Update the fields that need changing.



You can use the following cURL command to update a route:

curl -X PUT <ENDPOINT>/api/v2/routes/<ROUTE_ID> -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json" -d '{
"name": "ROUTE_NAME",
"rules": [
{
"locations": "LOCATIONS"],
"target_ids": "TARGET_ID"]
}
]
}'

Where



* <ENDPOINT> is the API endpoint in the region where you plan to configure or manage a route. For more information, see [Endpoints](https://cloud.ibm.com/docs/atracker?topic=atracker-endpointsendpoints_api).
* <ROUTE_ID> is the ID of the route to be updated
* ROUTE_NAME is the name of the route.
Are you getting an "invalid_value" error when creating a route? 

When creating a route, the following message is returned: Your request has failed because rules per route limit 4 is reached..

  What’s happening 

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

  Why it’s happening 

You are trying to create a new route and you already have 4 routes configured in your account.

  How to fix it 

Only 4 routes are supported in an account across all regions. If you need to create a new route, [delete an existing route](https://cloud.ibm.com/docs/atracker?topic=atracker-route_v2&interface=apiroute-delete-api) and retry the request.
if accessToken == nil && identityToken == nil {
//email verification is required
return
}
//User authenticated
}

public func onAuthorizationCanceled() {
//Sign up canceled by the user
}

public func onAuthorizationFailure(error: AuthorizationError) {
//Exception occurred
}
}

AppID.sharedInstance.loginWidget?.launchSignUp(delegate: delegate())
Show more







 Forgot password 



1. Configure your Cloud Directory [settings](https://cloud.ibm.com/docs/appid?topic=appid-cloud-directorycd-settings) in the GUI. Allow users to manage their account from your app must be set to On.
2. In the Reset Password tab of the service dashboard, be sure that Forgot password email is set to On.
3. Place the following code in your application. When one of your app users requests that their password is updated, the login widget is called and the process starts.

class delegate : AuthorizationDelegate {
public func onAuthorizationSuccess(accessToken: AccessToken?, identityToken: IdentityToken?, refreshToken: RefreshToken?, response:Response?) {
//forgot password finished, in this case accessToken and identityToken will be null.
}

public func onAuthorizationCanceled() {
//forgot password canceled by the user
}

public func onAuthorizationFailure(error: AuthorizationError) {
//Exception occurred
}
}

AppID.sharedInstance.loginWidget?.launchForgotPassword(delegate: delegate())
Show more







 Change details 



1. Configure your Cloud Directory [settings](https://cloud.ibm.com/docs/appid?topic=appid-cloud-directorycd-settings) in the GUI.