Seems like there are multiple issues with the Katello development environment. I wasn’t able to spin one up from staging repos or normally with centos7-katello-devel. Luckily, we have the stable box, but even that needs some tweaking to play nice with all the updates when you git pull (it was published 9 days ago before rails 6 updates).
Here is the only way I can figure out to get a working Katello environment:
vagrant box update centos7-katello-devel-stable is needed if you previously spun up a stable box
In forklift vagrant up centos7-katello-devel-stable
ssh into box and pull latest katello and foreman
update all the things: cd ~/foreman; rm Gemfile.lock && bundle install && bundle exec rake db:migrate && npm install
Can we use this thread to track any updates and discuss blockers? Its seems there is a permanent solution needed for the authorized hosts Rails 6 issue and my understanding is the nightly pipeline contains some fixes that are blocked. Please share any more information or updates as they develop, thanks!
For what it’s worth, I suspect we’ll also run into this in production mode and something the installer should fix for a proper secure env. Since we configure Apache to set a server name + aliases, we have the values for config.hosts but need a SETTING in settings.yaml to configure this.
It seems like this change is what will unblock spinning up a development environment for the koji repos and perhaps some other blockages. The better production fix can be applied to development environment when it is ready.