3.4. CLI Issues

This section describes known issues with the CLI component of Satellite 6.1.
BZ 1190902: hammer content upload can be very slow
Issue

When you upload packages to a repository the process can be very slow, and the hammer process can take 100% of CPU resources. No progress is indicated, which means that you cannot determine the status of the task without checking log files.

Workaround

None at this time. See the Bugzilla report for more detailed information.

BZ 1177570: "hammer host create" command using a MAC results in "mac value is blank"
Issue

If you try to create a new host using the hammer host create command, it can fail with the error message "mac value is blank," even if a MAC value is provided. For example: 

# hammer -d host create --architecture-id 1 --domain-id 1 --environment-id 3 --hostgroup-id 3 --medium-id 7 --mac 64:54:01:12:64:45 --name example-host [...]
  [ERROR 2014-12-23 11:50:02 Exception] mac value is blank!
Could not create the host:
mac value is blank!
Workaround

The error message for this issue is incorrect. You do not need to specify a MAC address because it gets updated after the VM is created. However, you do need to specify a value for either compute_attributes or compute_profile_id. See the Bugzilla report for more detailed information.

BZ 1230153: Cannot list available repositories in repository set using hammer
Issue

If you try to list available repositories using the hammer repository-set available-repositories command, and use the --product option to specify the product name, the command fails. For example: 

# hammer -v -u admin -p changeme --output=csv repository-set available-repositories --product="Red Hat Enterprise Linux Server" --name="Red Hat Enterprise Virtualization Agents for RHEL 6 Server (RPMs)" --organization-id="302"
[ERROR 2015-06-07 22:37:26 Exception] Error: product not found
Workaround

Use the --product-id option and specify the product ID.

BZ 1221122: "hammer content-view remove version" output is misleading
Issue

If you run the hammer content-view remove-version command, it returns The component version has been removed, but the versions might still be visible in the web UI.

Workaround

None required. Content View version removal is an asynchronous task. The versions have actually been scheduled for removal, and will be removed in due course. A more accurate output message is planned for a later release.

BZ 1180282: CLI does not display product enablement
Issue

In the CLI, you can perform a content-override on a product in an activation key. However, there is currently no way to view the enablement of a product in the CLI.

BZ 1230884: Hammer role filter does work with ID but not with name
Issue

If you attempt to assign permissions to a role, using the roles' names, you might see the following error message: 

Could not create the permission filter:
  Permissions Permissions must be of same resource type
Workaround

Specify the roles by their unique identifiers. For example: 

$ hammer filter create --permission-ids 115,116,117,118,119 --role dhtest
Permission filter for [Puppetclass] created
To list available roles and their identifiers, use the following command: 
hammer filter available-permissions
BZ 1236193: hammer repository-set available-repositories shows disabled when the repository is enabled
Issue

The Hammer command hammer repository-set available-repositories lists repositories as being disabled when in fact they are enabled.

The following example command lists all available repositories: 
# hammer --csv repository-set available-repositories --product "$product" --name "$set" --organization-id $ORG_ID
Name,Arch,Release,Enabled
Red Hat Satellite Capsule 6 Beta for RHEL 6 Server RPMs i386,i386,,false
Red Hat Satellite Capsule 6 Beta for RHEL 6 Server RPMs x86_64,x86_64,,false
Each of them are listed as not enabled, however the following Hammer command attempts to enable the x86_64 repository, but fails because it is already enabled. 
# hammer  repository-set enable --product "$product" --organization-id $ORG_ID  --name "$set" --releasever "" --basearch x86_64
Could not enable repository:
  Error: 409 Conflict
Workaround

No workaround is available for the CLI. The only other option is to use the web user interface for this operation.

BZ 1238458: Hammer ping output has no response for pulp_auth only on providing wrong credentials
Issue

The pulp_auth service does not provide a response to the Hammer ping command if incorrect credentials are provided.

The following example illustrates the output provided when the ping command is run with invalid credentials. 
# hammer ping
[Foreman] Username: admin
[Foreman] Password for admin: wrongPasswd
candlepin:
   Status:          ok
   Server Response: Duration: 18ms
candlepin_auth:
   Status:          ok
   Server Response: Duration: 20ms
pulp:
   Status:          ok
   Server Response: Duration: 18ms
pulp_auth:
   Status:
   Server Response: Message:
elasticsearch:
   Status:          ok
   Server Response: Duration: 10ms
foreman_tasks:
   Status:          ok
   Server Response: Duration: 1ms
Workaround

None at this time.