View Issue Details

IDProjectCategoryView StatusLast Update
0016700Buildsyscommunity buildsyspublic2020-01-10 07:37
Reporteraskb 
PriorityhighSeverityminorReproducibilityN/A
Status feedbackResolutionopen 
PlatformN/AOSN/AOS VersionN/A
Summary0016700: Create new tags for Opendaylight Sodium SR2 and Neon SR3 release
DescriptionPlease create the following new tags:

1. For Opendaylight Neon SR3 (10.3) release
nfv7-opendaylight-103-{candidate,release,testing}

2. For Opendaylight Sodium SR2 (11.2) release
nfv7-opendaylight-112-{candidate,release,testing}

https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
Steps To ReproduceN/A
Additional InformationN/A
TagsNo tags attached.

Relationships

related to 0016697 closedalphacc opendaylight-6.4.0 repository missing repodata 

Activities

arrfab

arrfab

2019-11-07 12:35

administrator   ~0035656

Last edited: 2019-11-07 12:36

View 2 revisions

Hi,
Before we create new tags in cbs, can you shed a light on the other issue linked to this one ?
It seems SIG NFV asks for tags, and even tag-build to -release but *never* asked any pkg to be officially signed and pushed to mirror network and so be consumed by users ?

The only request was for vpp but nothing else ?
See https://git.centos.org/centos/cbs-content-control/blob/master/f/sign_list#_299

askb

askb

2020-01-10 01:19

reporter   ~0035989

@arrfab Sorry for the delay in responding to this request, lost track of this.

The repository that is listed is listed on 0016697 is opendaylight 6 which is a pretty old release and already EOL-ed. They should be using a more recent version of the release 10.x and above.
arrfab

arrfab

2020-01-10 07:37

administrator   ~0035995

Created the tags, as requested :

* Checking distribution el7 configuration...
 -> Checking nfv config...
Creating tag : nfv7-opendaylight-103-candidate
Creating tag : nfv7-opendaylight-103-testing
Creating tag : nfv7-opendaylight-103-release
 -> creating nfv7-opendaylight-103-el7
Added external repo centos7-cr to tag nfv7-opendaylight-103-el7-build (priority 5)
Added external repo centos7-extras to tag nfv7-opendaylight-103-el7-build (priority 10)
Added external repo centos7-updates to tag nfv7-opendaylight-103-el7-build (priority 15)
Added external repo centos7-os to tag nfv7-opendaylight-103-el7-build (priority 20)
Adding nfv7-common-candidate as inheritance

* Checking distribution el7 configuration...
 -> Checking nfv config...
Creating tag : nfv7-opendaylight-112-candidate
Creating tag : nfv7-opendaylight-112-testing
Creating tag : nfv7-opendaylight-112-release
 -> creating nfv7-opendaylight-112-el7
Added external repo centos7-cr to tag nfv7-opendaylight-112-el7-build (priority 5)
Added external repo centos7-extras to tag nfv7-opendaylight-112-el7-build (priority 10)
Added external repo centos7-updates to tag nfv7-opendaylight-112-el7-build (priority 15)
Added external repo centos7-os to tag nfv7-opendaylight-112-el7-build (priority 20)
Adding nfv7-common-candidate as inheritance

But is that possible to *not* point to cbs.centos.org at all ? and follow the SIGGuide (https://wiki.centos.org/SIGGuide) to properly sign/release packages to the centos mirror network ?
@alphacc : wondering if we should block pkgs download directly from cbs.centos.org to ensure SIGs are following the guidelines and not pointing to single node

Issue History

Date Modified Username Field Change
2019-11-07 10:46 askb New Issue
2019-11-07 12:34 arrfab Relationship added related to 0016697
2019-11-07 12:35 arrfab Note Added: 0035656
2019-11-07 12:36 arrfab Note Edited: 0035656 View Revisions
2020-01-10 01:19 askb Note Added: 0035989
2020-01-10 07:37 arrfab Note Added: 0035995
2020-01-10 07:37 arrfab Status new => feedback