vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Deploy the ordering service in Region 1](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-hadr-mr-osibp-console-hadr-mr-os-region1)



* [Create the ordering service CA](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-hadr-mr-osibp-console-hadr-mr-os-region1-ca)
* [Associate the CA admin identity](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-hadr-mr-osibp-console-hadr-mr-os-region1-ca-admin)
* [Use your CA to register identities](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-hadr-mr-osibp-console-hadr-mr-os-region1-ca-reg)
* [Create the ordering service organization MSP definition](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-hadr-mr-osibp-console-hadr-mr-os-region1-msp)
* [Create single node ordering service in Region 1.](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-hadr-mr-osibp-console-hadr-mr-os-region1-osn1)
* [Add second ordering node in Region 1](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-hadr-mr-osibp-console-hadr-mr-os-region1-osn2)
console.log(ERROR: ${e.code} - ${e.message}n);
});
}





 Add or remove a legal hold to or from an object 

This implementation of the POST operation uses the legalHold query parameter and add and remove query parameters to add or remove a single legal hold from a protected object in a protected bucket.

The object can support 100 legal holds:



* A legal hold identifier is a string of maximum length 64 characters and a minimum length of one character. Valid characters are letters, numbers, !, _, ., , (, ), - and \.
* If the addition of the given legal hold exceeds 100 total legal holds on the object, the new legal hold will not be added, a 400 error is returned.
* If an identifier is too long, it will not be added to the object and a 400 error is returned.
* If an identifier contains invalid characters, it will not be added to the object and a 400 error is returned.
* If an identifier is already in use on an object, the existing legal hold is not modified and the response indicates that the identifier was already in use with a 409 error.
* If an object does not have retention period metadata, a 400 error is returned and adding or removing a legal hold is not allowed.



The presence of a retention period header is required, otherwise a 400 error is returned.

Syntax

POST https://{endpoint}/{bucket-name}/{object-name}?legalHold path style
POST https://{bucket-name}.{endpoint}/{object-name}?legalHold= virtual host style

Example request

POST /BucketName/ObjectName?legalHold&add=legalHoldID HTTP/1.1
Host: myBucket.mydsNet.corp.com
Date: Fri, 8 Dec 2018 17:50:00 GMT
Authorization: authorization string
Content-Type: text/plain

Example response

HTTP/1.1 200 OK
Date: Fri, 8 Dec 2018 17:51:00 GMT
Connection: close



* Java
* Python
* Node
If you see an error that a name has already been given to a channel on that ordering service, you will have to select a new name.
* Ordering service. Channels are hosted on a single ordering service and cannot be migrated from one ordering service to another.
* Organizations. This section of the panel is how organizations are added or removed from a channel. Organizations that can be added can be seen in the drop-down list. Note that an organization must be a member of the consortium of the ordering service before it can be added to a channel. For more information about how to add an organization to the consortium, see [Add your organization to list of organizations that can transact](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-add-org).



You can also update an organization's level of permission on the channel:



* A channel operator has permission to create and sign channel configuration updates. There must be at least one operator in each a channel.
* A channel writer can update the ledger by invoking a smart contract. A channel writer can also instantiate a smart contract on a channel.
* A channel reader can only query the ledger, by invoking a read only function in smart contract for example.
* Update policy. The update policy of a channel specifies how many organizations (out of the total number of operators in the channel), who must approve of an update to the channel configuration. To ensure a good balance between collaborative administration and efficient processing of channel configuration updates, consider setting this policy to a majority of admins. For example, if there are five admins in a channel, choose 3 out of 5.







 Advanced options 

