vania-janet/multiturn-rag-retrieval-data huggingface dataset:
When updating a monitor, the existing headers are replaced by the ones that you specify. To delete all existing headers, specify the option with an empty value (--header "").

--expected-body <expected-body>
: When type is HTTP or HTTPS: A case-insensitive substring that the health check looks for in the response body. If this string is not found, the IP is considered unhealthy.

--expected-codes <expected-codes>
: When type is HTTP or HTTPS: HTTP codes that the health check looks for in the response. If the HTTP code is not found, the IP is considered unhealthy. Default: 2xx.

--allows-insecure <true>
: When type is HTTP or HTTPS: Set to true to not validate the certificate.

--follows-redirects <true>
: When type is HTTP or HTTPS: Set to true to follow any redirects that are returned by the IP.

Example command

ibmcloud oc nlb-dns monitor configure --cluster mycluster --nlb-host mycluster-a1b2cdef345678g9hi012j3kl4567890-0001.us-south.containers.appdomain.cloud --enable --description "Login page monitor" --type HTTPS --method GET --path / --timeout 5 --retries 2 --interval 60 --header Host=example.com --header Origin=https://akamai.com --expected-body "healthy" --expected-codes 2xx --follows-redirects true
3. Verify that the health check monitor is configured with the correct settings.

ibmcloud oc nlb-dns monitor get --cluster <cluster_name_or_id> --nlb-host <host_name>

Example output

Created On: 2019-04-24 09:01:59.781392 +0000 UTC
Modified On: 2020-02-26 15:39:05.273217 +0000 UTC
Type: https
The following changes were made in build 8278:

IAM auth
: Improve compatibility during upgrades.

Document updates and compaction
: Improve efficiency of updating and compacting conflicted documents.





 11 March 2022 

The following changes were made in build 8269:

Runtime environment
: Upgrade runtime environment to Erlang/OTP 23.





 04 March 2022 

The following changes were made in build 8266:

Bulk docs
: Return 400 Bad Request error for _bulk_docs with new_edits:false and without _rev. Previously returned 500 error.
: Fix bug where Validate Document Update function interacts with new_edits:false setting.

Indexing
: Improve scalability by sharding the index server.

Replicator
: Set instance_start_time to the creation time of the database to restore the ability for the replicator to detect a database recreation event during a replication.

Search
: Expose index signature in the _search_info endpoint response.

Security
: Always send all the cookie attributes whenever we send a cookie. Only the value of AuthSession varies.

Views
: Track ICU collator version that is used to build the view and expose this information in existing endpoints.
: Exposes list of collator versions in _design//_info endpoint response.
: The opaque collator version in _node//_versions endpoint response.







 January 2022 



 28 January 2022 

Switch Legacy Credentials and IAM to IAM only
: It is now possible to switch authentication methods from Legacy Credentials and IAM to IAM only by using the IBM Cloud console.







 December 2021 



 03 December 2021 

IBM Cloud Monitoring integration
: Metrics are now available in the Frankfurt region.







 November 2021 



 01 November 2021 

The following changes were made in build 8243:

Audit messages
: Order customer supplied fields last in audit messages.

Changes feed
: Reduce changes feed rewinds when nodes are down or shards are moved.

View collation
: Fix reduce view collation results for Unicode equivalent keys.







 October 2021 



 01 October 2021
If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 vpn_connection_not_found 

Message: The VPN connection <vpn_connection_id> could not be found.

Check whether the connection ID is correct. Try again in a few minutes. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 vpn_connection_not_updated 

Message: The VPN connection <vpn_connection_id> could not be updated.

Try again in a few minutes. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 vpn_connection_pair_cidrs_duplicated 

Message: At least one pair of local CIDR and peer CIDR with the same peer gateway has been duplicated.

Another connection which has a matching local CIDR and peer CIDR to this one exists on this gateway. Provide a valid set of local / peer CIDRs.





 vpn_connection_peer_cidrs_required 

Message: At least one peer CIDR block is required when creating a VPN connection.

