Previously, we pulled the PCP RPM from their upstream repository; unfortunately, that repo no longer exists. Instead, we will now pull the RPM from the distro which corresponds to the base image that we're building on. This means that we won't be providing the latest-and-greatest PCP, and it means that the different versions of the containerized Agent may provide different versions of PCP (e.g., the RHEL-7-based image will provide PCP v4 while the CentOS Stream 9 image will provide PCP v6). Hopefully, this won't result in any surprise or disappointment. (If it does, people can use an Agent container built from a different base image, or they are free to build their own container image using ours as base images and install whatever version of PCP they want in their own layer.) This PR removes the special handling for the PCP RPM, and these dependencies are now satisfied in the normal way.
In preparation for the deployment of Pbench Server 1.0, which will require TLS access, this PR also adds the Red Hat Certificate Authority certificates required to validate the Agent's connection to the Pbench Server (e.g., for pbench-results-push).
Previously, we pulled the PCP RPM from their upstream repository; unfortunately, that repo no longer exists. Instead, we will now pull the RPM from the distro which corresponds to the base image that we're building on. This means that we won't be providing the latest-and-greatest PCP, and it means that the different versions of the containerized Agent may provide different versions of PCP (e.g., the RHEL-7-based image will provide PCP v4 while the CentOS Stream 9 image will provide PCP v6). Hopefully, this won't result in any surprise or disappointment. (If it does, people can use an Agent container built from a different base image, or they are free to build their own container image using ours as base images and install whatever version of PCP they want in their own layer.) This PR removes the special handling for the PCP RPM, and these dependencies are now satisfied in the normal way.
In preparation for the deployment of Pbench Server 1.0, which will require TLS access, this PR also adds the Red Hat Certificate Authority certificates required to validate the Agent's connection to the Pbench Server (e.g., for
pbench-results-push).