pungi

#1092 ostree_ref doesn't seem to work when yaml config is used
Closed: Fixed Opened by dustymabe.

Closed: Fixed
Reopen Issue

I recently switched the fedora 29 silverblue configs to use yaml. Since that point I believe the composes have been using the ref from the manifest rather than the specified refs in the pungi configs.

I think there is an interaction that is failing since the change to yaml that is causing the ostree_ref to not get used. We did not convert the atomic host config to yaml and it is behaving as expected.

Here are some more evidence of brokenness: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/RJ2OCWDD6KDEEQXI5B2R2GOLGYMNP3G7/

I proposed a workaround for us to use until this gets fixed: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/LGL6LPHSOPNKQUWGYHGZVSDOX466WHFH/

I think the problem is that the message to fedmsg contains the wrong ref:
2018-12-04 03:43:37 [DEBUG ] Notification: '/usr/bin/pungi-fedmsg-notification' 'ostree', {'variant': 'Everything', 'arch': 'x86_64', 'ref': 'fedora/29/x86_64/silverblue', 'commitid': '33b20cd7f31286861c7f7cdd78fe6211d76f2a1683141ed78290bc990ce64a52', …}

Proposed fix in PR#1093.

thanks @lsedlar

Commit 5f6dcb37 fixes this issue

Metadata Update from @lsedlar:
- Issue set to the milestone: 4.1.32

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/pungi/pungi/issues/1092

Please continue any further discussion there.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.