Skip to content
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

"pcdm" namespace is not registered by default #1817

Open
mjordan opened this issue May 7, 2021 · 9 comments
Open

"pcdm" namespace is not registered by default #1817

mjordan opened this issue May 7, 2021 · 9 comments
Labels
Type: bug identifies a problem in the software with clear steps to reproduce

Comments

@mjordan
Copy link
Contributor

mjordan commented May 7, 2021

The "pcdm" namespace needs to be registered by default. Here's a list of all registered namespaces in a vanilla Islandora:

image

@seth-shaw-unlv
Copy link
Contributor

I spun up a fresh playbook using the ubuntu base and it looks fine:
Screen Shot 2021-05-12 at 1 53 11 PM

Here is the JSON-LD config page:
Screen Shot 2021-05-12 at 12 32 10 PM

"rdau" and "pcdm" are both there.

How did you build your box, @mjordan?

@mjordan
Copy link
Contributor Author

mjordan commented May 12, 2021

Weird - I built it using a standard vagrant up in the Playbook, on May 4. Given that date, could there have been updates to the relevant modules that would explain the missing namespaces in my build?

@seth-shaw-unlv
Copy link
Contributor

seth-shaw-unlv commented May 12, 2021

The last playbook commit was on April 28th.

Perhaps you used the "islandora/8" base box (which is built on 1.1.0) instead of changing the base box to "ubuntu/focal64"? But then you shouldn't have had that report available, unless you checked out the most recent version of islandora_defaults after it completed provisioning. In that case, you need to update jsonld at the same time (well, jsonld's update needs to happen first).

@mjordan
Copy link
Contributor Author

mjordan commented May 12, 2021

Right, I did build with "ubuntu/focal64", sorry for not indicating that earlier. However, I don't recall checking out any newer code after building. Let me build a new box on "ubuntu/focal64" and confirm no new code checkouts to see what happens.

@mjordan
Copy link
Contributor Author

mjordan commented May 12, 2021

Ha, just cloned down a fresh copy of islandora-playbook and am seeing this error after vagrant upping (and changing to 'ubuntu/focal64'):

ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.

The error appears to have been in '/home/mark/Documents/hacking/vagrants/islandora-playbook-newer/post-install.yml': line 13, column 7, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


    - name: Create a directory if it does not exist
      ^ here

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

git diff shows the following:

 git diff
diff --git a/Vagrantfile b/Vagrantfile
index 778a594..d656562 100644
--- a/Vagrantfile
+++ b/Vagrantfile
@@ -14,7 +14,8 @@ $virtualBoxDescription = ENV.fetch("ISLANDORA_VAGRANT_VIRTUALBOXDESCRIPTION", "I
 # Available boxes are 'islandora/8' and 'ubuntu/focal64'
 # Use 'ubuntu/focal64' to build a dev environment from scratch.
 # Use 'islandora/8' if you just want to download a ready to run VM.
-$vagrantBox = ENV.fetch("ISLANDORA_DISTRO", "islandora/8")
+# $vagrantBox = ENV.fetch("ISLANDORA_DISTRO", "islandora/8")
+$vagrantBox = ENV.fetch("ISLANDORA_DISTRO", "ubuntu/focal64")

 # vagrant is the main user
 $vagrantUser = "vagrant"

@seth-shaw-unlv
Copy link
Contributor

The last update to post-install.yml was on April 8th. It worked fine for me just now. I have no idea why it is complaining to you. 😕🤷‍♂️

ansible version? I have 2.9.9.

@mjordan
Copy link
Contributor Author

mjordan commented May 12, 2021

2.5.1. Let me upgrade it. Sigh.

@mjordan
Copy link
Contributor Author

mjordan commented May 12, 2021

Which I can't do: "ansible is already the newest version (2.5.1+dfsg-1ubuntu0.1)".

This evening I'll build on my laptop that has what is probably a newer version of ansible.

@mjordan
Copy link
Contributor Author

mjordan commented May 12, 2021

My build wth ansible 2.9.6 died at deploying Matomo again exactly as described in #1810. I'm too tired to try again, so based on your successful build, I'm happy to label this current issue as "can't replicate."

@kstapelfeldt kstapelfeldt added Type: bug identifies a problem in the software with clear steps to reproduce and removed bug labels Sep 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: bug identifies a problem in the software with clear steps to reproduce
Projects
Development

No branches or pull requests

3 participants