# My galaxy content has evaporated **URL:** \ **Category:** Get Help\ **Tags:** galaxy-ng\ **Created:** [October 2, 2023, 5:48pm UTC](https://forum.ansible.com/t/my-galaxy-content-has-evaporated/1295 "2023-10-02T17:48:00Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![utoddl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/utoddl/32/249_2.png) [@utoddl](https://forum.ansible.com/u/utoddl)\ **Post date:** [October 2, 2023, 5:48pm UTC](https://forum.ansible.com/t/my-galaxy-content-has-evaporated/1295/1 "2023-10-02T17:48:00Z")
Browsing my namespace on galaxy, [utoddl.logical](https://galaxy.ansible.com/ui/repo/published/utoddl/logical/) seems to have gone on a diet: “0 Modules 0 Roles 0 Plugins 0 Dependencies”. There used to be a plugin in there, I promise! Perhaps related: looking at [My Namespaces](https://galaxy.ansible.com/ui/my-namespaces/) shows four other namespaces (1) that are totally empty and (2) that I was totally unaware of: `utoddl0`, `utoddl1`, `utoddl2`, and `utoddl3`. The docs talk about deleting various entities, but I don’t see a way I can delete these bogus (as far as I’m concerned) empty namespaces. ---
**Author:** ![jlmitch5](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jlmitch5/32/578_2.png) [@jlmitch5](https://forum.ansible.com/u/jlmitch5)\ **Post date:** [October 2, 2023, 6:41pm UTC](https://forum.ansible.com/t/my-galaxy-content-has-evaporated/1295/2 "2023-10-02T18:41:02Z")
Thanks @utoddl for the report and sorry for the inconvenience. The team is investigating some strangeness that happened with namespace migrations right now. ---
**Author:** ![tannerjc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/tannerjc/32/985_2.png) [@tannerjc](https://forum.ansible.com/u/tannerjc)\ **Post date:** [October 19, 2023, 6:14pm UTC](https://forum.ansible.com/t/my-galaxy-content-has-evaporated/1295/3 "2023-10-19T18:14:31Z")
I fixed the ownership for utoddl a couple days ago and also cleaned up the extra namespaces based on this post [Strangeness with my \*tiny\* namespace.collection migration from old-galaxy to galaxy-ng](http://forum.ansible.com/t/strangeness-with-my-tiny-namespace-collection-migration-from-old-galaxy-to-galaxy-ng/1612) The plugin metadata issue still remains though. I believe that is due to the galaxy-importer code complaining about problems with the collection and not sending back the data (which implies it wouldn’t successfully publish right now either). ---
**Author:** ![utoddl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/utoddl/32/249_2.png) [@utoddl](https://forum.ansible.com/u/utoddl)\ **Post date:** [October 19, 2023, 7:28pm UTC](https://forum.ansible.com/t/my-galaxy-content-has-evaporated/1295/4 "2023-10-19T19:28:47Z")
> [@tannerjc](#): > > […] implies it wouldn’t successfully publish right now either This is correct. The deficient 5-year-old metadata is easily fixed, but it’s the docs I’m stuck on. Internally we’re a gitlab shop. The bugaboo at the moment is that the `README.md` has to render well on github, gitlab, and galaxy-ng. Both `git*b` services have APIs to render HTML from markdown, but not so on `gal*`, at least not without actually publishing a new version. That’s a little late in the process to determine the tables in your markdown - which are fine on `git*b` - are borked on `galaxy`. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [October 19, 2023, 7:59pm UTC](https://forum.ansible.com/t/my-galaxy-content-has-evaporated/1295/5 "2023-10-19T19:59:01Z")
If it’s just about the import step failing, and not about rendering badly, you can simply run galaxy-importer in CI to see whether it accepts the collection: [https://github.com/felixfontein/ansible-acme/blob/main/.github/workflows/import-galaxy.yml](https://github.com/felixfontein/ansible-acme/blob/main/.github/workflows/import-galaxy.yml) ---
**Author:** ![utoddl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/utoddl/32/249_2.png) [@utoddl](https://forum.ansible.com/u/utoddl)\ **Post date:** [October 19, 2023, 8:37pm UTC](https://forum.ansible.com/t/my-galaxy-content-has-evaporated/1295/6 "2023-10-19T20:37:39Z")
Thanks for the link. `galaxy-importer` has already pointed out at least one missing file, and the old `meta/main.yml` is … older than most hummingbirds! Standards have risen. Like I said, that’s easily fixed. I need to rewrite the docs, and that’s going to take time. Fortunately, this collection may be the least important one on the whole platform. It’s literally two files: a plugin, and a `README.md`. (I’m not counting the metadata files.) I have lots more important stuff to put off before I can concentrate on putting this one off. ---
**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\ **Post date:** [November 18, 2023, 8:37pm UTC](https://forum.ansible.com/t/my-galaxy-content-has-evaporated/1295/7 "2023-11-18T20:37:47Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.