mtpti5iD/redhat-docs_dataset huggingface dataset:
4.221. perl-Date-Manip 4.221.1. RHEA-2011:1560 - perl-Date-Manip enhancement update An updated perl-Date-Manip package that upgrades the Date::Manip module to upstream version 6.24 is now available for Red Hat Enterprise Linux 6. The Date::Manip module provides a mechanism for Perl scripts to perform common date or time operations, such as comparing two timestamps or parsing international times. Enhancement BZ# 672934 Among other flaws, the version of the perl-Date-Manip package included outdated time zone definitions and an old API that is now considered deprecated. This update upgrades the perl-Date-Manip package to upstream version 6.24, which provides up-to-date time zone definitions and version 6 of the API. Users are still able to use the old API version 5 by explicitly using the Date::Manip::DM5 module. All users of perl-Date-Manip are advised to upgrade to this updated package, which adds this enhancement.

Commands:
API reference Red Hat build of MicroShift 4.18 MicroShift API reference Red Hat OpenShift Documentation Team

Commands:
(Note that <suffix> may be empty, from the "" case in <decimalSI>.)
(International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)
(Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)
type MyAPIObject struct { runtime.TypeMeta `json:",inline"` MyPlugin runtime.Object `json:"myPlugin"` }
type PluginA struct { AOption string `json:"aOption"` }
type MyAPIObject struct { runtime.TypeMeta `json:",inline"` MyPlugin runtime.RawExtension `json:"myPlugin"` }
type PluginA struct { AOption string `json:"aOption"` }
{ "kind":"MyAPIObject", "apiVersion":"v1", "myPlugin": { "kind":"PluginA", "aOption":"foo", }, }
Name: "mysvc", Subsets: [ { Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}], Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}] }, { Addresses: [{"ip": "10.10.3.3"}], Ports: [{"name": "a", "port": 93}, {"name": "b", "port": 76}] }, ]
Name: "mysvc", Subsets: [ { Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}], Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}] }, { Addresses: [{"ip": "10.10.3.3"}], Ports: [{"name": "a", "port": 93}, {"name": "b", "port": 76}] }, ]
{ Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}], Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}] }
a: [ 10.10.1.1:8675, 10.10.2.2:8675 ], b: [ 10.10.1.1:309, 10.10.2.2:309 ]
IP: An IP address allocated to the pod. Routable at least within the cluster.
Chapter 3. Configuring Capsule Servers with default SSL certificates for load balancing You can configure one or more Capsule Servers that use default SSL certificates for load balancing. If you use Puppet in your Satellite deployment, the configuration steps are different. See Chapter 5, Configuring Capsule Servers with default SSL certificates for load balancing (with Puppet) . 3.1. Prerequisites Prepare a new Capsule Server to use for load balancing. See Chapter 2, Preparing Capsule Servers for load balancing . Review Section 1.2, "Services and features supported in a load-balanced setup" . 3.2. Configuring Capsule Server with default SSL certificates for load balancing without Puppet On each Capsule Server that you want to configure for load balancing, install Katello certificates. Procedure On Satellite Server, generate Katello certificates for Capsule Server: Retain a copy of the example satellite-installer command that is output by the capsule-certs-generate command for installing Capsule Server certificate. Copy the certificate archive file from Satellite Server to Capsule Server. Append the following options to the satellite-installer command that you obtain from the output of the capsule-certs-generate command: On Capsule Server, enter the satellite-installer command:

