vania-janet/multiturn-rag-retrieval-data huggingface dataset:
location-modifier: modifier='' serviceName=myservice1;modifier='^' serviceName=myservice2
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Success 1m public-cr87c198fcf4bd458ca61402bb4c7e945a-alb1-258623678-gvf9n Successfully applied ingress resource.
Warning TLSSecretNotFound 1m public-cr87c198fcf4bd458ca61402bb4c7e945a-alb1-258623678-gvf9n Failed to apply ingress resource.
Normal Success 59s public-cr87c198fcf4bd458ca61402bb4c7e945a-alb1-258623678-gvf9n Successfully applied ingress resource.
Warning AnnotationError 40s public-cr87c198fcf4bd458ca61402bb4c7e945a-alb1-258623678-gvf9n Failed to apply ingress.bluemix.net/custom-port annotation. Error annotation format error : One of the mandatory fields not valid/missing for annotation ingress.bluemix.net/custom-port
Normal Success 40s public-cr87c198fcf4bd458ca61402bb4c7e945a-alb1-258623678-gvf9n Successfully applied ingress resource.
Warning AnnotationError 2s public-cr87c198fcf4bd458ca61402bb4c7e945a-alb1-258623678-gvf9n Failed to apply ingress.bluemix.net/custom-port annotation. Invalid port 7490.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.<-- </section "id="section-en-notice-warranty" "> --><-- <section "id="section-en-notice-limit-liab" "> --> 16. Limitation of Liability IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.<-- </section "id="section-en-notice-limit-liab" "> --><-- <section "id="section-en-notice-interpret" "> --> 17.
Later, you decide you do want to run the package on your peers. From the Channels tab, open the smart contract tile and click Update package details next to your organization. If you want to install the existing package, select it from the Existing package tab. Or, upload your own version of the smart contract package. Then select the peers to install it on. Since the smart contract definition is committed, the peer can immediately begin to process requests for the smart contract. 
 Install the smart contract on additional or new peers after it is committed to the channel After the smart contract definition is committed, maybe you need to install the smart contract package on additional peers or newly created peers. From the Channels tab, open the smart contract tile and click Update package details next to your organization. If you want to install the existing package, select it from the Existing package tab. Or, upload your own version of the smart contract package. Then select the peers to install it on. Since the smart contract definition is committed, the peer can immediately begin to process requests for the smart contract. 
 Change the smart contract endorsement policy of a smart contract definition Because the smart contract endorsement policy of a smart contract is agreed to by members of the channel before the smart contract can be committed to the channel, the endorsement policy cannot be updated without approval of other channel members, as defined in the channel lifecycle endorsement policy. Therefore, if you need to update the endorsement policy of a smart contract proposal or a committed smart contract, then you need to [submit a new proposal](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-install-propose) with the updated endorsement policy. You do not have to update the smart contract package in this case, but it is required to increment the smart contract version. 
 Change the lifecycle endorsement policy for the channel From the Channels tab, click Channel details and click the Settings icon and then click through to the Lifecycle endorsement policy step. 
 A new organization joins the channel and wants to approve a smart contract proposal. From the Channels tab, click the tile of the proposed smart contract and click Begin approval process.
Why does my Object Storage subscription never become ready? 

 What’s happening 

A cos subscription was created, but it does not have a ready status.

 Why it’s happening 

Check to see whether one of the following cases is true.



1. The Notifications Manager role is not set for your account nor project.
2. The Object Storage bucket doesn't exist, is not set to regional resiliency, or exists in a different region as the project.
3. An application or job is missing.



 How to fix it 

Look at the subscription source to see whether any error messages returned by running the [ibmcloud ce sub cos get --name SUB_NAME](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-get) command.



1. If the error message includes Verify you have assigned the Notifications Manager role to your project,



