Don't require Kerberos cache since we can't even use stage Koji to build modules anymore

This commit is contained in:
mprahl
2017-11-10 09:51:37 -05:00
parent c33a22fd8b
commit 0a1c270ff8
3 changed files with 1 additions and 22 deletions

4
Vagrantfile vendored
View File

@@ -3,8 +3,7 @@
$script = <<SCRIPT
grep -q '^127\.0\.0\.1 fedmsg-relay$' /etc/hosts || echo "127.0.0.1 fedmsg-relay" >> /etc/hosts
echo "export KRB5CCNAME=FILE:/var/tmp/krbcc" > /etc/profile.d/module_build_service_developer_env.sh
echo "export MODULE_BUILD_SERVICE_DEVELOPER_ENV=1" >> /etc/profile.d/module_build_service_developer_env.sh
echo "export MODULE_BUILD_SERVICE_DEVELOPER_ENV=1" > /etc/profile.d/module_build_service_developer_env.sh
source /etc/profile.d/module_build_service_developer_env.sh
dnf install -y \
fedmsg-hub \
@@ -52,7 +51,6 @@ Vagrant.configure("2") do |config|
config.vm.synced_folder "./", "/tmp/module_build_service"
# Disable the default share
config.vm.synced_folder ".", "/vagrant", disabled: true
config.vm.provision "file", source: "/tmp/mbs-krbcc", destination: "/var/tmp/krbcc", run: "always"
config.vm.network "forwarded_port", guest_ip: "0.0.0.0", guest: 5000, host: 5000
config.vm.network "forwarded_port", guest_ip: "0.0.0.0", guest: 2001, host: 5001
config.vm.network "forwarded_port", guest_ip: "0.0.0.0", guest: 13747, host: 13747

View File

@@ -29,16 +29,8 @@ services:
command: bash -c "while [ ! -f /etc/module-build-service/.ready ] ; do sleep 1 ; done ; fedmsg-hub"
links:
- fedmsg-relay
environment:
# Check /var/tmp/krbcc and make sure that it is not a directory. If it
# is, then delete it with 'sudo rm -rf /var/tmp/krbcc'.
# Initialize the file before running 'docker-compose up' with:
# $ KRB5CCNAME=FILE:/var/tmp/krbcc kinit YOUR_USERNAME@FEDORAPROJECT.ORG
- KRB5CCNAME=FILE:/var/tmp/krbcc
volumes_from:
- base
volumes:
- /tmp/mbs-krbcc:/var/tmp/krbcc:Z
frontend:
depends_on:

View File

@@ -53,17 +53,6 @@ refer to the `Running Tests` section first.
We have two mechanisms for quickly setting up a development environment,
`docker-compose` and `vagrant`.
In order to to setup a development environment, it is required that you have
your Fedora kerberos credentials generated in a *special location*. Before
starting your development environment, run the following::
$ KRB5CCNAME=FILE:/tmp/mbs-krbcc kinit YOUR_USERNAME@STG.FEDORAPROJECT.ORG
If you have problems in later steps with kerberos reading those credentials
inside the `scheduler` container, you should check that `/var/tmp/krbcc` exists
on your machine and that *it is not a directory*. Try removing it with `$ sudo
rm -rf /var/tmp/krbcc` and running `kinit` again. Also, check for permissions
and SELinux context of the credentials cache file.
PDC and pdc-updater
-------------------