[jira] [Commented] (MESOS-9581) Mesos package naming appears to be undeterministic.
[
https://issues.apache.org/jira/browse/MESOS-9581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780648#comment-16780648
]
Till Toenshoff commented on MESOS-9581:
---
The issues should be fixed now. Our CI is currently packaging numerous tags
that got left behind due to our previous problems.
> Mesos package naming appears to be undeterministic.
> ---
>
> Key: MESOS-9581
> URL: https://issues.apache.org/jira/browse/MESOS-9581
> Project: Mesos
> Issue Type: Bug
> Components: build
>Affects Versions: 1.7.1
>Reporter: Till Toenshoff
>Assignee: Till Toenshoff
>Priority: Major
> Labels: ci, integration, packaging, rpm
>
> Transcribed from slack;
> https://mesos.slack.com/archives/C7N086PK2/p1550158266006900
> It appears there are a number of RPM packages called
> “mesos-1.7.1-2.0.1.el7.x86_64.rpm” in the wild.
> I’ve caught specimens with build dates February 1st, 7th and 13th. While it’s
> somewhat troubling in itself, none of these packages is the one referred to
> in Yum repository metadata (repos.mesosphere.com), which is a package built
> today on the 14th, so I can’t install Mesos right now.
> Could it be that your pipeline is creating a new package with the same verson
> and release in every nightly build?
> Repository metadata
> {noformat}
> sqlite3 *primary.sqlite "select name, version, release, strftime('%d-%m-%Y
> %H:%M', datetime(time_build, 'unixepoch')) build_as_string, rpm_buildhost
> from packages where name = 'mesos' and version = '1.7.1';"
> mesos|1.7.1|2.0.1|14-02-2019 12:30|ip-172-16-10-254.ec2.internal
> Packages downloaded while investigating over the past few days
> Name : mesos
> Version : 1.7.1
> Release : 2.0.1
> Architecture: x86_64
> Install Date: (not installed)
> Group : misc
> Size : 298787793
> License : Apache-2.0
> Signature : RSA/SHA256, Fri 01 Feb 2019 11:38:47 PM UTC, Key ID
> df7d54cbe56151bf
> Source RPM : mesos-1.7.1-2.0.1.src.rpm
> Build Date : Fri 01 Feb 2019 11:15:17 PM UTC
> Build Host : ip-172-16-10-11.ec2.internal
> Relocations : /
> Packager : d...@mesos.apache.org
> URL : https://mesos.apache.org/
> Summary : Cluster resource manager with efficient resource isolation
> Description :
> [snip]
> Name : mesos
> Version : 1.7.1
> Release : 2.0.1
> Architecture: x86_64
> Install Date: (not installed)
> Group : misc
> Size : 298791347
> License : Apache-2.0
> Signature : RSA/SHA256, Thu 07 Feb 2019 10:33:06 PM UTC, Key ID
> df7d54cbe56151bf
> Source RPM : mesos-1.7.1-2.0.1.src.rpm
> Build Date : Thu 07 Feb 2019 10:31:02 PM UTC
> Build Host : ip-172-16-10-4.ec2.internal
> Relocations : /
> Packager : d...@mesos.apache.org
> URL : https://mesos.apache.org/
> Summary : Cluster resource manager with efficient resource isolation
> Description :
> [snip]
> Name : mesos
> Version : 1.7.1
> Release : 2.0.1
> Architecture: x86_64
> Install Date: (not installed)
> Group : misc
> Size : 298789309
> License : Apache-2.0
> Signature : RSA/SHA256, Wed Feb 13 04:35:02 2019, Key ID df7d54cbe56151bf
> Source RPM : mesos-1.7.1-2.0.1.src.rpm
> Build Date : Wed Feb 13 04:32:41 2019
> Build Host : ip-172-16-10-83.ec2.internal
> Relocations : /
> Packager : d...@mesos.apache.org
> URL : https://mesos.apache.org/
> Summary : Cluster resource manager with efficient resource isolation
> Description :
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-9581) Mesos package naming appears to be undeterministic.
[
https://issues.apache.org/jira/browse/MESOS-9581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771851#comment-16771851
]
Till Toenshoff commented on MESOS-9581:
---
We still have not fixed this issue - we disabled the pipeline for the time
being. There are underlying problems we need to solve; our Jenkins pipeline
relies on polling the apache git repo and that in turn has limitations. Changes
of our Jenkins setup now hit these limitations.
Related problem descriptions;
[https://issues.jenkins-ci.org/browse/JENKINS-10131]
[https://issues.jenkins-ci.org/browse/JENKINS-50683]
> Mesos package naming appears to be undeterministic.
> ---
>
> Key: MESOS-9581
> URL: https://issues.apache.org/jira/browse/MESOS-9581
> Project: Mesos
> Issue Type: Bug
> Components: build
>Affects Versions: 1.7.1
>Reporter: Till Toenshoff
>Assignee: Till Toenshoff
>Priority: Major
> Labels: ci, integration, packaging, rpm
>
> Transcribed from slack;
> https://mesos.slack.com/archives/C7N086PK2/p1550158266006900
> It appears there are a number of RPM packages called
> “mesos-1.7.1-2.0.1.el7.x86_64.rpm” in the wild.
> I’ve caught specimens with build dates February 1st, 7th and 13th. While it’s
> somewhat troubling in itself, none of these packages is the one referred to
> in Yum repository metadata (repos.mesosphere.com), which is a package built
> today on the 14th, so I can’t install Mesos right now.
> Could it be that your pipeline is creating a new package with the same verson
> and release in every nightly build?
> Repository metadata
> {noformat}
> sqlite3 *primary.sqlite "select name, version, release, strftime('%d-%m-%Y
> %H:%M', datetime(time_build, 'unixepoch')) build_as_string, rpm_buildhost
> from packages where name = 'mesos' and version = '1.7.1';"
> mesos|1.7.1|2.0.1|14-02-2019 12:30|ip-172-16-10-254.ec2.internal
> Packages downloaded while investigating over the past few days
> Name : mesos
> Version : 1.7.1
> Release : 2.0.1
> Architecture: x86_64
> Install Date: (not installed)
> Group : misc
> Size : 298787793
> License : Apache-2.0
> Signature : RSA/SHA256, Fri 01 Feb 2019 11:38:47 PM UTC, Key ID
> df7d54cbe56151bf
> Source RPM : mesos-1.7.1-2.0.1.src.rpm
> Build Date : Fri 01 Feb 2019 11:15:17 PM UTC
> Build Host : ip-172-16-10-11.ec2.internal
> Relocations : /
> Packager : d...@mesos.apache.org
> URL : https://mesos.apache.org/
> Summary : Cluster resource manager with efficient resource isolation
> Description :
> [snip]
> Name : mesos
> Version : 1.7.1
> Release : 2.0.1
> Architecture: x86_64
> Install Date: (not installed)
> Group : misc
> Size : 298791347
> License : Apache-2.0
> Signature : RSA/SHA256, Thu 07 Feb 2019 10:33:06 PM UTC, Key ID
> df7d54cbe56151bf
> Source RPM : mesos-1.7.1-2.0.1.src.rpm
> Build Date : Thu 07 Feb 2019 10:31:02 PM UTC
> Build Host : ip-172-16-10-4.ec2.internal
> Relocations : /
> Packager : d...@mesos.apache.org
> URL : https://mesos.apache.org/
> Summary : Cluster resource manager with efficient resource isolation
> Description :
> [snip]
> Name : mesos
> Version : 1.7.1
> Release : 2.0.1
> Architecture: x86_64
> Install Date: (not installed)
> Group : misc
> Size : 298789309
> License : Apache-2.0
> Signature : RSA/SHA256, Wed Feb 13 04:35:02 2019, Key ID df7d54cbe56151bf
> Source RPM : mesos-1.7.1-2.0.1.src.rpm
> Build Date : Wed Feb 13 04:32:41 2019
> Build Host : ip-172-16-10-83.ec2.internal
> Relocations : /
> Packager : d...@mesos.apache.org
> URL : https://mesos.apache.org/
> Summary : Cluster resource manager with efficient resource isolation
> Description :
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-9581) Mesos package naming appears to be undeterministic.
[
https://issues.apache.org/jira/browse/MESOS-9581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770687#comment-16770687
]
Till Toenshoff commented on MESOS-9581:
---
Turns out we do publish the same tag (1.7.1) with new packages every day since
January 30th. That should have stopped by now. The reasons for that breakage
were unintended changes.
> Mesos package naming appears to be undeterministic.
> ---
>
> Key: MESOS-9581
> URL: https://issues.apache.org/jira/browse/MESOS-9581
> Project: Mesos
> Issue Type: Bug
> Components: build
>Affects Versions: 1.7.1
>Reporter: Till Toenshoff
>Assignee: Till Toenshoff
>Priority: Major
> Labels: ci, integration, packaging, rpm
>
> Transcribed from slack;
> https://mesos.slack.com/archives/C7N086PK2/p1550158266006900
> It appears there are a number of RPM packages called
> “mesos-1.7.1-2.0.1.el7.x86_64.rpm” in the wild.
> I’ve caught specimens with build dates February 1st, 7th and 13th. While it’s
> somewhat troubling in itself, none of these packages is the one referred to
> in Yum repository metadata (repos.mesosphere.com), which is a package built
> today on the 14th, so I can’t install Mesos right now.
> Could it be that your pipeline is creating a new package with the same verson
> and release in every nightly build?
> Repository metadata
> {noformat}
> sqlite3 *primary.sqlite "select name, version, release, strftime('%d-%m-%Y
> %H:%M', datetime(time_build, 'unixepoch')) build_as_string, rpm_buildhost
> from packages where name = 'mesos' and version = '1.7.1';"
> mesos|1.7.1|2.0.1|14-02-2019 12:30|ip-172-16-10-254.ec2.internal
> Packages downloaded while investigating over the past few days
> Name : mesos
> Version : 1.7.1
> Release : 2.0.1
> Architecture: x86_64
> Install Date: (not installed)
> Group : misc
> Size : 298787793
> License : Apache-2.0
> Signature : RSA/SHA256, Fri 01 Feb 2019 11:38:47 PM UTC, Key ID
> df7d54cbe56151bf
> Source RPM : mesos-1.7.1-2.0.1.src.rpm
> Build Date : Fri 01 Feb 2019 11:15:17 PM UTC
> Build Host : ip-172-16-10-11.ec2.internal
> Relocations : /
> Packager : d...@mesos.apache.org
> URL : https://mesos.apache.org/
> Summary : Cluster resource manager with efficient resource isolation
> Description :
> [snip]
> Name : mesos
> Version : 1.7.1
> Release : 2.0.1
> Architecture: x86_64
> Install Date: (not installed)
> Group : misc
> Size : 298791347
> License : Apache-2.0
> Signature : RSA/SHA256, Thu 07 Feb 2019 10:33:06 PM UTC, Key ID
> df7d54cbe56151bf
> Source RPM : mesos-1.7.1-2.0.1.src.rpm
> Build Date : Thu 07 Feb 2019 10:31:02 PM UTC
> Build Host : ip-172-16-10-4.ec2.internal
> Relocations : /
> Packager : d...@mesos.apache.org
> URL : https://mesos.apache.org/
> Summary : Cluster resource manager with efficient resource isolation
> Description :
> [snip]
> Name : mesos
> Version : 1.7.1
> Release : 2.0.1
> Architecture: x86_64
> Install Date: (not installed)
> Group : misc
> Size : 298789309
> License : Apache-2.0
> Signature : RSA/SHA256, Wed Feb 13 04:35:02 2019, Key ID df7d54cbe56151bf
> Source RPM : mesos-1.7.1-2.0.1.src.rpm
> Build Date : Wed Feb 13 04:32:41 2019
> Build Host : ip-172-16-10-83.ec2.internal
> Relocations : /
> Packager : d...@mesos.apache.org
> URL : https://mesos.apache.org/
> Summary : Cluster resource manager with efficient resource isolation
> Description :
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
