#7803 Greenwave in stg is talking to production koji
Closed: Fixed a year ago by gnaponie. Opened a year ago by bowlofeggs.

The Greenwave deployment in staging is talking to production Koji, which means we can't meaningfully test Bodhi:

$ curl 'https://greenwave-web-greenwave.app.os.stg.fedoraproject.org/api/v1.0/decision' -H 'User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0' -H 'Accept: */*' -H 'Accept-Language: en-US,en;q=0.5' --compressed -H 'Content-Type: application/json' -H 'Origin: https://bodhi.stg.fedoraproject.org' -H 'DNT: 1' -H 'Connection: keep-alive' -H 'Cache-Control: max-age=0' --data '{"product_version":"fedora-29","decision_context":"bodhi_update_push_testing","subject":[{"item":"python-rpdb-0.1.6-18.fc29","type":"koji_build"},{"original_spec_nvr":"python-rpdb-0.1.6-18.fc29"},{"item":"FEDORA-2019-f79bd591e7","type":"bodhi_update"}],"verbose":true}'
{"message":"Failed to find Koji build for \"python-rpdb-0.1.6-18.fc29\" at \"https://koji.fedoraproject.org/kojihub\""}

Bodhi in staging must be tested with builds made in stg because composes in staging fail with builds from production. Furthermore, we won't be able to test waivers in staging if Greenwave is using production data because we obviously don't want to make production waivers to test staging, and we do want to create waivers in staging.

Hello, there's a comment in the code about it:

# We are using prod koji in staging since resultsdb results comes from the production environment.

I'm not familiar with it, but it looks like greenwave won't quite work since it won't find results from resultsdb since that one uses prod info.
But I can make the change if that's an issue.
I'm on it right now.

Metadata Update from @gnaponie:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Metadata Update from @gnaponie:
- Issue assigned to gnaponie

a year ago

Login to comment on this ticket.