'current' repo is being used instead of 'current-tripleo' for non tripleo packages during rpmbuild in tripleo jobs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Incomplete
|
High
|
wes hayutin |
Bug Description
rpmbuild should use the same set of repos with mirror config as defined in release files[1]. 'current-tripleo' repo should be used for non tripleo packages and 'current' for tripleo packages.
@ramishra noticed it during one of the CentOS8 job [2], similar usage are there in CentOS7 jobs. repos are configured correctly in build-test-packages role [3], DLRN is pulling additional repos which should be skipped. This is happening as --dev is used during dlrn build[4] and DLRN based on it[5] setups repos. --dev shouldb't be needed in upstream jobs as we are not testing distgit changes, but if it's needed need to have an option in DLRN to skip repo setup.
[1] https:/
[2] https:/
[3] https:/
[4] https:/
[5] https:/
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → yatin (yatinkarel) |
milestone: | none → ussuri-3 |
tags: | added: alert |
Changed in tripleo: | |
status: | Triaged → In Progress |
Changed in tripleo: | |
milestone: | ussuri-3 → ussuri-rc3 |
Changed in tripleo: | |
milestone: | ussuri-rc3 → victoria-1 |
Changed in tripleo: | |
milestone: | victoria-1 → victoria-3 |
Changed in tripleo: | |
milestone: | victoria-3 → wallaby-1 |
Changed in tripleo: | |
milestone: | wallaby-1 → wallaby-2 |
Changed in tripleo: | |
milestone: | wallaby-2 → wallaby-3 |
Changed in tripleo: | |
milestone: | wallaby-3 → wallaby-rc1 |
Changed in tripleo: | |
milestone: | wallaby-rc1 → xena-1 |
It does in fact look like --dev is introducing an error. /github. com/softwarefac tory-project/ DLRN/blob/ db90a76a2c4ba74 4212eec92a605bf 131d6d19a9/ dlrn/build. py#L215- L233
https:/
So yes.. we should fix the bug! Thanks for your bug report!
# I do want to describe what is the current expected design for packages. tripleoclient for example.
This design *does* create a problem if openstack client libraries are not
promoted to a version required for changes in python-
The current design for tripleo upstream ci would be the following.
TripleO Packages:
* these commits can be pulled in immediately after merge upstream.
# name of delorean- tripleo- component- current? naming is hard current. repo /trunk. rdoproject. org/{{ distro_ver }}-{{ release }}/component/ tripleo/ current/ delorean. repo" role-container- registry role-tripleo* tripleo- ipsec config_ template
- type: file
reponame: delorean-current
filename: delorean-
down_url: "https:/
priority: 10
includepkgs:
- ansible-
- ansible-
- ansible-
- instack
- instack-undercloud
- openstack-tripleo-*
- os-apply-config
- os-collect-config
- os-net-config
- os-refresh-config
- puppet-*
- python*-tripleo*
- python*-paunch*
- paunch-services
- tripleo-ansible
- ansible-
Non-TripleO Packages should come from a validated set of rpms: ( current-tripleo )
https:/ /trunk. rdoproject. org/centos8- master/ current- tripleo/ delorean. repo