mtpti5iD/redhat-docs_dataset huggingface dataset:
25.4. Storing a User's Personal Secret This section shows how a user can create one or more private vaults to securely store personal secrets. The user then retrieves the secrets when required, on any machine in the domain. For example, the user can archive a personal certificate in a vault, thus storing the certificate securely in a centralized location. This section includes these procedures: Section 25.4.1, "Archiving a User's Personal Secret" Section 25.4.2, "Retrieving a User's Personal Secret" In the procedures: user is the user who wants to create the vault my_vault is the vault used to store the user's certificate the vault type is standard , so that accessing the archived certificate does not require the user to provide a vault password secret.txt is the file containing the certificate that the user wants to store in the vault secret_exported.txt is the file to which the user exports the archived certificate 25.4.1. Archiving a User's Personal Secret Create a private user vault and store your certificate in it. The vault type is standard, which ensures you will not be required to authenticate when accessing the certificate. Log in as user : Use the ipa vault-add command to create a standard vault: Important Make sure the first user vault for a user is created by the same user. For example, if another user, such as admin , creates the first user vault for user1 , the owner of the user's vault container will also be admin , and user1 will be unable to access the user vault or create new user vaults. See also Section B.5.1, "Users Cannot Access Their Vault Due To Insufficient 'add' Privilege" . Use the ipa vault-archive --in command to archive the secret.txt file into the vault: Note One vault can only store one secret. 25.4.2. Retrieving a User's Personal Secret Export the certificate from your private standard vault. Log in as user : Use the ipa vault-retrieve --out command to retrieve the contents of the vault and save them into the secret_exported.txt file.

Commands:
kinit user
ipa vault-add my_vault --type standard ---------------------- Added vault "my_vault" ---------------------- Vault name: my_vault Type: standard Owner users: user Vault user: user
ipa vault-archive my_vault --in secret.txt ----------------------------------- Archived data into vault "my_vault" -----------------------------------
kinit user
ipa vault-retrieve my_vault --out secret_exported.txt -------------------------------------- Retrieved data from vault "my_vault" --------------------------------------
3.3. CPU Performance Options Several CPU related options are available to your guest virtual machines. Configured correctly, these options can have a large impact on performance. The following image shows the CPU options available to your guests. The remainder of this section shows and explains the impact of these options. Figure 3.3. CPU Performance Options 3.3.1. Option: Available CPUs Use this option to adjust the amount of virtual CPUs (vCPUs) available to the guest. It is also possible to change the number of vCPUs while the guest is running, which is referred to as hot plugging and hot unplugging . Important The hot unplugging feature is only available as a Technology Preview. Therefore, it is not supported and not recommended for use in high-value deployments. If you allocate more than is available on the host (known as overcommitting ), a warning is displayed, as shown in the following image: Figure 3.4. CPU overcommit CPUs are overcommitted when the sum of vCPUs for all guests on the system is greater than the number of host CPUs on the system. You can overcommit CPUs with one or multiple guests if the total number of vCPUs is greater than the number of host CPUs. Important As with memory overcommitting, CPU overcommitting can have a negative impact on performance, for example in situations with a heavy or unpredictable guest workload. Refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide for more details on overcommitting.

Commands:
31.2.2. Connect Mode Certain firewall configurations or instances where the target system is configured to obtain a dynamic IP address may cause trouble with the direct VNC mode in anaconda. In addition, if you lack a console on the target system to see the message that tells you the IP address to connect to, then you will not be able to continue the installation. The VNC connect mode changes how VNC is started. Rather than anaconda starting up and waiting for you to connect, the VNC connect mode allows anaconda to automatically connect to your view. You won't need to know the IP address of the target system in this case. To activate the VNC connect mode, pass the vncconnect boot parameter: Replace HOST with your VNC viewer's IP address or DNS host name. Before starting the installation process on the target system, start up your VNC viewer and have it wait for an incoming connection. Start the installation and when your VNC viewer displays the graphical installer, you are ready to go.

