Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1394028

Summary: Problem occurred - neither one of {0} paths exists
Product: [Fedora] Fedora Reporter: Gerald Cox <gbcox>
Component: tracerAssignee: Jakub Kadlčík <jkadlcik>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 24CC: jkadlcik, laurent.rineau__fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: tracer-0.6.12-4.fc23 tracer-0.6.12-4.fc24 tracer-0.6.12-4.fc25 tracer-0.6.12-4.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-07 01:22:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gerald Cox 2016-11-10 20:55:13 UTC
Description of problem:
Receiving following error:

Problem occurred - neither one of {0} paths exists
Please contact maintainer of tracer package in your distribution.

For more information run:
    sudo tracer -iat 1478810910.6744466



Problem starting occurring with tracer-0.6.12-1

Left negative feedback on bodhi

Comment 1 Fedora Update System 2016-11-22 21:46:29 UTC
tracer-0.6.12-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-18a670dee9

Comment 2 Fedora Update System 2016-11-22 21:46:45 UTC
tracer-0.6.12-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-e339624cad

Comment 3 Fedora Update System 2016-11-22 21:50:22 UTC
tracer-0.6.12-3.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-d319944f11

Comment 4 Fedora Update System 2016-11-23 16:05:03 UTC
tracer-0.6.12-4.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5365a57b39

Comment 5 Fedora Update System 2016-11-24 19:19:01 UTC
tracer-0.6.12-4.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-3f9b4e3c43

Comment 6 Fedora Update System 2016-11-24 19:19:15 UTC
tracer-0.6.12-4.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-edc56e4114

Comment 7 Fedora Update System 2016-11-24 19:19:29 UTC
tracer-0.6.12-4.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-9debe3dcd9

Comment 8 Fedora Update System 2016-11-25 00:22:43 UTC
tracer-0.6.12-4.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5365a57b39

Comment 9 Fedora Update System 2016-11-25 09:38:24 UTC
tracer-0.6.12-3.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e339624cad

Comment 10 Fedora Update System 2016-11-25 09:40:43 UTC
tracer-0.6.12-3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-18a670dee9

Comment 11 Fedora Update System 2016-11-27 17:26:10 UTC
tracer-0.6.12-4.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-9debe3dcd9

Comment 12 Fedora Update System 2016-11-28 01:55:19 UTC
tracer-0.6.12-4.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-edc56e4114

Comment 13 Fedora Update System 2016-12-04 08:07:11 UTC
tracer-0.6.12-4.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-3f9b4e3c43

Comment 14 Fedora Update System 2016-12-07 01:22:56 UTC
tracer-0.6.12-4.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 15 Fedora Update System 2016-12-07 07:54:35 UTC
tracer-0.6.12-4.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

Comment 16 Fedora Update System 2016-12-11 19:26:17 UTC
tracer-0.6.12-4.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 17 Fedora Update System 2016-12-12 17:19:37 UTC
tracer-0.6.12-4.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.