vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The requested resource group id is invalid or required permissions for performing the action are not present on resource group. Please check the resource group ID and permissions.

 How to fix it 

Check that the resource group that is specified on the --resource_group option is valid and that the user has the correct Schematics [IAM permissions](https://cloud.ibm.com/docs/schematics?topic=schematics-accessblueprint-permissions) to create blueprints.

Rerun the blueprints create operation with the correct group name or permissions.





 Blueprint create fails with the error blueprint JSON validation failed: field missing or invalid in config 

 What’s happening 

When you create the configuration, the create fails before the config is created with the error that the config JSON validation failed due to an invalid or missing field in the config.

 Why it’s happening 

On create, Schematics validates that all the template inputs are satisfied. If inputs are missing the validation fails, and the create stops.

Sample error

FAILED
Could not create the blueprint. Please verify that your request is correct. If the problem persists, contact IBM Cloud support.

Invalid blueprint templates. Error - Blueprint json validation failed - Field config[resource_group_name] missing or invalid - Value for resource_group_name not defined in config

 How to fix it 

The blueprint template is expecting more input values that are not specified in any of the input files or passed as dynamic inputs. The error output lists name of the expected missing or invalid input. Check the template readme file to determine the needed dynamic inputs or add the input to an input file.

Rerun the blueprint create operation with all the needed inputs.





 Blueprint create fails with the error blueprint JSON validation failed - field missing or invalid 

 What’s happening 

When you create a configuration in Schematics, the create fails before the config is created with an error that the config contains invalid definitions.

 Why it’s happening 

The blueprint create validates the syntax of the YAML blueprint template file.
The CNAME, including the IBM suffix .cdn.appdomain.cloud., must be used for access to the service. For example, https://www.example-cname.cdn.appdomain.cloud

In the case of SAN certificate, multiple customer domains share a single SAN certificate by adding their domain names into the SAN entries. The service can then be accesses using the hostname, for instance https://www.example.com





 How is Domain Validation with redirect accomplished? 

It depends on your server. The procedure for completing Domain Validation for Apache and Nginx servers can be found on the [Completing Domain Control Validation for HTTPS](https://cloud.ibm.com/docs/CDN?topic=CDN-completing-domain-control-validation-for-https-with-dv-sanredirect) page.





 How long does Domain Validation take? 

Domain Validation normally takes 2 - 4 hours, but it varies depending on the method that is chosen for validation. DV with CNAME validation is the fastest, typically taking under an hour. DV using the Standard and Redirect methods typically take 4 hours after the challenge has been addressed.





 How long does it take to create and enable HTTPS for my CDN with a DV SAN certificate? 

A normal request to enable HTTPS takes an average of 3 - 9 hours, from the initial request to running.





 How long does it take to delete a CDN with a DV SAN certificate? 

Deleting your CDN requires that your domain be removed from the certificate on all of the Edge servers. This process can take up to 8 hours to complete.





 Is there any additional cost associated with using a DV SAN certificate for my CDN? 

No. DV SAN certificate configurations are provided to you at no additional charge that is compared with HTTP or HTTPS with a Wildcard certificate.





 Can my CDN created using HTTPS with Wildcard be updated to use a DV SAN certificate? 

No, a wildcard mapping cannot be changed to SAN certificate.





 What is a certificate authority? 

A certificate authority (CA) is an entity that issues digital certificates.





 Which CA does IBM Cloud® CDN service use for issuing a DV SAN certificate?
Why does the Ingress status show an ESSDNE error? 

Virtual Private Cloud

Classic infrastructure

Satellite

  What’s happening 

When you check the status of your cluster's Ingress components by running the ibmcloud ks ingress status-report get command, you see an error similar to the following example.

The secret is not present on the cluster or is in the wrong namespace (ESSDNE).

  Why it’s happening 

A secret created via the ibmcloud ks ingress secret create command was manually deleted from the cluster.

  How to fix it 

If the secret is no longer needed, delete it. If the secret is still needed, reapply it to the cluster.



*  If the secret is no longer needed, run the ibmcloud ks ingress secret rm command to remove it from the managed secret list.
*  If the secret is still needed, run the ibmcloud ks ingress secret update command to reapply the secret to the cluster.



If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In the case details, be sure to include any relevant log files, error messages, or command outputs.
Why does the Ingress status show an ESSDNE error? 

Virtual Private Cloud

Classic infrastructure

Satellite

  What’s happening 

When you check the status of your cluster's Ingress components by running the ibmcloud oc ingress status-report get command, you see an error similar to the following example.

The secret is not present on the cluster or is in the wrong namespace (ESSDNE).

  Why it’s happening 

A secret created via the ibmcloud oc ingress secret create command was manually deleted from the cluster.

  How to fix it 

If the secret is no longer needed, delete it. If the secret is still needed, reapply it to the cluster.



*  If the secret is no longer needed, run the ibmcloud oc ingress secret rm command to remove it from the managed secret list.
*  If the secret is still needed, run the ibmcloud oc ingress secret update command to reapply the secret to the cluster.



If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In the case details, be sure to include any relevant log files, error messages, or command outputs.
Why does the cluster master return a VPN server error? 

Virtual Private Cloud

Classic infrastructure

  What’s happening 

After you create or update a cluster, the master status returns a VPN server configuration error message similar to the following.

VPN server configuration update failed. IBM Cloud support has been notified and is working to resolve this issue.

  Why it’s happening 

The infrastructure credentials that are associated with the resource group that the cluster is created in are missing (such as the API key owner is no longer part of the account) or missing required permissions.

  How to fix it 

[Complete the troubleshooting guide](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster_infra_errors) to check and update the infrastructure credentials that are used for the resource group.
If you are already familiar with the manual process to deploy the components with the console, you can check out the [Ansible playbooks](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ansible), a powerful tool for scripting the deployment of components in your blockchain network.

This tutorial is meant to show how to join a peer to an existing network. It presumes that an ordering service has already been created using another IBM Blockchain Platform console (it is possible to join peers created in the IBM Blockchain Platform to any network running Hyperledger Fabric based components using the Fabric APIs or the CLI, but we will not show that process here). If you don't have an existing network to join, visit the [Build a network tutorial](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network) to learn how to create one. The Join a network tutorial takes you through the steps to create the following Org2 blockchain components, highlighted in the blue box:

Zoom

![Join network structure](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/ibp2-join-network.svg)

Figure 1. Join network structure

Perform the steps in the Join a network tutorial to create the following components and complete the following actions:



* One peer organizationOrg2
Create the Org2 Membership Services Provider (MSP) definition which defines the organization Org2.
* One peerPeer Org2
The ledger, Ledger x in the illustration above, is maintained by distributed peers. The peer is deployed with [Couch DB](https://hyperledger-fabric.readthedocs.io/en/release-2.2/couchdb_as_state_database.html) as the state database.
An API key is a unique code that is passed to an API to identify the application or user that is calling it. To prevent malicious use of an API, you can use API keys to track and control how that API is used. For more information about API keys, see [Understanding API keys](https://cloud.ibm.com/docs/account?topic=account-manapikey).



 Creating an API key in the console 



1. Log in to [IBM Cloud](http://cloud.ibm.com).
2. Go to [https://cloud.ibm.com/iam/serviceids](https://cloud.ibm.com/iam/serviceids).
3. Select the Service ID that you want to create an API for.
4. In the API keys tab, click Create.
5. Enter a name and description for the API key to specify the private worker installation, such as Pipeline Private Worker in IBM Cloud Private.
6. Click Create.
7. Copy or download your API key. You cannot retrieve your API key again after you create it.







 Creating an API key by using the CLI 

From the IBM Cloud CLI, type the following command:

$ ibmcloud iam service-api-key-create {worker-api-key-name} (SERVICE_ID_NAME|SERVICE_ID_UUID) [-d, --description DESCRIPTION] [--file OUT_FILE]

Creating API key {worker-api-key-name} of service
SERVICE_ID_NAME as username@domain.com...
OK
Service API key {worker-api-key-name} is created
Successfully saved API key information to FILE
Please preserve the API key! It cannot be retrieved after it's created.

Name {worker-api-key-name}
Description Description
Why did my app stop running? 

 What’s happening 

After you deploy an app, the app runs for a while and then ends unexpectedly.

 Why it’s happening 

Determine whether one of the following cases is true.



1. Your app code includes an exit when it completes its running cycle.
2. Your app code contains an error that is causing the app to end unexpectedly.
3. The image that your app is pulling from no longer exists because you deleted it or your [image retention policy](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention) in IBM Cloud Container Registry caused it to be deleted. For example, your app is scaling up because of incoming requests. However, the scale-up fails because the image no longer exists in Container Registry. Another typical situation is if your app is on a worker node that is scheduled to receive the latest security fixes. If Code Engine attempts to move your app to a different worker node and cannot find the image, the move fails and the app stops working.
4. The image that your app is pulling from no longer exists because while the image with the provided tag exists, it was overwritten after an application revision was created. The image that is associated with your specific application revision uses a unique container registry digest, and this digest is used for the life of your application revision. If you create a newer version of the image with the same tag as the original image, the original image is overwritten in the container registry. However, Code Engine cannot find this newer image, because the newer image has a different digest than the digest for the application revision. No new instances of the application can be created, and this scenario results in a failure of the application.



 How to fix it 

Try the following solutions to resolve your problem.



1. Code Engine apps are designed to run without exiting. If your app code includes an exit, then consider [running your code as a job](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-plan) instead.
2. Check for messages that might help you determine the cause.
What’s happening 

When a service that you bind to an app crashes, problems such as outages, exceptions, and connection failures might occur on the app. IBM Cloud doesn't automatically restart the app to recover from these problems.

 Why it’s happening 

This behavior is by design of Cloud Foundry.

 How to fix it 

You can manually restart an app that is already deployed by typing the following command in the command-line interface:

ibmcloud cf restart <APPNAME>

In addition, you can code the app to identify and recover from problems such as outages, exceptions, and connection failures.





 Orgs can't be found on IBM Cloud 

You might not be able to locate your organization on IBM Cloud when working on an IBM Cloud region.

 What’s happening 

You can log in to the IBM Cloud console successfully, but you can't push apps by using the Cloud Foundry command line interface.

When you try to push an app to IBM Cloud by using the Cloud Foundry command line interface, you see one of the following error messages with the organization name that is specified in the message:

Error finding org

Organization not found

 Why it’s happening 

This problem occurs because the API endpoint of the region that you want to work with isn't specified, and the organization you're looking for might be in a different region.

 How to fix it 

If you are pushing your app to IBM Cloud by using the Cloud Foundry command line interface, enter the ibmcloud cf api command and specify the API endpoint of the region. For example, enter the following command to connect to the IBM Cloud Europe United Kingdom region:

ibmcloud cf api https://api.eu-gb.cf.cloud.ibm.com





 App routes can't be created 

When you deploy an app to IBM Cloud, the route of the app can't be created if the host name that you specified is already being used.

 What’s happening 

When you deploy an app to IBM Cloud, you see the following error message:

Creating route hostname.domainname ... FAILED Server error, status code: 400, error code: 210003, message: The host is taken: hostname

 Why it’s happening
Rerun the blueprint create operation with all the needed inputs.





 Blueprint create fails with the error blueprint JSON validation failed - field missing or invalid 

 What’s happening 

When you create a configuration in Schematics, the create fails before the config is created with an error that the config contains invalid definitions.

 Why it’s happening 

The blueprint create validates the syntax of the YAML blueprint template file. If the syntax is specified incorrectly the create fails.

Sample error

Could not create the blueprint. Please verify that your request is correct. If the problem exists, contact IBM Cloud support.

Invalid blueprint templates. Error - Blueprint json validation failed - Field blueprint.modules missing or invalid

 How to fix it 

Correct the errors as identified in the validation messages. For more information about the syntax, see [blueprint template YAML schema](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-template-schema-yaml).

Push the changes to template and input files to the Git repositories.

Rerun the blueprint create operation with the corrected syntax.





 Why is Schematics not able to clone the private GitHub repository? 

 What’s happening 

Schematics isn't able to clone the private GitHub repository, and you are seeing the following error message: Failed to clone git repository, repository not found (check url, also check the scope 'repo' of the personal access token if SCHEMATICSGITTOKEN is used)

 Why it’s happening 

You didn't provide the correct GitHub token, or you didn't provide a GitHub token altogether.

 How to fix it 

Provide a [GitHub token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) and check to see whether the correct GitHub token has been provided in the github_token parameter in the create workspace or create blueprint API.





 Why is Schematics not able to clone the public GitHub repository?
Auditing events for VMware as a Service 

Use the IBM Cloud® Activity Tracker service to track how users and applications interact with IBM Cloud for VMware as a Service in IBM Cloud.

IBM Cloud Activity Tracker records user-initiated activities that change the state of a service in IBM Cloud. You can use this service to investigate for abnormal activity and critical actions, and comply with regulatory audit requirements. In addition, you can be alerted on actions as they happen. The events that are collected comply with the Cloud Auditing Data Federation (CADF) standard. For more information, see [Getting started with Activity Tracker](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-getting-started).



 Events that are related to virtual data centers 

Events are generated to track how users and applications interact with virtual data centers. The following table lists the actions that generate and send events to Activity Tracker.



Table 1. Description of actions that generate events related to virtual data centers

 Action Description 

 vmware.vdc.create An event is generated when a virtual data center instance is created. 
 vmware.vdc.delete An event is generated when a virtual data center instance is deleted. 
 vmware.vdc.update An event is generated when a virtual data center instance is modified. 







 Events that are related to director site management 

Events are generated when you access VMware Cloud Director™ in VMware as a Service. The following table provides the actions that generate and send events to Activity Tracker.



Table 2. Description of actions that generate events related to VMware Cloud Director site management

 Action Description 

 vmware.directorsite.create An event is generated when a VMware Cloud Director site is created. 
 vmware.directorsite.delete An event is generated when a VMware Cloud Director site is deleted. 
 vmware.directorsite-pvdc.create An event is generated when a VMware Cloud Director site provider virtual data center (PVDC) is created. 
 vmware.directorsite-pvdc.delete An event is generated when a VMware Cloud Director site PVDC is deleted.
[Overflow menu](https://cloud.ibm.com/docs-content/v1/content/006fd22ab2811b7d19804c763a00568b3da4c03a/CDN/images/overflow.png) menu until your CDN shows Running status. Alternatively, if you are on the CDN's details page, click Actions > Get status.



Your CDN is now running. From here, you can review the "How to" topics in the table of contents to further configure and manage your CDN.





 CDN CNAME 

IBM CDN CNAME (also called an endpoint) can make your CDN mapping status to Running because it can resolve your domain to Akamai edge servers if you cname your domain to it. IBM provides two CNAMEs, and you can create CNAME record in your DNS system to point your CDN domain to one of the CNAMEs.



 IBM CNAME 

IBM CNAME is the default CNAME. It is suffixed with cdn.appdomain.cloud. or cdnedge.bluemix.net. (The old mapping created before 08/05/2019), and you can define the prefix during [creating new CDN mapping](https://cloud.ibm.com/docs/CDN?topic=CDN-order-a-cdn).

The IBM CNAME is managed by IBM, and it is pointed to the Akamai's endpoint. The main function of IBM CNAME is ensuring your domain is still accessible when the CDN mapping is [Stopped](https://cloud.ibm.com/docs/CDN?topic=CDN-stopping-a-cdn) by switching the DNS record to point to the origin.

Let's take a SAN HTTPS CDN mapping example.cdn-demo.com for example: IBM CNAME: example-cname.cdn.appdomain.cloud. Origin's hostname: origin.example.com..

When the mapping is Running, the dig result of the domain resembles the following:

% dig +short example.cdn-demo.com
2. One public Ingress controller per zone is triggered for creation.
3. A load balancer service that exposes the Ingress controller is created and assigned a hostname.
4. The load balancer hostname is used to register the Ingress subdomain in Akamai. Akamai might have latency during the registration process.



Creating a cluster after deleting a cluster the same or similar name? See [No Ingress subdomain exists after you create clusters of the same or similar name](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_rate_limit) instead.

 How to fix it 

Typically, after the cluster is ready, the Ingress subdomain and secret are created after 15 minutes. If the Ingress subdomain and secret are still unavailable after your cluster is in a normal state for more than 15 minutes, you can check the progress of the creation process by following these steps:



1. [Log in to your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster). Because the subdomain is not available, the Red Hat OpenShift console can't open. Instead, you can set the cluster context with the --admin option through the CLI.

ibmcloud oc cluster config -c <cluster_name_or_ID> --admin
2. Verify that the worker nodes have a State of normal and a Status of Ready. After you create the cluster, it can take up to 20 minutes for the worker nodes to be ready.

ibmcloud oc worker ls -c <cluster_name_or_ID>

Example output

ID Public IP Private IP Flavor State Status Zone Version
kube-blrs3b1d0p0p2f7haq0g-mycluster-default-000001f7 169.xx.xxx.xxx 10.xxx.xx.xxx u3c.2x4.encrypted deployed Ready dal10 1.26
3.
If you have other clusters in the same region and resource that require the previous infrastructure credentials, repeat Step 3 to reset the infrastructure credentials to the previous account. Note that if you created clusters with a different infrastructure account than the account that you switch to, you might orphan those clusters.

Tired of switching infrastructure accounts each time you need to perform a cluster or worker action? Consider re-creating all the clusters in the region and resource group in the same infrastructure account. Then, migrate your workloads and remove the old clusters from the different infrastructure account.







 Unable to create or delete worker nodes due to endpoints error 

 What’s happening 

You can't manage worker nodes for your cluster, and you receive an error message similar to one of the following.

Worker deploy failed due to network communications failing to master or registry endpoints. Please verify your network setup is allowing traffic from this subnet then attempt a worker replace on this worker

Pending endpoint gateway creation

 Why it’s happening 

Worker nodes can communicate with the Kubernetes master through the cluster's virtual private endpoint (VPE).

One VPE gateway resource is created per cluster in your VPC. If the VPE gateway for your cluster is not correctly created in your VPC, the VPE gateway is deleted from your VPC, or the IP address that is reserved for the VPE is deleted from your VPC subnet, worker nodes lose connectivity with the Kubernetes master.

 How to fix it 

Re-establish the VPE connection between your worker nodes and Kubernetes master.



1. To check the VPE gateway for your cluster in the VPC infrastructure console, open the [Virtual private endpoint gateways for VPC dashboard](https://cloud.ibm.com/vpc-ext/network/endpointGateways) and look for the VPE gateway in the format iks-<cluster_ID>.



* If the gateway for your cluster is not listed, continue to the next step.
* If the gateway for your cluster is listed but its status is not Stable, [open a support case](https://cloud.ibm.com/docs/openshift?topic=openshift-get-helphelp-support).