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.
Description of problem:
Start fdo-aio service failed when the "files:" section configured, like
sudo /usr/local/bin/yq -iy '.service_info.files |= [{path: "/etc/sudoers.d/fdouser", source_path: "/tmp/fdouser"}]' /etc/fdo/aio/configs/serviceinfo_api_server.yml
If removed files section configuration and set to "files: null", service fdo-aio can get started.
I also tried "service_info.diskencryption_clevis" and "service_info.initial_user", service can get started.
This issue does not exist on CS9 repo CentOS-Stream-9-20230626.0
Version-Release number of selected component (if applicable):
fdo-admin-cli-0.4.7-3.el9.x86_64
fdo-client-0.4.7-3.el9.x86_64
fdo-init-0.4.7-3.el9.x86_64
fdo-manufacturing-server-0.4.7-3.el9.x86_64
fdo-owner-cli-0.4.7-3.el9.x86_64
fdo-owner-onboarding-server-0.4.7-3.el9.x86_64
fdo-rendezvous-server-0.4.7-3.el9.x86_64
How reproducible:
Steps to Reproduce:
1. Deploy a CS9 instance from GCP
2. git clone https://github.com/virt-s1/rhel-edge.git
3. cd rhel-edge && ./ostree-simplified-installer.sh
Actual results:
Service fdo-aio should get started
Expected results:
Failed to start fdo-aio service
Additional info:
this is the concrete error:
systemd[1]: Started FDO service info API server.
fdo-serviceinfo-api-server[75684]: Error: Error preparing ServiceInfo configuration
fdo-serviceinfo-api-server[75684]: Caused by:
fdo-serviceinfo-api-server[75684]: 0: Failed to read file /tmp/fdouser
fdo-serviceinfo-api-server[75684]: 1: Permission denied (os error 13)
fdo-serviceinfo-api-server.service: Main process exited, code=exited, status=1/FAILURE
fdo-serviceinfo-api-server.service: Failed with result 'exit-code'.
So I think if we run all the services in permssive mode and gather the AVC logs for all the services, looks like it's manufacturing and service-info-api at the moment but I bet they'll all have issues, we should be able to come up with a set of rules for this. Xiaofeng are you able to do this? Maybe one comment for each of the services?
Description of problem: Start fdo-aio service failed when the "files:" section configured, like sudo /usr/local/bin/yq -iy '.service_info.files |= [{path: "/etc/sudoers.d/fdouser", source_path: "/tmp/fdouser"}]' /etc/fdo/aio/configs/serviceinfo_api_server.yml If removed files section configuration and set to "files: null", service fdo-aio can get started. I also tried "service_info.diskencryption_clevis" and "service_info.initial_user", service can get started. This issue does not exist on CS9 repo CentOS-Stream-9-20230626.0 Version-Release number of selected component (if applicable): fdo-admin-cli-0.4.7-3.el9.x86_64 fdo-client-0.4.7-3.el9.x86_64 fdo-init-0.4.7-3.el9.x86_64 fdo-manufacturing-server-0.4.7-3.el9.x86_64 fdo-owner-cli-0.4.7-3.el9.x86_64 fdo-owner-onboarding-server-0.4.7-3.el9.x86_64 fdo-rendezvous-server-0.4.7-3.el9.x86_64 How reproducible: Steps to Reproduce: 1. Deploy a CS9 instance from GCP 2. git clone https://github.com/virt-s1/rhel-edge.git 3. cd rhel-edge && ./ostree-simplified-installer.sh Actual results: Service fdo-aio should get started Expected results: Failed to start fdo-aio service Additional info: