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

/pelican/monitoring directories use incorrect base path #1840

Closed
jhiemstrawisc opened this issue Dec 18, 2024 · 0 comments · Fixed by #1841
Closed

/pelican/monitoring directories use incorrect base path #1840

jhiemstrawisc opened this issue Dec 18, 2024 · 0 comments · Fixed by #1841
Assignees
Labels
bug Something isn't working cache Issue relating to the cache component critical High priority for next release
Milestone

Comments

@jhiemstrawisc
Copy link
Member

In the upcoming 7.12 release, we created a new default directory for storing our namespace symlinks. Setting:

Cache:
  StorageLocation: /cache

Should result in the automatic generation of these directories:

/cache
  /data
  /meta
  /namespace
    /<namespace1>
    /<namespace2>
    /pelican
      /monitoring
      ...

However, the modifications to self test directory creation incorrectly used the Cache.StorageLocation as their base path, resulting in:

/cache
  /data
  /meta
  /pelican
    /monitoring
  /namespace
    /<namespace1>
    /<namespace2>

where the pelican monitoring namespace is created in the wrong spot. This prevents self test files from being read and from being cleaned up.

@jhiemstrawisc jhiemstrawisc added bug Something isn't working critical High priority for next release cache Issue relating to the cache component labels Dec 18, 2024
@jhiemstrawisc jhiemstrawisc added this to the v7.12.0 milestone Dec 18, 2024
@jhiemstrawisc jhiemstrawisc self-assigned this Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cache Issue relating to the cache component critical High priority for next release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant