Project

General

Profile

Actions

Bug #11147

closed

hammer says "Error: 301 Moved Permanently" when you are missing "https://" in server option

Added by Bryan Kearney over 9 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Category:
Foreman commands (obsolete)
Target version:
Difficulty:
Triaged:
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1242488
Description of problem:
Hammer says "Error: 301 Moved Permanently" when you are missing "https://" in server option. It is not user-friendly and I had to bug developer to find that typo.

Version-Release number of selected component (if applicable):
rubygem-hammer_cli-0.1.4.11-1.el6_6sat.noarch

How reproducible:
always

Steps to Reproduce:
1. hammer --server $(hostname) --username admin --password changeme organization create --label 'satellite-qa' --name 'satellite-qa'

Actual results:
  1. hammer --server $(hostname) --username admin --password changeme organization create --label 'satellite-qa' --name 'satellite-qa'
    Could not create the organization:
    Error: 301 Moved Permanently

Expected results:
Some useful error message explaining what is wrong

Additional info:
Running with "https://" is OK:

  1. hammer --server https://$(hostname) --username admin --password changeme organization create --label 'satellite-qa' --name 'satellite-qa'
    Organization created

Related issues 1 (0 open1 closed)

Related to Hammer CLI - Bug #14312: hammer-cli-foreman-0.6.1 misses dependency on apipie-bindings >=0.0.16ClosedTomáš Strachota03/22/2016Actions
Actions

Also available in: Atom PDF