openstack-ansible

metadata file `MANIFEST.json`is expected to have a valid SemVer version value but got None

Bug #1970220 reported by Peter Struys
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-ansible
New
Undecided
Unassigned

Bug Description

While running bootstrap-ansible.sh when upgrading van stable/wallaby to stable/xena, pretty quicly into this script I get the error "ERROR! Collection metadata file `MANIFEST.json` at `/etc/ansible/ansible_collections/ansible/netcommon` is expected to have a valid SemVer version value but got None".

The file MANIFEST.json is present.

ps : is this related to bug 1963686 ?

thank you
Peter

Revision history for this message
Peter Struys (peterstruys) wrote (last edit ):

Deleting this file MANIFEST.json triggered the download of a newer netcommon version (2.5.1) and the script is continuing

Revision history for this message
Jonathan Rosser (jrosser) wrote :

I think that is is a result of switching back and forward between the version of netcommon installed from git and the one from ansible-galaxy as a result of bug 1963686 that you linked. I don't think it is a bug in openstack-ansible as it looks like the error actually comes from ansible-galaxy?

As far as I can see we have merged fixes to the openstack-ansible stable branches so that this should not happen again - see https://review.opendev.org/q/Ic110f8cc425482680070d71f8fe3dacfd1f561fd. You should make sure that the checkout of the stable branch you are using is new enough to include these fixes.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.