Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
There are few compute resource fields that are not returned when person try to update existing entity:

* provider
* organization
* location

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

How reproducible:
Always

Steps to Reproduce:
1. Issue HTTP PUT request to https://sat.example.com/api/compute_resources/:id
2. Capture the response. Examine the JSON payload and discover that several
   attributes are not mentioned.

Actual results:
See "Description of problem" section.

Expected results:
See "Description of problem" section.

Additional info:

this seems to be by design, and unrelated to compute resources. in Foreman's API, all create/update actions use the "process_response" method which simply runs #to_json on the relevant object and returns it.
Generally, if one wishes to see all the object's attributes, they should use the show API call. create/update actions should actually just return a status, not the object's attributes, which are actually unimportant (the response code tells the user of the status, everything else is unimportant in my opinion)

This is an older bug which I do not envision being fixed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.