Commands:
capsule-certs-generate --certs-tar "/root/ capsule.example.com -certs.tar" --foreman-proxy-cname loadbalancer.example.com --foreman-proxy-fqdn capsule.example.com
scp /root/ capsule.example.com -certs.tar root@ capsule.example.com :/root/ capsule.example.com -certs.tar
--certs-cname " loadbalancer.example.com " --enable-foreman-proxy-plugin-remote-execution-script
satellite-installer --scenario capsule --certs-cname " loadbalancer.example.com " --certs-tar-file " capsule.example.com-certs.tar " --enable-foreman-proxy-plugin-remote-execution-script --foreman-proxy-foreman-base-url " https://satellite.example.com " --foreman-proxy-oauth-consumer-key " oauth key " --foreman-proxy-oauth-consumer-secret " oauth secret " --foreman-proxy-register-in-foreman "true" --foreman-proxy-trusted-hosts " satellite.example.com " --foreman-proxy-trusted-hosts " capsule.example.com "
Appendix C. Using AMQ Broker with the examples The AMQ Spring Boot Starter examples require a running message broker with a queue named example . Use the procedures below to install and start the broker and define the queue. C.1. Installing the broker Follow the instructions in Getting Started with AMQ Broker to install the broker and create a broker instance . Enable anonymous access. The following procedures refer to the location of the broker instance as <broker-instance-dir> . C.2. Starting the broker Procedure Use the artemis run command to start the broker. USD <broker-instance-dir> /bin/artemis run Check the console output for any critical errors logged during startup. The broker logs Server is now live when it is ready. USD example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server ... 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... C.3. Creating a queue In a new terminal, use the artemis queue command to create a queue named example . USD <broker-instance-dir> /bin/artemis queue create --name example --address example --auto-create-address --anycast You are prompted to answer a series of yes or no questions. Answer N for no to all of them. Once the queue is created, the broker is ready for use with the example programs. C.4. Stopping the broker When you are done running the examples, use the artemis stop command to stop the broker. USD <broker-instance-dir> /bin/artemis stop Revised on 2021-08-24 14:29:42 UTC

Commands:
<broker-instance-dir> /bin/artemis run
example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
<broker-instance-dir> /bin/artemis queue create --name example --address example --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop
8.140. mksh 8.140.1. RHBA-2014:0533 - mksh bug fix Updated mksh packages that fix one bug are now available for Red Hat Enterprise Linux 6. The mksh package provides the MirBSD enhanced version of the Public Domain Korn shell (pdksh), a Bourne-compatible shell, which is largely similar to the original AT&T Korn shell. Shift_JIS, also known as "SJIS", is a character encoding for the Japanese language. This package provides mksh support for the Shift_JIS encoding. Bug Fix BZ# 771198 Previously, the mksh shell worked with bytes instead of characters when looking for the common part of a file name. As a consequence, the common part of the file name could contain only the beginning part of the border character, and only a part of the character was printed. With this update, mksh works with whole characters when looking for the longest common prefix, and tab completion prints the correct common part as expected. Users of mksh are advised to upgrade to these updated packages, which fix this bug.

Commands:
6.3. Firewall Configuration The following table lists the default ports used by Certificate System subsystems: Table 6.1. Certificate System Default Ports Service Port Protocol HTTP 8080 TCP HTTPS 8443 TCP Tomcat Management 8005 TCP When you set up Certificate System using the pkispawn utility, you can customize the port numbers. If you use different ports than the defaults listed above, open them correspondingly in the firewall as described in Section 6.3.1, "Opening the Required Ports in the Firewall" . For further details about ports, see Section 5.5.3, "Planning Ports" . For ports required to access Directory Server, see the corresponding section in the Directory Server Installation Guide . 6.3.1. Opening the Required Ports in the Firewall To enable communication between the clients and Certificate System, open the required ports in your firewall: Make sure the firewalld service is running. To start firewalld and configure it to start automatically when the system boots: Open the required ports using the firewall-cmd utility. For example, to open the Certificate System default ports in the default firewall zone: For details on using firewall-cmd to open ports on a system, see the in the Securing Networks or the firewall-cmd (1) man page. Reload the firewall configuration to ensure that the change takes place immediately:

