vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The recommended best practice is to cancel your automated order and submit a new case to complete the Direct Link questionnaire. You should indicate whether you prefer another subnet in the 10.254.x.x range or the 172.16.x.x range.





 What is the difference between Direct Link Exchange and Direct Link Connect? 

These two services are similar, relatively low-cost, latency tolerant, and rapid entry points to the benefits of IBM Cloud Direct Link. In a nutshell, Exchange uses data center providers and Connect uses Telco carriers. Here are some additional details:

Direct Link Exchange is recommended for customers who prefer to use an exchange inside a data center. With an Exchange service, customers can enable multi-cloud connectivity to their colocation rapidly because the underlying circuits are provisioned already (these other cloud providers must already have a physical interconnection present within the facility).

Direct Link Exchange can allow for a multi-cloud, shared-use environment through a single cloud exchange port, created by an NNI connection at Layer 2 between IBM Cloud and the Cloud Exchange Service Provider. Port speeds are available up to 5 Gb.

Direct Link Connect is for customers who prefer to use their existing network between their own on-premises deployment and IBM Cloud. With a Direct Link Connect service, customers can use new and existing Telco networks (such as MPLS) to enable IBM Cloud rapidly, by using pre-provisioned underlying circuits.

With Direct Link Connect, customers can connect to IBM Cloud through the Connect provider, over a Network-to-Network Interface (NNI) connection, operated by IBM partners in facilities worldwide. Port speeds are available up to 5 Gb.





 How do Direct Link Connect and Direct Link Exchange providers compare? 

Connect providers are Telcos who have network reach beyond the data center. Exchange providers are limited to their data centers. Both can enable the multi-cloud experience for customers. Exchange providers usually require colocation in their data centers, while Connect providers can reach a customer's on-premises site and data centers.





 Can IBM Support IPv6 over Direct Link? 

Not for the BGP Session. We must assign our /30 from IPv4, and we need the same in return from the customer.





 Can IBM do IPV6 on the private network?
For example, if the client MQTT is set incorrectly, pings are not received in a timely manner, and the connection is closed.

You can fix this problem by confirming that you have properly set the ping and KeepAlive parameters for your connection.





 Subscription to Device events fails using MQTT 

When you subscribe to events for a device, the connection always closes so the subscription does not take effect.

You see a message like the following on the dashboard: Closed connection. The topic is not valid: format_string. The topic does not match an authorized rule

This error occurs if you try to subscribe using an incorrect Client ID format.

When you make an MQTT connection to subscribe to an events topic, you must



* Generate and use an API Key
* Use a client ID format of a:orgId:appId



Fix the ID format, then try again. For details, refer to [MQTT authentication](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/platform/applications/mqtt.html).
Why can't I use the Git Repos and Issue Tracking tool integration in my toolchain from one region in a toolchain within a different region? 

You cannot use an instance of Git Repos and Issue Tracking across multiple regions.

 What’s happening 

When I attempt to add the Git Repos and Issue Tracking tool integration to my toolchain, I receive the following error message:

Repository URL is not valid. The repository must be on {local GitLab URL}.

Where {local GitLab URL} is the URL of the Git Repos and Issue Tracking tool integration, in the region where the toolchain resides.

 Why it’s happening 

Because Git Repos and Issue Tracking is tightly integrated with the Continuous Delivery service in the region in which they are running, you cannot use an instance of Git Repos and Issue Tracking across multiple regions.

 How to fix it 

Instead of creating a Git Repos and Issue Tracking tool integration, create a generic GitLab integration and use this integration to point to the Git Repos and Issue Tracking repository (repo) in a different region.



1. From the IBM Cloud console, click the menu icon ![hamburger icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_hamburger.svg), and select DevOps. On the Toolchains page, click the toolchain that you want to add this integration to. Alternatively, on the app's Overview page, on the Continuous delivery card, click View toolchain and click Overview.
2. Click Add tool.
3. In the Tool Integrations section, click GitLab.
4. Click the GitLab server that you want to use. If the GitLab server where the repo you want to access resides does not appear in this list, add a custom server:

a. Click Custom Server.

b. Type a name for the server.
* [Blueprint apply failures that require changes to values in input files](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-apply-failsbp-apply-fails4)
* [Blueprint apply failures that require changes to dynamic inputs](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-apply-failsbp-apply-fails5)







 Troubleshooting Agents 

