Bug 2109807 - Ansible galaxy not able to recognize stable/1.0.0 version
Summary: Ansible galaxy not able to recognize stable/1.0.0 version
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: ansible-collections-openstack
Version: unspecified
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Jakob Meng
QA Contact: Jakob Meng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-22 08:01 UTC by Amol K
Modified: 2022-08-03 09:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-25 12:25:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-17804 0 None None None 2022-07-22 08:04:24 UTC

Description Amol K 2022-07-22 08:01:33 UTC
Description of problem:
Ansible galaxy not able to recognize stable/1.0.0 version

Version-Release number of selected component (if applicable):
stable/1.0.0

How reproducible:
Always

Steps to Reproduce:


Actual results:
Starting galaxy collection install process
2022-07-22 03:32:03.698896 | primary | ERROR! Unexpected Exception, this is probably a bug: Non integer values in LooseVersion ('stable/1.0.0')
2022-07-22 03:32:03.698979 | primary | to see the full traceback, use -vvv
2022-07-22 07:32:04.061132 | primary | ERROR
2022-07-22 07:32:04.061355 | primary | {
2022-07-22 07:32:04.061400 | primary | "delta": "0:01:54.886069",
2022-07-22 07:32:04.061426 | primary | "end": "2022-07-22 03:32:03.781466",
2022-07-22 07:32:04.061448 | primary | "msg": "non-zero return code",
2022-07-22 07:32:04.061478 | primary | "rc": 250,
2022-07-22 07:32:04.061498 | primary | "start": "2022-07-22 03:30:08.895397"
2022-07-22 07:32:04.061518 | primary | }

Expected results:


Additional info:

Comment 7 Amol K 2022-08-03 09:01:53 UTC
This bug is fixed. Clearing needinfo.


Note You need to log in before you can comment on or make changes to this bug.