Project

General

Profile

Actions
Copy link

Feature #9381

closed

Registering a host (which is not provisioned by foreman) via rhsm should show up in foreman

Added by Thomas McKay almost 10 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Hosts
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
1100284
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1100284
Description of problem:
Currently (with sat6 beta snap5 compose3), if I provisioned a host via foreman and later register it via rhsm.. the host is listed under content host. However on other hand, if I register a host (which is not provisioned by foreman) via rhsm, then it is listed only under content host, not under foreman hosts.

I think for host/system unification, it should be two way.

Version-Release number of selected component (if applicable):
sat6 beta snap5 compose3
  • candlepin-0.9.7-1.el6_5.noarch
  • candlepin-scl-1-5.el6_4.noarch
  • candlepin-scl-quartz-2.1.5-5.el6_4.noarch
  • candlepin-scl-rhino-1.7R3-1.el6_4.noarch
  • candlepin-scl-runtime-1-5.el6_4.noarch
  • candlepin-selinux-0.9.7-1.el6_5.noarch
  • candlepin-tomcat6-0.9.7-1.el6_5.noarch
  • elasticsearch-0.90.10-4.el6sat.noarch
  • foreman-1.6.0.9-1.el6sat.noarch
  • foreman-compute-1.6.0.9-1.el6sat.noarch
  • foreman-gce-1.6.0.9-1.el6sat.noarch
  • foreman-libvirt-1.6.0.9-1.el6sat.noarch
  • foreman-ovirt-1.6.0.9-1.el6sat.noarch
  • foreman-postgresql-1.6.0.9-1.el6sat.noarch
  • foreman-proxy-1.6.0.6-1.el6sat.noarch
  • foreman-selinux-1.6.0-2.el6sat.noarch
  • foreman-vmware-1.6.0.9-1.el6sat.noarch
  • katello-1.5.0-24.el6sat.noarch
  • katello-ca-1.0-1.noarch
  • katello-certs-tools-1.5.5-1.el6sat.noarch
  • katello-installer-0.0.40-1.el6sat.noarch
  • openldap-2.4.23-32.el6_4.1.x86_64
  • pulp-katello-plugins-0.3-1.el6sat.noarch
  • pulp-nodes-common-2.4.0-0.17.beta.el6sat.noarch
  • pulp-nodes-parent-2.4.0-0.17.beta.el6sat.noarch
  • pulp-puppet-plugins-2.4.0-0.17.beta.el6sat.noarch
  • pulp-puppet-tools-2.4.0-0.17.beta.el6sat.noarch
  • pulp-rpm-plugins-2.4.0-0.17.beta.el6sat.noarch
  • pulp-selinux-2.4.0-0.17.beta.el6sat.noarch
  • pulp-server-2.4.0-0.17.beta.el6sat.noarch
  • python-ldap-2.3.10-1.el6.x86_64
  • ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
  • ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch
  • rubygem-hammer_cli-0.1.0-13.el6sat.noarch
  • rubygem-hammer_cli_foreman-0.1.0-13.el6sat.noarch
  • rubygem-hammer_cli_foreman_tasks-0.0.2-6.el6sat.noarch
  • rubygem-hammer_cli_katello-0.0.3-24.el6sat.noarch
apr-util-ldap-1.3.9-3.el6_0.1.x86_64

How reproducible:
always

Steps to Reproduce:
1. register a host (which is not provisioned by foreman) via rhsm
2. host is listed under content hosts but not under foreman host
3.

Actual results:
register a host (which is not provisioned by foreman) via rhsm, then it is listed only under content host, not under foreman hosts.

Expected results:
host should be listed under both sides ( under foreman hosts as well as content-hosts)

Additional info:

Related issues 1 (0 open — 1 closed)

Blocks Katello - Tracker #8161: Host UnificationRejected

Actions
Actions
Copy link
 #1

Updated by Thomas McKay almost 10 years ago

Actions
Copy link
 #2

Updated by Eric Helms almost 10 years ago

  • Translation missing: en.field_release set to 31
Actions
Copy link
 #3

Updated by Eric Helms over 9 years ago

  • Category set to 83
  • Triaged changed from No to Yes
Actions
Copy link
 #4

Updated by Eric Helms over 9 years ago

  • Translation missing: en.field_release deleted (31)
Actions
Copy link
 #5

Updated by Eric Helms about 9 years ago

  • Translation missing: en.field_release set to 114
Actions
Copy link
 #6

Updated by John Mitsch over 5 years ago

  • Status changed from New to Rejected
  • Target version deleted (Katello Backlog)

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Actions
Copy link

Also available in: Atom PDF