vania-janet/multiturn-rag-retrieval-data huggingface dataset:
$ cat data.txt | cocoa change-request attachment update --change-request-id='CHGXXXXXXX' --change-attachment-id='CTASKXXXXXXX' --data='@/dev/stdin'

$ cocoa change-request attachment update --change-request-id='CHGXXXXXXX' --change-attachment-id='CTASKXXXXXXX' --data='@<path/to/file>'







 cocoa evidence commands 



 cocoa evidence create 

Creates evidence from the specified options and saves it to a file or prints it to the console.

Running the command:

$ cocoa evidence create --namespace=[choices: "ci", "cd"] Pipeline type the evidence was collected from
--evidence-name=<evidence-name> It will be used to name evidence-file in git
--evidence-type=<evidence-type> e.g: com.ibm.unit_test
--evidence-type-version=<evidence-type-version> --result=[choices: "failure", "success"] The result of the scan/test
--issue=<issue-url> e.g: --issue=foo --issue=bar || --issue=foo
--artifact=<artifact_url> <artifact_hash> Url and hash pair(s) to the test artifact(s)
--log=<log_url> <log_hash> Url and hash pair(s) to the log(s)
--pipeline-id=<pipeline-id> --pipeline-run-id=<pipeline-run-id> --pipeline-run-url=<pipeline-run-url> --toolchain-crn=<toolchain-crn> Name of the toolchain cloud resource
--output=<filename> If present, the evidence will be saved to the given file.

CLI options can be also set from environment variables except for issue, log, and artifact. Multiple issues or artifacts must be provided with multiple issue or artifact flags. For example:
$ cocoa evidence upload --backend=[choices: "git", "insights", "cos"] e.g. --backend=cos,git,insights
--namespace=[choices: "ci", "cd"] Pipeline type the evidence was collected from
--evidence-name=<evidence-name> It will be used to name evidence-file in git
--evidence-type=<evidence-type> e.g: com.ibm.unit_test
--evidence-type-version=<evidence-type-version> --result=[choices: "failure", "success"] The result of the scan/test
--issue=<issue-url> e.g: --issue=foo --issue=bar || --issue=foo
--artifact=<artifact_url> <artifact_hash> Url and hash pair(s) to the test artifact(s)
--log=<log_url> <log_hash> Url and hash pair(s) to the log(s)
--pipeline-id=<pipeline-id> --pipeline-run-id=<pipeline-run-id> --pipeline-run-url=<pipeline-run-url> --toolchain-crn=<toolchain-crn> Name of the toolchain cloud resource
Show more

CLI options can be also set from environment variables except for backend, issue, log, and artifact. Multiple issues or artifacts must be provided with multiple issue or artifact flags. For example:

cocoa evidence upload --backend=git --artifact <url> <hash> --artifact <url> <hash> --issue <issue-url> --issue <issue-url> --git-provider='github'

artifact consists of a URL that points to the artifact file and a hash, provide these items in the same way as in the previous example.





 cocoa evidence summarize 

Queries evidence from the Evidence Locker and generates an Evidence Summary from their contents.
VRVDR-52722 9.8 DLA-2337-1 CVE-2018-20852, CVE-2019-10160, CVE-2019- 16056, CVE-2019-20907, CVE-2019-5010, CVE- 2019-9636, CVE-2019-9740, CVE-2019-9947, CVE- 2019-9948: Debian DLA-2337-1 : python2.7 security update 
 VRVDR-52618 9.8 DLA-2323-1 CVE-2019-18814, CVE-2019-18885, CVE-2019- 20810, CVE-2020-10766, CVE-2020-10767, CVE- 2020-10768, CVE-2020-12655, CVE-2020-12771, CVE-2020-13974, CVE-2020-15393: Debian DLA- 2323-1 : linux-4.19 new package 
 VRVDR-52476 5.9 DLA-2303-1 CVE-2020-16135: Debian DLA-2303-1 : libssh security update 
 VRVDR-52197 N/A N/A Privilege escalation in "reset ipv6 neighbors" / "reset ip arp" commands 









 1912e 



 Issues Resolved 



