vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Boot via: image
HW model: PIO-518D-TLN4F-ST031
HW S/N: S14073214705613
HW UUID: 00000000-0000-0000-0000-0CC47A07EF22
Uptime: 12:57:47 up 59 min, 1 user, load average: 0.35, 0.27, 0.26
vyatta@acs-jmat-vyatta01:$

All your commands now work again, and you can proceed normally.

The HTTPS certificate /etc/lighttpd/server.pem might also fail to copy during the OS upgrade process, which can cause High Availability (HA) configurations to fail to synchronize. To fix this problem, copy over the old server.pem file in addition to the files listed (issue su - to reach root level, then issue the copy command), then issue restart https to restart the HTTPS demon.m file (and the files listed previously).
r4+8dKA1xz+jPhWDQgQYb3Wnh8VK8Ouids6uFnsoc3KDymbzoWZYctp8PA6uBzJ/
25RGiZquRu9MYJIWkQ46WQ14PoJ8BiYuJa/N6L47+Jr2vaCntmXBU4rFrjctHqq8
Hct9q5OVYXbYLQB+MM3gYyyFBQpZ1sHZD4D6K3AISRGsOE9rrovGjUfO8mLKE6a
AQEFBQADggEBAMe+kmdPNtt8LOpaAy+u5i9GpgHfH5zW2sX4Lj7srkqwmyxavqjE
XvM9PPudXV9OCUWewtlm/Eqo1pYIRudFBrjg5UJyKpM4sWWdKIrTk8RZusdOUvKU
0vBRJRJ3Yy/1olXFO05FFSotAyB9P5v9siMwdWUhM9pSiGwoNXCB74m2sxgUh10J
H0IvDl3SL4ptosV10KJtbOiO/YV9XXNaW8/X/2uM9Y3stcnSvzJGrFlPmbhK7Vsd
uL6/wSnV1E70CDT+KPPapzVJr/S8nP5xHVVl/5/JUGZa8rx01g9EBmX36H3T
kHD85XOkSI4y04Y3t6pMVbIAz0vipOmHYlM=
-----END NEW CERTIFICATE REQUEST-----
Show more
2. Copy the content of the file starting with ---BEGIN NEW CERTIFICATE REQUEST--- all the way to ---END NEW CERTIFICATE REQUEST---.
3.
Waiting for service binding to become ready...
Status: Pending (Processing Resource)
Status: Pending (Processing Resource)
Status: Creating service binding
Status: Creating service binding
Status: Ready
Waiting for application revision to become ready...
Traffic is not yet migrated to the latest revision.
Ingress has not yet been reconciled.
Waiting for load balancer to be ready
OK







 ibmcloud ce application create 

Create an application.

