Project

General

Profile

Actions

Bug #31384

closed

hammer os list fails with default organization set

Added by yifat makias about 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1649011

Description of problem:
When a default organization is set `hammer os list` returns "Association not found for organization. Removing the organization default results in the OS list returning.

Version-Release number of selected component (if applicable): 6.4.0-15

How reproducible:
Always

Steps to Reproduce:
1. Execute `hammer defaults add --param-name organization_id --param-value 1
2. Execute `hammer os list`

Actual results:
Command returns with "Association not found for organization"

Expected results:
List of operating systems:
ID,TITLE,RELEASE NAME,FAMILY
1,RedHat 7.4,,Redhat

Additional info:
The expected result is returned if the default organization id is removed; however, this results in a change in behavior from 6.2.15, the previous release we used. Alternatively, if there is an argument to pass to hammer to either specify an organization-id of null or to ignore defaults.yml, it would allow us to avoid significantly rewriting our deployment automation.


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #32695: API has inconsistent behavior with taxable parametersClosedyifat makiasActions
Actions

Also available in: Atom PDF