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.
DescriptionGarik Khachikyan
2012-01-05 11:22:27 UTC
Description of problem:
doing `system update --new-name` command for the registered system through CLI breaks the all facts
And another issue: update of the name works wrong: it gives name for the system "-name" - it does not matter what you specify in --new-name argument.
---
system update --new-name localhost --name <reg.ed-system> --org ACME_Corporation
---
Version-Release number of selected component (if applicable):
katello-0.1.161-1.git.2.b050732.el6.noarch
katello-cli-0.1.32-1.fc16.noarch
candlepin-0.5.8-1.el6.noarch
pulp-0.0.255-1.el6.noarch
How reproducible:
always using CLI
Steps to Reproduce:
1. register a system through RHSM
2. make the system update --new-name call through CLI for that system name
3. refer to UI and look ad the facts of that system (or request system info)
Actual results:
Unable to find a useful facts (like kernel, ip, os, virt. type, etc.)
Expected results:
all the rest of the facts should be untouched, changing only the one requsting by a user.
Additional info:
agree: now it does not break all the existing settings, but it still not work as expected, for updating system name:
katello system update --new-name localhost --name <your-system> --org ACME_Corporation
the result brings system's name to be: "-name"
I think it's worth fixing (or if it's another bug - let me know I'll open a new one).
keeping the status the same - still.
The change is introduced in katello-0.1.168-1.
I've also fixed the problem with success message in katello-cli-0.1.34-1
(commit 47bb6835659310408ae9e624203343fc8507e365)