[atomic-wg] Issue #441: get autocloud testing F28 media

[Dusty Mabe]

dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
right now I don't see [autocloud](https://apps.fedoraproject.org/autocloud/) testing
F28 media. let's figure out why this is so we can get some test results for f28 if
possible. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/441

[Dusty Mabe]

The status of the issue: `get autocloud testing F28 media` of project: `atomic-wg` has
been updated to: Closed by dustymabe.

https://pagure.io/atomic-wg/issue/441

[Dusty Mabe]

The status of the issue: `get autocloud testing F28 media` of project: `atomic-wg` has
been updated to: Open by dustymabe.

https://pagure.io/atomic-wg/issue/441

[Kushal Das]

kushal added a new comment to an issue you are following:
``
This must be due to the name change in the fedmsg(s) (as discussed in the IRC channel).
The code which fires up the jobs is here:
https://github.com/kushaldas/autocloud/blob/develop/autocloud/consumer.py 

This has to be patched accordingly. @sayanchowdhury may have more details.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/441

[Sayan Chowdhury]

sayanchowdhury added a new comment to an issue you are following:
``
The fedimg patch needs to be ported here too. Can we have a SOP setup for this kind of
changes? Both fedimg and autocloud has faced issues in the past also because of the sudden
changes to the compose messages. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/441

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
>  Can we have a SOP setup for this kind of changes?
>  
Maybe @sinnykumari and @sayanchowdhury can work out an SOP for this with help from me on
the atomic/releng side? 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/441

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
so I see that autocloud now shows f28 runs but they are all queued and don't seem to
be completing.. Does anybody know why that is? 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/441

[Sayan Chowdhury]

sayanchowdhury added a new comment to an issue you are following:
``
Yes, there was a issue with the code. There is a PR[1] for the issue. `0.8.0` should have
the fix for the issue.

[1] https://github.com/kushaldas/autocloud/pull/62
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/441

[Sayan Chowdhury]

sayanchowdhury added a new comment to an issue you are following:
``
autocloud-0.8.0 has been deployed to production.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/441

[Sinny Kumari]

sinnykumari added a new comment to an issue you are following:
``
>  autocloud-0.8.0 has been deployed to production.
>  
Awesome, thanks!
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/441

[Sinny Kumari]

The status of the issue: `get autocloud testing F28 media` of project: `atomic-wg` has
been updated to: Closed as Fixed by sinnykumari.

https://pagure.io/atomic-wg/issue/441

[Sinny Kumari]

sinnykumari added a new comment to an issue you are following:
``
We have autocloud tests running for F28 and rawhide compose. Closing this ticket.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/441