You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking to experiment with hammer content-view version export / import. It seems that forklift wants to stand up separate katello-devel and hammer-devel VMs. The bundle exec for hammer content-view version export complained it must be on the local katello host to work. I have subsequently setup a separate vagrant config combining both of the roles as follows:
This appears to have created a working katello-devel with hammer-devel included, however I've run into issues with the vagrant user using content-view version export not having permissions to various files / dirs and running bundle exec as root with sudo doesn't work as it seems the environment isn't setup.
Am I going about this all wrong or is is it something else like perhaps is this a fridge case not covered?
Thanks,
-Jeff
The text was updated successfully, but these errors were encountered:
jeffmcutter
changed the title
content-view version
hammer content-view version export needs to run on katello-devel
Oct 22, 2019
I'm looking to experiment with hammer content-view version export / import. It seems that forklift wants to stand up separate katello-devel and hammer-devel VMs. The bundle exec for hammer content-view version export complained it must be on the local katello host to work. I have subsequently setup a separate vagrant config combining both of the roles as follows:
The playbook appears as follows:
This appears to have created a working katello-devel with hammer-devel included, however I've run into issues with the vagrant user using content-view version export not having permissions to various files / dirs and running bundle exec as root with sudo doesn't work as it seems the environment isn't setup.
Am I going about this all wrong or is is it something else like perhaps is this a fridge case not covered?
Thanks,
-Jeff
The text was updated successfully, but these errors were encountered: