Bug 2144753 - The osp-tox-pep8 job is broken because flake8 repository was migrated to github
Summary: The osp-tox-pep8 job is broken because flake8 repository was migrated to github
Keywords:
Status: MODIFIED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z10
: 16.1 (Train on RHEL 8.2)
Assignee: Takashi Kajinami
QA Contact: David Rosenfeld
URL:
Whiteboard:
Depends On: 2144752
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-22 08:29 UTC by Takashi Kajinami
Modified: 2023-07-12 14:24 UTC (History)
4 users (show)

Fixed In Version: openstack-tripleo-common-15.4.1-0.20221122090255.51f6577.el9ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2144752
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1996668 0 None None None 2022-11-22 08:31:04 UTC
OpenStack gerrit 864689 0 None MERGED Pull flake8 from Github 2022-11-22 08:31:04 UTC
Red Hat Issue Tracker OSP-20354 0 None None None 2022-11-22 08:39:20 UTC

Description Takashi Kajinami 2022-11-22 08:29:09 UTC 
+++ This bug was initially created as a clone of Bug #2144752 +++

Description of problem:

The osp-tox-pep8 job consistently fails with the following error.

```
[INFO] Initializing environment for https://gitlab.com/pycqa/flake8.git.
An unexpected error has occurred: CalledProcessError: command: ('/usr/bin/git', 'fetch', 'origin', '--tags')
return code: 128
expected return code: 0
stdout: (none)
stderr:
    fatal: could not read Username for 'https://gitlab.com': No such device or address
```

This was already fixed in upstream by [1].
We have to backport the fix to our downstream branch which no longer imports the upstream branches.

[1] https://review.opendev.org/q/I0a30b9ae7ccc2d5faf67e78c1f2d04cea446cecc 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


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