Red Hat Bugzilla – Bug 1380117
content hosts show no info under "registered by" in 6.2.x
Last modified: 2017-09-25 14:59:44 EDT
Created attachment 1205589 [details] screen shot of the empty registered by Description of problem: In satellite 6.1.9 and below when clicking on a content host and looking at the "registered by" column you could see what user registered it or what activation key was used to register it. Now on 6.2.x this column still exists but only does it show any info if an activation key registers the system. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. register a new client ( or look at your old clients) in the webui under content hosts 2. do not use an activation key 3. attach a sub Actual results: registered by shows no info Expected results: registered by should show information if its registered by an activation key or not. Looks like a regression from 6.1.9 Additional info: screen shot attached. looks like its missing from here. /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.78/engines/bastion_katello/app/assets/javascripts/bastion_katello/content-hosts/details/views/content-host-info.html 266 <section> 267 <h4 translate>Content Host Status</h4> 268 269 <div class="detail"> 270 <span class="info-label" translate>Registered</span> 271 <span class="info-value">{{ host.created | date:'short' }}</span> 272 </div> 273 274 <div class="detail"> 275 <span class="info-label" translate> Registered By</span> 276 <span class="info-value" 277 translate 278 ng-show="host.subscription_facet_attributes.activation_keys.length == 0"> 279 {{ contentHost.registered_by }} 280 </span> 281 <span class="info-value" 282 ng-show="host.subscription_facet_attributes.activation_keys.length > 0" 283 translate 284 translate-n="host.subscription_facet_attributes.activation_keys.length" 285 translate-plural="Activation Keys"> 286 Activation Key 287 </span> 288 <span class="info-value"> 289 <ul ng-show="host.subscription_facet_attributes.activation_keys.length > 0"> 290 <li ng-repeat="activation_key in host.subscription_facet_attributes.activation_keys"> 291 <span> 292 <a ui-sref="activation-keys.details.info({activationKeyId: activation_key.id})"> 293 {{ activation_key.name }} 294 </a> 295 </span> 296 <span ng-show="activation_key.description"> - {{ activation_key.description }}</span> 297 </li> 298 </ul> 299 </span> 300 </div> 301 302 <div class="detail"> 303 <span class="info-label" translate>Last Checkin</span> 304 <span class="info-value">{{ (host.subscription_facet_attributes.last_checkin | date:'short') || ("Never checked in" | translate) }}</span> 305 </div> 306
Created redmine issue http://projects.theforeman.org/issues/16780 from this bug
Upstream Katello PR : https://github.com/Katello/katello/pull/6387
*** Bug 1431231 has been marked as a duplicate of this bug. ***
Looking at the upstream patch, I'd actually say that it does not completely fix the regression. In 6.1 the column would have * the username, if the the host was registered by a user * the UUID of the submitting host, if the host was submitted by another one, like it happens in the virt-who case The first is fixed by the patch, but the second (which is more interesting for me, personally) is not :(
Verified in Satellite 6.3 Snap 10. The content hosts now correctly show what activation key they were registered with. See attached screenshot for verification.
I believe the fix for this BZ is causing a regression described in: https://bugzilla.redhat.com/show_bug.cgi?id=1485942 can you confirm?
Roman, good catch. It did and it was solved upstream with http://projects.theforeman.org/issues/17128. I am linking that issue to bug 1485942 and we'll get it pulled in.
Verified in Satellite 6.2.12 Snap 1. The registered by functionality is back in place. Also, it correctly links to the appropriate activation key. See attached screenshot for verification.
Created attachment 1319197 [details] verification screenshot
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/RHBA-2017:2803