Commands:
boot: linux vncconnect= HOST
Chapter 9. Fixed issues in Red Hat Decision Manager 7.13.1 Red Hat Decision Manager 7.13.1 provides increased stability and fixed issues listed in this section. 9.1. Business Central The test scenario returns an error when it is executed in the mvn test command [ RHDM-1539 ] 9.2. KIE Server A ClassCastException occurs if you submit a form in a kie-server that contains the date process variable [ RHPAM-4326 ] The EJB service saveContentFromUser method does not works with the custom usercallback and you receive an error message [ RHPAM-4234 ] The custom query response does not return the SLAdueDate with the UserTasksWithCustomVariables mapper [ RHPAM-4232 ] The EventEmitter returns wrong task statuses [ RHPAM-4091 ] The properties on custom settings are not available on the KIE Server deployments [ RHPAM-3976 ] Class retention by JSONMashaller ObjectMapper._typeFactory._typeCache [ RHDM-1933 ] The class retention by JSONMashaller ObjectMapper._typeFactory._typeCache and you receive OutOfMemoryError: Metaspace error [ RHDM-1933 ] 9.3. Red Hat build of Kogito Kogito aligned with non supported Spring Boot version [ RHPAM-4419 ] 9.4. DMN designer In the DMN designer, a text annotation is not saved correctly if it created by copying and pasting [ RHDM-1890 ] Unable to include the DMN model [ RHDM-1850 ] 9.5. Configuration Wrong managed version of Spring Boot dependencies [ RHPAM-4413 ] 9.6. Red Hat OpenShift Container Platform Upgrade Red Hat JBoss EAP version to 7.4.6 on RHPAM image [ RHPAM-4481 ] Sensitive information such as user names and passwords are exposed in environment variables and pod logs [ RHPAM-4438 ] The Kie Server OpenShift startup strategy watcher is closed and the DeploymentConfig is not updated [ RHPAM-3333 ] 9.7. Decision engine When you are using generics in accumulate inline code, you receive an error with the ClassNotFoundException exception [ RHPAM-4444 ] The metrics of rule execution must include the rules fired from a BPMN process [ RHPAM-4248 ] The kie-server-client fails to unmarshall a response suddenly with the NumberFormatException [ RHDM-1942 ] The build fails with a "_this cannot be resolved" message during the compilation of a generated executable model [ RHDM-1940 ] In an executable model, you receive a NullPointerException in LambdaConsequence error with global variable [ RHDM-1920 ] Fails to parse a constraint connected with OR with a bind variable on right side in an executable model [ RHDM-1910 ] In an executable model, when a BigDecimal literal is set to a variable with a MVEL dialect, you receive the ClassCastException exception [ RHDM-1908 ] In an executable model, a prop with method invocation is not recognized in a modify block [ RHDM-1907 ] In an executable model, an arithmetic operation with a String coercion in constraint fails to execute [ RHDM-1905 ] In an executable model, an arithmetic operation with a BigDecimal in constraint fails [ RHDM-1904 ]

Commands:
Chapter 2. AMQ Streams deployment of Kafka Apache Kafka components are provided for deployment to OpenShift with the AMQ Streams distribution. The Kafka components are generally run as clusters for availability. A typical deployment incorporating Kafka components might include: Kafka cluster of broker nodes ZooKeeper cluster of replicated ZooKeeper instances Kafka Connect cluster for external data connections Kafka MirrorMaker cluster to mirror the Kafka cluster in a secondary cluster Kafka Exporter to extract additional Kafka metrics data for monitoring Kafka Bridge to make HTTP-based requests to the Kafka cluster Not all of these components are mandatory, though you need Kafka and ZooKeeper as a minimum. Some components can be deployed without Kafka, such as MirrorMaker or Kafka Connect. 2.1. Kafka component architecture A cluster of Kafka brokers handles delivery of messages. A broker uses Apache ZooKeeper for storing configuration data and for cluster coordination. Before running Apache Kafka, an Apache ZooKeeper cluster has to be ready. Each of the other Kafka components interact with the Kafka cluster to perform specific roles. Kafka component interaction Apache ZooKeeper Apache ZooKeeper is a core dependency for Kafka as it provides a cluster coordination service, storing and tracking the status of brokers and consumers. ZooKeeper is also used for controller election. Kafka Connect Kafka Connect is an integration toolkit for streaming data between Kafka brokers and other systems using Connector plugins. Kafka Connect provides a framework for integrating Kafka with an external data source or target, such as a database, for import or export of data using connectors. Connectors are plugins that provide the connection configuration needed. A source connector pushes external data into Kafka. A sink connector extracts data out of Kafka External data is translated and transformed into the appropriate format. You can deploy Kafka Connect with build configuration that automatically builds a container image with the connector plugins you require for your data connections. Kafka MirrorMaker Kafka MirrorMaker replicates data between two Kafka clusters, within or across data centers. MirrorMaker takes messages from a source Kafka cluster and writes them to a target Kafka cluster. Kafka Bridge Kafka Bridge provides an API for integrating HTTP-based clients with a Kafka cluster. Kafka Exporter Kafka Exporter extracts data for analysis as Prometheus metrics, primarily data relating to offsets, consumer groups, consumer lag and topics. Consumer lag is the delay between the last message written to a partition and the message currently being picked up from that partition by a consumer