Commands:
systemctl status firewalld
systemctl start firewalld systemctl enable firewalld
firewall-cmd --permanent --add-port={8080/tcp,8443/tcp,8009/tcp,8005/tcp}
firewall-cmd --reload
Chapter 3. Opening a new certification case using the Red Hat Certification Tool As a partner, you can start the certification process by opening a new certification case in the Red Hat Certification Tool. When you complete this task, Red Hat prepares a test plan based on the product specification you provide. Prerequisites You have established a certification relationship with Red Hat. You have the user login credentials. You have the vendor and products linked to your user login. Procedure Log in to Red Hat Certification Portal . On the home page, click Open Certification . The Open a New Certification Case dialog opens. Click . Select an option from the Partner and Product list. If your product does not appear, create it by entering its name in the Product field. Then, select it. In the What kind of product is this? section, select the checkbox applicable to your product. Your product might qualify for more than one ecosystem. Click . Enter the Make . The Model is displayed based on the previously entered information. Select the applicable checkbox under Which category best describes your product? Optional: Enter the Product URL , Support URL , and Specification URL . Click . Based on your inputs, a new product is created in the Partner Product list. Select an option from the Red Hat Certification list and click . Review the information you provided and click . Verification If you have successfully created a new certification case for your product, a message is displayed. steps While Red Hat prepares a test plan for the product, you can Set up the test environment to prepare the systems for running tests.

Commands:
Chapter 7. Creating additional distributed compute node sites A new distributed compute node (DCN) site has its own directory of YAML files on the undercloud. For more information, see Section 2.3, "Managing separate heat stacks" . This procedure contains example commands. Procedure As the stack user on the undercloud, create a new directory for dcn1 : Copy the existing dcn0 templates to the new directory and replace the dcn0 strings with dcn1 : Review the files in the dcn1 directory to confirm that they suit your requirements. Verify that your nodes are available and in Provisioning state : When your nodes are available, run the deploy.sh for the dcn1 site:

Commands:
cd ~ mkdir dcn1
cp dcn0/ceph.yaml dcn1/ceph.yaml sed s/dcn0/dcn1/g -i dcn1/ceph.yaml cp dcn0/overrides.yaml dcn1/overrides.yaml sed s/dcn0/dcn1/g -i dcn1/overrides.yaml sed s/"0-ceph-%index%"/"1-ceph-%index%"/g -i dcn1/overrides.yaml cp dcn0/deploy.sh dcn1/deploy.sh sed s/dcn0/dcn1/g -i dcn1/deploy.sh
openstack baremetal node list
bash dcn1/deploy.sh
5.5. Troubleshooting with the multipathd Interactive Console The multipathd -k command is an interactive interface to the multipathd daemon. Entering this command brings up an interactive multipath console. After entering this command, you can enter help to get a list of available commands, you can enter a interactive command, or you can enter CTRL-D to quit. The multipathd interactive console can be used to troubleshoot problems you may be having with your system. For example, the following command sequence displays the multipath configuration, including the defaults, before exiting the console. The following command sequence ensures that multipath has picked up any changes to the multipath.conf , Use the following command sequence to ensure that the path checker is working properly.

Commands:
multipathd -k > > show config > > CTRL-D
multipathd -k > > reconfigure > > CTRL-D
multipathd -k > > show paths > > CTRL-D
1.3. About Querying in Red Hat JBoss Data Grid 1.3.1. Hibernate Search and the Query Module Users have the ability to query the entire stored data set for specific items in Red Hat JBoss Data Grid. Applications may not always be aware of specific keys, however different parts of a value can be queried using the Query Module. The JBoss Data Grid Query Module utilizes the capabilities of Hibernate Search and Apache Lucene to index and search objects in the cache. This allows objects to be located within the cache based on their properties, rather than requiring the keys for each object. Objects can be searched for based on some of their properties. For example: Retrieve all red cars (an exact metadata match). Search for all books about a specific topic (full text search and relevance scoring). An exact data match can also be implemented with the MapReduce function, however full text and relevance based scoring can only be performed via the Query Module. Warning The query capability is currently intended for rich domain objects, and primitive values are not currently supported for querying. Report a bug 1.3.2. Apache Lucene and the Query Module In order to perform querying on the entire data set stored in the distributed grid, Red Hat JBoss Data Grid utilizes the capabilities of the Apache Lucene indexing tool, as well as Hibernate Search. Apache Lucene is a document indexing tool and search engine. JBoss Data Grid uses Apache Lucene 3.6. JBoss Data Grid's Query Module is a toolkit based on Hibernate Search that reduces Java objects into a format similar to a document, which is able to be indexed and queried by Apache Lucene. In JBoss Data Grid, the Query Module indexes keys and values annotated with Hibernate Search indexing annotations, then updates the index based in Apache Lucene accordingly. Hibernate Search intercepts changes to entries stored in the data grid to generate corresponding indexing operations Report a bug

