# apt update
Get:2 http://nova.clouds.archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Hit:3 http://security.ubuntu.com/ubuntu jammy-security InRelease
[...]
Get:7 https://artifacts.elastic.co/packages/8.x/apt stable InRelease [3,255 B]
Hit:8 http://nova.clouds.archive.ubuntu.com/ubuntu jammy-backports InRelease
[...]
E: Repository 'https://artifacts.elastic.co/packages/8.x/apt stable InRelease' changed its 'Origin' value from 'elastic' to 'Artifactory'
E: Repository 'https://artifacts.elastic.co/packages/8.x/apt stable InRelease' changed its 'Label' value from '. stable' to 'Artifactory'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N]
Seeing the same here, and it's breaking all my ansible plays.. would be good to get clarification on whether this change is here to stay or if it's an accident.
this is causing us a customer-facing outage since we run apt-get update in userdata scripts and are using the elastic apt repo. c'mon guys, fix your stuff.
RH Satellite 6.16.1 with the repo's added for Elastic 7 and Elastic 8. Both with the same key I got from the docs this morning.
The Elastic7 repo is syncing OK, while the Elastic 8 repo fails, so the key is OK too afaik.
I'm afraid Rhel 6 is not supported starting with 8.0.0 see Support Matrix | Elastic so we are not testing the repos against this version. I'll double check that we have no issues with a pre-configured repository for a newer version just to be sure
Sorry, but we are not using rhel 6. We are using RH Satellite 6.16.1 on RHEL 9.
To be more clear, I have an older satellite 6.11 on rhel 7 which also had problems with this repo today. However, the last attempt, a few mins ago succeeded. The newer satellite I am building still does not, but since the older satellite succeed,, I will consider it my problem now
Thnx for the replies.
As for the confusion, Satellite is widely know with companies as the primairy way to maintain and provision their RedHat systems. It currently is on version 6.16 which is not to be confused with rhel6 .
It seems to still be a problem with the upstream repositories. We have the same issue from Satellite 6.15 on RHEL8 and Satellite 6.16 on RHEL9. The following URLs all return 404 (Not Found):
Also note that we have had the 8.x yum repo working with Satellite 6.16 until a week or two ago, so there must have been some changes to the upstream repository that causes the repository sync to fail now.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.