Issues resolved for 1912e

 Issue Number Priority Summary 

 VRVDR-51957 Blocker Modelled copy command incorrectly enforcing ssh-known-host check in 1912e 
 VRVDR-51952 Blocker Group ownership for non ROOT files got changed to ssh @ 1912e 
 VRVDR-51937 Blocker show interface dataplane dp0xe<x> displays incorrect speed for copper ports when interface is down 
 VRVDR-51828 Major SIAD ACL: BCM SDK error when deleting ACL configuration 
 VRVDR-51639 Critical Response for "request hardware-diag version" takes much longer with 1912b 
 VRVDR-51619 Critical SIAD ACL: Ensure that rulesets which would exceed the TCAM are rejected 
 VRVDR-51616 Critical Storm Control triggered snmpd warning messages in journal
Troubleshooting for GitHub, GitLab, and Git Repos and Issue Tracking 

General problems with using GitHub, GitLab, and Git Repos and Issue Tracking might include GitHub authentication or tool integration configuration issues. In many cases, you can recover from these problems by following a few easy steps.



 I tried to add the GitHub tool integration to my toolchain, why wasn't the tool integration added? 

You must authorize with GitHub so that IBM Cloud is authorized to access your GitHub account.

 What’s happening 

The GitHub tool integration wasn't added to your toolchain. If you are using Terraform or the API to create the GitHub tool integration, the attempt fails with the User is not authorized with https://api.github.com error message.

 Why it’s happening 

If IBM Cloud is not authorized to access your GitHub account, the tool integration is not added to your toolchain.

 How to fix it 

If you are configuring the GitHub tool integration by using the console while you are creating your toolchain, follow these steps to authorize with GitHub:



1. In the Configurable Integrations section, click GitHub.
2. If you are creating the toolchain on IBM Cloud Public and IBM Cloud is not authorized to access GitHub, select the method of authentication that will be used to access Github.



* If you choose OAuth, click Authorize to go to the GitHub website. If you don't have an active GitHub session, you are prompted to log in. Click Authorize IBM-Cloud to allow IBM Cloud to access your GitHub account.
* If you choose Personal Access Token, specify a valid personal access token for GitHub.





If you are using the console and you already have a toolchain, update the GitHub tool integration's configuration:



1. From the IBM Cloud console, click the menu icon !
You can override this behavior by providing following environment variables:



* MAX_RETRY_ATTEMPTS - The number of retry attempts Cocoa CLI makes before it gives up. For example, MAX_RETRY_ATTEMPTS=5
* RETRY_STATUS_CODE - The response status codes for which the retry happens. For example, RETRY_STATUS_CODE=409,422,500 to retry on these three status codes.



export MAX_RETRY_ATTEMPTS=5 Retry API calls 5 times.
export RETRY_STATUS_CODE=409,422,500 Retry API calls for response codes 409, 422 and 500.

The retries are exponentially spaced in time, so setting up higher retry attempts causes the retries to be spaced further apart.





 Elapsed time for command execution 

Cocoa CLI can display the elapsed time of any command in seconds by setting DISPLAY_ELAPSED_TIME to a nonempty string as follows:

export DISPLAY_ELAPSED_TIME=1 Display a snippet showing the total execution time of the cli command, example Elapsed time: 5.32 seconds





 CLI commands 

