-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
You have requested a non-existent service "islandora_riprap.islandora_riprap_utils" #46
Comments
I have only enabled this module in a standard Islandora Playbook VM (also running Drupal 9.3.0-dev), and can't replicate it:
Mind you, I'm running that manually as the vagrant user, not via an ansible role. Can you not deploy Islandora Riprap via your playbook, but run it manually after the install is complete? If it gets enabled like it does for me, we've narrowed down the problem to being specific to its being enabled via ansible. At least then we'd know where to look to modify the module. |
Ok, good to know you're on 9.3.0-dev. I thought that may have been the underlying problem. Good call on moving enabling it. I'll give that a shot and see what happens. |
Did a fresh build on our playbook, which is largely the Islandora Playbook, and got the same thing 😢
The only think that I can think of is that there might be something off in our yudl8_defaults, which is a modified islandora_defaults. I'll dig into that, and if you have any other ideas, let me know, and I'll dig into those. |
I've added the Riprap playbook to the Islandora Playbook, and I get the same error. So, I believe I've eliminated the York playbook. Though, it might be our Riprap playbook, but I'm not positive it is the case. This is my diff on the Islandora playbook if you want to try and reproduce: |
Was wondering if there's any updates about this? What I've tried so far was following the messaging and replacing the service call with "islandora.utils" and it seemed to work and allowed me to install the module. Then afterwards, I was able to revert the code back. Not quite sure if this is a legit way, seems to be a problem for Drupal 9 as I tried with Drupal 8 and got no errors. Any ideas, thoughts, feedbacks? Also I was curious what's the reason for the Islandora dependency? Thanks! P.S. I'm a newbie to Drupal, Islandora, etc. So sorry if I'm a bit clueless on all of this. |
@mjordan that sounds like a possible solution, and I'd be happy to give that a test. |
Great, thanks. I notice that i did a piss-poor job of removing references to Gemini (#39) so I'm going to clean those up as well. |
OK, the issue-46 branch incorporates both services into one, eliminating "islandora_riprap.utils". Can you see if this version solves the issue? |
Thanks @mjordan for the update and all your efforts. I just pulled down branch issue-46 and tried installing this version of the islandora-playbook module but unfortunately I get a similar error:
I've been trying to look around on the internet to look for a potential fix but so far nothing works. |
I can confirm the same error as @t-cao19 on my end with issue-46. The only thing that I have found that works, is to delete
and
I tried a bunch of stuff on a local branch, and couldn't get anything to work before I disappeared on vacation. |
OK, thanks to both of you for testing. @ruebot I've relocated the |
@mjordan sure thing! |
@mjordan I think we're good to go now! I was able to fire-up machine cleanly with that branch. thank you! 🙏 |
Awesome! That took a while to track down. Thanks for finding it, and for the leads as to what could have been the problem. It was pretty esoteric. @t-cao19 no need for you to test, but if you can that would be great. |
Excellent - thanks both! I can't merge at the moment but will do so this evening. |
Resolved with a5d7d50. |
- See: mjordan/islandora_riprap#46 and related islandora_riprap commits - Resolves #36
I'm running into this issue trying in install Islandora Riprap in our Playbooks. We're running Drupal 9.3.0-dev, so that might be the cause of the issue based on what I see here.
I tried adding an
alias
to theservices.yml
and setting upautowire
, but neither of those options worked. I thought it also might be a namespace issue, and tried (below diff) throughout the module to no avail as well.The text was updated successfully, but these errors were encountered: