Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionAndreas Bleischwitz
2019-10-16 13:09:11 UTC
Description of problem:
After running foreman-maintain, /var/lib/pulp/job1.0.0 is still on the disk. This file was created by the fio disk-benchmark.
fio --name=job1 --rw=read --size=1g --output-format=json --directory=/var/lib/pulp --direct=1
# ls -lh /var/lib/pulp/job1.0.0
-rw-r--r--. 1 root root 1.0G Oct 16 12:51 /var/lib/pulp/job1.0.0
Version-Release number of selected component (if applicable):
# rpm -qa |grep maintain
rubygem-foreman_maintain-0.3.5-1.el7sat.noarch
satellite-maintain-0.0.1-1.el7sat.noarch
How reproducible:
Always
Steps to Reproduce:
1. run "foreman-maintain health check --label disk-performance"
2. see "/var/lib/pulp/job1.0.0" created, but never removed
3.
Actual results:
Leftovers from those benchmark tests.
Expected results:
Leftovers removed after benchmark has been run
Additional info:
/usr/share/gems/gems/foreman_maintain-0.3.5/lib/foreman_maintain/utils/disk/io_device.rb should probably add a file-removal after fio finished.
28 def fio
29 cmd = "fio --name=job1 --rw=read --size=1g --output-format=json\
30 --directory=#{dir} --direct=1"
31 stdout = execute(cmd)
32 output = JSON.parse(stdout)
33 @fio ||= output['jobs'].first['read']['bw'].to_i
>> probably here??
34 end
Additional, I see that /usr/share/gems/gems/foreman_maintain-0.3.5/definitions/checks/disk/performance.rb should test pulp, mongo and pgsql directories for speed, I only saw pulp being tested.
17 DEFAULT_DIRS = ['/var/lib/pulp', '/var/lib/mongodb', '/var/lib/pgsql'].freeze
Hello Andreas,
Updating package rubygem-foreman_maintain to 0.5.3 will resolve this.
As you mentioned, included in Satellite 6.7.
Moving this BZ to ON_QA for verification
Verified
Verified with:
- Satellite 6.8.0 snap 3
- rubygem-foreman_maintain-0.6.4-1.el7sat.noarch
Test steps:
- Run foreman-maintain health check --label disk-performance
- ls -lh /var/lib/pulp/job1.0.0
Observation:
- While check is running it creates /var/lib/pulp/job1.0.0
- /var/lib/pulp/job1.0.0 is not present ones check finishes execution.
Note: disk-performance check won't run with other pre-upgrade checks.
Refer BZ#1827219 for more information.
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 (Satellite 6.8 Satellite Maintenance Release), 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-2020:4365
Description of problem: After running foreman-maintain, /var/lib/pulp/job1.0.0 is still on the disk. This file was created by the fio disk-benchmark. fio --name=job1 --rw=read --size=1g --output-format=json --directory=/var/lib/pulp --direct=1 # ls -lh /var/lib/pulp/job1.0.0 -rw-r--r--. 1 root root 1.0G Oct 16 12:51 /var/lib/pulp/job1.0.0 Version-Release number of selected component (if applicable): # rpm -qa |grep maintain rubygem-foreman_maintain-0.3.5-1.el7sat.noarch satellite-maintain-0.0.1-1.el7sat.noarch How reproducible: Always Steps to Reproduce: 1. run "foreman-maintain health check --label disk-performance" 2. see "/var/lib/pulp/job1.0.0" created, but never removed 3. Actual results: Leftovers from those benchmark tests. Expected results: Leftovers removed after benchmark has been run Additional info: /usr/share/gems/gems/foreman_maintain-0.3.5/lib/foreman_maintain/utils/disk/io_device.rb should probably add a file-removal after fio finished. 28 def fio 29 cmd = "fio --name=job1 --rw=read --size=1g --output-format=json\ 30 --directory=#{dir} --direct=1" 31 stdout = execute(cmd) 32 output = JSON.parse(stdout) 33 @fio ||= output['jobs'].first['read']['bw'].to_i >> probably here?? 34 end Additional, I see that /usr/share/gems/gems/foreman_maintain-0.3.5/definitions/checks/disk/performance.rb should test pulp, mongo and pgsql directories for speed, I only saw pulp being tested. 17 DEFAULT_DIRS = ['/var/lib/pulp', '/var/lib/mongodb', '/var/lib/pgsql'].freeze