1. Go to [Manage access and users](https://cloud.ibm.com/iam/overview) and click Authorizations.
2. Click Create.
3. Select Code Engine as the Source Service and Cloud Object Storage as the Target Service.
4. Be sure to select the Notifications Manager service access checkbox.
5. Click Authorize.



2. If the error message includes Error accessing bucket in region, check the region that your project is in by running [ibmcloud ce project current](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-current). Find your bucket region by running [ibmcloud cos bucket-location-get --bucket BUCKET_NAME](https://cloud.ibm.com/docs/cloud-object-storage-cli-plugin?topic=cloud-object-storage-cli-plugin-ic-cos-cliic-find-bucket). Both the project and bucket must be in the same region. In addition, be sure that the resiliency is set to regional.
3.
HTTP2/H2DEMO/TMPL.GO [net]
(https://github.com/golang/net/archive/eb5bcb51f2a31c7d5141d810b70815c05d9c9146.zip),
SPDX-EXCEPTIONS
(http://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-2.2.0.tgz),
SPDX STANDARD [spdx-expression-parse]
(https://github.com/jslicense/spdx-expression-parse.js/releases/tag/v3.0.0)

END OF CREATIVE COMMONS ATTRIBUTION 3.0 GENERIC NOTICES AND INFORMATION
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

CREATIVE COMMONS ATTRIBUTION 4.0 GENERIC

The Program includes some or all of the following works licensed under
the Creative Commons.
The url to the license is https://creativecommons.org/licenses/by/4.0/legalcode

CANIUSE-LITE(NODE)
(http://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30000979.tgz),
CANIUSE-LITE
(http://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30000979.tgz),
FOOTER.JS [React-Router] (https://github.com/ReactTraining/react-router)

END OF CREATIVE COMMONS ATTRIBUTION 4.0 GENERIC NOTICES AND INFORMATION
Complete the following steps to determine whether you are impacted by this issue and, if necessary, apply the patch to resolve it:



1. To determine whether you are impacted, run the following command to see whether the CR was applied successfully:

oc get dataexhaust wa-data-governor -n $OPERAND_NS -o yaml

If you do not receive any error, then you do not need to apply the patch. If you receive an error similar to the following example, complete the next step to apply the patch:

message: 'Failed to create object: b''{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Internal
error occurred: replace operation does not apply: doc is missing path: /metadata/labels/icpdsupport/serviceInstanceId:
missing value","reason":"InternalError","details":{"causes":[{"message":"replace
operation does not apply: doc is missing path: /metadata/labels/icpdsupport/serviceInstanceId:
missing value"}]},"code":500}n'''
reason: Failed
status: "True"
type: Failure
ibmDataGovernorService: InProgress
2. From your operand namespace, run the following command to apply the patch. In the command, wa is used as the name of the instance. Replace this value with the name of your Watson Assistant instance:

cat <<EOF | oc apply -f -
apiVersion: assistant.watson.ibm.com/v1
kind: TemporaryPatch
metadata:
name: wa-data-governor
spec:
apiVersion: assistant.watson.ibm.com/v1
kind: WatsonAssistant
name: wa Replace wa with the name of your Watson Assistant instance
patch:
data-governor:
dataexhaust:
spec:
additionalLabels:
icpdsupport/serviceInstanceId: inst-1
kafkauser:
To resolve, the problem, use one of the following methods.



* Using runmqsc, run the following commands:

SET AUTHREC PROFILE('TEST.QUEUE') OBJTYPE(QUEUE) GROUP('demoapp') AUTHADD(PUT,GET,BROWSE,INQ)

SET AUTHREC PROFILE('TEST.QUEUE') OBJTYPE(TOPIC) GROUP('demoapp') AUTHADD(SUB,PUB)

Replace 'TEST.QUEUE' with the name of your queue., and 'demoapp' wither your application username. If you wish, you can grant access to an object to all connected applications by specifying the group 'mqwriter'.
* Via the web console:



* Select the new queue then 'Configuration' under the three dots at the top of the screen.
* Select 'Security' and click 'Add +'.
* Select 'Group' and enter the name 'mqwriter' as the 'Group Name'. Tick the 'MQI' checkbox, and ensure only the boxes below MQI are checked.
* Click the 'Create' button.
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. If you want to update your capabilities on the system channel screen, you must first upgrade your nodes.





 Capabilities in application channels 

Application capabilities define the way transactions are handled exclusively by the peers. As a result, these capabilities are not inherited from the system channel (which is managed by the ordering service) and the full list of capabilities can be seen, starting with 1.1, when creating a channel. Note that the Fabric version of all peers in the channel must be at least at the level of the application capability level and the channel capability level inherited from the ordering service. When creating a channel, the default application capability might be lower than the highest available level. This is done in cases where a new Fabric version with a new application capability has been released but it is not expected that most peers will be at the new Fabric version. You will see the default application capability in the Review channel information screen before creating the channel.

If you attempt create a channel with a orderer capability other than the default, the channel creation request must be signed by an ordering service organization. If this capability is incompatible with the Fabric version of your ordering nodes, the console blocks the signature from completing, as a successful signature would crash any ordering nodes at the lower Fabric version. You must upgrade all of the relevant nodes before the channel creation request can be signed.

Similarly, the console will block any attempt to join a peer to a channel with an application or channel capability it is incompatible with to prevent the peer from crashing. The peer must be upgraded before it can be joined to the channel.

Because channel creation requests cannot be edited, if a capability is selected in error, a new channel creation request must be made. {tip}

The following table shows the compatibility levels of peer image versions with the application capability level of a channel and which smart contract deployment process is used:
echo '{"network.hostname-override":"'${profileName}'"}' > /etc/rhsm/facts/katello.facts

echo "Registering system..."
subscription-manager register --org="${organization}" --activationkey="${activationKey}" --force

To run the script:



1. chmod +x reregister-ng-rhel-vsi.sh
2. ./reregister-ng-rhel-vsi.sh



If the script fails, provide the following parameters:



* capsule hostname
* organization
* activation key
* profile name







 Can I configure nested virtualization on a virtual server instance? 

Nested virtualization on virtual server instances is not a supported configuration.





 How do I resolve a SSH key error? 

When you copy an SSH key from a terminal to add the key to your VPC, sometimes extra line breaks are introduced which cause a parsing error. To avoid this issue, first paste your SSH key into a text editor and remove any extra line breaks. Then, copy the SSH key from text editor and paste it into the VPC UI, CLI, or API.





 Why do I receive an SSH key permission denied error? 

When you receive a SSH key permission denied error, your host might not be recognized as an authorized host. To add your host as a known host, run the following command in your terminal. Make sure that you replace [sFTP] with your host.

ssh-keyscan -t rsa [sFTP] >> /.ssh/known_hosts

If you need more help, you can open a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).

For troubleshooting information about z/OS virtual server instances, see [IBM Wazi as a Service documentation](https://www.ibm.com/docs/en/wazi-aas/1.0.0?topic=vpc-troubleshooting-zos-virtual-server-instances).
Problem authorizing the credit card. We're afraid this transaction has been rejected. Inactive card or card not authorized for card-not-present transactions.

 Why it’s happening 

Some credit card issuers don't allow transactions when it is being initiated by using a credit card on file. You might see this error message if your credit card has been deactivated.

 How to fix it 

Contact your credit card issuer for more information.





 Why is my credit card not authorized to place an order? 

 What’s happening 

You tried to place an order in the IBM Cloud console [Payments page](https://cloud.ibm.com/billing/payments), but you get the following error message:

> Could not place order. Problem authorizing the credit card.

 Why it’s happening 

Your credit card issuer has declined the transaction.

 How to fix it 

Contact your credit card issuer for more information.





 Why is IBM Cloud unable to process my order request? 

 What’s happening 

You tried to place an order in the IBM Cloud console [Payments page](https://cloud.ibm.com/billing/payments), but you get the following error message:

> Could not place order. Problem authorizing the credit card. We are unable to process your request: Transaction Rejected. Please contact Cloud Trust Enablement at [verify@us.ibm.com](mailto:verify@us.ibm.com).

 Why it’s happening 

IBM Cloud® was unable to process your transaction.

 How to fix it 

Contact the Cloud Trust and Enablement team by email at [verify@us.ibm.com](mailto:verify@us.ibm.com).





 Why was my change request rejected? 

 What’s happening 

You tried to place an order in the IBM Cloud console [Payments page](https://cloud.ibm.com/billing/payments), but you get one of the following error messages:

> Failed to complete the Change Request process due to the following error: We're afraid this transaction has been rejected. Invalid account number.

or
* To resolve this problem in your browser, you need to import those identities and associate them with the corresponding node:



* In the browser where you are experiencing the problem, click the Wallet tab followed by Add identity to import the JSON file into your wallet.
* Click Upload JSON and browse to the JSON file you exported using the Add files button.
* Click Submit.
* Now open the peer or ordering service node that this identity was originally associated to, and click on the Settings icon.
* Click the Associate identity button.
* Select the identity you just imported to your console wallet from the drop-down list.
* Click Associate.



* Repeat this process for each identity that was in the wallet of the original browser.



 Why it’s happening 

This problem can also occur when the console has lost contact with your Kubernetes cluster on IBM Cloud. This can happen if your console has not recently communicated with your cluster, or if you have made changes to your cluster that have overridden the settings used by the IBM Blockchain platform.

 How to fix it 

You can renew the communication between your console and the IBM Kubernetes service cluster on IBM Cloud by clicking on the service instance of your console in your Resource list and clicking the Refresh cluster button. When the link between your cluster and your console has been refreshed, click the Launch the IBM Blockchain Platform button.





 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? 

 What’s happening 

When you attempt to create a new organization MSP definition from the Organizations tab, you experience the error Unable to authenticate with the enroll ID and secret you provided.

 Why it’s happening 

This error occurs when the value that you specified for the enroll secret is not valid for the enroll ID that you selected in the Generate organization admin certificate section of the panel.

 How to fix it 

Verify that you have selected the correct organization admin enroll ID from enroll ID drop down list and enter the correct value for the enroll secret.





 Why am I getting the error An error occurred when updating channel when I try to add an organization to my channel? 

 What’s happening
Why can't I add a permitted network? 

You tried to add a permitted network, and couldn't.

  What’s happening 

You are unable to add a permitted network.

  Why it’s happening 

You cannot add duplicate zone and networks combinations.

  How to fix it 

Verify that you are trying to add unique zone and networks combinations.

For example:



*  Create zone1.com with network-1



*  Create zone1.com is successful
*  Add network-1 is successful



*  Create duplicate zone1.com with network-1



*  Create zone1.com is successful
*  Add network-1 fails
Arguments:
subscription_name Name the subscription channel to refresh
db_name The name of the replicated database

Usage:
exampledb=> SELECT refresh_subscription('subs1','exampledb');







 Setting up Logical Replication on the Publisher 

To configure your external PostgreSQL as a publisher,



* Edit your local pg_hba.conf and add the following

hostssl replication replicator 0.0.0.0/0 md5
hostssl all replicator 0.0.0.0/0 md5

The "replicator" field is the user that you set up with the [PostgreSQL privilege REPLICATION](https://www.postgresql.org/docs/current/sql-createrole.htmlreplication).
* Edit your local postgresql.conf with the required [logical replication configuration](https://www.postgresql.org/docs/current/logical-replication-config.html). Set wal_level to 'logical', and set listen_addresses='' to accept connections from any host.

listen_addresses=''
wal_level = logical
* Restart your PostgreSQL server.



Now you can define a publisher on the database and add the tables that you want to replicate to the subscriber.



* Log in to database you want to publish from with your replication user.

psql -U replicator -d exampledb
* Create the publication channel.

exampledb=> CREATE PUBLICATION my_publication;
* Add tables to publisher.

exampledb=> ALTER PUBLICATION my_publication ADD TABLE my_table;







 Setting up Logical Replication on the Subscriber 

To configure your Databases for EnterpriseDB deployment as a subscriber,



* Log in to the database created for replication with admin user.

psql -U admin -d exampledb
* Run the following query to call the create_subscription function and create the subscriber channel.
Why can't I migrate all of my services? 

Not all IBM Cloud® services are eligible for migration.

  What’s happening 

You're unable to migrate certain services.

  Why it’s happening 

Services that can't be added to resource groups and aren't managed by using Identity and Access Management (IAM) can't be migrated. If a service is not eligible, there isn't an option for migration.

  How to fix it 

Check the services to confirm they're eligible for migration. You receive a notification and a Migrate icon ![Migrate icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/migrate.svg) is displayed to indicate if a service is eligible for migration.
Message: The private registry name is already being used.

Use a different name and try again.





 BXNUI0096E 

Message: The app wasn't created.

Your account is inactive because it was canceled or suspended.

For instructions to fix this problem, see the [Account is inactive](https://cloud.ibm.com/docs/account?topic=account-ts_accnt_inactive) troubleshooting topic.





 BXNUI0097E 

Message: Before you can add an app, at least one space must be associated with your organization and region.

In the IBM Cloud console, go to Manage > Account > Cloud Foundry Orgs, and click Create. When the space is created, try again. For more instructions to fix this problem, see [no spaces associated with my current org](https://cloud.ibm.com/docs/account?topic=account-ts_no_space).





 BXNUI0098E 

Message: The list of credentials can't be retrieved at the moment.

Try again later. If you see this message again, go to the [IBM Cloud status page](https://cloud.ibm.com/status?selected=status) to check whether a service or component has an issue. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0099E 

Message: The '{0}' credential wasn't added.

Try to use a different name, or try again later. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0100E 

Message: The '{0}' credential wasn't deleted.

The credential might have already been deleted.

Return to the resource list and try again. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0101E
spdx-exceptions ([https://github.com/jslicense/spdx-exceptions.json/archive/v2.2.0.zip](https://github.com/jslicense/spdx-exceptions.json/archive/v2.2.0.zip)), SPDX ([https://github.com/spdx](https://github.com/spdx)), SPDX STANDARD [spdx-expression-parse] ([https://github.com/spdx/spdx-spec](https://github.com/spdx/spdx-spec)), GO GOPHER [gonum/gonum](https://github.com/gonum/gonum/archive/4340aa3071a0.zip), DOCUMENTATION [opencontainers/runc](https://github.com/opencontainers/runc/tree/v0.1.1), H2DEMO/TMPL.GO [x/net], POLY [google-api-go-client](https://github.com/googleapis/google-api-go-client/tree/5213b8090861), DIR.TMPL [x/tools], THE IVY MASCOT [x/mobile](https://github.com/golang/mobile/tree/e47acb2ca7f9)





 Creative Commons Attribution 4.0 Generic 

The Program includes some or all of the following works licensed under the Creative Commons. The URL to the license is [https://creativecommons.org/licenses/by/4.0/legalcode](https://creativecommons.org/licenses/by/4.0/legalcode)