[How can you provide value to schematics_resource_crn variable?](https://cloud.ibm.com/docs/schematics?topic=schematics-agent-crn-not-foundagent-crn-not-found)

[Why are you getting create endpoint gateway failure with wrong number of segments in CRN?](https://cloud.ibm.com/docs/schematics?topic=schematics-agent-endpoint-erroragent-endpoint-error)

[Troubleshooting errors](https://cloud.ibm.com/docs/schematics?topic=schematics-handling-errorhandling-error)



* [Action error messages](https://cloud.ibm.com/docs/schematics?topic=schematics-handling-erroraction-errmsg)



* [Parameter error](https://cloud.ibm.com/docs/schematics?topic=schematics-handling-errorparam-error)
* [Service error](https://cloud.ibm.com/docs/schematics?topic=schematics-handling-errorsvc-error)
* [State error](https://cloud.ibm.com/docs/schematics?topic=schematics-handling-errorstate-error)
* [Job error](https://cloud.ibm.com/docs/schematics?topic=schematics-handling-errorjob-error)











 Getting help and support
You can also connect to the NetScaler device directly using your favorite SSH client. Use the private IP and login information for the NetScaler device from the device list page and make sure you are connected to the IBM Cloud VPN.







 Caution regarding HA configurations and portal passwords 

You must keep your Cloud portal root username and password consistent with the root username and password of the physical device. If these are not kept consistent, upgrades and licensing operations can fail, resulting in production outages. Ensure any administrator tasked with supervision of a VPX is aware of this issue to avoid unexpected downtime.
(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?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-sc-install)
* [Why is my Node.js smart contract fail to endorse?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-nodejs-endorsement)
* [Why is the smart contract that I installed on the peer not listed in the UI?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-console-build-network-troubleshoot-missing-sc)
* [My nodes, channels, smart contracts, and identities have disappeared from the console. How can I get them back?](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)
What’s happening 

PipelineRuns fails with an error when any of the secure properties in the pipeline don't resolve at the start of the pipeline run.

 Why it’s happening 

Pipelines that cannot retrieve a secret value from a secrets store or from either Secrets Manager, Key Protect, or HashiCorp Vault, fail with an error message that indicates which properties cannot be resolved. Resolution failures can occur even if the properties are not used directly in the triggered run. For example, resolution failures might occur if the path to the secret in the store is no longer valid, the secret store is inaccessible, or for authorization issues.

 How to fix it 

If your pipelines contain secure properties that do not currently resolve, update these properties to refer to valid, retrievable secrets that are located in Secrets Manager, Key Protect, or HashiCorp Vault.

Make sure that your pipeline specifies only those secure properties that are required for the successful completion of a triggered PipelineRun as pipeline trigger properties, instead of as pipeline level environment properties. Use pipeline level environment properties only when required.
Your workload is restarted on other hosts if a host failure occurs. 
 Availability % 99.99% Multiple instances that are distributed across multiple zones or regions. Workload is not automatically restarted across zones or regions, but must be designed and implemented for continuous availability or warm standby between zones or regions. 



The SLO is not a warranty and IBM will not issue credits for failure to meet an objective. Refer to the SLAs for commitments and credits that are issued for failure to meet any committed SLAs. For a summary of all SLOs, see [IBM Cloud service level objectives](https://cloud.ibm.com/docs/overview?topic=overview-slo).

A complete business continuity plan also addresses cases such as regional or site failure; and events such as corruption, malware, and user error. Consider the use of [replication and backup](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-bc-dr) as part of your planning.





 Locations 

For more information about service availability within regions and data centers, see [Service and infrastructure availability by location](https://cloud.ibm.com/docs/overview?topic=overview-services_region).
If you receive any of the following errors, you need to have your own accounts with the respective vendors and configure the corresponding variables within /etc/vztt/url.map (/etc/vztt/vztt.conf in Virtuozzo 3.)





 TIMESTAMP Click here to open/close the operation details.Update OS Template Cache Failed 
 TIMESTAMP Operation update with the Env(s) "virtuozzo00.softlayer.local" and package(s) .redhat-as4-x86_64 is started 
 TIMESTAMP Operation update with the Env(s) "virtuozzo00.softlayer.local" is finished with errors: Can not update packages: exec failed: Error: URL $RH_SERVER/download/mirrors/redhat-as4 contents undefined variable You can define this variable in /etc/vztt/url.map. . Failed 
 TIMESTAMP Click here to open/close the operation details.Update OS Template Cache Failed 
 TIMESTAMP Operation update with the Env(s) "virtuozzo00.softlayer.local" and package(s) .redhat-el5-x86_64 is started 
 TIMESTAMP Operation update with the Env(s) "virtuozzo00.softlayer.local" is finished with errors: Can not update packages: exec failed: Error: URL $RH_SERVER/download/mirrors/redhat-el5 contents undefined variable You can define this variable in /etc/vztt/url.map. See Virtuozzo Installation Guide for more details. . Failed 
 TIMESTAMP Click here to open/close the operation details.Update OS Template Cache Failed 
 TIMESTAMP Operation update with the Env(s) "virtuozzo00.softlayer.local" and package(s) .sles-10-x86_64 is started
6.7R14S2 

Released October 10, 2017.



 Issues Resolved 



Issues resolved in 6.7R14S2

 Issue Number Priority Summary 

 VSE-9837 Minor “show system commit different” showing permission denied after upgrade from 6.7R11S9 to 6.7R13S3 







 Security Vulnerabilities Resolved 



Security vulnerabilties resolved in 6.7R14S2

 Issue Number CVSS score Advisory Summary 

 VSE-9845 9.8 DLA-1124-1 CVE-2017-14491, CVE-2017-14492, CVE-2017-14494: Debian DLA-1124-1: dnsmasq security update 









 6.7R14S1 

Released September 22, 2017.



 Issues Resolved 



Issues resolved in 6.7R14S1

 Issue Number Priority Summary 

 VSE-9831 Major MTU setting reverts back to default after reboot on a VIF interface 







 Security Vulnerabilities Resolved 



Security vulnerabilties resolved in 6.7R14S1

 Issue Number CVSS score Advisory Summary 

 VSE-9841 9.8 DLA-1060-1 CVE-2017-0663, CVE-2017-7376: Debian DLA-1060-1: libxml2 security update 
 VSE-9840 6.5 DLA-1062-1 CVE-2017-1000100: Debian DLA-1062-1: curl security update 
 VSE-9839 7.5 DLA-1059-1 CVE-2017-11185: Debian DLA-1059-1: strongswan security update 
 VSE-9835 7.5 DSA-3900-1 CVE-2017-7522, CVE-2017-7521, CVE-2017-7520, CVE-2017-7508 OpenVPN security update
The following table shows the changes that are in the worker node fix pack 1.14.6_1532.



Table 1. Changes since version 1.14.5_1530

 Component Previous Current Description 

 containerd v1.2.7 v1.2.8 See the [containerd release notes](https://github.com/containerd/containerd/releases/tag/v1.2.8). Update resolves [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 
 Kubernetes v1.14.5 v1.14.6 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.14.6).
The following table shows the changes that are in the patch 1.14.1_1518.



Table 1. Changes since version 1.14.1_1516

 Component Previous Current Description 

 Cluster master HA proxy 1.9.6-alpine 1.9.7-alpine See the [HAProxy release notes](https://www.haproxy.org/download/1.9/src/CHANGELOG). Update resolves [CVE-2019-6706](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6706). 
 Kubernetes configuration N/A N/A The Kubernetes API server audit policy configuration is updated to not log the /openapi/v2* read-only URL. In addition, the Kubernetes controller manager configuration increased the validity duration of signed kubelet certificates from 1 to 3 years. 
 OpenVPN client configuration N/A N/A The OpenVPN client vpn-* pod in the kube-system namespace now sets dnsPolicy to Default to prevent the pod from failing when cluster DNS is down. 
 Trusted compute agent e7182c7 13c7ef0 Updated image for [CVE-2016-7076](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7076) and [CVE-2017-1000368](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000368). 







 Change log for 1.14.1_1516, released 7 May 2019 

The following table shows the changes that are in the patch 1.14.1_1516.



Table 1. Changes since version 1.13.5_1519

 Component Previous Current Description 

 Calico v3.4.4 v3.6.1 See the [Calico release notes](https://docs.tigera.io/archive/v3.6/release-notes/).
The following table shows the changes that are in the worker node fix pack 1.15.3_1516.



Table 1. Changes since version 1.15.2_1514

 Component Previous Current Description 

 containerd v1.2.7 v1.2.8 See the [Containerd release notes](https://github.com/containerd/containerd/releases/tag/v1.2.8). Update resolves [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 
 Kubernetes v1.15.2 v1.15.3 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.15.3).
v14.16.1

 npm --version
6.14.12

 jq --version
jq-1.6

 yq --version
yq version 2.4.1

 yq3 --version
yq version 3.4.1

 yq4 --version
yq version 4.6.2

 kubectl version --client
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.5", GitCommit:"6b1d87acf3c8253c123756b9e61dac642678305f", GitTreeState:"clean", BuildDate:"2021-03-18T01:10:43Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}

 buildctl --version
buildctl github.com/moby/buildkit v0.8.2 9065b18ba4633c75862befca8188de4338d9f94a

 helm version --client
Client: &version.Version{SemVer:"v2.17.0", GitCommit:"a690bad98af45b015bd3da1a41f6218b1a451dbe", GitTreeState:"clean"}

 helm3 version --client
version.BuildInfo{Version:"v3.5.3", GitCommit:"041ce5a2c17a58be0fcd5f5e16fb3e7e95fea622", GitTreeState:"dirty", GoVersion:"go1.15.8"}

 ibmcloud -version
ibmcloud version 1.4.0+4705d79-2021-02-24T21:18:06+00:00

 ibmcloud plugin list
Listing installed plug-ins...
Version 1.15 change log (unsupported 22 September 2020) 

Version 1.15 is unsupported. You can review the following archive of 1.15 change logs.



 Change log for worker node fix pack 1.15.12_1552, released 14 September 2020 

The following table shows the changes that are in the worker node fix pack 1.15.12_1552. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.15.12_1551

 Component Previous Current Description 

 HAProxy 1.8.25-384f42 1.8.26-561f1a See the [HAProxy change log](https://www.haproxy.org/download/1.8/src/CHANGELOG). 
 Ubuntu 18.04 packages 4.15.0-112-generic 4.15.0-117-generic Updated worker node image with kernel and package updates for [CVE-2020-14344](https://nvd.nist.gov/vuln/detail/CVE-2020-14344), [CVE-2020-14363](https://nvd.nist.gov/vuln/detail/CVE-2020-14363), and [CVE-2020-14386](https://nvd.nist.gov/vuln/detail/CVE-2020-14386). 
 Ubuntu 16.04 packages 4.4.0-187-generic 4.4.0-189-generic Updated worker node image with kernel and package updates for [CVE-2020-14344](https://nvd.nist.gov/vuln/detail/CVE-2020-14344) and [CVE-2020-14363](https://nvd.nist.gov/vuln/detail/CVE-2020-14363). 







 Change log for worker node fix pack 1.15.12_1551, released 31 August 2020 

The following table shows the changes that are in the worker node fix pack 1.15.12_1551.
Change log for worker node fix pack 1.14.1_1519, released 20 May 2019 

The following table shows the changes that are in the patch 1.14.1_1519.



Table 1. Changes since version 1.14.1_1518

 Component Previous Current Description 

 Ubuntu 16.04 kernel 4.4.0-145-generic 4.4.0-148-generic Updated worker node images with kernel update for [CVE-2018-12126](https://ubuntu.com/security/CVE-2018-12126.html), [CVE-2018-12127](https://ubuntu.com/security/CVE-2018-12127.html), and [CVE-2018-12130](https://ubuntu.com/security/CVE-2018-12130.html). 
 Ubuntu 18.04 kernel 4.15.0-47-generic 4.15.0-50-generic Updated worker node images with kernel update for [CVE-2018-12126](https://ubuntu.com/security/CVE-2018-12126.html), [CVE-2018-12127](https://ubuntu.com/security/CVE-2018-12127.html), and [CVE-2018-12130](https://ubuntu.com/security/CVE-2018-12130.html). 







 Change log for 1.14.1_1518, released 13 May 2019 

The following table shows the changes that are in the patch 1.14.1_1518.



Table 1. Changes since version 1.14.1_1516

 Component Previous Current Description 

 Cluster master HA proxy 1.9.6-alpine 1.9.7-alpine See the [HAProxy release notes](https://www.haproxy.org/download/1.9/src/CHANGELOG).
dc (GNU bc 1.07.1) 1.4.1

 ed --version
GNU Ed 1.10
Show more





 Version 2.14 

To view the contents of version 2.14, from the running image, type default_versions.sh. This image includes the following tools:

 node --version
v14.17.6

 npm --version
6.14.15

 jq --version
jq-1.6

 yq --version
yq version 2.4.1

 yq3 --version
yq version 3.4.1

 yq4 --version
yq (https://github.com/mikefarah/yq/) version 4.12.1

 kubectl version --client
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.5", GitCommit:"6b1d87acf3c8253c123756b9e61dac642678305f", GitTreeState:"clean", BuildDate:"2021-03-18T01:10:43Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}

 buildctl --version
buildctl github.com/moby/buildkit v0.9.0 c8bb937807d405d92be91f06ce2629e6202ac7a9

 helm version --client
Client: &version.Version{SemVer:"v2.17.0", GitCommit:"a690bad98af45b015bd3da1a41f6218b1a451dbe", GitTreeState:"clean"}

 helm3 version --client
To view the contents of version 2.10, from the running image, type default_versions.sh. This image includes the following tools:

 node --version
v12.20.0

 npm --version
6.14.9

 jq --version
jq-1.6

 yq --version
yq version 2.4.1

 yq3 --version
yq version 3.4.1

 kubectl version --client
Client Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.16-rc.0", GitCommit:"737e2c461a2999fa242d39e77b9252d0eee7167e", GitTreeState:"clean", BuildDate:"2020-12-09T11:14:02Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

 buildctl --version
buildctl github.com/moby/buildkit v0.8.0 73fe4736135645a342abc7b587bba0994cccf0f9

 helm version --client
Client: &version.Version{SemVer:"v2.17.0", GitCommit:"a690bad98af45b015bd3da1a41f6218b1a451dbe", GitTreeState:"clean"}

 helm3 version --client
version.BuildInfo{Version:"v3.4.2", GitCommit:"23dd3af5e19a02d4f4baa5b2f242645a1a3af629", GitTreeState:"clean", GoVersion:"go1.14.13"}

 ibmcloud -version
Change log for worker node fix pack 1.14.7_1535, released 14 October 2019 

The following table shows the changes that are in the worker node fix pack 1.14.7_1535.



Table 1. Changes since version 1.14.7_1534

 Component Previous Current Description 

 Ubuntu 16.04 packages and kernel 4.4.0-164-generic 4.4.0-165-generic Updated worker node images with kernel and package updates for [CVE-2019-5094](https://nvd.nist.gov/vuln/detail/CVE-2019-5094), [CVE-2018-20976](https://nvd.nist.gov/vuln/detail/CVE-2018-20976), [CVE-2019-0136](https://nvd.nist.gov/vuln/detail/CVE-2019-0136), [CVE-2018-20961](https://nvd.nist.gov/vuln/detail/CVE-2018-20961), [CVE-2019-11487](https://nvd.nist.gov/vuln/detail/CVE-2019-11487), [CVE-2016-10905](https://nvd.nist.gov/vuln/detail/CVE-2016-10905), [CVE-2019-16056](https://nvd.nist.gov/vuln/detail/CVE-2019-16056), and [CVE-2019-16935](https://nvd.nist.gov/vuln/detail/CVE-2019-16935).
OS name: "linux", version: "4.9.184-linuxkit", arch: "amd64", family: "unix"

 gradle -version

Welcome to Gradle 5.6!

Here are the highlights of this release:
- Incremental Groovy compilation
- Groovy compile avoidance
- Test fixtures for Java projects
- Manage plugin versions via settings script

For more details see https://docs.gradle.org/5.6/release-notes.html

------------------------------------------------------------
Gradle 5.6
------------------------------------------------------------

Build time: 2019-08-14 21:05:25 UTC
Revision: f0b9d60906c7b8c42cd6c61a39ae7b74767bb012

Kotlin: 1.3.41
Groovy: 2.5.4
Ant: Apache Ant(TM) version 1.9.14 compiled on March 12 2019
JVM: 1.8.0_222 (Private Build 25.222-b10)
OS: Linux 4.9.184-linuxkit amd64

 oc version
oc v3.11.0+0cbc58b
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
Show more





 Version 2.3 

To view the contents of version 2.3, from the running image, type default_versions.sh. This image includes the following tools:

 node --version
v10.16.0