Commands:
6.3. Booleans SELinux is based on the least level of access required for a service to run. Services can be run in a variety of ways; therefore, you need to specify how you run your services. Use the following Booleans to set up SELinux: named_write_master_zones When disabled, this Boolean prevents named from writing to zone files or directories labeled with the named_zone_t type. named does not usually need to write to zone files; but in the case that it needs to, or if a secondary server needs to write to zone files, enable this Boolean to allow this action. named_bind_http_port When enabled, this Boolean allows BIND to bind an Apache port. Note Due to the continuous development of the SELinux policy, the list above might not contain all Booleans related to the service at all times. To list them, run the following command as root:

Commands:
~]# semanage boolean -l | grep service_name
6.4. Using the Certificates on Tokens for Mail Clients In Mozilla Thunderbird, open the Edit menu, choose Preferences , and then click Advanced . Open the Certificate tab. Add a PKCS #11 driver. Click Security Devices to open the Device Manager window. Click the Load button. Enter the module name, such as token keypk11 driver . Click Browse , find the Enterprise Security Client PKCS #11 driver, and click OK . The PKCS #11 module used by these applications, by default, is located in /usr/lib/libcoolkeypk11.so . If the CA is not yet trusted, download and import the CA certificate. Open the SSL End Entity page on the CA. For example: Click the Retrieval tab, and then click Import CA Certificate Chain . Click Download the CA certificate chain in binary form and then click Submit . Choose a suitable directory to save the certificate chain, and then click OK . In Mozilla Thunderbird, open the Edit menu, choose Preferences , and then click Advanced . Open the Certificate tab, and click the View Certificates button. Click the Authorities tab, and import the CA certificate. Set up the certificate trust relationships. In Mozilla Thunderbird, open the Edit menu, choose Preferences , and then click Advanced . Open the Certificate tab, and click the View Certificates button. In the Authorities tab, select the CA, and click the Edit button. Set the trust settings for identifying websites and mail users. In the Digital Signing section of the Security panel, click Select to choose a certificate to use for signing messages. In the Encryption of the Security panel, click Select to choose the certificate to encrypt and decrypt messages.

Commands:
http s ://server.example.com: 9444/ca/ee/ca/
Chapter 12. Fixed issues in Red Hat Process Automation Manager 7.13.2 Red Hat Process Automation Manager 7.13.2 provides increased stability and fixed issues listed in this section. 12.1. Business Central You cannot save a DMN model if you use the ()not function [ RHDM-1895 ] You cannot deploy a KJAR to a remote maven repository that requires access via a proxy in Business Central[ RHPAM-4509 ] The Table 'rhpam.taskEvent' doesn't exist error appears after upgrading to 7.12.0 or later [ RHPAM-4578 ] The commit history of the Metrics tab is not refreshed on branches other than the main branch [ RHPAM-2603 ] 12.2. KIE Server Cannot commit a session during a retry of the parent process [ RHPAM-4499 ] Unable to connect to a PostgresSQL DB over SSL from a kieserver image [ RHPAM-4400 ] When a process has variable of type java.util.Date , if the showTime attribute on the generated form is set to true , you cannot inser the time part [ RHPAM-4513 ] The ISPN000474 error is generated by kie-server when two nodes are configured to support failover [ RHPAM-4223 ] 12.3. Process engine Orphaned records in the sessionInfo table [ RHPAM-4403 ] Signals inside a multinode process are not captured correctly by that process [ RHPAM-4548 ] Event types in the TaskLifeCycleEventListener interface do not match with the human task life cycle status [ RHPAM-3934 ] A signal with a process scope is sent twice in a Case project [ RHPAM-4603 ] The PIM tool allow process instances to migrate even when they have different definitions from the source migration plan [ RHPAM-4544 ] Migrations that take more time to complete that the value of the quarkus.transaction-manager.default-transaction-timeout parameter are not persisted [ RHPAM-4608 ] If the entity manager references are not closed, an exception might occur [ RHPAM-4613 ] Avoid any escape characters in SOAP headers [ RHPAM-4501 ] 12.4. Red Hat OpenShift Container Platform Cannot use special characters in passwords in the Business Central operator [ RHPAM-4529 ] The baseFilter(AUTH_LDAP_BASE_FILTER) filter is incompatible with versions earlier than 7.12.0 [ RHPAM-4147 ] Upgrade Red Hat JBoss EAP version to 7.4.8 on Red Hat Process Automation Manager image [ RHPAM-4616 ] 12.5. Decision engine Equality conditions between the BigDecimal property and a numeric value does not work correctly in a non-executable model [ RHDM-1944 ] An unexpected rule fires after upgrading from 7.10.1 to 7.12.1 when capitalized property is updated in modify block [ RHDM-1945 ] The non-executable-model does not react to the bind-only Map property with map access operator [ RHDM-1952 ] Even after modifying, a non-matching rule is fired again when modified facts are provided by a from statement [ RHDM-1951 ]