By clicking the box under advanced options, users can access parameters that users should take caution in updating. Note that if you are attempting to change any parameter that requires the signature of ordering service admins (for example, the Block cutting parameters or ordering service consenters) and are one of the ordering service admins on this channel, you will see a field for the ordering service organization.
For example to add newly created orderers, if a system channel is being used they are first added to the system channel, then to the consenter set of an application channel. To add a node to the consenter set, first ensure that the organization that owns the consenter is an admin of the ordering service of the application channel through the Ordering service administrator panel. You can then add the consenter through this Consenter set panel by opening the drop-down list, clicking on a node, and clicking Add. For information about creating a new ordering node and adding it to a consenter set, see the [Adding and removing ordering service nodes](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-add-remove-ordereribp-console-add-remove-orderer) tutorial. If you modify the consenter set, you also have the ability to change the size of the ordering service Snapshot. For more information about Snapshots, see [Snapshots](https://hyperledger-fabric.readthedocs.io/en/release-2.2/orderer/ordering_service.htmlsnapshots) in the Fabric documentation.
* Ordering service signature. If changes to the configuration are made that require the signature of an ordering service org admin (for example, to the block cutting parameters, orderer capability, or consenter set), this panel will allow you to send the change to the relevant ordering service admin organization. The console where the ordering service organization MSP was created will see a signature notification. After the ordering service organization signs the channel update request, it is sent back to the organization that requested the channel update to be submitted.
* Access control lists (ACLs). To specify a finer grained control over resources, you can restrict access to a resource to an organization and a role within that organization. For example, setting access to the resource ChaincodeExists to Application/Admins would mean that only the admin of an application would be able to access the ChaincodeExists resource. Users have the option to edit the access control list one at a time or by uploading a JSON containing the list.
Place or verify an order:

ibmcloud sl order place PACKAGE_KEYNAME LOCATION ORDER_ITEM1,ORDER_ITEM2,ORDER_ITEM3,ORDER_ITEM4... [OPTIONS]



 Command options 

--preset
: The order preset (if required by the package).<

--verify
: Flag denoting whether to verify the order, or not place it.

--quantity
: The quantity of the item being ordered. This value defaults to 1.

--billing<
: Billing rate [hourly|monthly], [default: hourly].

--complex-type
: The complex type of the order. The type begins with SoftLayer_Container_Product_Order_.

--extras
: JSON string that denotes extra data needs to be sent with the order.

-f, --force
: Force operation without confirmation.





 Examples 

This command orders an hourly VSI with 4 CPU, 16 GB RAM, 100 GB SAN disk, Ubuntu 16.04, and 1 Gbps public & private uplink in datacenter dal13.

ibmcloud sl order place CLOUD_SERVER DALLAS13 GUEST_CORES_4,RAM_16_GB,REBOOT_REMOTE_CONSOLE,1_GBPS_PUBLIC_PRIVATE_NETWORK_UPLINKS,BANDWIDTH_0_GB_2,1_IP_ADDRESS,GUEST_DISK_100_GB_SAN,OS_UBUNTU_16_04_LTS_XENIAL_XERUS_MINIMAL_64_BIT_FOR_VSI,MONITORING_HOST_PING,NOTIFICATION_EMAIL_AND_TICKET,AUTOMATED_NOTIFICATION,UNLIMITED_SSL_VPN_USERS_1_PPTP_VPN_USER_PER_ACCOUNT,NESSUS_VULNERABILITY_ASSESSMENT_REPORTING --billing hourly --extras '{"virtualGuests": [{"hostname": "test", "domain": "softlayer.com"}]}' --complex-type SoftLayer_Container_Product_Order_Virtual_Guest







 ibmcloud sl order place-quote 

Place a quote:
When you're ready to submit your order, you can place it in the [console](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-orderingBlockStorageorderingthroughConsole), from the [SLCLI](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-orderingBlockStorageorderingthroughCLI), or the [IBMCLOUD CLI](https://cloud.ibm.com/docs/cli?topic=cli-sl-block-storagesl_block_volume_order), with the API, or [Terraform](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-orderingBlockStorageorderingthroughTerraform).





 Step 4: Connecting and configuring your new storage 

When your provisioning request is complete, authorize your hosts to access the new storage, and configure your connection. Depending on your host's operating system, follow the appropriate link.



RHEL 6

[Mount iSCSI LUNs on Linux® - RHEL6 and CentOS6](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingLinux).
RHEL 8

[Mount iSCSI LUN on Red Hat Enterprise Linux® 8](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingRHEL8).
Cloudlinux 6

[Mount iSCSI LUNs on CloudLinux 6.10](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingCloudLinux).
CloudLinux 8

[Mount iSCSI LUN on CloudLinux 8](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingCloudLin8).
Ubuntu 20
(https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-browser-storage)
* [Why am I getting the error Unable to authenticate with the enroll ID and secret you provided when I create a new organization MSP definition?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-create-msp)
* [Why am I getting the error An error occurred when updating channel when I try to add an organization to my channel?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-update-channel)
* [When I log in to my console, why am I getting a 401 Unauthorized error?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-console-401)
* [Why am I getting a Cluster linking is taking too long error when I try to link my Kubernetes cluster in IBM Cloud to my IBM Blockchain Platform service instance?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-console-helm-reset)
* [Why am I getting an error “all SubConns are in TransientFailure” on the console?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-console-transientfailure)
* [Why is my first invoke of a smart contract returns the following error: no suitable peers available to initialize from?]
Requested action can only be completed with a root key

Reason code: KEY_ROOT_REQ_REG_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 error applies to keys used for "Registrations." A "root" key is required to create a registration. This error is returned when a [create registration API request](https://cloud.ibm.com/apidocs/key-protectcreateregistration) is made.

Registrations are associations between root keys and other cloud resources, such as Cloud Object Storage (COS) buckets or Cloud Databases deployments.

For more information about Registrations, see [viewing associations between root keys and encrypted IBM Cloud resources](https://cloud.ibm.com/docs/key-protect?topic=key-protect-view-protected-resources).







 19 - Requested change is not compliant... 



 Message 

Requested change is not compliant with configuration rules

Reason code: CONFIG_RULE_CONFLICT_ERR





 HTTP status code 

403 - Forbidden

The HTTP 403 Forbidden client error status response code indicates that the server understood the request but refuses to authorize it.

This status is similar to 401, but in this case, re-authenticating will make no difference. The access is permanently forbidden and tied to the application logic, such as insufficient rights to a resource.





 Context 

This error message occurs when an instance policy prevents access to a resource. For example, if the request originated from a public IP address and the instance policy prohibits access from a public IP address, then you will receive this error message.







 20 - Signature is invalid 



 Message 

Signature is invalid

Reason code: INVALID_SIG_EXP_ERR





 HTTP status code 

422 - Unprocessable Entity
[More options](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/kebab.png) icon on the @order_number node, and then select Add node below.
19. Type true into the If assistant recognizes field of this node.
20. Add the following message in the response text field:

I need the order number to cancel the order for you. If you don't know the order number, please call us at 958-234-3456 to cancel over the phone.

![Shows the node that responds when the user does not provide a valid order number.](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/gs-ass-cant-help-you.png)
21. Click ![Close](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/close.png) to close the edit view.
22. Add a node after the initial order cancellation request node that responds in the case where the user provides the order number in the initial request, so you don't have to ask for it again. Click the More![More options](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/kebab.png) icon on the cancel_order node, and then select Add child node.
23. Add a label to the node to distinguish it from other child nodes. In the name field, add Number provided.
* [Resource allocation](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-allocate-resources)



7. Click Next.
8. On the next step, the Add ordering service page



* Select Ordering Service CA as your CA.
* Then, select the enroll ID for the node identity that you created for your ordering service from the drop-down list, OS1.
* Enter the associated secret, OS1pw.
* Select your MSP, Ordering Service MSP from the drop-down list.
* When you created the CA, a TLS CA was automatically created alongside it. The TLS CA is used to create certificates for the secure communication layer for nodes. The TLS Certificate Signing Request (CSR) hostname is an option available to advanced users who want to specify a custom domain name that can be used to address the ordering service endpoint. Custom domain names are not a part of this tutorial, so leave the TLS CSR hostname blank for now.
* In the Fabric version drop down list, the best practice is to select the latest available version, as it will contain the latest bug fixes. It might also be necessary to select the latest version in order to have access to the latest features.
* Click Next.



9. The Associate identity step allows you to choose an admin for your ordering service. Select Ordering Service MSP Admin as before and click Next.
10. Review the Summary page and click Add ordering service. The Edit configuration JSON button allows you to override configuration settings for the ordering service. For this tutorial, the default settings are sufficient. See [Customizing an ordering service configuration](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-orderer-create-json) to learn more about the options that are available.





 Task: Create an ordering service 



Table 13. Create an ordering service

 Display name MSP ID Enroll ID Secret
2022-05-09 14:35:48,968 - INFO - 10.241.1.9 : ok=3 changed=1 unreachable=0 failed=0 skipped=1 rescued=0 ignored=0

2022-05-09 14:35:48,968 - INFO -

2022-05-09 14:35:49,118 - INFO - CLOUD-DEPLOY] Uploading the success status file.
2022-05-09 14:35:49,119 - INFO - CLOUD-DEPLOY] ! ! Uploaded the success status file successfully.
<-- </section "id="section-success-cluster-deployment" "> --><-- <section "id="section-failed-cluster-deployment" "> --> Failed cluster deployment If you see the log status "INFO -| Error", the cluster deployment failed at that particular point, and you need to debug the issue. You will also see a message at the end of the response: "Uploading the failure status file". See the following sample response of a failed deployment: 2022-05-10 09:35:55,204 - INFO - │ “Result”: {
2022-05-10 09:35:55,204 - INFO - │ “errors”:
2022-05-10 09:35:55,204 - INFO - │ {
2022-05-10 09:35:55,204 - INFO - │ “code”: “not_authorized”,
2022-05-10 09:35:55,204 - INFO - │ “message”: “the provided token is not authorized to list keys in this account”
2022-05-10 09:35:55,204 - INFO - │ }
2022-05-10 09:35:55,205 - INFO - │ ],
2022-05-10 09:35:55,205 - INFO - │ “trace”: “70a2a6d5-48a5-4f08-8055-4fd21529dd1a”
2022-05-10 09:35:55,205 - INFO - │ },
* [Why am I getting Authorization required errors?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-auth-req)