Commands:
Chapter 8. Monitoring Red Hat Hyperconverged Infrastructure for Virtualization 8.1. Monitoring Virtual Data Optimizer (VDO) Monitoring VDO helps in understanding when the physical storage is running out of space. Physical space in VDO needs to be monitored like thin provisioned storage. VDO devices should use thin provisioning because more logical space will be available and VDO space will be used in a more effective way. By default thin provisioning is enabled and it can be unchecked as required. You can check available blocks, used space, and device information by clicking on View Details . 8.1.1. Monitoring VDO using the command line interface There are several options for monitoring VDO using the command line interface. The vdostats command This command displays volume statistics including available blocks, number of blocks used, device name, percentage of physical blocks saved, and percentage of physical blocks on a VDO volume. For more information on vdostats, see the manual page: man vdostats . The vdo status command This command reports VDO system and volume status in YAML format. The /sys/kvdo/<vdo_volume>/statistics directory Files in this directory include volume statistics for VDO. You can read these files instead of using the vdostats command. 8.1.2. Monitoring VDO using the Web Console Events related to VDO usage are displayed under the Notifications tab. Events provide information about the physical space remaining on the VDO volume, and keep you up to date about whether more physical space is needed. Table 8.1. Types of Event Notification Type Text Actions Warn Warning, low confirmed disk space. StorageDomainName domain has DiskSpace GB of confirmed free space. Delete data that is not required. Replace existing disks with larger disks. Add more Red Hat Gluster Storage servers and expand the volume across the new servers. Add more disks and expand the logical volumes underlying the Gluster volume.

Commands:
Chapter 4. Technology Preview This section lists Technology Preview features in Red Hat Developer Hub 1.3. Important Technology Preview features provide early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. However, these features are not fully supported under Red Hat Subscription Level Agreements, may not be functionally complete, and are not intended for production use. As Red Hat considers making future iterations of Technology Preview features generally available, we will attempt to resolve any issues that customers experience when using these features. See: Technology Preview support scope . 4.1. Registering existing entities from multiple Git repositories simultaneously With this update, you can register entities from multiple repositories simultaneously, without the need to register them individually. For repositories without a catalog-entity.yaml file, the plugin creates a pull request. Once the pull request is merged, Developer Hub registers the entity in the software catalog. Additional resources RHIDP-1397 4.2. Added the catalog backend module logs plugin With this update, Developer Hub includes the @backstage/plugin-catalog-backend-module-logs plugin as a dynamic plugin to help surface catalog errors into the logs. This dynamic plugin is disabled by default. Additional resources RHIDP-3713

Commands:
Chapter 3. Known issues Installation might fail due to a known issue with RHTAP SecureSign. To recover, simply delete the namespace into which you've deployed RHTAP ( rhtap by default) and rerun the installer. On the second run, the installation should be successful. RHTAP 1.0 does not install Red Hat Trusted Profile Analyzer (RHTPA); instead, it installs an upstream tool called Trustification . RHTAP 1.0.2, however, installs RHTPA. You can configure GitLab as an authentication provider in the private-values.yaml file you create for installation. However, once GitLab is configured, it still doesn't show up as a sign in option. The login for GitLab is accessible in the settings page, <host>/settings/auth-providers , but requires signing in to GitHub to access that page. The pull-request pipeline often fails with the build-container task and displays the following error message: Access to the requested resource is not authorized . To fix this, push your container image to Quay.io and run the pipeline again. When promoting applications, the verify-enterprise-contract task currently fails. However, to fix this issue, you simply need to remove the Rekor custom resource (CR). A new Rekor CR then starts up, but the task no longer fails. Remove the CR with one of the following methods: Delete the Rekor CR in your command line. oc delete rekor -n USD<namespace where rhtap is installed> rhtap-securesign In the OCP console, in the Admin view, click on Search under the Home tab. Search for "Rekor" in the rhtap namespace, and delete the instance of the CR that you find. When you promote a new container image to the RHTAP stage environment from a Go or Python software template, you run the verify-enterprise-contract step. This step might cause the following error: No image attestations found matching the given public key. You must manually update the image repository so that it's public. RHTAP 1.0 does not support the following environments: any air-gapped environment, IBM Power Platform, IBM Z Platform, ARM64, and Federal Information Processing Standards (FIPS) mode OCP. Uninstallation of RHTAP is not currently supported, but it can be done by removing all RHTAP namespaces from the cluster. Revised on 2024-07-15 21:03:50 UTC

