Re: FBR: Signing f27-u-t ostrees

2017-10-31 Thread Pierre-Yves Chibon 
On Tue, Oct 31, 2017 at 12:53:09PM +0100, Patrick Uiterwijk wrote:
> Hi,
> 
> The Atomic SIG really wants the F27 atomic tree refs to be created,
> which only happens if robosignatory signs them.
> Could I get +1/-1s for the underneath patch?
> 
> Patrick
> 
> 
> commit dfbd764b0ce16b9c4df190801bdc32a9e9b9b985 (HEAD -> master)
> Author: Patrick Uiterwijk 
> Date:   Tue Oct 31 12:51:44 2017 +0100
> 
> Enable signing of f27-u-t ostrees
> 
> Signed-off-by: Patrick Uiterwijk 
> 
> diff --git a/roles/robosignatory/files/robosignatory.production.py
> b/roles/robosignatory/files/robosignatory.production.py
> index 66a9ef674..bae63c46c 100644
> --- a/roles/robosignatory/files/robosignatory.production.py
> +++ b/roles/robosignatory/files/robosignatory.production.py
> @@ -179,6 +179,10 @@ config = {
>  'directory': '/mnt/fedora_koji/koji/compose/ostree/27/',
>  'key': 'fedora-27'
>  },
> +'fedora/27/x86_64/testing/atomic-host': {
> +'directory': '/mnt/fedora_koji/koji/compose/updates/atomic/',
> +'key': 'fedora-27'
> +},
>  'fedora/rawhide/x86_64/atomic-host': {
>  'directory': '/mnt/fedora_koji/koji/compose/atomic/rawhide/',
>  'key': 'fedora-28'

Looks simple enough for me, +1


Pierre


signature.asc
Description: PGP signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: Signing f27-u-t ostrees

2017-10-31 Thread Dusty Mabe 


On 10/31/2017 07:53 AM, Patrick Uiterwijk wrote:
> Hi,
> 
> The Atomic SIG really wants the F27 atomic tree refs to be created,
> which only happens if robosignatory signs them.
> Could I get +1/-1s for the underneath patch?
> 
> Patrick
> 
> 
> commit dfbd764b0ce16b9c4df190801bdc32a9e9b9b985 (HEAD -> master)
> Author: Patrick Uiterwijk 
> Date:   Tue Oct 31 12:51:44 2017 +0100
> 
> Enable signing of f27-u-t ostrees
> 
> Signed-off-by: Patrick Uiterwijk 
> 
> diff --git a/roles/robosignatory/files/robosignatory.production.py
> b/roles/robosignatory/files/robosignatory.production.py
> index 66a9ef674..bae63c46c 100644
> --- a/roles/robosignatory/files/robosignatory.production.py
> +++ b/roles/robosignatory/files/robosignatory.production.py
> @@ -179,6 +179,10 @@ config = {
>  'directory': '/mnt/fedora_koji/koji/compose/ostree/27/',
>  'key': 'fedora-27'
>  },
> +'fedora/27/x86_64/testing/atomic-host': {
> +'directory': '/mnt/fedora_koji/koji/compose/updates/atomic/',
> +'key': 'fedora-27'
> +},
>  'fedora/rawhide/x86_64/atomic-host': {
>  'directory': '/mnt/fedora_koji/koji/compose/atomic/rawhide/',
>  'key': 'fedora-28'

LGTM - +1 :)

/me is going to pretend like I matter until I do matter

#fakeittilyoumakeit
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Freeze Break Request: update rpm on builders

2017-10-31 Thread Mohan Boddu 
+1 if its not going to affect on our f27 final or f27 modular server beta 
releases. Having rollback will help us getting back to the previous rpm version 
so I think its okay.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: Signing f27-u-t ostrees

2017-10-31 Thread Kevin Fenzi 
+1

kevin




signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Freeze Break Request: fix purge-ami's cron

2017-10-31 Thread Kevin Fenzi 
Greetings. 

I happened to notice some cron output a while back and looked into it and found 
a slight mistake in the purge-ami's cron. 

'git clone -n' was being used which tells it to not bother checking out HEAD 
after the clone. Just leave the checkout empty. Then it tries to run things 
from the checkout that just fails. :) 

The solution is just to drop the -n I think, but I'd love to have sayan 
confirm. 

kevin
--
diff --git a/roles/releng/files/purge-amis b/roles/releng/files/purge-amis
index b49942a..be677e5 100644
--- a/roles/releng/files/purge-amis
+++ b/roles/releng/files/purge-amis
@@ -1,5 +1,5 @@
 # Remove launch permissions from the AMIs after every 5 days
