Bug #22132
Updated by Tomáš Strachota over 6 years ago
*Steps How reproducible: Steps to Reproduce:* Reproduce: 1. Run hammer host info --id <id> against a host 2. There is no compliance status info , unlike the Web UI where we have compliance status of host. *Actual results:* Actual results: No compliance status from hammer info *Expected results:* Expected results: Compliance status should be provided for particular host *Additional info:* Additional info: <pre> hammer> host info --id 3 Id: 3 UUID: <uid> Name: hazel-sagel.xyz.com Organization: Default Organization Location: Default Location Host Group: rhel7_hstgrp Compute Resource: libvirt Compute Profile: 2-Medium Environment: production Puppet CA Id: 1 Puppet Master Id: 1 Cert name: hazel-sagel.xyz.com Managed: yes Installed at: 2016/09/27 11:42:26 Last report: 2016/09/28 06:43:35 Network: IP: 192.168.100.4 MAC: 52:54:00:b8:5b:b6 Subnet: subnet192 Domain: xyz.com Network interfaces: 1) Id: 7 Identifier: eth0 Type: interface (primary, provision) MAC address: 52:54:00:b8:5b:b6 IP address: 192.168.100.4 FQDN: Operating system: Architecture: x86_64 Operating System: RedHat 7.2 Build: no Partition Table: Kickstart default Custom partition table: Parameters: Additional info: Owner Id: 3 Owner Type: User Enabled: yes Model: KVM Comment: Content Information: Content View: rhel7_cv Lifecycle Environment: Dev Applicable Errata: Enhancement: 0 Bug Fix: 0 Security: 0 Subscription Information: UUID: <uid> Last Checkin: 2016-09-28 03:43:28 UTC Service Level: Release Version: Autoheal: true Registered At: 2016-09-27 11:36:45 UTC Registered by Activation Keys: 1) rhel_ak Host Collections: </pre>