Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debian packaging test failure #42017

Closed
davidkyle opened this issue May 9, 2019 · 1 comment · Fixed by #42056
Closed

Debian packaging test failure #42017

davidkyle opened this issue May 9, 2019 · 1 comment · Fixed by #42056
Assignees
Labels
:Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@davidkyle
Copy link
Member

https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+packaging-tests/762/console
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+packaging-tests/349/console

Task :qa:vagrant:vagrantDebian8#up

Process 'vagrant [up, debian-8, --provision, --provider, virtualbox]' finished with non-zero exit value 1

debian-8: WARNING: The following packages cannot be authenticated!
debian-8:   lintian
debian-8: E: There are problems and -y was used without --force-yes
@davidkyle davidkyle added :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts >test-failure Triaged test failures from CI labels May 9, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@rjernst rjernst self-assigned this May 9, 2019
rjernst added a commit to rjernst/elasticsearch that referenced this issue May 10, 2019
On debian-8, when trying to apt-get update, it currently (sometimes)
fails on one of the extra repositories. This failure to update causes
keys to not be updated, which later can cause some packages to not
install due to lack of key verification. This commit removes the
troublesome repository before we attemp to update.

closes elastic#42017
rjernst added a commit that referenced this issue May 10, 2019
On debian-8, when trying to apt-get update, it currently (sometimes)
fails on one of the extra repositories. This failure to update causes
keys to not be updated, which later can cause some packages to not
install due to lack of key verification. This commit removes the
troublesome repository before we attemp to update.

closes #42017
rjernst added a commit that referenced this issue May 10, 2019
On debian-8, when trying to apt-get update, it currently (sometimes)
fails on one of the extra repositories. This failure to update causes
keys to not be updated, which later can cause some packages to not
install due to lack of key verification. This commit removes the
troublesome repository before we attemp to update.

closes #42017
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this issue May 27, 2019
On debian-8, when trying to apt-get update, it currently (sometimes)
fails on one of the extra repositories. This failure to update causes
keys to not be updated, which later can cause some packages to not
install due to lack of key verification. This commit removes the
troublesome repository before we attemp to update.

closes elastic#42017
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants