[Self-scheduling API] Owner mismatch

[josecastillolema]

Describe the bug
After creating a self scheduling assignment (step 6) and the corresponding schedule (step 7) following the Self scheduling manual QA document:

> curl -k -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" -d '{"description": "Short description here", "owner": "tester", "qinq": 1, "vlan": "619", "wipe": "true"}' http://quads2-stage.rdu2.scalelab.redhat.com/api/v3/assignments/self
{
  "active": null,
  "ccuser": null,
  "cloud": {
    "id": 2,
    "last_redefined": "Tue, 26 Nov 2024 19:05:00 GMT",
    "name": "cloud02"
  },
  "cloud_id": 2,
  "created_at": null,
  "description": "Short description here",
  "id": null,
  "is_self_schedule": true,
  "notification": {
    "assignment_id": null,
    "fail": null,
    "five_days": null,
    "id": null,
    "initial": null,
    "one_day": null,
    "pre": null,
    "pre_initial": null,
    "seven_days": null,
    "success": null,
    "three_days": null
  },
  "ostype": "RHEL 8.6",
  "owner": "tester",
  "provisioned": null,
  "qinq": 1,
  "ticket": "4034",
  "validated": null,
  "vlan": {
    "gateway": "",
    "id": 1,
    "ip_free": 62,
    "ip_range": "",
    "netmask": "",
    "vlan_id": 619
  },
  "vlan_id": 1,
  "wipe": "true"
}

> curl -k -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" -d '{"cloud":"cloud02", "hostname": "e22-h26-b01-fc640.stage.rdu2.scalelab.redhat.com"}' http://quads2-stage.rdu2.scalelab.redhat.com/api/v3/schedules
{"assignment":{"active":true,"ccuser":[],"cloud":{"id":2,"last_redefined":"Tue, 26 Nov 2024 19:05:00 GMT","name":"cloud02"},"cloud_id":2,"created_at":"Wed, 15 Jan 2025 11:00:22 GMT","description":"Short description here","id":51,"is_self_schedule":true,"notification":{"assignment_id":51,"fail":false,"five_days":false,"id":51,"initial":false,"one_day":false,"pre":false,"pre_initial":true,"seven_days":false,"success":false,"three_days":false},"ostype":null,"owner":"athiruma_tes","provisioned":true,"qinq":null,"ticket":null,"validated":false,"vlan_id":null,"wipe":false},"assignment_id":51,"build_end":null,"build_start":null,"created_at":"Sun, 02 Feb 2025 17:10:56 GMT","end":"Fri, 07 Feb 2025 17:10:56 GMT","host":{"blade":null,"broken":false,"build":true,"can_self_schedule":true,"cloud":{"id":1,"last_redefined":"Tue, 30 Apr 2024 12:07:05 GMT","name":"cloud01"},"cloud_id":1,"created_at":"Fri, 31 May 2024 13:27:16 GMT","default_cloud":{"id":1,"last_redefined":"Tue, 30 Apr 2024 12:07:05 GMT","name":"cloud01"},"default_cloud_id":1,"disks":[{"count":1,"disk_type":"sata","host_id":26,"id":12,"size_gb":480}],"host_type":"vendor","id":26,"interfaces":[{"bios_id":null,"host_id":26,"id":41,"mac_address":"","maintenance":false,"name":"em1","pxe_boot":false,"speed":10,"switch_ip":"10.1.34.204","switch_port":"xe-0/0/11:0","vendor":"Intel Corporation"},{"bios_id":null,"host_id":26,"id":42,"mac_address":"","maintenance":false,"name":"em2","pxe_boot":true,"speed":1,"switch_ip":"","switch_port":"et-0/0/27:2","vendor":"Intel Corporation"},{"bios_id":null,"host_id":26,"id":43,"mac_address":"","maintenance":false,"name":"em3","pxe_boot":false,"speed":1,"switch_ip":"","switch_port":"et-0/0/27:3","vendor":"Intel Corporation"}],"last_build":"Sun, 12 Jan 2025 09:35:00 GMT","model":"FC640","name":"e22-h26-b01-fc640.stage.rdu2.scalelab.redhat.com","rack":null,"retired":false,"switch_config_applied":true,"uloc":null,"validated":false},"host_id":26,"id":303,"start":"Sun, 02 Feb 2025 17:10:56 GMT"}

This is what we observe in the summary of the RDU2 scale lab stage allocations:

NAME	SUMMARY	OWNER	REQUEST	STATUS	OSPENV	OCPINV
[cloud02](https://quads2-stage.rdu2.scalelab.redhat.com/assignments#cloud02)	2 (Short description here)	athiruma_tes		100%	[download](http://quads2-stage.rdu2.scalelab.redhat.com/instack/cloud02_instackenv.json)	[download](http://quads2-stage.rdu2.scalelab.redhat.com/instack/cloud02_ocpinventory.json)

As you can see the owner of the cloud is set to athiruma_tes instead of tester.

[josecastillolema]

Probably related to this issue we are unable to terminate the assignment (step 8):

> curl -k -X POST -H "Authorization: Bearer $TOKEN" http://quads2-stage.rdu2.scalelab.redhat.com/api/v3/assignments/terminate/51
{"error":"Forbidden","message":"You(tester) don't have permission to terminate this assignment(athiruma_tes)","status_code":403}

[grafuls]

Issue addressed here:
https://review.gerrithub.io/c/redhat-performance/quads/+/1208231