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.
Bug 1018236 - node sync silently fails/says success when there obviously isn't any.
Summary: node sync silently fails/says success when there obviously isn't any.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Katello QA List
URL:
Whiteboard:
: 1017921 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-11 14:13 UTC by Corey Welton
Modified: 2019-09-26 13:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-24 17:07:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Corey Welton 2013-10-11 14:13:46 UTC
Description of problem:

We're telling users a sync was successful even if there's no way it could be.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Create a child node from parent but don't actually complete process on child side (i.e., run node-install) -- or assure there's something that causes the install to fail on child.
2.  katello --user admin --password admin node sync --id 1
3. View results.

Actual results:
[root@ibm-x3500m4-01 ~]# katello --user admin --password admin node --help
Usage:  katello options node command
Supported Commands:
	add_environment add an environment
	list           list all known nodes
	remove_environment remove an environment
	sync           Sync a node

Options:
  -h, --help  show this help message and exit
[root@ibm-x3500m4-01 ~]# katello --user admin --password admin node sync --id 1
Sync Complete                   


Expected results:
The text implies that we're performing some sort of sync against child node - but if nothing is taking place and/or if it failed, we shouldn't just say "sync complete".


Additional info:

Comment 2 Justin Sherrill 2013-10-15 13:42:10 UTC
I don't think this is really a 'high' priority, but will take a look.

Comment 3 Brad Buckingham 2013-10-16 12:26:29 UTC
*** Bug 1017921 has been marked as a duplicate of this bug. ***

Comment 4 Brad Buckingham 2013-10-16 12:32:36 UTC
katello-cli pull request: 
https://github.com/Katello/katello-cli/pull/109

The the output should now be similar to the following:

katello> node sync --org ACME_Corporation --environment dev --id 1
Sync of environment [ dev ] completed successfully.

# if the child node was down (e.g. httpd not running on node)
katello> node sync --org ACME_Corporation --environment dev --id 1
Sync of environment [ dev ] failed:[Errno 111] Connection refused

Comment 7 Corey Welton 2013-10-23 19:57:05 UTC
QA Verified in Satellite-6.0.2-RHEL-6-20131021.0

Comment 10 Bryan Kearney 2014-04-24 17:07:52 UTC
This was verified and delivered with MDP2. Closing it out.


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