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:
In virt-sandbox-service: Container.gen_machine_id():
330 journalfile = "/var/log/journal/" + uuid
331 fd=open(self.dest + journalfile, "w")
332 fd.close()
333 os.symlink(self.dest + journalfile, journalfile)
334
335 def __gen_filesystems(self):
336 if self.use_image:
It assumes that /var/log/journal/ exists.
But according to journald.conf(5), missing /var/log/journal is allowed.
Actually, that directory won't be created by default and is shipped with no packages.
Version-Release number of selected component (if applicable):
v0.1.2
How reproducible:
100%
Steps to Reproduce:
run virt-sandbox-service while /var/log/journal/ doesn't exist.
Actual results:
virt-sandbox-service exit halfway and print:
/usr/bin/virt-sandbox-service: [Errno 2] No such file or directory
Expected results:
a) create /var/log/journal/ automatically
or b) don't create the symbol link
Anyway, virt-sandbox-service should not die of non-fatal exception.
commit 6b8a314f58e1678a4ba419aaa17c88145a7a5105
Author: Daniel P. Berrange <berrange>
Date: Wed Mar 20 16:08:55 2013 +0000
Don't assume /var/log/journal exists
When creating the journal symlink, create /var/log/journal if
it does not already exist. Also handle fact that the journal
symlink might have been removed, when deleting a sandbox.
When I upgrade systemd to systemd-198-4.el7, the /var/log/journal will created by default. But it's still necessary to determine whether folder exists or not.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.