Re: Beta blocker/FE update karma requests

[Stephen Gallagher]

On Tue, 2015-04-14 at 14:40 -0700, Adam Williamson wrote:
>  Hi folks! As some of you know, part of the release validation 
>  process is
>  to make sure the fixes for blocker and freeze exception bugs are 
>  tested
>  and confirmed, and give karma to the updates so they can be pushed to
>  stable.
>  
>  For F22 Beta, the following updates for blocker/FE bugs have been
>  included in Beta RC2, and we need to confirm the fixes and provide
>  karma. It would be great if folks could help with this. Of course not
>  everyone will have the necessary configuration or Cloud accounts or
>  whatever to test every fix, don't worry! Just do whatever you can if 
>  you
>  have some time to help out.
>   

...

>  * 
>  https://admin.fedoraproject.org/updates/FEDORA-2015-5960/realmd-0.15.2-2....
>  
>  This one fixes  https://bugzilla.redhat.com/show_bug.cgi?id=1210483.
>  Testing the blocker fix requires you to have an Active Directory 
>  domain
>  controller available (you'd have to install Fedora 22 Beta RC2 Server
>  and then enrol the newly installed system in the AD domain using 
>  realmd
>  - test cases at
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_22_Beta_RC2_Server#Dom...
>
>  - but if you have a FreeIPA domain you could at least check this 
>  realmd build works OK for enrolling in that domain.
>   
I've been testing this one fairly thoroughly for the last couple days 
(since I've also been working on a (non-security) bug in the SSSD AD 
provider). I'm confident this is working now. It was really a matter 
of a file that realmd needed getting moved to another subpackage 
package of samba, so I fixed the dependency.

I submitted this one for stable this morning on my own judgement (and 
because upstream released a new version to updates-testing and we want 
to make sure the RC2 tree doesn't end up with a different version than 
the stable tree).


>  * 
>  https://admin.fedoraproject.org/updates/FEDORA-2015-4922/rolekit-0.3.2-1....
>  
>  This fixes  https://bugzilla.redhat.com/show_bug.cgi?id=1209602and 
>  also
>   https://bugzilla.redhat.com/show_bug.cgi?id=1207872(an FE bug), both
>  related to deployment of the database 'Server Role'. To test it, 
>  install
>  Fedora 22 Beta RC2 Server (DVD, or if you use the netinst, ensure you
>  get that version of rolekit from updates-testing) and then try to 
>  deploy
>  the database server role...which I can't find any instructions for 
>  ATM,
>  but sgallagh might be able to provide some. Then check you can log 
>  into
>  the deployed pgsql instance with the password from the role config.
>   
== Database Server Role ==
* Install the first instance from a mostly pristine Server install.
* Install additional instance
* Install some instances with the default owner, others with a custom 
one.
* Decommission them in random order.
* Ensure that they can be reached over TCP/IP sockets

Just to clarify, you can create DB Role instances as follows:

 * Create a file something.json with the following contents:

{
    "database": "a_database_name",
    "owner": "an_optional_name",
    "password": "an_optional_owner_password"
}


Then install with:
$ rolectl deploy --settings-file=something.json databaseserver"

See rolekit.roles.databaseserver(5) for all possible options for the 
JSON file and how they work.