Commands:
Chapter 8. Creating Disaster Recovery Policy on Hub cluster OpenShift DR uses Disaster Recovery Policy (DRPolicy) resources (cluster scoped) on the RHACM hub cluster to deploy, failover, and relocate workloads across managed clusters. Prerequisites Ensure that there is a set of two clusters, which are peered for storage level replication and that CSI Volume Replication is enabled. Ensure that there is a scheduling interval that determines at what frequency data replication is performed which also serves as a coarse grained Recovery Point Objective (RPO) for the workload using the DRPolicy. Ensure that each cluster in the policy is assigned a S3 profile name, which is configured using the ConfigMap of the OpenShift DR cluster and hub operators. Procedure On the Hub cluster, navigate to Installed Operators in the openshift-dr-system project and click on OpenShift DR Hub Operator . You should see two available APIs, DRPolicy and DRPlacementControl. Click Create instance for DRPolicy and click YAML view . Copy and save the following YAML to filename drpolicy.yaml after replacing <cluster1> and <cluster2> with the correct names of your managed clusters in RHACM. Note There is no need to specify a namespace to create this resource because DRPolicy is a cluster-scoped resource. Copy the contents of your unique drpolicy.yaml file into the YAML view. You must completely replace the original content. Click Create on the YAML view screen. Important The DRPolicy scheduling interval must match the interval configured in the Creating VolumeReplicationClass resource section. Verify that the DRPolicy is created successfully by running the command: Example output:

Commands:
apiVersion: ramendr.openshift.io/v1alpha1 kind: DRPolicy metadata: name: odr-policy-5m spec: drClusterSet: - name: <cluster1> s3ProfileName: s3-primary - name: <cluster2> s3ProfileName: s3-secondary schedulingInterval: 5m
oc get drpolicy odr-policy-5m -n openshift-dr-system -o jsonpath='{.status.conditions[].reason}{"\n"}'
Succeeded
Preface These Technical Notes provide documentation of the changes made between release 4.2 and release 4.3 of Red Hat Virtualization. They are intended to supplement the information contained in the text of the relevant errata advisories available through the Content Delivery Network. Red Hat Virtualization errata advisories are available at https://access.redhat.com/errata/ . A more concise summary of the features added in Red Hat Virtualization 4.3 is available in the Red Hat Virtualization 4.3 Release Notes.

Commands:
6.3. Connect JBDS to a Remote Red Hat JBoss Data Virtualization Server Select File - New - Other - Server Select Red Hat JBoss Middleware -> JBoss Enterprise Application Platform 6.x+ Set the host to your remote server host name (such as myserver01.labs.mycompany.com) and click . Select Remote, select Management Operations, check Server lifecycle is externally managed, uncheck Assign a runtime to this server and click . Click New Host, select SSH Only and then click . The Hostname should be pre-filled but otherwise paste in your host name (that is, myserver01.labs.mycompany.com), set the connection name and click Finish. Click Finish again (there is no need to fill in Remote Server Home entry). Double-click the server in Servers View, set the admin username/password and save. Note You do not need to set up the users on the local machine.

Commands: