Project

General

Profile

Bug #30651

Remote Execution Capsules are not listed when querying the subnet using API and hammer.

Added by Adam Ruzicka almost 2 years ago. Updated almost 2 years ago.


Description

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

Description of problem:
Remote Execution Capsules are not listed when querying the subnet using API and hammer.

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

Steps to Reproduce:

Uses either the following hammer command or API

  1. hammer subnet info --id 1
  2. curl -v -k -u "myusername:mypass" https://mysatellite.example.com/api/subnets/1 | python -m json.tool

Example API output: {
...
"dns_secondary": "",
"domains": [ {
"id": 2,
"name": "example.com"
}
],
"from": "",
"gateway": "xxx.xxx.xxx.xxx",
"httpboot": {
"id": 1,
"name": "mysatellite.example.com",
"url": "https://mysatellite.example.com:9090"
},
"httpboot_id": 1,
"httpboot_name": "mysatellite.example.com",
"id": 1,
"interfaces": [
...
],
"ipam": "None",
"locations": [ {
"description": "",
"id": 2,
"name": "somewhere",
"title": "somewhere"
},
],
...
"organizations": [ {
"description": "",
"id": 1,
"name": "redhat",
"title": "redhat"
},
],
"parameters": [],
"priority": null,
"template": {
"id": 1,
"name": "mysatellite.example.com",
"url": "https://mysatellite.example.com:9090"
},
"template_id": 1,
"template_name": "mysatellite.example.com",
"tftp": {
"id": 1,
"name": "mysatellite.example.com",
"url": "mysatellite.example.com:9090"
},
"tftp_id": 1,
"tftp_name": "mysatellite.example.com",
...
}

Actual results:
Missing Remote execution Capsules

Expected results:
Remote execution Capsules should be listed


Related issues

Related to Foreman - Tracker #27680: API bugs that need workarounds in foreman-ansible-modulesNew

Has duplicate Foreman Remote Execution - Bug #19086: option to add remote execution proxy to a subnet is not shown in apidocDuplicate

Associated revisions

Revision e1c5d282 (diff)
Added by Adam Růžička almost 2 years ago

Fixes #30651 - Expose subnet-rex proxy associations in the API (#527)

Revision 5c418a24 (diff)
Added by Adam Růžička almost 2 years ago

Fixes #30651 - Show REX proxies in subnet info (#33)

History

#1 Updated by The Foreman Bot almost 2 years ago

  • Assignee set to Adam Ruzicka
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/527 added

#2 Updated by The Foreman Bot almost 2 years ago

  • Pull request https://github.com/theforeman/hammer_cli_foreman_remote_execution/pull/33 added

#3 Updated by The Foreman Bot almost 2 years ago

  • Fixed in Releases added

#4 Updated by Anonymous almost 2 years ago

  • Status changed from Ready For Testing to Closed

#5 Updated by Adam Ruzicka almost 2 years ago

  • Subject changed from Remote Execution Capsules are not listed when querying the subnet using API and hammer. to Remote Execution Capsules are not listed when querying the subnet using API and hammer.
  • Fixed in Releases foreman_remote_execution 4.1.0 added
  • Fixed in Releases deleted ()

#6 Updated by The Foreman Bot almost 2 years ago

  • Fixed in Releases hammer_cli_foreman_remote_execution 0.1.2 added

#7 Updated by Evgeni Golov almost 2 years ago

  • Related to Tracker #27680: API bugs that need workarounds in foreman-ansible-modules added

#8 Updated by Adam Ruzicka almost 2 years ago

  • Has duplicate Bug #19086: option to add remote execution proxy to a subnet is not shown in apidoc added

#9 Updated by Adam Ruzicka almost 2 years ago

  • Fixed in Releases hammer_cli_foreman_remote_execution 0.2.0 added
  • Fixed in Releases deleted (hammer_cli_foreman_remote_execution 0.1.2)

Also available in: Atom PDF