-0 0 */5 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XX` && pushd $TMPDIR && 
git clone -n https://pagure.io/releng.git && cd releng/scripts && 
AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ 
ec2_image_delete_access_key }} ./clean-amis.py --change-perms && popd && rm -rf 
$TMPDIR
+0 0 */5 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XX` && pushd $TMPDIR && 
git clone https://pagure.io/releng.git && cd releng/scripts && 
AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ 
ec2_image_delete_access_key }} ./clean-amis.py --change-perms && popd && rm -rf 
$TMPDIR
 
 # Delete the AMIs after every 10 days.
-0 0 */10 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XX` && pushd $TMPDIR && 
git clone -n https://pagure.io/releng.git && cd releng/scripts && 
AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ 
ec2_image_delete_access_key }} ./clean-amis.py --delete && popd && rm -rf 
$TMPDIR
+0 0 */10 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XX` && pushd $TMPDIR && 
git clone https://pagure.io/releng.git && cd releng/scripts && 
AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ 
ec2_image_delete_access_key }} ./clean-amis.py --delete && popd && rm -rf 
$TMPDIR



signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Freeze Break Request: fix purge-ami's cron

2017-10-31 Thread Patrick Uiterwijk 
On Wed, Nov 1, 2017 at 12:10 AM, Kevin Fenzi  wrote:
> Greetings.
>
> I happened to notice some cron output a while back and looked into it and 
> found a slight mistake in the purge-ami's cron.
>
> 'git clone -n' was being used which tells it to not bother checking out HEAD 
> after the clone. Just leave the checkout empty. Then it tries to run things 
> from the checkout that just fails. :)
>
> The solution is just to drop the -n I think, but I'd love to have sayan 
> confirm.

+1 from me, looks like you're right on this one.

>
> kevin
> --
> diff --git a/roles/releng/files/purge-amis b/roles/releng/files/purge-amis
> index b49942a..be677e5 100644
> --- a/roles/releng/files/purge-amis
> +++ b/roles/releng/files/purge-amis
> @@ -1,5 +1,5 @@
>  # Remove launch permissions from the AMIs after every 5 days
> -0 0 */5 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XX` && pushd $TMPDIR 
> && git clone -n https://pagure.io/releng.git && cd releng/scripts && 
> AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ 
> ec2_image_delete_access_key }} ./clean-amis.py --change-perms && popd && rm 
> -rf $TMPDIR
> +0 0 */5 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XX` && pushd $TMPDIR 
> && git clone https://pagure.io/releng.git && cd releng/scripts && 
> AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ 
> ec2_image_delete_access_key }} ./clean-amis.py --change-perms && popd && rm 
> -rf $TMPDIR
>
>  # Delete the AMIs after every 10 days.
> -0 0 */10 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XX` && pushd $TMPDIR 
> && git clone -n https://pagure.io/releng.git && cd releng/scripts && 
> AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ 
> ec2_image_delete_access_key }} ./clean-amis.py --delete && popd && rm -rf 
> $TMPDIR
> +0 0 */10 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XX` && pushd $TMPDIR 
> && git clone https://pagure.io/releng.git && cd releng/scripts && 
> AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ 
> ec2_image_delete_access_key }} ./clean-amis.py --delete && popd && rm -rf 
> $TMPDIR
>
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
>
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

FBR: Signing f27-u-t ostrees

2017-10-31 Thread Patrick Uiterwijk 
Hi,

The Atomic SIG really wants the F27 atomic tree refs to be created,
which only happens if robosignatory signs them.
Could I get +1/-1s for the underneath patch?

Patrick


commit dfbd764b0ce16b9c4df190801bdc32a9e9b9b985 (HEAD -> master)
Author: Patrick Uiterwijk 
Date:   Tue Oct 31 12:51:44 2017 +0100

Enable signing of f27-u-t ostrees

Signed-off-by: Patrick Uiterwijk 

diff --git a/roles/robosignatory/files/robosignatory.production.py
b/roles/robosignatory/files/robosignatory.production.py
index 66a9ef674..bae63c46c 100644
--- a/roles/robosignatory/files/robosignatory.production.py
+++ b/roles/robosignatory/files/robosignatory.production.py
@@ -179,6 +179,10 @@ config = {
 'directory': '/mnt/fedora_koji/koji/compose/ostree/27/',
 'key': 'fedora-27'
 },
+'fedora/27/x86_64/testing/atomic-host': {
+'directory': '/mnt/fedora_koji/koji/compose/updates/atomic/',
+'key': 'fedora-27'
+},
 'fedora/rawhide/x86_64/atomic-host': {
 'directory': '/mnt/fedora_koji/koji/compose/atomic/rawhide/',
 'key': 'fedora-28'
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org