Closed dgoetz closed 1 year ago
Not sure what exactly is happening here, but I suppose that foreman-installer runs adds all permissions from the engine file and the permissions are being added during db migration. The migration should not be used for new SCC manager installations I suppose. Here is the commit where the permissions have been adjusted:
https://github.com/ATIX-AG/foreman_scc_manager/commit/582bea6383158a6ad1d50a5a659ac5900fdac843
Same issue here. Any news on this? #106 has been closed without comment.
@loopway @dgoetz I have opened a new PR #117 to fix the issue. Do you mind testing?
Back from vacation, so I found some time to test and it works fine. Thanks! Can you tag a new release? I can then handle packaging if you want.
Can you tag a new release? I can then handle packaging if you want.
Both already done. The package is available in rpm/develop, I have also open PRs for rpm/3.4 and rpm/3.5.
After installing the plugin, when running the foreman-installer I got an error that
foreman-rake db:migrate
failed. To reproduce it and provide some clean output I build a new machine.As you can see I prepared the repos, installed and run the installer. Afterwards I verified the permissions are not present. Then I installed the plugin and another verification already shows the permissions. When I run the migrations now it fails. Deleting the migration seems fine as migrate and seed run fine afterwards as the installer does and from looking into the Roles "SCCViewer" and "SCCManager" I would say it is also fine. So I have no idea why it fails now as it seems like the migration is in for a while and I also do not know how the permissions are created during plugin installation without any scripts or commands executed.