Prep cloud.common 3.0.0 release

[alinabuzachis]

SUMMARY

Prep cloud.common 3.0.0 release

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

several

[softwarefactory-project-zuul[bot]]

Build failed. https://ansible.softwarefactory-project.io/zuul/buildset/841cc21d4dd649e9bb3045dac5709347

:heavy_check_mark: build-ansible-collection SUCCESS in 11m 26s :x: ansible-galaxy-importer RETRY_LIMIT in 4m 38s

[alinabuzachis]

recheck

[softwarefactory-project-zuul[bot]]

Build failed. https://ansible.softwarefactory-project.io/zuul/buildset/821e05bdeb264b46bd527a8b97438c8f

:heavy_check_mark: build-ansible-collection SUCCESS in 11m 42s :x: ansible-galaxy-importer RETRY_LIMIT in 4m 37s

[alinabuzachis]

recheck

[softwarefactory-project-zuul[bot]]

Build failed. https://ansible.softwarefactory-project.io/zuul/buildset/251e12bc8e6342e0af0053eea72df76c

:heavy_check_mark: build-ansible-collection SUCCESS in 11m 37s :x: ansible-galaxy-importer RETRY_LIMIT in 3m 13s

[softwarefactory-project-zuul[bot]]

Build failed. https://ansible.softwarefactory-project.io/zuul/buildset/d42bcf343bb24a60a192d1e234444dbc

:heavy_check_mark: build-ansible-collection SUCCESS in 11m 25s :x: ansible-galaxy-importer RETRY_LIMIT in 4m 22s

[jillr]

recheck

[softwarefactory-project-zuul[bot]]

Build failed. https://ansible.softwarefactory-project.io/zuul/buildset/07ed2c5655b54a62ba0aac408f767b56

:heavy_check_mark: build-ansible-collection SUCCESS in 11m 12s :x: ansible-galaxy-importer RETRY_LIMIT in 4m 41s

[mariolenz]

ansible-galaxy-importer failed with:

ERROR! Failed to resolve the requested dependencies map. Got the candidate cloud.common:3.0.0 (dependency of vmware.vmware_rest:3.0.0) which didn't satisfy all of the following requirements:
* cloud.common:3.0.0
* cloud.common:>=2.0.4,<3.0.0
Hint: Pre-releases hosted on Galaxy or Automation Hub are not installed by default unless a specific version is requested. To enable pre-releases globally, use --pre.
Starting galaxy collection install process
Process install dependency map

Do we have some kind of circular dependency here? Does anyone know where the vmware.vmware_rest:3.0.0 comes from?

[GomathiselviS]

ansible-galaxy-importer failed with:

ERROR! Failed to resolve the requested dependencies map. Got the candidate cloud.common:3.0.0 (dependency of vmware.vmware_rest:3.0.0) which didn't satisfy all of the following requirements:
* cloud.common:3.0.0
* cloud.common:>=2.0.4,<3.0.0
Hint: Pre-releases hosted on Galaxy or Automation Hub are not installed by default unless a specific version is requested. To enable pre-releases globally, use --pre.
Starting galaxy collection install process
Process install dependency map

Do we have some kind of circular dependency here? Does anyone know where the vmware.vmware_rest:3.0.0 comes from?

It comes from here. I will work on removing this job since it has already been invoked in the GitHub Actions workflow.

[GomathiselviS]

recheck

[softwarefactory-project-zuul[bot]]

Build succeeded. https://ansible.softwarefactory-project.io/zuul/buildset/facc2b43193c44649d4adcf4e8cc92f3

:heavy_check_mark: ansible-galaxy-importer SUCCESS in 4m 56s :heavy_check_mark: build-ansible-collection SUCCESS in 7m 25s

[softwarefactory-project-zuul[bot]]

Build succeeded (gate pipeline). https://ansible.softwarefactory-project.io/zuul/buildset/cf9e8713a7204594a273aec1f7598096

:heavy_check_mark: ansible-galaxy-importer SUCCESS in 3m 50s :heavy_check_mark: build-ansible-collection SUCCESS in 7m 57s

[mariolenz]

Excuse me, but now that this is merged (and tagged 3.0.0) I tried to find it on Galaxy but couldn't.

Isn't this collection published there automatically when you tag it?

[alinabuzachis]

Excuse me, but now that this is merged (and tagged 3.0.0) I tried to find it on Galaxy but couldn't.

Isn't this collection published there automatically when you tag it?

The job that publishes the collection to Ansible Galaxy failed, however, @jillr will fix this by manually pushing the release.

[mariolenz]

@alinabuzachis If the collection should be published automatically, the problem might be related to Bot used for publishing has lost namespace access.

But @jillr should know about this, I think I've seen her somewhere in the thread.

[jillr]

They have manually published the release, and fixed the namespace permissions for the bot account on galaxy (we can do that ourselves now, it's super awesome!).

[mariolenz]

They

Sorry, I didn't want to be disrespectful. I'll try to remember.

have manually published the release, and fixed the namespace permissions for the bot account on galaxy

Great, thanks!