Merge #339 Have the Kerberos ticket be located at /tmp/mbs-krbcc instead of /var/tmp/krbcc

This commit is contained in:
Ralph Bean
2017-02-20 13:50:13 +00:00
3 changed files with 3 additions and 3 deletions

2
Vagrantfile vendored
View File

@@ -49,7 +49,7 @@ SCRIPT_SERVICES
Vagrant.configure("2") do |config|
config.vm.box = "fedora/24-cloud-base"
config.vm.synced_folder "./", "/tmp/module_build_service"
config.vm.provision "file", source: "/var/tmp/krbcc", destination: "/var/tmp/krbcc", run: "always"
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

@@ -38,7 +38,7 @@ services:
volumes_from:
- base
volumes:
- /var/tmp/krbcc:/var/tmp/krbcc:Z
- /tmp/mbs-krbcc:/var/tmp/krbcc:Z
frontend:
depends_on:

View File

@@ -8,7 +8,7 @@ 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:/var/tmp/krbcc kinit YOUR_USERNAME@STG.FEDORAPROJECT.ORG
$ 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