7:26 a.m.
Someone with privs please kick it. Thanks
https://bodhi.fedoraproject.org/updates/FEDORA-2019-995f3ae953
1:16 p.m.
On 9/19/19 5:26 AM, Kaleb Keithley wrote:
Someone with privs please kick it. Thanks
https://bodhi.fedoraproject.org/updates/FEDORA-2019-995f3ae953
Done. Do note that you can do this too, just untag it from f32-pending
and tag it again into f32-pending.
And I am again sorry we don't have this fixed...
kevin
6:33 p.m.
On Thu, Sep 19, 2019 at 2:18 PM Kevin Fenzi <kevin(a)scrye.com> wrote:
On 9/19/19 5:26 AM, Kaleb Keithley wrote:
> Someone with privs please kick it. Thanks
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2019-995f3ae953
Done. Do note that you can do this too, just untag it from f32-pending
and tag it again into f32-pending.
Okay, cool. I wish someone had told me sooner, I'd have stopped bothering
people for this. :-)
Thanks
--
Kaleb
8:07 a.m.
On Thu, Sep 19, 2019 at 7:33 PM Kaleb Keithley <kkeithle(a)redhat.com> wrote:
On Thu, Sep 19, 2019 at 2:18 PM Kevin Fenzi <kevin(a)scrye.com>
wrote:
> On 9/19/19 5:26 AM, Kaleb Keithley wrote:
> > Someone with privs please kick it. Thanks
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-2019-995f3ae953
>
> Done. Do note that you can do this too, just untag it from f32-pending
> and tag it again into f32-pending.
Question: you did it. I did it. In Koji[1] it has f32 and
f32-updates-candidate tags. And in bodhi[2] it's still showing as pending
testing. What should it be? What should I do at this point to get it out of
pending testing and into testing?
[1]https://koji.fedoraproject.org/koji/buildinfo?buildID=1379110
[2]https://bodhi.fedoraproject.org/updates/FEDORA-2019-995f3ae953
Thanks
--
Kaleb
10:33 a.m.
On 9/20/19 6:07 AM, Kaleb Keithley wrote:
On Thu, Sep 19, 2019 at 7:33 PM Kaleb Keithley
<kkeithle(a)redhat.com> wrote:
> On Thu, Sep 19, 2019 at 2:18 PM Kevin Fenzi <kevin(a)scrye.com> wrote:
>
>> On 9/19/19 5:26 AM, Kaleb Keithley wrote:
>>> Someone with privs please kick it. Thanks
>>>
>>> https://bodhi.fedoraproject.org/updates/FEDORA-2019-995f3ae953
>>
>> Done. Do note that you can do this too, just untag it from f32-pending
>> and tag it again into f32-pending.
>
>
Question: you did it. I did it. In Koji[1] it has f32 and
f32-updates-candidate tags. And in bodhi[2] it's still showing as pending
testing. What should it be? What should I do at this point to get it out of
pending testing and into testing?
There is no testing for rawhide.
The f32 tag means it should be in composes.
The issue here is that you created this bodhi update... for rawhide
gating it just does all the work, you should not create updates for
rawhide.
I can see if I can get someone to poke it and make it reflect reality,
but it's already stable and there's nothing further to do (except clean
up what bodhi thinks).
kevin
11:12 a.m.
On Fri, Sep 20, 2019 at 11:41 AM Kevin Fenzi <kevin(a)scrye.com> wrote:
On 9/20/19 6:07 AM, Kaleb Keithley wrote:
> On Thu, Sep 19, 2019 at 7:33 PM Kaleb Keithley <kkeithle(a)redhat.com>
wrote:
>
>> On Thu, Sep 19, 2019 at 2:18 PM Kevin Fenzi <kevin(a)scrye.com> wrote:
>>
>>> On 9/19/19 5:26 AM, Kaleb Keithley wrote:
>>>> Someone with privs please kick it. Thanks
>>>>
>>>> https://bodhi.fedoraproject.org/updates/FEDORA-2019-995f3ae953
>>>
>>> Done. Do note that you can do this too, just untag it from f32-pending
>>> and tag it again into f32-pending.
>>
>>
> Question: you did it. I did it. In Koji[1] it has f32 and
> f32-updates-candidate tags. And in bodhi[2] it's still showing as
pending
> testing. What should it be? What should I do at this point to get it out
of
> pending testing and into testing?
There is no testing for rawhide.
The f32 tag means it should be in composes.
The issue here is that you created this bodhi update... for rawhide
gating it just does all the work, you should not create updates for
rawhide.
I can see if I can get someone to poke it and make it reflect reality,
but it's already stable and there's nothing further to do (except clean
up what bodhi thinks).
Okay. Other builds I've done for f32 (gluster, nfs-ganesha, earlier ceph
builds even) all went straight to stable in bodhi, but this one didn't,
despite waiting several hours.
Then there's the ceph build for f31[1] that's still stuck in pending
testing after two days.
And the ceph build for f30[2] that's been in testing for 15 days that isn't
allowing me push it to stable.
???
Thanks for your help though, greatly appreciated.
Regards,
[1]https://bodhi.fedoraproject.org/updates/FEDORA-2019-62e251afd9
[2]https://bodhi.fedoraproject.org/updates/FEDORA-2019-f47093cc3d
--
Kaleb
3:02 p.m.
On Fri, Sep 20, 2019 at 12:12:58PM -0400, Kaleb Keithley wrote:
Okay. Other builds I've done for f32 (gluster, nfs-ganesha,
earlier ceph
builds even) all went straight to stable in bodhi, but this one didn't,
despite waiting several hours.
Well, all of those likely were autosubmitted by gating? It looks like
you submitted the ceph one manually before the gating could catch it. ;(
https://bodhi.fedoraproject.org/updates/FEDORA-2019-6ebb10dcbc
"This update was automatically created"
https://bodhi.fedoraproject.org/updates/FEDORA-2019-995f3ae953
"This update has been submitted for testing by kkeithle."
I know the folks working on gating were trying to make it so this
happened before anyone could submit a manual update. It would be nice if
it just blocked that entirely.
Then there's the ceph build for f31[1] that's still stuck in
pending
testing after two days.
I got that one unstuck.
And the ceph build for f30[2] that's been in testing for 15 days
that isn't
allowing me push it to stable.
???
I think it's due to it being a critical path update...
Thanks for your help though, greatly appreciated.
Thanks for bringing this stuff up, we need to improve things. ;(
kevin
--
7:32 a.m.
And for https://bodhi.fedoraproject.org/updates/FEDORA-2019-6f79c53e44
I don't have permission to untag and retag the f30-signing-pending tag.
Many thanks for your help.
On Sun, Sep 22, 2019 at 4:02 PM Kevin Fenzi <kevin(a)scrye.com> wrote:
On Fri, Sep 20, 2019 at 12:12:58PM -0400, Kaleb Keithley wrote:
> Okay. Other builds I've done for f32 (gluster, nfs-ganesha, earlier ceph
> builds even) all went straight to stable in bodhi, but this one didn't,
> despite waiting several hours.
Well, all of those likely were autosubmitted by gating? It looks like
you submitted the ceph one manually before the gating could catch it. ;(
https://bodhi.fedoraproject.org/updates/FEDORA-2019-6ebb10dcbc
"This update was automatically created"
https://bodhi.fedoraproject.org/updates/FEDORA-2019-995f3ae953
"This update has been submitted for testing by kkeithle."
I know the folks working on gating were trying to make it so this
happened before anyone could submit a manual update. It would be nice if
it just blocked that entirely.
> Then there's the ceph build for f31[1] that's still stuck in pending
> testing after two days.
I got that one unstuck.
> And the ceph build for f30[2] that's been in testing for 15 days that
isn't
> allowing me push it to stable.
>
> ???
I think it's due to it being a critical path update...
> Thanks for your help though, greatly appreciated.
Thanks for bringing this stuff up, we need to improve things. ;(
kevin
--
>
> Regards,
>
> [1]https://bodhi.fedoraproject.org/updates/FEDORA-2019-62e251afd9
> [2]https://bodhi.fedoraproject.org/updates/FEDORA-2019-f47093cc3d
>
> --
>
> Kaleb
3:42 p.m.
On Wed, Sep 25, 2019 at 08:32:15AM -0400, Kaleb Keithley wrote:
And for
https://bodhi.fedoraproject.org/updates/FEDORA-2019-6f79c53e44
I don't have permission to untag and retag the f30-signing-pending tag.
Many thanks for your help.
ok. Fixed.
I actually already had this on my list. I have been trying to watch the
updates push logs and catch when it warns about an unsigned ceph.
kevin
--
On Sun, Sep 22, 2019 at 4:02 PM Kevin Fenzi <kevin(a)scrye.com> wrote:
> On Fri, Sep 20, 2019 at 12:12:58PM -0400, Kaleb Keithley wrote:
>
> > Okay. Other builds I've done for f32 (gluster, nfs-ganesha, earlier ceph
> > builds even) all went straight to stable in bodhi, but this one didn't,
> > despite waiting several hours.
>
> Well, all of those likely were autosubmitted by gating? It looks like
> you submitted the ceph one manually before the gating could catch it. ;(
> https://bodhi.fedoraproject.org/updates/FEDORA-2019-6ebb10dcbc
> "This update was automatically created"
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2019-995f3ae953
> "This update has been submitted for testing by kkeithle."
>
> I know the folks working on gating were trying to make it so this
> happened before anyone could submit a manual update. It would be nice if
> it just blocked that entirely.
>
> > Then there's the ceph build for f31[1] that's still stuck in pending
> > testing after two days.
>
> I got that one unstuck.
>
> > And the ceph build for f30[2] that's been in testing for 15 days that
> isn't
> > allowing me push it to stable.
> >
> > ???
>
> I think it's due to it being a critical path update...
>
> > Thanks for your help though, greatly appreciated.
>
> Thanks for bringing this stuff up, we need to improve things. ;(
>
> kevin
> --
> >
> > Regards,
> >
> > [1]https://bodhi.fedoraproject.org/updates/FEDORA-2019-62e251afd9
> > [2]https://bodhi.fedoraproject.org/updates/FEDORA-2019-f47093cc3d
> >
> > --
> >
> > Kaleb
>
1673
days inactive
1679
days old
8 comments
2 participants
participants (2)
-
Kaleb Keithley -
Kevin Fenzi