ibmcloud ce application create --name APP_NAME ((--image IMAGE_REF | (--build-source SOURCE [--image IMAGE_REF])) [--argument ARGUMENT] [--build-commit BUILD_COMMIT] [--build-context-dir BUILD_CONTEXT_DIR] [--build-dockerfile BUILD_DOCKERFILE] [--build-git-repo-secret BUILD_GIT_REPO_SECRET] [--build-size BUILD_SIZE] [--build-strategy BUILD_STRATEGY] [--build-timeout BUILD_TIMEOUT] [--cluster-local] [--command COMMAND] [--concurrency CONCURRENCY] [--concurrency-target CONCURRENCY_TARGET] [--cpu CPU] [--env ENV] [--env-from-configmap ENV_FROM_CONFIGMAP] [--env-from-secret ENV_FROM_SECRET] [--ephemeral-storage EPHEMERAL_STORAGE] [--force] [--max-scale MAX_SCALE] [--memory MEMORY] [--min-scale MIN_SCALE] [--mount-configmap MOUNT_CONFIGMAP] [--mount-secret MOUNT_SECRET] [--no-cluster-local] [--no-wait] [--output OUTPUT] [--port PORT] [--quiet] [--registry-secret REGISTRY_SECRET] [--request-timeout REQUEST_TIMEOUT] [--revision-name REVISION_NAME] [--service-account SERVICE_ACCOUNT] [--user USER] [--visibility VISIBILITY] [--wait] [--wait-timeout WAIT_TIMEOUT]



 Command Options
1.40.4 14 December 2022 <br><br> * Fixed various bugs.<br><br><br> 
 1.40.3 07 December 2022 <br><br> * Fixed various bugs.<br><br><br> 
 1.40.2 01 December 2022 <br><br> * Updated the output of the project get command to display the resource quota for custom domain mappings for a project.<br> * Fixed various bugs.<br> * Updated translations for the CLI.<br><br><br> 
 1.40.1 10 November 2022 <br><br> * Fixed various bugs.<br> * Updated translations for the CLI.<br><br><br> 
 1.40.0 27 October 2022 <br><br> * Added validation checks for ephemeral storage to clarify the relationship between ephemeral storage and memory. Ephemeral storage is bounded by the configured memory. See [Limits and quotas for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limits) and [Supported memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo).<br> * Fixed various bugs.<br><br><br> 
 1.39.6 20 October 2022 <br><br> * Fixed various bugs.<br> * Updated translations for the CLI.<br><br><br> 
 1.39.5 06 October 2022 <br><br> * Fixed various bugs.<br><br><br> 
 1.39.3 15 September 2022 <br><br> * Fixed various bugs.<br> * Updated translations for the CLI.<br><br><br> 
 1.39.2 31 August 2022 <br><br> * Fixed various bugs.<br> * Upgraded to Go 1.19.0.<br><br><br>
Generate an API key, then request a refresh token. For more information, see [Generating an IBM Cloud IAM token by using an API key](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey).
2. Copy one of the following example requests and replace the variables that you want to use.

Example request to create a version 1.4.0 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "ibm-system-storage-block-csi-driver", "storage-template-version": "1.4.0", "update-assignments": true, "user-config-parameters": { "entry.name": "NAMESPACE","user-secret-parameters": }

Example request to create a version 1.5.0 configuration.
To view a full list of valid operator conditions for a claim rule, see [Trusted Profiles API](https://cloud.ibm.com/apidocs/iam-identity-token-apiupdate-claim-rule)



 Command options 

NAME|ID (required)
: Name or ID of the trusted profile to to update a rule for.

RULE_NAME|RULE_ID (required)
: The name or ID of the rule to update.

--type
: 'Profile-SAML' for a SAML rule or 'Profile-CR' for a compute resource rule.

--conditions
: List of conditions, provided as comma separated list of triple values "claim:CLAIM,operator:OPERATOR,value:VALUE". To specify mutiple conditions, specify the flag multiple times --conditions "claim:CLAIM1,operator:OPERATOR1,value:VALUE1" --conditions "claim:CLAIM2,operator:OPERATOR2,value:VALUE2".

--cr-type
: The compute resource type the rule applies to, required only if type is specified as 'Profile-CR'. Values are VSI for Virtual Service Instance on VPC, IKS_SA for Service Accounts on Kubernetes clusters, or ROKS_SA for managed Red Hat OpenShift.

--expiration
: Specify an expiration in seconds for SAML rules. Must not be provided for trusts established to Compute Resources (type = Profile-CR).

--name
: New name for the rule.

--realm-name
: Issuer Id for trusts established via IBMid with federation, or appid:// for trusts established via App ID federation. Must not be provided for trusts established to Compute Resources (type = Profile-CR).

--output FORMAT
: Specify output format. Only 'JSON' is supported.

-f, --force
: Force failure if multiple rules are found.

-q, --quiet
: Suppress verbose output.





 Examples 

Update rule ClaimRule-test-id in profile my-profile with new name test-rule:
}'





 Upgrading through the API 

Similar to provisioning through the API, you need to complete [the necessary steps to use the resource controller API](https://cloud.ibm.com/docs/databases-for-mongodb?topic=cloud-databases-provisioningprovisioning-through-the-resource-controller-api) before you can use it to upgrade from a backup. Then, send the API a POST request. The parameters name, target, resource_group, and resource_plan_id are all required. You also supply the version and backup ID. The new deployment has the same memory and disk allocation as the source deployment at the time of the backup.

Upgrade from MongoDB 4.2 to 5.0 by first [restoring a backup](https://cloud.ibm.com/docs/databases-for-mongodb?topic=databases-for-mongodb-dashboard-backups&interface=uirestore-backup) of your data into a new version 4.4 deployment. Then, follow the same process to upgrade to version 5.0. Upgrading through PITR is not supported.

curl -X POST https://resource-controller.cloud.ibm.com/v2/resource_instances -H 'Authorization: Bearer <>' -H 'Content-Type: application/json' -d '{
"name": "my-instance",
"target": "bluemix-us-south",
"resource_group": "5g9f447903254bb58972a2f3f5a4c711",
"resource_plan_id": "databases-for-mongodb-standard",
* Error: When you upgrade with a user ID other than admin, the migration job fails.
* Cause: The migration script assumes that the script is run by a user with the admin user ID.
* Solution: Apply a patch that allows the migration to be successful. Complete the following steps:



1. From the Cloud Pak for Data web client, get the user ID of the owner of the instance that you want to upgrade.
2. Download the wd-migration-uid-patch.zip patch file from the [Watson Developer Cloud GitHub](https://github.com/watson-developer-cloud/doc-tutorial-downloads/blob/master/discovery-data/latest/wd-migration-uid-patch.zip) repository.
3. Extract the wd-migration-uid-patch.yaml file from the archive file, and then open it in a text editor.
4. Replace the <user_id> variable with the user ID of the owner of the instance that you want to upgrade.
5. Run the following command in a terminal that is logged in to the cluster:

oc create -f wd-migration-uid-patch.yaml
6. Delete the previous migration job by using the following command:

oc delete job wd-discovery-multi-tenant-migration





After the job is deleted, the migration job restarts and the migration resumes.

The issue is fixed with the 4.0.9 release.
* Discovery generates a partial failure status message for the IBM Cloud Pak for Data OpenShift® APIs for Data Protection (OADP) backup and restore utility.



* Error: When you check the status of the OADP backup utility after using it to backup a cluster where Discovery is installed, a Phase: PartiallyFailed message is displayed. One or more Discovery components are included in the Failed list.
* Cause: Discovery cannot be backed up and restored by using the OADP backup and restore utility. When the Discovery service is present, and an administrator backs up an entire IBM Cloud Pak for Data instance, a status message is displayed that indicates a partial failure.
Generate an API key, then request a refresh token. For more information, see [Generating an IBM Cloud IAM token by using an API key](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey).
2. Copy one of the following example requests and replace the variables that you want to use.

Example request to create a version 1.1.0 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "aws-ebs-csi-driver", "storage-template-version": "1.1.0", "update-assignments": true, "user-config-parameters":"user-secret-parameters": { "entry.name": "AWS-ACCESS-KEY",{ "entry.name": "AWS-SECRET-ACCESS-KEY",}

Example request to create a version 1.5.1 configuration.
* Error: When you upgrade with a user ID other than admin, the migration job fails.
* Cause: The migration script assumes that the script is run by a user with the admin user ID.
* Solution: Apply a patch that allows the migration to be successful. Complete the following steps:



1. From the Cloud Pak for Data web client, get the user ID of the owner of the instance that you want to upgrade.
2. Download the wd-migration-uid-patch.zip patch file from the [Watson Developer Cloud GitHub](https://github.com/watson-developer-cloud/doc-tutorial-downloads/blob/master/discovery-data/latest/wd-migration-uid-patch.zip) repository.
3. Extract the wd-migration-uid-patch.yaml file from the archive file, and then open it in a text editor.
4. Replace the <user_id> variable with the user ID of the owner of the instance that you want to upgrade.
5. Run the following command in a terminal that is logged in to the cluster:

oc create -f wd-migration-uid-patch.yaml
6. Delete the previous migration job by using the following command:

oc delete job wd-discovery-multi-tenant-migration





After the job is deleted, the migration job restarts and the migration resumes.

The issue is fixed with the 4.0.9 release.







 4.0.5, 26 January 2022 



* Discovery generates an error in the IBM Cloud Pak for Data OpenShift® APIs for Data Protection (OADP) backup and restore utility.



* Error: The utility does not complete successfully and the following message is written to the log: preBackupViaConfigHookRule on backupconfig/watson-discovery in namespace cpd (status=error)
* Cause: Discovery cannot be backed up and restored by using the OADP backup and restore utility. When the Discovery service is present, and an administrator attempts to backup an entire IBM Cloud Pak for Data instance, Discovery prevents the utility from completing successfully.