settingsLogin | Registersettings

Re: [openstack-dev] [Release-job-failures][telemetry][gnocchi] Release of openstack/python-gnocchiclient failed

0 votes

Gnocchi team,

The client release you tagged had a build failure. It looks like
the tag was pushed directly, so I will relay the results of the
debugging work but let you decide how to deal with it.

Clark determined that the files on PyPI do not exactly match the files
on our tarballs server. One of the JSON metadata files was regenerated,
and because dictionaries are unordered it came out in a different order.

Clark also checked the MD5 sum on PyPI and found that the signatures
match.

It's not clear why the job failed. Subsequent jobs have passed. One
course of action you could take is to retag the same commit with a new
version number to get new packages, just to be safe.

If you choose to stick with the existing packages, you will need to
manually submit the constraint update, since that job was skipped after
the upload job reported a failure.

Please also file the update in the releases repository, so that
there is a record of the fact that the release was made.

Excerpts from jenkins's message of 2017-04-12 09:29:09 +0000:

Build failed.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Apr 12, 2017 in openstack-dev by Doug_Hellmann (87,520 points)   4 4 13

3 Responses

0 votes

Excerpts from Doug Hellmann's message of 2017-04-12 13:49:54 -0400:

Gnocchi team,

The client release you tagged had a build failure. It looks like
the tag was pushed directly, so I will relay the results of the
debugging work but let you decide how to deal with it.

Clark determined that the files on PyPI do not exactly match the files
on our tarballs server. One of the JSON metadata files was regenerated,
and because dictionaries are unordered it came out in a different order.

Clark also checked the MD5 sum on PyPI and found that the signatures
match.

It's not clear why the job failed. Subsequent jobs have passed. One
course of action you could take is to retag the same commit with a new
version number to get new packages, just to be safe.

If you choose to stick with the existing packages, you will need to
manually submit the constraint update, since that job was skipped after
the upload job reported a failure.

Please also file the update in the releases repository, so that
there is a record of the fact that the release was made.

Excerpts from jenkins's message of 2017-04-12 09:29:09 +0000:

Build failed.

The Gnocchi server release had a similar issue, and should be treated
the same way.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 12, 2017 by Doug_Hellmann (87,520 points)   4 4 13
0 votes

Thanks for the investigation.

I see two things:

  • I have forgotten than pushing tag will build the tarball
    automatically.
  • I have thought I should do the tagging manually because of [1]

For the second point, if I was wrong and we should continue to use the
release repo, I have prepared two reviews to regularize the already
tagged releases and retag a versions to fix the jobs.

If I was right, I will manually retag a new version without uploading the
tarballs myself this time and wait for the tooling to do it.

[1] https://review.openstack.org/#/c/447438/

On Wed, Apr 12, 2017 at 01:49:54PM -0400, Doug Hellmann wrote:

Gnocchi team,

The client release you tagged had a build failure. It looks like
the tag was pushed directly, so I will relay the results of the
debugging work but let you decide how to deal with it.

Clark determined that the files on PyPI do not exactly match the files
on our tarballs server. One of the JSON metadata files was regenerated,
and because dictionaries are unordered it came out in a different order.

Clark also checked the MD5 sum on PyPI and found that the signatures
match.

It's not clear why the job failed. Subsequent jobs have passed. One
course of action you could take is to retag the same commit with a new
version number to get new packages, just to be safe.

If you choose to stick with the existing packages, you will need to
manually submit the constraint update, since that job was skipped after
the upload job reported a failure.

Please also file the update in the releases repository, so that
there is a record of the fact that the release was made.

Excerpts from jenkins's message of 2017-04-12 09:29:09 +0000:

Build failed.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Mehdi Abaakouk
mail: sileht@sileht.net
irc: sileht


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

responded Apr 13, 2017 by Mehdi_Abaakouk (4,040 points)   3 5
0 votes

Excerpts from Mehdi Abaakouk's message of 2017-04-13 07:51:36 +0200:

Thanks for the investigation.

I see two things:

  • I have forgotten than pushing tag will build the tarball
    automatically.
  • I have thought I should do the tagging manually because of [1]

For the second point, if I was wrong and we should continue to use the
release repo, I have prepared two reviews to regularize the already
tagged releases and retag a versions to fix the jobs.

If I was right, I will manually retag a new version without uploading the
tarballs myself this time and wait for the tooling to do it.

Because Gnocchi is an independent project, you can choose to push
the tags yourself. You should still rely on the automation to build
and upload the artifacts, though. Some jobs, like the announce job,
may not work properly because they require metadata in the tag
message that is added by the release tools but not necessarily
present when you tag by hand. You may end up having to send your
own release announcements (or use the tools by hand, instead of
just running git tag).

As an official project, we would still like to have correct release
information for gnocchi recorded in the openstack/releases repository,
even if you do tag it yourself. So, either

  1. tag and then update openstack/releases, or
  2. use openstack/releases to start the release (taking full advantage of
    the automation), or
  3. remove references to the deliverables from openstack/releases so we
    do not have incomplete information there

Doug

[1] https://review.openstack.org/#/c/447438/

On Wed, Apr 12, 2017 at 01:49:54PM -0400, Doug Hellmann wrote:

Gnocchi team,

The client release you tagged had a build failure. It looks like
the tag was pushed directly, so I will relay the results of the
debugging work but let you decide how to deal with it.

Clark determined that the files on PyPI do not exactly match the files
on our tarballs server. One of the JSON metadata files was regenerated,
and because dictionaries are unordered it came out in a different order.

Clark also checked the MD5 sum on PyPI and found that the signatures
match.

It's not clear why the job failed. Subsequent jobs have passed. One
course of action you could take is to retag the same commit with a new
version number to get new packages, just to be safe.

If you choose to stick with the existing packages, you will need to
manually submit the constraint update, since that job was skipped after
the upload job reported a failure.

Please also file the update in the releases repository, so that
there is a record of the fact that the release was made.

Excerpts from jenkins's message of 2017-04-12 09:29:09 +0000:

Build failed.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 13, 2017 by Doug_Hellmann (87,520 points)   4 4 13
...