Provide a valid peer CIDR that meets the requirements given by the [API documentation](https://cloud.ibm.com/apidocs/vpc-on-classic).





 vpn_connection_peer_subnets_quota_exceeded 

Message: Peer subnets across VPN connections for the VPN gateway <vpn_gateway_id> has reached the quota.

The quotas per resource are specified on the [Quotas](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-quotasvpn-quotas) page.
RHEL 7 Packages N/A N/A Updated worker node with package updates for [CVE-2020-8625](https://nvd.nist.gov/vuln/detail/CVE-2020-8625), [CVE-2020-14372](https://nvd.nist.gov/vuln/detail/CVE-2020-14372), [CVE-2020-25632](https://nvd.nist.gov/vuln/detail/CVE-2020-25632), [CVE-2020-25647](https://nvd.nist.gov/vuln/detail/CVE-2020-25647), [CVE-2020-27749](https://nvd.nist.gov/vuln/detail/CVE-2020-27749), [CVE-2020-27779](https://nvd.nist.gov/vuln/detail/CVE-2020-27779), [CVE-2021-20225](https://nvd.nist.gov/vuln/detail/CVE-2021-20225), [CVE-2021-20233](https://nvd.nist.gov/vuln/detail/CVE-2021-20233), and [CVE-2021-27803](https://nvd.nist.gov/vuln/detail/CVE-2021-27803). 







 Change log for worker node fix pack 4.4.33_1534_openshift, released 1 March 2021 

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



Changes since version 4.4.33_1533_openshift

 Component Previous Current Description 

 Image garbage collection N/A N/A Fixed a race condition during the provisioning of worker nodes that might cause image garbage collection to fail.
Considerations for updating apps or jobs with environment variables 

Consider the following information when you update an app or job that has an environment variable that references configmaps or secrets.



* When you update an app or job that has an environment variable that fully references a configmap (or secret) to fully reference a different configmap (or secret), full references override other full references in the order in which they are set (the last referenced set overrides the first set).
* When you update an app or job that has an environment variable that references a key in one configmap (or secret) to reference the same key in a different configmap (or secret), then the last referenced key is used.
* When you update an app or job that has an environment variable that fully references a configmap (or secret) to add a reference to a specific key, then the specific key reference overrides the full configmap (or secret) reference.







 Deleting environment variables 

When you no longer need an environment variable, you can delete it.



 Deleting environment variables from the console 



1. From the console, go to the app or job that has the environment variable that you want to delete. Click the Environment variables tab.
2. From the table of environment variables, delete the environment variable that you want to remove from the app or job.
3. Click Save and deploy to update the app or click Save to update your job with the new environment variables. When your app or job is in Ready state, your app or job is updated with your current environment variables.







 Deleting environment variables with the CLI 

When you work with environment variables with the CLI, you can reference existing configmaps or secrets, or you can work with literal environment variables. These instructions describe deleting literal environment variables with the CLI.

For detailed scenarios about removing references to full secrets and configmaps in the CLI, see [Referencing secrets and configmaps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secretcm-reference).



 Delete environment variables for your app
RHEL 7 Packages N/A N/A Updated worker node with package updates for [CVE-2020-8625](https://nvd.nist.gov/vuln/detail/CVE-2020-8625), [CVE-2020-14372](https://nvd.nist.gov/vuln/detail/CVE-2020-14372), [CVE-2020-25632](https://nvd.nist.gov/vuln/detail/CVE-2020-25632), [CVE-2020-25647](https://nvd.nist.gov/vuln/detail/CVE-2020-25647), [CVE-2020-27749](https://nvd.nist.gov/vuln/detail/CVE-2020-27749), [CVE-2020-27779](https://nvd.nist.gov/vuln/detail/CVE-2020-27779), [CVE-2021-20225](https://nvd.nist.gov/vuln/detail/CVE-2021-20225), [CVE-2021-20233](https://nvd.nist.gov/vuln/detail/CVE-2021-20233), and [CVE-2021-27803](https://nvd.nist.gov/vuln/detail/CVE-2021-27803). 







 Change log for worker node fix pack 4.5.31_1531_openshift, released 1 March 2021 

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



Changes since version 4.5.31_1529_openshift

 Component Previous Current Description 

 Image garbage collection N/A N/A Fixed a race condition during the provisioning of worker nodes that might cause image garbage collection to fail.
RHEL 7 Packages N/A N/A Updated worker node with package updates for [CVE-2020-8625](https://nvd.nist.gov/vuln/detail/CVE-2020-8625), [CVE-2020-14372](https://nvd.nist.gov/vuln/detail/CVE-2020-14372), [CVE-2020-25632](https://nvd.nist.gov/vuln/detail/CVE-2020-25632), [CVE-2020-25647](https://nvd.nist.gov/vuln/detail/CVE-2020-25647), [CVE-2020-27749](https://nvd.nist.gov/vuln/detail/CVE-2020-27749), [CVE-2020-27779](https://nvd.nist.gov/vuln/detail/CVE-2020-27779), [CVE-2021-20225](https://nvd.nist.gov/vuln/detail/CVE-2021-20225), [CVE-2021-20233](https://nvd.nist.gov/vuln/detail/CVE-2021-20233), and [CVE-2021-27803](https://nvd.nist.gov/vuln/detail/CVE-2021-27803). 







 Change log for worker node fix pack 4.6.18_1533_openshift, released 1 March 2021 

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



Changes since version 4.6.16_1529_openshift

 Component Previous Current Description 

 Image garbage collection N/A N/A Fixed a race condition during the provisioning of worker nodes that might cause image garbage collection to fail.
Rules: [: b1ea1ad9-71ac-493e-abb1-1261f9110b07]]
Created: 2021-07-21T18:10:44.456Z
Updated: 2021-07-21T18:10:44.456Z







 Updating a route using the CLI 

Use this command to update a route for an IBM Cloud Activity Tracker Event Routing target in a region. Any specified value that is different from when the route was originally created will be updated to the value specified in the command.

ibmcloud atracker route update --route <ROUTE> [--name <ROUTE_NAME>] [--receive-global-events ( TRUE | FALSE )] [--target <TARGET>] [--region <REGION>] [--output JSON]



 Command options 

--route <ROUTE>
: The name or ID of the route to be updated.

--target <TARGET>
: The ID or name of the target.

--region <REGION> | -r <REGION>
: Name of the region, for example, us-south or eu-gb. If not specified, the region logged into, or targeted, will be used.

--name <ROUTE_NAME>
: The name to be given to the route.

Do not include any personal identifying information (PII) in any resource names.

--receive-global-events (TRUE | FALSE)
: Specifies that the route will receive [global events](https://cloud.ibm.com/docs/atracker?topic=atracker-event_typesevent_types_global). If not specified, global events will not be sent on the route

--output JSON
: If specified, output will be returned in JSON format. If JSON is not specified, output will be returned in a tabular format.

help | --help | -h
: List options available for the command.





 Example 

The following is an example using the ibmcloud atracker route update --route my_route --receive-global-events false command.

Route
Updated universal base image (UBI) to the latest 8.4 version to resolve CVEs. 
 IBM Cloud Controller Manager v1.19.15-1 v1.19.15-3 Updated to ignore VPC load balancer (LB) state when a LB delete is requested. 
 IBM Cloud File Storage for Classic plug-in and monitor 400 401 Updated universal base image (UBI) to the latest 8.4-210 version to resolve CVEs. 
 Key Management Service provider v2.3.7 v2.3.8 Updated universal base image (UBI) to the latest 8.4 version to resolve CVEs: [CVE-2021-36222](https://nvd.nist.gov/vuln/detail/CVE-2021-36222), [CVE-2021-37750](https://nvd.nist.gov/vuln/detail/CVE-2021-37750), [CVE-2021-22922](https://nvd.nist.gov/vuln/detail/CVE-2021-22922), [CVE-2021-22923](https://nvd.nist.gov/vuln/detail/CVE-2021-22923), and [CVE-2021-22924](https://nvd.nist.gov/vuln/detail/CVE-2021-22924). 







 Change log for worker node fix pack 1.19.15_1566, released 25 October 2021 

The following table shows the changes that are in the worker node fix pack patch update 1.19.15_1566. 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.19.15_1562

 Component Previous Current Description 

 Ubuntu 18.04 packages N/A N/A Updated worker node images with package updates. Contains fix for cloud-init performance problem. 
 Worker-pool taint automation N/A N/A Fixes known issue related to worker-pool taint automation that prevents workers from getting providerID.
Waiting:2    Draft:0    Connecting:0    InProgress:0    Inactive:0    Active:0    Failed:0   

Type        Name                         Status                     Job ID   
Blueprint   blueprints-starter-example   CREATE_FAILED   eu-gb.JOB.blueprints-starter-example.e44adbab   
Terraform   terraform_module2            NA                 
Terraform   terraform_module1            NA                 
            
Blueprint create_failed at Tue Jun 14 13:21:49 BST 2022
OK

The job status shows as create_failed. Additionally the Terraform job status shows as NA indicating that Schematics failed to create the modules and no logs are available.

 How to fix it 

Review the error messages from the log of the failing blueprint job, the blueprint module definitions, and Git repositories to determine the cause of the initialization failure.

Typical issues are:



* An incorrectly specified module repo URL
* Repo is private and an access token is not specified
* Invalid Git access token



Correct the cause of the failure. Most typically it is an invalid module repo URL and the blueprint module statement require updating.



* Update the blueprint module statements to specify the correct Git repo URL
* Push the new release of the blueprint template to its Git source repository. With an updated release tag if needed.



If you use the blueprint template current version, run the ibmcloud schematics blueprint update command to refresh the blueprint configuration that is stored by Schematics with the update to the blueprint template.

ibmcloud schematics blueprint update -id <blueprint_ID> 

If explicit blueprint template versioning is used with release tags for each template release, the blueprint configuration must be updated in Schematics with the new release tag.

ibmcloud schematics blueprint update --id <blueprint_ID> --bp-git-release x.y.z  

Verify that the blueprint config is updated successfully. When you update the config using the CLI. The command displays details of the modules to be updated, and continuously updating status of the progress of the Schematics jobs initializing the modules.
* UI
* CLI
* API







 Updating a direct link 

You can update a direct link either before or after the gateway moves to the Provisioned state. However, a gateway is restricted from editing during In review, Configuring, and some in-progress states.



 Updating a direct link in the UI 

To edit a direct link, follow these steps:



1. Click the Direct Link name in the table to show its details. Alternatively, you can click the Actions icon at the end of the table row of a provisioned direct link to edit gateway features.sc

If your Direct Link connection was ordered through a third-party service provider (as described in [IBM Cloud Getting started with IBM Cloud Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl)), you might not be able to edit your BGP configuration as described here. The direct link's details page will display a note stating, "This direct link is read-only. Link-specific actions must be initiated through the provider portal." To edit your BGP configuration, contact your provider either directly, or through the provider's portal.
2. Click Edit link in the upper right of the Details or BGP section. A page with the current configuration shows. For example, you can update the BGP Autonomous System Number (ASN), or enable a BGP feature.

Important: Keep in mind that the following tasks result in downtime where traffic is interrupted:



* Activating and deactivating MD5 authentication, or rotating MD5 key authentication after a BGP session is established
* Activating and deactivating Bidirectional Forwarding Detection (BFD) after establishing a BGP session
* Modifying BGP ASN and BGP peer IP addresses after initial configuration



3. Update the content as needed.

If you modify the speed or routing option, the pricing changes. Any updated charges take effect during the next billing cycle.

4.
OpenVPN client N/A N/A Fixed a problem that might cause the vpn-config secret in the kube-system namespace to be deleted during cluster master operations. 
 Operator Lifecycle Manager Catalog v1.5.11 v1.6.1 See the [Operator Lifecycle Manager Catalog release notes](https://github.com/operator-framework/operator-registry/releases/tag/v1.6.1). 







 Change log for worker node fix pack 1.16.8_1528, released 13 April 2020 

The following table shows the changes that are in the worker node fix pack 1.16.8_1528. 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.16.8_1527

 Component Previous Current Description 

 HA proxy 1.8.23 1.8.25 See the [HA proxy change logs](https://www.haproxy.org/download/1.8/src/CHANGELOG). The update addresses [CVE-2020-11100](https://nvd.nist.gov/vuln/detail/CVE-2020-11100). 
 Ubuntu 18.04 packages 4.15.0-91-generic 4.15.0-96-generic Updated worker node images with package and kernel updates for [CVE-2020-8831](https://nvd.nist.gov/vuln/detail/CVE-2020-8831), [CVE-2020-8833](https://nvd.nist.gov/vuln/detail/CVE-2020-8833), [CVE-2020-11100](https://nvd.nist.gov/vuln/detail/CVE-2020-11100), and [CVE-2020-8834](https://nvd.nist.gov/vuln/detail/CVE-2020-8834).
Message: The IPsec policy <ipsec_policy_id> could not be updated.

Try again in a few minutes. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 key_content_exists 

Message: The same key content already exists.

If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 key_name_exists 

Message: The same key name already exists.

If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 key_invalid_name 

Message: The key cannot be created because the name is not valid.

The key name must meet the following requirements:



* it must begin with alphabetical character, [A-Za-z]
* it must contain only alphanumeric characters, dashes or underscores, [-A-Za-z0-9_]
* the length must not exceed 65 characters







 key_invalid_type 

Message: The key cannot be created because the type is not valid.

The only supported key type is rsa.





 key_parse_failure 

Message: The key cannot be created because the public key value is not valid.

The public key provided in the request is not valid. Check the value or regenerate the public key and try again.

In Linux or macOS operating systems, you can run the following command to validate the public key ssh-keygen -l -v -f <key_file>.





 listener_certificate_not_found 

Message: Certificate instance with CRN <listener_certificate_crn> cannot be found or no permission to access the certificate instance.

Provide an existing certificate instance CRN or ask your account administrator to grant you access permissions to the provided certificate instance.
Updating OS packages 

The apt update command downloads package information from all configured sources. The system knows which packages are available for upgrade, and where to retrieve that software. The apt upgrade command uses this information and upgrades all installed packages to their most recent versions.



1. From your laptop, connect to the automation server by using the IP address and the root credentials from the IBM Cloud® Portal ssh root@<public_ip_address>.
2. At the command line, use command apt update && apt upgrade -y to update and upgrade the OS packages.







 Changing DNS 

After provisioning, the VSI is configured to use the IBM Cloud DNS resolvers: 10.0.80.11 and 10.0.80.12, and not your VMware vCenter Server® instance - Active Directory™ DNS (AD/DNS) servers. You can change this configuration by using the following commands, and changing <addns_1> and <addns_2> to the IP addresses of your AD/DNS servers. Replace <root_domain> with your vCenter Server instance domain. For example, test.ibmloud.local.

sudo sed -i 's/10.0.80.11/<addns_1>/g' /etc/netplan/50-cloud-init.yaml
sudo sed -i 's/10.0.80.12/<addns_2>/g' /etc/netplan/50-cloud-init.yaml
sudo sed -i 's/search: []/search: [<root_domain>]/g' /etc/netplan/50-cloud-init.yaml
sudo netplan apply

Use the following commands for verification.

systemd-resolve --status | grep 'DNS Servers' -A2
resolvectl status





 Configuring NTP 

The following commands install NTP, configure "servertime.service.softlayer.com" as the NTP time source, remove the "ubuntu.pool.ntp.org" servers, and then restart the NTP service.

apt install ntp -y
Updating Veeam Backup and Replication 

Use the following information to update Veeam Backup and Replication when new updates are available.



  Prerequisites 



*  A Veeam account. You can sign up at [Veeam registration](https://www.veeam.com/signin.html).
*  Internet Explorer, Chrome, Firefox, or Safari installed.







  Checking for updates 

Veeam Backup and Replication includes an update checker. To make sure that you are notified about updates, go to the upper-left menu icon and click General options > Notifications. Make sure that Check for product and hypervisor updates periodically is selected.





  Updating Veeam 

To start the update, follow these steps.



1.  Open the Back up infrastructure view.
2.  In the inventory page, go to Managed servers node > Missing updates.
3.  Click the update link.



Before you start the update, keep the following information in mind.



*  Make sure that the current run for all existing jobs is complete. If some jobs failed, rerun the failed jobs.
*  Make sure that no jobs are running, including restore sessions, Instant VM Recovery sessions, and SureBackup jobs. It is recommended that you do not stop running jobs.
*  Temporarily disable any periodic and backup copy jobs to prevent them from starting during the upgrade.







  Next steps 

You can now extract the downloaded update and double-click the Veeam update installer. The update pushes to both the local Veeam server and the hypervisors that the Veeam agent is on. After the process completes, start Veeam Backup and Replication, and re-enable your backup jobs.