Bug 1108172 – Typo in dynflow logging.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1108172 - Typo in dynflow logging.

Summary:	Typo in dynflow logging.

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	Infrastructure (Show other bugs)
Sub Component:
Version:	6.0.3
Hardware:	Unspecified Unspecified

Priority	unspecified Severity low (vote)
Target Milestone:	Unspecified
Target Release:	Unused
Assigned To:	Ivan Necas
QA Contact:	jcallaha
Docs Contact:

URL:	http://projects.theforeman.org/issues...
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2014-06-11 09:57 EDT by Corey Welton
Modified:	2017-02-23 16:15 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-08-12 01:09:19 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	6310	None	None	None	2016-04-22 12:21 EDT
Red Hat Product Errata	RHSA-2015:1592	normal	SHIPPED_LIVE	Important: Red Hat Satellite 6.1.1 on RHEL 6	2015-08-12 05:04:35 EDT

Groups: None (edit)

Description Corey Welton 2014-06-11 09:57:08 EDT

Description of problem:
An error message in logging, provided by dynflow, has a typo

Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140605.0

How reproducible:


Steps to Reproduce:
1.  Get some tasks in dynflow into a locked state
2.  View foreman log


Actual results:

ForemanTasks::Lock::LockConflict: Required lock is already taken by other running tasks.
Please inspect their state, fix their errors nad resume them.

Expected results:
ForemanTasks::Lock::LockConflict: Required lock is already taken by other running tasks.
Please inspect their state, fix their errors and resume them.


Additional info:

Comment 2 Ivan Necas 2014-06-20 09:07:23 EDT

Created redmine issue http://projects.theforeman.org/issues/6310 from this bug

Comment 3 Ivan Necas 2014-06-23 04:20:44 EDT

Fix proposed at https://github.com/theforeman/foreman-tasks/pull/73

Comment 4 Ivan Necas 2014-06-23 08:27:17 EDT

Fix proposed in https://github.com/theforeman/foreman-tasks/pull/73

Comment 5 Bryan Kearney 2014-08-29 10:02:23 EDT

Moving to POST since upstream bug http://projects.theforeman.org/issues/6310 has been closed
-------------
Ivan Necas
https://github.com/theforeman/foreman-tasks/pull/73

Comment 6 jcallaha 2014-12-05 15:42:46 EST

*** This bug is verified in upstream.  This fix should eventually land in future downstream builds ***

Version Tested:
RHEL 65/66/7

ruby193-rubygem-foreman_hooks-0.3.7-2.el7.noarch
foreman-postgresql-1.8.0-0.develop.201412040955git563fa28.el7.noarch
qe-foreman-rhel7.usersys.redhat.com-qpid-client-cert-1.0-1.noarch
foreman-libvirt-1.8.0-0.develop.201412040955git563fa28.el7.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2-1.el7.noarch
foreman-compute-1.8.0-0.develop.201412040955git563fa28.el7.noarch
ruby193-rubygem-foreman_discovery-1.4.1-1.el7.noarch
foreman-proxy-1.8.0-0.develop.201411261259git6ddd00d.el7.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410git163c264.git.0.988ca80.el7.noarch
qe-foreman-rhel7.usersys.redhat.com-foreman-proxy-1.0-1.noarch
foreman-release-1.8.0-0.develop.201412040955git563fa28.el7.noarch
foreman-gce-1.8.0-0.develop.201412040955git563fa28.el7.noarch
foreman-vmware-1.8.0-0.develop.201412040955git563fa28.el7.noarch
rubygem-hammer_cli_foreman-0.1.3-1.201411121216git9381fc5.el7.noarch
ruby193-rubygem-foreman-tasks-0.6.9-1.el7.noarch
foreman-ovirt-1.8.0-0.develop.201412040955git563fa28.el7.noarch
foreman-selinux-1.8.0-0.develop.201411281557gitf4a857f.el7.noarch
foreman-1.8.0-0.develop.201412040955git563fa28.el7.noarch
qe-foreman-rhel7.usersys.redhat.com-foreman-client-1.0-1.noarch
qe-foreman-rhel7.usersys.redhat.com-apache-1.0-1.noarch
qe-foreman-rhel7.usersys.redhat.com-parent-cert-1.0-1.noarch
ruby193-rubygem-foreman_docker-0.2.0-2.el7.noarch
qe-foreman-rhel7.usersys.redhat.com-puppet-client-1.0-1.noarch
qe-foreman-rhel7.usersys.redhat.com-qpid-broker-1.0-1.noarch

Comment 7 Bryan Kearney 2015-08-11 09:27:00 EDT

This bug is slated to be released with Satellite 6.1.

Comment 8 errata-xmlrpc 2015-08-12 01:09:19 EDT

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, 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/RHSA-2015:1592

Note You need to log in before you can comment on or make changes to this bug.