Commands:
Chapter 35. Storage DM Multipath no longer crashes when adding a feature to an empty string Previously, the DM Multipath service terminated unexpectedly when it attempted to add a feature to the features string of a built-in device configuration that had no features string. With this update, DM Multipath first checks if the features string exists, and creates one if necessary. As a result, DM Multipath no longer crashes when trying to modify a nonexistent features string. (BZ# 1459370 ) I/O operations no longer hang with RAID1 Previously, the kernel did not handle Multiple Devices (MD) I/O errors properly in dm-raid . As a consequence, the I/O sometimes became unresponsive. With this update, dm-raid now handles I/O errors correctly, and I/O operations no longer hang with RAID1. (BZ#1506338)

Commands:
Chapter 8. Performing Bare Metal certification The Red Hat OpenStack Platform Bare Metal certification validates that your system can be orchestrated as part of an OpenStack environment. 8.1. Creating a RHOSP Bare Metal supplemental certification The Red Hat OpenStack Platform Bare Metal certification may have already been created for you as part of the Red Hat Enterprise Linux System certification. If it was not automatically created for you, or if you need to apply for the certification at a later date, perform the following steps: Prerequisites Your server must have already earned the following certifications: Red Hat Enterprise Linux System Red Hat OpenStack Platform Compute Node If you need information about creating the Red Hat OpenStack Platform Compute Node layered certification, see Certifying layered products . Procedure Log in to the Red Hat Partner Connect portal. Click the Red Hat Enterprise Linux System certification that is related to the bare-metal certification you want to open. Go to the Related Certifications tab. Click the Red Hat OpenStack Platform Compute node certification that is related to the bare-metal certification you want to open. Go to the Related Certifications tab. At the top of the certifications table, click Add Related Certification . The Create Related Certification window appears. Choose Supplemental and click . Review the certification information and click Open . The supplemental certification is created, and the Red Hat certification team will add the Bare Metal Management component to the test plan. After you get the new test plan, start testing.

Commands:
Chapter 63. Data objects Data objects are the building blocks for the rule assets that you create. Data objects are custom data types implemented as Java objects in specified packages of your project. For example, you might create a Person object with data fields Name , Address , and DateOfBirth to specify personal details for loan application rules. These custom data types determine what data your assets and your decision services are based on. 63.1. Creating data objects The following procedure is a generic overview of creating data objects. It is not specific to a particular business asset. Procedure In Business Central, go to Menu Design Projects and click the project name. Click Add Asset Data Object . Enter a unique Data Object name and select the Package where you want the data object to be available for other rule assets. Data objects with the same name cannot exist in the same package. In the specified DRL file, you can import a data object from any package. Importing data objects from other packages You can import an existing data object from another package directly into the asset designers like guided rules or guided decision table designers. Select the relevant rule asset within the project and in the asset designer, go to Data Objects New item to select the object to be imported. To make your data object persistable, select the Persistable checkbox. Persistable data objects are able to be stored in a database according to the JPA specification. The default JPA is Hibernate. Click Ok . In the data object designer, click add field to add a field to the object with the attributes Id , Label , and Type . Required attributes are marked with an asterisk (*). Id: Enter the unique ID of the field. Label: (Optional) Enter a label for the field. Type: Enter the data type of the field. List: (Optional) Select this check box to enable the field to hold multiple items for the specified type. Figure 63.1. Add data fields to a data object Click Create to add the new field, or click Create and continue to add the new field and continue adding other fields. Note To edit a field, select the field row and use the general properties on the right side of the screen.

Commands:
A.18. Troubleshooting SR-IOV This section contains solutions for problems which may affect SR-IOV. If you need additional help, see Section 16.2.4, "Setting PCI device assignment from a pool of SR-IOV virtual functions" . Error starting the guest When starting a configured virtual machine, an error occurs as follows: This error is often caused by a device that is already assigned to another guest or to the host itself. Error migrating, saving, or dumping the guest Attempts to migrate and dump the virtual machine cause an error similar to the following: Because device assignment uses hardware on the specific host where the virtual machine was started, guest migration and save are not supported when device assignment is in use. Currently, the same limitation also applies to core-dumping a guest; this may change in the future. It is important to note that QEMU does not currently support migrate, save, and dump operations on guest virtual machines with PCI devices attached, unless the --memory-only option is specified. Currently, it only can support these actions with USB devices. Work is currently being done to improve this in the future.

Commands:
virsh start test error: Failed to start domain test error: Requested operation is not valid: PCI device 0000:03:10.1 is in use by domain rhel7
virsh dump rhel7/tmp/rhel7.dump error: Failed to core dump domain rhel7 to /tmp/rhel7.dump error: internal error: unable to execute QEMU command 'migrate': State blocked by non-migratable device '0000:00:03.0/vfio-pci'