Bug 1505976 - satellite-clone does not populate logs/playbook.log
Summary: satellite-clone does not populate logs/playbook.log
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Clone
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: John Mitsch
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 1533259
TreeView+ depends on / blocked
 
Reported: 2017-10-24 17:48 UTC by sthirugn@redhat.com
Modified: 2019-09-26 14:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-04 21:43:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description sthirugn@redhat.com 2017-10-24 17:48:25 UTC
Description of problem:
satellite-clone does not populate logs/playbook.log

Version-Release number of selected component (if applicable):
satellite-clone-1.1.3-1.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Provision a new rhel7vm
2. Install satellite-clone from satellite-maintenance repo
3. Update required variables and run satellite-clone

Actual results:
This is all I saw in logs/playbook.log:

2017-10-24 11:36:11,641 p=12097 u=root |  [DEPRECATION WARNING]: The use of 'include' for tasks has been deprecated. Use 'import_tasks' for static inclusions or 'include_tasks' for dynamic inclusions. This
feature will be removed in a future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
2017-10-24 11:36:11,718 p=12097 u=root |  [DEPRECATION WARNING]: include is kept for backwards compatibility but usage is discouraged. The module documentation details page may explain more about this
rationale.. This feature will be removed in a future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
2017-10-24 11:36:11,940 p=12097 u=root |  ERROR! Unexpected Exception, this is probably a bug: 'CallbackModule' object has no attribute 'set_options'
2017-10-24 11:36:11,941 p=12097 u=root |  to see the full traceback, use -vvv
2017-10-24 11:36:11,941 p=12097 u=root |  the full traceback was:

Traceback (most recent call last):
  File "/usr/bin/ansible-playbook", line 106, in <module>
    exit_code = cli.run()
  File "/usr/lib/python2.7/site-packages/ansible/cli/playbook.py", line 130, in run
    results = pbex.run()
  File "/usr/lib/python2.7/site-packages/ansible/executor/playbook_executor.py", line 90, in run
    self._tqm.load_callbacks()
  File "/usr/lib/python2.7/site-packages/ansible/executor/task_queue_manager.py", line 203, in load_callbacks
    callback_obj .set_options(C.config.get_plugin_options('callback', callback_plugin._load_name))
AttributeError: 'CallbackModule' object has no attribute 'set_options'

2017-10-24 11:39:24,781 p=12270 u=root |  ERROR! Unexpected Exception, this is probably a bug: 'CallbackModule' object has no attribute 'set_options'
2017-10-24 11:39:24,782 p=12270 u=root |  to see the full traceback, use -vvv
2017-10-24 11:39:24,782 p=12270 u=root |  the full traceback was:

Traceback (most recent call last):
  File "/usr/bin/ansible-playbook", line 106, in <module>
    exit_code = cli.run()
  File "/usr/lib/python2.7/site-packages/ansible/cli/playbook.py", line 130, in run
    results = pbex.run()
  File "/usr/lib/python2.7/site-packages/ansible/executor/playbook_executor.py", line 90, in run
    self._tqm.load_callbacks()
  File "/usr/lib/python2.7/site-packages/ansible/executor/task_queue_manager.py", line 203, in load_callbacks
callback_obj .set_options(C.config.get_plugin_options('callback', callback_plugin._load_name))
AttributeError: 'CallbackModule' object has no attribute 'set_options'

Expected results:
The ansible run output should be saved in logs for records.

Additional info:

Comment 2 John Mitsch 2017-11-30 18:26:48 UTC
This was fixed upstream as part of a larger change and will be available in 1.2.0+ 

https://github.com/RedHatSatellite/satellite-clone/pull/245

Comment 3 John Mitsch 2017-12-18 14:10:51 UTC
in 1.2.0, /var/log/satellite-clone/playbook.log is the location of the log file

Comment 4 sthirugn@redhat.com 2018-01-04 21:42:49 UTC
Verified in satellite-clone-1.2.0-1.el7sat.noarch (released to Prod on 1/4/2017)

Now -
1. I am able to see the satellite-clone logs in the terminal while running `satellite-clone` command
2. The logs are also getting populated in /var/log/satellite-clone/playbook.log


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