* [Why am I getting an Unauthorized error when I'm using Code Engine?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-unauthorized-ce)



* [Why am I getting Access denied errors?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-access-denied)



* [Why am I getting Access denied errors for a resource?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-resource)
* [Why am I getting Access denied errors about insufficient scope?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-scope)
* [Why am I getting Access denied errors about my quota?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-quota)
* [Why am I getting Access denied errors over a private network?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-private)
* [Why am I getting a Forbidden error when I'm using Code Engine?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-forbidden-ce)
* [Why do images fail to pull from registry with ImagePullBackOff or authorization errors?](https://cloud.ibm.com/docs/Registry?topic=Registry-ts-app-image-pull)









 Troubleshooting CLI commands 

Troubleshoot CLI command problems.



* [Why can't I add a namespace?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-add-namespace)
* [When I create a namespace, why aren't I authorized to access the specified resource?]
* [Why is my IBM Blockchain Platform user interface unable to connect to cluster after deployment (Ingress issue)?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-ingress-issue)
* [Why are my console actions failing in my Chrome browser Version 77.0.3865.90 (Official Build) (64-bit)?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-chrome-v77)
* [When I hover over my node, the status is Status unavailable or Status unknown, what does this mean?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-status-unavailable)
* [When I hover over my node, the status is Status undetectable, what does this mean?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-status-undetectable)
* [Why am I getting the error Unable to get system channel when I open my ordering service?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-troubleshoot-ordering-service)
* [Why did my smart contract installation, instantiation or upgrade fail?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-console-smart-contracts-troubleshoot-entry1)
* [Why is my smart contract fail to install with an error on my peer?]
Why is my rule not working? 

  What’s happening 

You have a rule that should execute, but it isn't working.

  Why it’s happening 

The order of execution can sometimes disrupt the rules you have in place.

  How to fix it 

Check to confirm that the rule you are expecting to execute is not getting dropped because another rule is executing before it.

The following list shows the execution order from our partner, Cloudflare. Evaluate where your rule lands in the order of execution and adjust the rule as needed.



1.  L7 DDoS mitigation
2.  URL rewrites
3.  Page rules
4.  Origin rules
5.  Cache rules
6.  Configuration rules
7.  Redirect rules
8.  IP Firewall (Access Rules)
9.  Bots
10. Web Application Firewall (including CIS Rule set, OWASP, and Custom rules)
11. Header modification
12. Cloudflare Access
13. Edge Functions
14. Load balancing
// Submit the 'createCar' transaction to the smart contract, and wait for it
// to be committed to the ledger.
await contract.submitTransaction('createCar', 'CAR12', 'Honda', 'Accord', 'Black', 'Tom');
console.log('Transaction has been submitted');

await gateway.disconnect();

} catch (error) {
console.error(Failed to submit transaction: ${error});
process.exit(1);
}
}
main();
Show more
2. Edit invoke.js to replace the following values:



* Replace <channel_name> with the name of the channel the smart contract was deployed on. You can find your CA name under the "Certificate Authorities" section of your connection profile.
* Replace <smart_contract_name> with the name of the installed smart contract. You can get this value from your network operator.
* Edit the contents of submitTransaction to invoke a function inside your smart contract. The invoke.js file is written to invoke the [FabCar smart contract](https://github.com/hyperledger/fabric-samples/tree/release-1.4/chaincode/fabcar). If you want to run the following file to submit a transaction, install FabCar and instantiate the smart contract on one of your channels.



3. Navigate to invoke.js using a terminal and run node invoke.js. If the command runs successfully, you should see the following output:

Transaction has been submitted

If you navigate to your channel by using the console, you are able to see that another block was added by the transaction.



Your transaction might fail if you did not configure an anchor peer on your channel. Unless you manually updated your connection profile, your application needs to use the [Service Discovery](https://hyperledger-fabric.readthedocs.io/en/release-2.2/discovery-overview.html) feature to learn about the peers it needs to submit the transaction to.