Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
.RHEL-Edge container image now uses `nginx` and serves on port 8080
Previously, the `edge-container` image type was unable to run in non-root mode. As a result, Red Hat OpenShift 4 was unable to use the `edge-container` image type. With this enhancement, the container now uses `nginx` HTTP server to serve the commit and a configuration file that allows the server to run as a non-root user inside the container, enabling its use on Red Hat OpenShift 4. The internal web server now uses the port `8080` instead of `80`.
Created attachment 1768092[details]
edge image ocp4 template
Description of problem:
When I run edge container image on OpenShift 4. I got the following error:
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 172.20.7.62. Set the 'ServerName' directive globally to suppress this message
(13)Permission denied: AH00058: Error retrieving pid file run/httpd.pid
AH00059: Remove it before continuing if it is corrupted.
Error "(13)Permission denied: AH00058: Error retrieving pid file run/httpd.pid" should be related with ocp arbitrary UID issue.
Version-Release number of selected component (if applicable):
I have to use scratch ostree build due to bz#1944473
python3-osbuild-27-1.20210330gitf119243.20210330gitf119243.el8.noarch
osbuild-composer-core-28.3-1.el8.x86_64
osbuild-selinux-27-1.20210330gitf119243.20210330gitf119243.el8.noarch
osbuild-ostree-27-1.20210330gitf119243.20210330gitf119243.el8.noarch
osbuild-composer-28.3-1.el8.x86_64
osbuild-27-1.20210330gitf119243.20210330gitf119243.el8.noarch
osbuild-composer-worker-28.3-1.el8.x86_64
How reproducible:
Steps to Reproduce:
1. Install osbuild*
2. Configure blueprint in container.toml
$ cat container.toml
name = "container"
description = "A base rhel-edge container image"
version = "0.0.1"
modules = []
groups = []
[[packages]]
name = "python36"
version = "*"
[customizations.kernel]
name = "kernel-rt"
[[customizations.user]]
name = "admin"
description = "Administrator account"
password = "$6$GRmb7S0p8vsYmXzH$o0E020S.9JQGaHkszoog4ha4AQVs3sk8q0DvLjSMxoxHBKnB2FBXGQ/OkwZQfW/76ktHd0NX5nls2LPxPuUdl."
key = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC61wMCjOSHwbVb4VfVyl5sn497qW4PsdQ7Ty7aD6wDNZ/QjjULkDV/yW5WjDlDQ7UqFH0Sr7vywjqDizUAqK7zM5FsUKsUXWHWwg/ehKg8j9xKcMv11AkFoUoujtfAujnKODkk58XSA9whPr7qcw3vPrmog680pnMSzf9LC7J6kXfs6lkoKfBh9VnlxusCrw2yg0qI1fHAZBLPx7mW6+me71QZsS6sVz8v8KXyrXsKTdnF50FjzHcK9HXDBtSJS5wA3fkcRYymJe0o6WMWNdgSRVpoSiWaHHmFgdMUJaYoCfhXzyl7LtNb3Q+Sveg+tJK7JaRXBLMUllOlJ6ll5Hod root@localhost"
home = "/home/admin/"
groups = ["wheel"]
3. Push container.toml
$ sudo composer-cli blueprints push container.toml
4. Check package dependens
$ sudo composer-cli blueprints depsolve container
5. Build image
$ sudo composer-cli compose start-ostree --ref rhel/8/x86_64/edge container rhel-edge-container
6. Wait until it's FINISHED
$ sudo composer-cli compose status
6. Download image
$ sudo composer-cli compose image e4fa3a99-11f4-4035-971c-fbc58c49725c
7. Upload image to docker.io
$ skopeo copy --dest-creds username:password oci-archive:e4fa3a99-11f4-4035-971c-fbc58c49725c-rhel84-container.tar docker://docker.io/username/rhel-edge:latest
8. Download attachment template and run it(image repository in template might be changed according to where to save image)
$ oc login --server=<ocp4 api server>
$ oc process -f edge-stage-server-template.yaml | oc4 apply -f
Actual results:
Can't run container and have error message "(13)Permission denied: AH00058: Error retrieving pid file run/httpd.pid"
Expected results:
Run edge container image on ocp4 successfully.
Additional info:
Comment 1Achilleas Koutsou
2021-04-21 12:40:17 UTC
The plan for this is to change the web service in the container from httpd (apache) to nginx. On top of that, we need to configure the service to run without root privileges, which requires a more flexible OCI container creation stage and maybe a service config stage of some kind.
Pre-verified on the following build:
python3-osbuild-30-1.20210722git35de309.20210722git35de309.el8.noarch
osbuild-composer-30-1.20210728git6ecb00a.el8.x86_64
osbuild-30-1.20210722git35de309.20210722git35de309.el8.noarch
osbuild-ostree-30-1.20210722git35de309.20210722git35de309.el8.noarch
osbuild-composer-worker-30-1.20210728git6ecb00a.el8.x86_64
osbuild-composer-core-30-1.20210728git6ecb00a.el8.x86_64
osbuild-selinux-30-1.20210722git35de309.20210722git35de309.el8.noarch
Comment 5Alexander Todorov
2021-08-24 07:42:02 UTC
(In reply to Xiaofeng Wang from comment #2)
> Pre-verified on the following build:
> python3-osbuild-30-1.20210722git35de309.20210722git35de309.el8.noarch
> osbuild-composer-30-1.20210728git6ecb00a.el8.x86_64
> osbuild-30-1.20210722git35de309.20210722git35de309.el8.noarch
> osbuild-ostree-30-1.20210722git35de309.20210722git35de309.el8.noarch
> osbuild-composer-worker-30-1.20210728git6ecb00a.el8.x86_64
> osbuild-composer-core-30-1.20210728git6ecb00a.el8.x86_64
> osbuild-selinux-30-1.20210722git35de309.20210722git35de309.el8.noarch
@Xiaofeng, @Yi,
can you verify with the latest official builds in a nightly/devel tree ?
Comment 7Alexander Todorov
2021-08-24 12:32:17 UTC
(In reply to Xiaofeng Wang from comment #6)
> @atodorov, the fix PR(https://github.com/osbuild/osbuild-composer/pull/1595)
> still not got merged. So have to wait PR merged and new RHEL 8.5 release.
In 8.5 we've got osbuild-composer-31-1.el8 and in Comment #2 you indicated that you have tested with v30-1. How is it possible that you were able to pre-verify with an older build but not with the latest one?
Comment 8Alexander Todorov
2021-08-24 12:33:34 UTC
(In reply to Xiaofeng Wang from comment #6)
> @atodorov, the fix PR(https://github.com/osbuild/osbuild-composer/pull/1595)
> still not got merged. So have to wait PR merged and new RHEL 8.5 release.
@Achilleas,
what's the hold up for this PR being merged and how does that relate to this particular BZ ? Please see my reminder about schedule on the internal ML.
Comment 9Achilleas Koutsou
2021-08-26 10:31:08 UTC
No hold-up or blockage. Just needs to be reviewed again and merged.
Comment 10Alexander Todorov
2021-08-31 08:45:54 UTC
(In reply to Achilleas Koutsou from comment #9)
> No hold-up or blockage. Just needs to be reviewed again and merged.
I see PR has already been merged. Can you update the Fixed in version field ? Will this be in 33-1 ?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (osbuild bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:4273