Bug #13994

Cannot dis-associate a Subnet from a Domain using Hammer

Added by Brad Buckingham over 1 year ago. Updated 8 months ago.

Status:New
Priority:Normal
Assigned To:-
Category:Other commands
Target version:Foreman - Team Marek backlog
Difficulty: Bugzilla link:1305747
Found in release: Pull request:
Story points-
Velocity based estimate-

Description

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

Description of problem:

Cannot dis-associate a Subnet from a Domain using Hammer.

- Due to which can not delete a Subnet using hammer command

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

Satellite Server v.6.1.6

Steps to Reproduce:

1. Create a Domain and Subnet using hammer command:

  1. hammer domain create --name "test-domain"
    Domain [test-domain] created
  1. hammer subnet create --name "test" --network "x.x.x.x" --mask "255.255.255.0" --domains "test-domain"
    Subnet created

2. Try deleting the subnet and it will fail with the below error :

  1. hammer subnet delete --name "test"
    Could not delete the subnet:
    test (x.x.x.x/24) is used by test-domain
  1. hammer domain delete --name "test-domain"
    Could not delete the domain:
    test-domain is used by test (x.x.x.x/24)

Actual results:

Could not delete the subnet:
test (x.x.x.x/24) is used by test-domain

Expected results:

Subnet Deleted successfully

Additional info:

It is due to the association created between the Subnet and the Domain.

If a Subnet is created without the Domain association, then it is deleted successfully.

Currently we can remove the association manually over the Satellite Server Web UI

--> log in to Satellite --> Infrastructure --> Subnet --> Select the Subnet "test" --> Domains --> Remove the check mark from "test-domain" --> Submit

  1. hammer subnet delete --name "test"

- Below Hammer command does not remove the association using hammer command:

  1. hammer subnet update --domains "" --name "test" ---> Rather it associates the Subnet with all the Domain's.

Related issues

Related to Hammer CLI - Bug #17252: Unable to set empty parameter via hammer New 11/07/2016

History

#1 Updated by Dominic Cleal over 1 year ago

  • Project changed from Foreman to Hammer CLI
  • Category set to Foreman commands

hammer subnet update --domain-ids '' works fine.

#2 Updated by Tomáš Strachota 8 months ago

  • Category changed from Foreman commands to Other commands
  • Target version set to Team Marek backlog

#3 Updated by Tomáš Strachota 8 months ago

  • Related to Bug #17252: Unable to set empty parameter via hammer added

#4 Updated by Tomáš Strachota 8 months ago

  • Description updated (diff)

#5 Updated by Tomáš Strachota 8 months ago

Re-tested with

hammer-cli[-foreman] 0.8.0
foreman 1.13.0

and the issue is still there.

Also available in: Atom PDF