Although ServiceNow is documented, it is not supported by the default IBM Cloud DevSecOps reference implementation. However, if you want to learn about using ServiceNow with the DevSecOps reference implementation, get help from IBM Cloud development teams by joining us on [Slack](https://ic-devops-slack-invite.us-south.devops.cloud.ibm.com/).





 cocoa pull request commands 



 cocoa check pull-request-approval 

Checks the approval state of a Pull Request on a commit hash. If the Pull Request was not approved, it creates a new incident issue in the specified repository. The command can identify emergency pull requests marked with a label, in this case it has an exit code of 0.

Required Environment Variables:

GHE_TOKEN= Github Enterprise API Token (Optional if you are using --git-token-path field)
GHE_ORG= The owner of the repository
GHE_REPO= The repository name
INCIDENT_ISSUE_REPO= The incident issue repo name
EMERGENCY_LABEL= Emergency Label name
1.0.18 20 June 2018 <br><br> * Added a fix for unbinding user-provided service instances.<br> * Performance improvements.<br><br><br> 
 1.0.17 12 June 2018 Added support for binding (ibmcloud wsk service bind) and unbinding (ibmcloud wsk service unbind) user-provided service instances that are created by using the ibmcloud cf create-user-provided-service command. 
 1.0.16 24 May 2018 Minor bug fixes and improvements. 
 1.0.15 21 May 2018 Minor bug fixes and improvements. 
 1.0.14 17 May 2018 Enabled support for the & character in org and space names. 
 1.0.13 07 May 2018 Minor bug fixes and error handling improvements. 
 1.0.12 30 April 2018 IBM Cloud SDK updates to maintain bx CLI compatibility. 
 1.0.11 23 April 2018 Minor bug fixes and improvements. 
 1.0.10 09 April 2018 <br><br> * Added new --web-secure option to the ibmcloud wsk action create and update commands to secure web action endpoints.<br> * Fixed back-to-back path parameter [defect](https://github.com/apache/openwhisk-cli/issues/237).<br><br><br> 
 1.0.9 16 March 2018 Enabled support for service bind at the package level. 
 1.0.8 22 February 2018 Enabled support for IAM service bind. 
 1.0.7 02 February 2018 <br><br> * Updated ibmcloud wsk api to accept path parameters such as /api/{id}.<br> * Restored proxy support.<br> * Removed swift:3.<br><br><br> 
 1.0.6 30 January 2018 Fixed a bug with the command ibmcloud wsk service bind for actions inside a package.
If neither are provided, the App ID SDK tries to retrieve the application_uri of the app that is running on IBM Cloud and append a default suffix /ibm/cloud/appid/callback.
5. By using the information obtained in the previous steps, initialize the SDK.

passport.use(new WebAppStrategy({
tenantId: "<tenantID>",
clientId: "<clientID>",
secret: "<secret>",
oauthServerUrl: "<oauthServerURL>",
redirectUri: "<appURL>" + CALLBACK_URL
}));
6. Configure passport with serialization and deserialization. This configuration step is required for authenticated session persistence across HTTP requests. For more information, see the [passport docs](http://www.passportjs.org/docs/).

passport.serializeUser(function(user, cb) {
cb(null, user);
});
passport.deserializeUser(function(obj, cb) {
cb(null, obj);
});
7. Add the following code to your server.js file to issue the service redirects.

app.get(CALLBACK_URL, passport.authenticate(WebAppStrategy.STRATEGY_NAME));
8. Register your protected endpoint by adding the following code snippet into your app.js file.

app.get(‘/protected_resource’, passport.authenticate(WebAppStrategy.STRATEGY_NAME), function(req, res) {res.json(req.user); });



For more information, see the [App ID Node.js GitHub repository](https://github.com/ibm-cloud-security/appid-serversdk-nodejs).







 Configuring the Liberty for Java SDK 

You can configure App ID to work with your Liberty for Java web applications.



 Before you begin
You can use this instance of Bitbucket Issues for your entire toolchain, even if the toolchain contains multiple Bitbucket repos.



If you don't have owner or master privileges for the repo that you are linking to, your integration is limited because you can't use a webhook. Webhooks are required to automatically run a pipeline when a commit is pushed to the repo. Without a webhook, you must start your pipelines manually.



 Configuring Bitbucket by using the API 

The Bitbucket tool integration supports the following configuration parameters that you can use with the [Toolchain HTTP API and SDKs](https://cloud.ibm.com/apidocs/toolchain) when you [create](https://cloud.ibm.com/apidocs/toolchaincreate-tool), [read](https://cloud.ibm.com/apidocs/toolchainget-tool-by-id), and [update](https://cloud.ibm.com/apidocs/toolchainupdate-tool) tool integrations.

You must specify the tool_type_id property in the request body with the bitbucketgit value.



Table 1. Bitbucket tool integration parameters

 Parameter Usage Type Terraform argument Description 

 api_root_url optional, updatable String api_root_url The URL of the Bitbucket API, such as https://api.bitbucket.org. 
 default_branch optional, updatable String default_branch The name of the default branch, for example, main. 
 enable_traceability optional, updatable, Default: false Boolean enable_traceability Set this value to true to track the deployment of code changes by creating tags, labels and comments on commits, pull requests, and referenced issues. 
 git_id optional, immutable String git_id Set this value to bitbucketgit for bitbucket.org, or to the GUID of a custom Bitbucket server.
You can use this instance of GitLab Issues for your entire toolchain, even if the toolchain contains multiple GitLab repos.

If you don't have owner or master privileges for the repo that you are linking to, your integration is limited because you can't use a webhook. Webhooks are required to automatically run a pipeline when a commit is pushed to the repo. Without a webhook, you must start your pipelines manually.





 Configuring GitLab by using the API 

The GitLab tool integration supports the following configuration parameters that you can use with the [Toolchain HTTP API and SDKs](https://cloud.ibm.com/apidocs/toolchain) when you [create](https://cloud.ibm.com/apidocs/toolchaincreate-tool), [read](https://cloud.ibm.com/apidocs/toolchainget-tool-by-id), and [update](https://cloud.ibm.com/apidocs/toolchainupdate-tool) tool integrations.

You must specify the tool_type_id property in the request body with the gitlab value.



Table 1. GitLab tool integration parameters

 Parameter Usage Type Terraform argument Description 

 api_root_url optional, updatable String api_root_url The URL of the GitLab API. 
 api_token optional, updatable Password api_token The Personal Access Token (PAT). This parameter is required only if the auth_type is set to pat, otherwise it is ignored. 
 auth_type optional, updatable, Default: oauth String auth_type Set the authentication method to use to access the Git provider. 
 default_branch optional, updatable String default_branch The name of the default branch of the Git repo. 
 enable_traceability optional, updatable, Default: false Boolean enable_traceability Set this value to true to track the deployment of code changes by creating tags, labels and comments on commits, pull requests, and referenced issues.
HCX troubleshooting 

Review the following information for common HCX™ issues and fixes.



 HCX Client user interface issues 



 HCX user interface token timeout 

Typically, if the VMware vCenter Server® user interface has been opened for some time you might encounter a timeout in the HCX™ user interface, because the login token to the HCX Manager server timed out. Log out of the vSphere web user interface and back in to refresh the token.





 HCX Client user interface displaying “NaN” for all metrics on the dashboard screen 

This issue is related to the permissions of the currently logged in vCenter account. Ensure that the Enterprise Administrator group is set in the HCX cloud side appliance manager user interface.







 Migration issues 

Migration issues in the current versions of HCX are usually in three categories: licensing, cloud gateway networking connectivity, and destination hardware compatibility.



 Licensing 

If a migration fails because of a licensing issue, current versions of HCX clearly display this issue in the error message with the client web user interface within the vCenter user interface.





 Network (WAN) connectivity 

If you have any WAN connectivity issues, always check the Interconnect -> HCX Components screen within the HCX user interface for tunnel status. The fleet components typically do not need to be reset or rebooted. If WAN connectivity is restored, they reconnect automatically.

If any fixes and updates were applied to the HCX managers (Client and Cloud) and those updates also patch issues with the fleet components, you must redeploy the Cloud Gateway and any L2Cs deployed. It is possible to do further tunnel status debugging, by connecting to HCX Manager through an SSH client such as ccli.



1. SSH to HCX Manager by using the admin account and the supplied password.
2. Run the su – command and enter the password of the root user (same as admin password) to change to root.
3. Change the directory to /opt/vmware/bin and run the ./ccli command. If this attempt is not successful because the environment is not set up for root, run the ./ccliSetup.pl command.
4.
Before you debug Ingress, first check out [Debugging app deployments](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_apps). Ingress issues are often caused by underlying issues in your app deployment or in the ClusterIP service that exposes your app. For example, your app label and service selector might not match, or your app and service target ports might not match.
2. Check your Ingress resource deployment and look for warnings or error messages.

oc describe ingress <ingress_resource_name>

In the Events section of the output, you might see warning messages about invalid values in your Ingress resource or in certain annotations that you used. For annotations, note that the IBM Cloud Kubernetes Service annotations (ingress.bluemix.net/<annotation>) and NGINX annotations (nginx.ingress.kubernetes.io/<annotation>) are not supported for the Ingress controller or the Ingress resource in Red Hat OpenShift version 4. If you want to customize routing rules for apps in a cluster that runs Red Hat OpenShift version 4, you can use [route-specific HAProxy annotations](https://docs.openshift.com/container-platform/4.11/networking/routes/route-configuration.htmlnw-route-specific-annotations_route-configuration), which are in the format haproxy.router.openshift.io/<annotation> or router.openshift.io/<annotation>.

NAME: myingress
Namespace: default
Address: 169.xx.xxx.xxx,169.xx.xxx.xxx
Default backend: default-http-backend:80 (<none>)
Rules:
Host Path Backends
---- ---- --------
mycluster-<hash>-0000.us-south.containers.appdomain.cloud
/tea myservice1:80 (<none>)
Debugging Ingress 

Virtual Private Cloud

Classic infrastructure

 What’s happening 

You exposed your app by creating an Ingress resource for your app in your cluster. However, when you try to connect to your app through the Ingress subdomain or the IP address of the Ingress controller, the connection fails or times out.

 How to fix it 

The steps in the following sections can help you debug your Ingress setup.

Before you begin, ensure you have the following [IBM Cloud IAM access policies](https://cloud.ibm.com/docs/openshift?topic=openshift-users) for IBM Cloud Kubernetes Service: - Editor or Administrator platform access role for the cluster - Writer or Manager service access role

Seeing an Application is not available page when you try to access your app's subdomain? [Check your app deployment and Ingress resource configuration](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-debug-roks4app-debug-ingress-43). Seeing a Connection timeout page? [Check the health of the Ingress controller pods](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-debug-roks4errors-43).



 Step 1: Check your app deployment and Ingress resource configuration 

Start by checking for errors in your app deployment and the Ingress resource deployment. Error messages in your deployments can help you find the root causes for failures and further debug your Ingress setup in the next sections.



1. Before you debug Ingress, first check out [Debugging app deployments](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_apps). Ingress issues are often caused by underlying issues in your app deployment or in the ClusterIP service that exposes your app. For example, your app label and service selector might not match, or your app and service target ports might not match.
2. Check your Ingress resource deployment and look for warnings or error messages.
VM performance issues You can troubleshoot the symptoms of VM performance issues, including guest OS starting slowly, applications that experience poor performance, applications that take a long time to start, or applications become unresponsive. For more information, see [Troubleshooting ESX/ESXi virtual machine performance issues (2001003)](https://kb.vmware.com/s/article/2001003). 
 Recover orphaned VM Orphaned VMs are VMs that exist in the vCenter database, but are not recognized by the vSphere ESXi host. For more information about recovering orphaned VMs, see [Recover orphaned virtual machines](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-BFD8C9BC-30FB-4A92-AFEC-2FC9FF387920.html). 
 VM does not power on For more information, see [Troubleshooting a virtual machine that is unable to power on (2001005)](https://kb.vmware.com/s/article/2001005). 
 VM does not power on after cloning or deploying from a template [VMware article](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-2742CE14-20FD-416F-B89C-A156053A973F.html) looks at issues that affect a VM after it is cloned or deployed from a template. 
 Old VM network devices For VM network devices that are not kept up-to-date, network performance and application performance might be impacted. For more information about deploying a new virtual network device and driver, see [Choosing a network adapter for your virtual machine (1001805)](https://kb.vmware.com/s/article/1001805). 
 Virtual Machine Memory Limit Memory limits are often used.
Limitations and known issues 



*  The Cloud Pak for Data on IBM Cloud installation from the IBM Cloud catalog is not supported on Red Hat OpenShift Satellite clusters.
*  The installation does not verify whether you have enough resources on the cluster to install Cloud Pak for Data. If you are running other applications on your Red Hat OpenShift cluster, make sure that you have enough resources on the cluster before you install Cloud Pak for Data.
*  When you create a service instance, the service instance initially appears as Failed or Red in the Cloud Pak for Data console until the persistent volume claim is bound to a persistent volume on the cluster.
*  On the Settings page in Schematics > Workspaces, you cannot change the Override value from false to true to install a service. For more information, see [Installing services](https://cloud.ibm.com/docs/cloud-pak-data?topic=cloud-pak-data-install-services).
*  On the Settings page in Schematics > Workspaces, you cannot change the Override value from true to false to uninstall a service. For more information, see [Uninstalling](https://cloud.ibm.com/docs/cloud-pak-data?topic=cloud-pak-data-uninstalling).



For more information, see [Troubleshooting problems in Cloud Pak for Data](https://www.ibm.com/docs/SSQNUZ_4.6.x/cpd/troubleshoot/troubleshooting.html).