Re: [Release-job-failures] Release of openstack/ansible-role-redhat-subscription for ref refs/tags/1.1.1 failed
zuul@openstack.org wrote:
- release-openstack-python https://zuul.opendev.org/t/openstack/build/652843f2641e47d781264a815a14894d : POST_FAILURE in 2m 54s
During the release job for ansible-role-redhat-subscription 1.1.1, twine upload to PyPI failed with: HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/ The description failed to render in the default format of reStructuredText. See https://pypi.org/help/#description-content-type for more information. It's weird because it looks like this was addressed about a year ago, and nothing significant changed in that area in the months following 1.1.0 release. Current status: Tag was pushed OK No tarball upload No PyPI upload Once the issue is fixed, the tag reference should be reenqueued. -- Thierry Carrez (ttx)
On Thu, Nov 5, 2020 at 1:03 PM Thierry Carrez <thierry@openstack.org> wrote:
zuul@openstack.org wrote:
- release-openstack-python https://zuul.opendev.org/t/openstack/build/652843f2641e47d781264a815a14894d : POST_FAILURE in 2m 54s
During the release job for ansible-role-redhat-subscription 1.1.1, twine upload to PyPI failed with:
HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/ The description failed to render in the default format of reStructuredText. See https://pypi.org/help/#description-content-type for more information.
It's weird because it looks like this was addressed about a year ago, and nothing significant changed in that area in the months following 1.1.0 release.
Hi Thierry, thanks for the update on that I would have missed it if you didn't send this mail. I am a bit confused though as you mentioned 1.1.0 here do you mean this is something to do with the ansible-role-redhat-subscription repo itself?
Current status: Tag was pushed OK No tarball upload No PyPI upload
Once the issue is fixed, the tag reference should be reenqueued.
Indeed I see the tag is pushed OK https://opendev.org/openstack/ansible-role-redhat-subscription/src/tag/1.1.1 - so with respect to the pypi upload is there something for us to investigate or are we waiting on a rerun of the job? thanks, marios
-- Thierry Carrez (ttx)
Marios Andreou wrote:
thanks for the update on that I would have missed it if you didn't send this mail.
This is actually in reaction to a release job failure email that I received, so that we discuss the solution on the list. There was no prior email on the topic.
I am a bit confused though as you mentioned 1.1.0 here do you mean this is something to do with the ansible-role-redhat-subscription repo itself?
The failure is linked to the content of the repository: basically, PyPI is rejecting how the README is specified. So it will likely require a patch to ansible-role-redhat-subscription itself, in which case we'd push a new tag (1.1.2). That said, it's unclear what the problem is, as the same problem was fixed[1] a year ago already and nothing really changed since the (successful) 1.1.0 publication. We'll explore more and let you know if there is anything you can help with :) [1] https://opendev.org/openstack/ansible-role-redhat-subscription/commit/fceb51... -- Thierry Carrez (ttx)
On Thu, Nov 5, 2020 at 3:24 PM Thierry Carrez <thierry@openstack.org> wrote:
Marios Andreou wrote:
thanks for the update on that I would have missed it if you didn't send this mail.
This is actually in reaction to a release job failure email that I received, so that we discuss the solution on the list. There was no prior email on the topic.
I am a bit confused though as you mentioned 1.1.0 here do you mean this is something to do with the ansible-role-redhat-subscription repo itself?
The failure is linked to the content of the repository: basically, PyPI is rejecting how the README is specified. So it will likely require a patch to ansible-role-redhat-subscription itself, in which case we'd push a new tag (1.1.2).
That said, it's unclear what the problem is, as the same problem was fixed[1] a year ago already and nothing really changed since the (successful) 1.1.0 publication. We'll explore more and let you know if there is anything you can help with :)
ack! Thank you much clearer for me now. If there is an update required then no problem we can address that and update with a newer tag
[1]
https://opendev.org/openstack/ansible-role-redhat-subscription/commit/fceb51...
-- Thierry Carrez (ttx)
I confirm the markdown issue was fixed 1 year ago [1] by myself and since 3 new versions of ansible-role-redhat-subscription have been released [2]. The markdown fix is embedded in the three releases: $ git tag --contains fceb51c66e 1.0.4 1.1.0 1.1.1 2 releases was successfully uploaded to pypi: - https://pypi.org/project/ansible-role-redhat-subscription/1.1.0/ - https://pypi.org/project/ansible-role-redhat-subscription/1.0.4/ I saw a couple of changes in your README and they seem to mix markdown and restructuredText [3], maybe it could explain this issue but these changes are also in previous versions: $ git tag --contains 0949f34ffb 1.0.3 1.0.4 1.1.0 1.1.1 Maybe pypa introduced more strict checks on their side since our last release... I tried to generate a PKG-INFO locally and everything seems ok. Also I didn't see any new bugs that seem related to this issue on the pypa side [4]. [1] https://opendev.org/openstack/ansible-role-redhat-subscription/commit/fceb51... [2] https://opendev.org/openstack/releases/commits/branch/master/deliverables/_i... [3] https://opendev.org/openstack/ansible-role-redhat-subscription/commit/0949f3... [4] https://github.com/search?q=org%3Apypa+The+description+failed+to+render+in+the+default+format+of+reStructuredText&type=issues Le jeu. 5 nov. 2020 à 14:26, Thierry Carrez <thierry@openstack.org> a écrit :
Marios Andreou wrote:
thanks for the update on that I would have missed it if you didn't send this mail.
This is actually in reaction to a release job failure email that I received, so that we discuss the solution on the list. There was no prior email on the topic.
I am a bit confused though as you mentioned 1.1.0 here do you mean this is something to do with the ansible-role-redhat-subscription repo itself?
The failure is linked to the content of the repository: basically, PyPI is rejecting how the README is specified. So it will likely require a patch to ansible-role-redhat-subscription itself, in which case we'd push a new tag (1.1.2).
That said, it's unclear what the problem is, as the same problem was fixed[1] a year ago already and nothing really changed since the (successful) 1.1.0 publication. We'll explore more and let you know if there is anything you can help with :)
[1]
https://opendev.org/openstack/ansible-role-redhat-subscription/commit/fceb51...
-- Thierry Carrez (ttx)
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE----- Le jeu. 5 nov. 2020 à 16:21, Marios Andreou <marios@redhat.com> a écrit :
On Thu, Nov 5, 2020 at 3:24 PM Thierry Carrez <thierry@openstack.org> wrote:
Marios Andreou wrote:
thanks for the update on that I would have missed it if you didn't send this mail.
This is actually in reaction to a release job failure email that I received, so that we discuss the solution on the list. There was no prior email on the topic.
I am a bit confused though as you mentioned 1.1.0 here do you mean this is something to do with the ansible-role-redhat-subscription repo itself?
The failure is linked to the content of the repository: basically, PyPI is rejecting how the README is specified. So it will likely require a patch to ansible-role-redhat-subscription itself, in which case we'd push a new tag (1.1.2).
That said, it's unclear what the problem is, as the same problem was fixed[1] a year ago already and nothing really changed since the (successful) 1.1.0 publication. We'll explore more and let you know if there is anything you can help with :)
ack! Thank you much clearer for me now. If there is an update required then no problem we can address that and update with a newer tag
[1]
https://opendev.org/openstack/ansible-role-redhat-subscription/commit/fceb51...
-- Thierry Carrez (ttx)
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
The weird thing is that the PyPI error message says: "The description failed to render in the default format of reStructuredText" while we specify: long_description_content_type='text/markdown' in setup.py. It looks like PyPI is ignoring our indication in setup.py, and therefore (accurately) reporting failure to render in RST. Herve Beraud wrote:
I confirm the markdown issue was fixed 1 year ago [1] by myself and since 3 new versions of ansible-role-redhat-subscription have been released [2].
The markdown fix is embedded in the three releases: $ git tag --contains fceb51c66e 1.0.4 1.1.0 1.1.1
2 releases was successfully uploaded to pypi: - https://pypi.org/project/ansible-role-redhat-subscription/1.1.0/ - https://pypi.org/project/ansible-role-redhat-subscription/1.0.4/
I saw a couple of changes in your README and they seem to mix markdown and restructuredText [3], maybe it could explain this issue but these changes are also in previous versions:
$ git tag --contains 0949f34ffb 1.0.3 1.0.4 1.1.0 1.1.1
Maybe pypa introduced more strict checks on their side since our last release...
I tried to generate a PKG-INFO locally and everything seems ok.
Also I didn't see any new bugs that seem related to this issue on the pypa side [4].
[1] https://opendev.org/openstack/ansible-role-redhat-subscription/commit/fceb51... [2] https://opendev.org/openstack/releases/commits/branch/master/deliverables/_i... [3] https://opendev.org/openstack/ansible-role-redhat-subscription/commit/0949f3... [4] https://github.com/search?q=org%3Apypa+The+description+failed+to+render+in+the+default+format+of+reStructuredText&type=issues
Le jeu. 5 nov. 2020 à 14:26, Thierry Carrez <thierry@openstack.org <mailto:thierry@openstack.org>> a écrit :
Marios Andreou wrote: > thanks for the update on that I would have missed it if you didn't send > this mail.
This is actually in reaction to a release job failure email that I received, so that we discuss the solution on the list. There was no prior email on the topic.
> I am a bit confused though as you mentioned 1.1.0 here do you > mean this is something to do with the ansible-role-redhat-subscription > repo itself?
The failure is linked to the content of the repository: basically, PyPI is rejecting how the README is specified. So it will likely require a patch to ansible-role-redhat-subscription itself, in which case we'd push a new tag (1.1.2).
That said, it's unclear what the problem is, as the same problem was fixed[1] a year ago already and nothing really changed since the (successful) 1.1.0 publication. We'll explore more and let you know if there is anything you can help with :)
[1] https://opendev.org/openstack/ansible-role-redhat-subscription/commit/fceb51...
-- Thierry Carrez (ttx)
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
Le jeu. 5 nov. 2020 à 16:21, Marios Andreou <marios@redhat.com <mailto:marios@redhat.com>> a écrit :
On Thu, Nov 5, 2020 at 3:24 PM Thierry Carrez <thierry@openstack.org <mailto:thierry@openstack.org>> wrote:
Marios Andreou wrote: > thanks for the update on that I would have missed it if you didn't send > this mail.
This is actually in reaction to a release job failure email that I received, so that we discuss the solution on the list. There was no prior email on the topic.
> I am a bit confused though as you mentioned 1.1.0 here do you > mean this is something to do with the ansible-role-redhat-subscription > repo itself?
The failure is linked to the content of the repository: basically, PyPI is rejecting how the README is specified. So it will likely require a patch to ansible-role-redhat-subscription itself, in which case we'd push a new tag (1.1.2).
That said, it's unclear what the problem is, as the same problem was fixed[1] a year ago already and nothing really changed since the (successful) 1.1.0 publication. We'll explore more and let you know if there is anything you can help with :)
ack! Thank you much clearer for me now. If there is an update required then no problem we can address that and update with a newer tag
[1] https://opendev.org/openstack/ansible-role-redhat-subscription/commit/fceb51...
-- Thierry Carrez (ttx)
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
-- Thierry Carrez (ttx)
I reported a related bug on pypa: https://github.com/pypa/warehouse/issues/8791 Le ven. 6 nov. 2020 à 13:49, Thierry Carrez <thierry@openstack.org> a écrit :
The weird thing is that the PyPI error message says:
"The description failed to render in the default format of reStructuredText"
while we specify:
long_description_content_type='text/markdown'
in setup.py. It looks like PyPI is ignoring our indication in setup.py, and therefore (accurately) reporting failure to render in RST.
Herve Beraud wrote:
I confirm the markdown issue was fixed 1 year ago [1] by myself and since 3 new versions of ansible-role-redhat-subscription have been released [2].
The markdown fix is embedded in the three releases: $ git tag --contains fceb51c66e 1.0.4 1.1.0 1.1.1
2 releases was successfully uploaded to pypi: - https://pypi.org/project/ansible-role-redhat-subscription/1.1.0/ - https://pypi.org/project/ansible-role-redhat-subscription/1.0.4/
I saw a couple of changes in your README and they seem to mix markdown and restructuredText [3], maybe it could explain this issue but these changes are also in previous versions:
$ git tag --contains 0949f34ffb 1.0.3 1.0.4 1.1.0 1.1.1
Maybe pypa introduced more strict checks on their side since our last release...
I tried to generate a PKG-INFO locally and everything seems ok.
Also I didn't see any new bugs that seem related to this issue on the pypa side [4].
[1]
https://opendev.org/openstack/ansible-role-redhat-subscription/commit/fceb51...
[2]
https://opendev.org/openstack/releases/commits/branch/master/deliverables/_i...
[3]
https://opendev.org/openstack/ansible-role-redhat-subscription/commit/0949f3...
[4]
Le jeu. 5 nov. 2020 à 14:26, Thierry Carrez <thierry@openstack.org <mailto:thierry@openstack.org>> a écrit :
Marios Andreou wrote: > thanks for the update on that I would have missed it if you didn't send > this mail.
This is actually in reaction to a release job failure email that I received, so that we discuss the solution on the list. There was no prior email on the topic.
> I am a bit confused though as you mentioned 1.1.0 here do you > mean this is something to do with the ansible-role-redhat-subscription > repo itself?
The failure is linked to the content of the repository: basically,
PyPI
is rejecting how the README is specified. So it will likely require a patch to ansible-role-redhat-subscription itself, in which case we'd push a new tag (1.1.2).
That said, it's unclear what the problem is, as the same problem was fixed[1] a year ago already and nothing really changed since the (successful) 1.1.0 publication. We'll explore more and let you know
if
there is anything you can help with :)
[1]
https://opendev.org/openstack/ansible-role-redhat-subscription/commit/fceb51...
-- Thierry Carrez (ttx)
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
Le jeu. 5 nov. 2020 à 16:21, Marios Andreou <marios@redhat.com <mailto:marios@redhat.com>> a écrit :
On Thu, Nov 5, 2020 at 3:24 PM Thierry Carrez <thierry@openstack.org <mailto:thierry@openstack.org>> wrote:
Marios Andreou wrote: > thanks for the update on that I would have missed it if you didn't send > this mail.
This is actually in reaction to a release job failure email that
I
received, so that we discuss the solution on the list. There was
no
prior email on the topic.
> I am a bit confused though as you mentioned 1.1.0 here do you > mean this is something to do with the ansible-role-redhat-subscription > repo itself?
The failure is linked to the content of the repository: basically, PyPI is rejecting how the README is specified. So it will likely require a patch to ansible-role-redhat-subscription itself, in which case we'd push a new tag (1.1.2).
That said, it's unclear what the problem is, as the same problem was fixed[1] a year ago already and nothing really changed since the (successful) 1.1.0 publication. We'll explore more and let you know if there is anything you can help with :)
ack! Thank you much clearer for me now. If there is an update required then no problem we can address that and update with a newer
tag
[1]
https://opendev.org/openstack/ansible-role-redhat-subscription/commit/fceb51...
-- Thierry Carrez (ttx)
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
-- Thierry Carrez (ttx)
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
On 2020-11-06 13:47:11 +0100 (+0100), Thierry Carrez wrote:
The weird thing is that the PyPI error message says:
"The description failed to render in the default format of reStructuredText"
while we specify:
long_description_content_type='text/markdown'
in setup.py. It looks like PyPI is ignoring our indication in setup.py, and therefore (accurately) reporting failure to render in RST. [...]
After nearly hitting bedrock, I think I've dug down far enough to figure this one out: Between the working and failing uploads, we switched our CI system to install the wheel module from distro packaging rather than from PyPI by default. Since the recent build was performed on an Ubuntu 18.04 LTS instance, it used the available python3-wheel 0.30.0-0.2 available there. As wheel did not introduce support for Python packaging metadata version 2.1 until its 0.31.0 release, the failing upload declared "Metadata-Version: 2.0" in the METADATA file. This seems to cause the "Description-Content-Type: text/markdown" line (first introduced in the metadata 2.1 specification) to be ignored and fall back to assuming the long description is in the reStructuredText default. I propose we switch release jobs to run on an ubuntu-focal nodeset, as most official OpenStack jobs did already during the Victoria cycle. This will result in using python3-wheel 0.34.2-1 which is plenty new enough to support the necessary metadata version. If for some reason running release jobs for older stable branches on a newer distro causes issues, we can try to make use of Zuul's new branch-guessing mechanism for Git tags to create job variants running stable point releases for older branches on the older nodeset. -- Jeremy Stanley
On 2020-11-06 17:35:21 +0000 (+0000), Jeremy Stanley wrote: [...]
I propose we switch release jobs to run on an ubuntu-focal nodeset, as most official OpenStack jobs did already during the Victoria cycle. [...]
Now up for review: https://review.opendev.org/761776 -- Jeremy Stanley
On 2020-11-06 17:50:52 +0000 (+0000), Jeremy Stanley wrote:
On 2020-11-06 17:35:21 +0000 (+0000), Jeremy Stanley wrote: [...]
I propose we switch release jobs to run on an ubuntu-focal nodeset, as most official OpenStack jobs did already during the Victoria cycle. [...]
Now up for review: https://review.opendev.org/761776
This seems to have solved the problem. We also observed successful releases for the nova repository, including stable point releases for stable/stein and stable/train, so this presumably hasn't broken more common cases. -- Jeremy Stanley
From the release management side I confirm that this fix solved the problem, ansible-role-redhat-subscription 1.1.1 have been re-enqueued and successfully released on pypi [1].
Thanks Jeremy for all things done on this topic. [1] https://pypi.org/project/ansible-role-redhat-subscription/#history Le lun. 9 nov. 2020 à 14:52, Jeremy Stanley <fungi@yuggoth.org> a écrit :
On 2020-11-06 17:50:52 +0000 (+0000), Jeremy Stanley wrote:
On 2020-11-06 17:35:21 +0000 (+0000), Jeremy Stanley wrote: [...]
I propose we switch release jobs to run on an ubuntu-focal nodeset, as most official OpenStack jobs did already during the Victoria cycle. [...]
Now up for review: https://review.opendev.org/761776
This seems to have solved the problem. We also observed successful releases for the nova repository, including stable point releases for stable/stein and stable/train, so this presumably hasn't broken more common cases. -- Jeremy Stanley
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
participants (4)
-
Herve Beraud
-
Jeremy Stanley
-
Marios Andreou
-
Thierry Carrez