You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by Yuepeng Pan <hi...@gmail.com> on 2026/04/19 05:51:16 UTC
Help Needed - About 2.3 Release: S3 Missing flink‑2.4‑SNAPSHOT Binaries Causing flink-docker CI Failure
Hi, community.
When the RMs were advancing the rolling upgrade of the flink‑2.4‑SNAPSHOT
[1] version for the flink‑docker repository’s dev‑master branch, we
encountered a CI failure [2].
We conducted a preliminary investigation and believe the likely cause is
that the resource flink‑2.4‑SNAPSHOT‑bin‑scala_2.12.tgz does not exist in
the S3 path.
This is because the flink‑2.4‑SNAPSHOT [3] resource cannot be downloaded,
whereas the flink‑2.3‑SNAPSHOT [4] resource is accessible.
However, I'm not familiar with how the latest SNAPSHOT version tgz file
from the main Flink repository is uploaded to the S3 file system.
Could someone help on this issue?
Thank you very much !
[1] https://github.com/apache/flink-docker/pull/248
[2]
https://github.com/apache/flink-docker/actions/runs/24569669345/job/71839037545?pr=248
[3]
https://s3.amazonaws.com/flink-nightly/flink-2.4-SNAPSHOT-bin-scala_2.12.tgz
[4]
https://s3.amazonaws.com/flink-nightly/flink-2.3-SNAPSHOT-bin-scala_2.12.tgz
Best regards,
Yuepeng Pan.
Re: Help Needed - About 2.3 Release: S3 Missing flink‑2.4‑SNAPSHOT Binaries Causing flink-docker CI Failure
Posted by Yuepeng Pan <hi...@gmail.com>.
Thank you Matthias Pohl, Sergey Nuyanzin and Qingsheng Ren very much!
Best regards,
Yuepeng Pan.
Sergey Nuyanzin <sn...@gmail.com> 于2026年4月24日周五 06:50写道：
> Right now there is issue with nightly: they are not running for some
> releases, I create an issue for that
> https://issues.apache.org/jira/browse/FLINK-39496
>
> we had similar issues in past (see link in mentioned issue)
> I already chatted with Qingsheng Ren who is looking into it
>
> On Wed, Apr 22, 2026 at 2:47 PM Matthias Pohl <ma...@apache.org> wrote:
> >
> > Hi Yuepeng,
> > There is a general problem with the CI pipeline. Sergey (CC'd) also runs
> > into issues with it for the minor releases he planned to roll out.
> >
> > The nightly builds [1] seem to miss uploading snapshot versions which
> > probably causes the missing binaries.
> >
> > Looking back into nightly runs: master [2] seems to not upload anything
> (no
> > files are listed in the logs).
> > Compare the most-recent release-2.1 CI run [3], where binary file uploads
> > are occurring.
> >
> > Looks like we didn't upload any snapshot version for 2.4, yet?
> >
> > Apparently, there is an issue with the VMs that the CI agents are running
> > on. Sergey can provide more insights here, I guess.
> >
> > Best,
> > Matthias
> >
> > [1]
> >
> https://dev.azure.com/apache-flink/apache-flink/_build?definitionId=1&_a=summary
> > [2]
> >
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=74339&view=logs&j=585d8b77-fa33-51bc-8163-03e54ba9ce5b&t=2f31de30-3dd6-5bd6-d86d-dcdc2d7cc3de&l=26
> > [3]
> >
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=74230&view=logs&j=585d8b77-fa33-51bc-8163-03e54ba9ce5b&t=2f31de30-3dd6-5bd6-d86d-dcdc2d7cc3de&l=27
> >
> > On Tue, Apr 21, 2026 at 9:28 AM Yuepeng Pan <pa...@apache.org>
> wrote:
> >
> > > Bumping this thread. Thanks!
> > >
> > > Best regards,
> > > Yuepeng Pan
> > >
> > >
> > >
> > > On 2026/04/19 05:51:16 Yuepeng Pan wrote:
> > > > Hi, community.
> > > >
> > > > When the RMs were advancing the rolling upgrade of the
> flink‑2.4‑SNAPSHOT
> > > > [1] version for the flink‑docker repository’s dev‑master branch, we
> > > > encountered a CI failure [2].
> > > > We conducted a preliminary investigation and believe the likely
> cause is
> > > > that the resource flink‑2.4‑SNAPSHOT‑bin‑scala_2.12.tgz does not
> exist in
> > > > the S3 path.
> > > > This is because the flink‑2.4‑SNAPSHOT [3] resource cannot be
> downloaded,
> > > > whereas the flink‑2.3‑SNAPSHOT [4] resource is accessible.
> > > >
> > > > However, I'm not familiar with how the latest SNAPSHOT version tgz
> file
> > > > from the main Flink repository is uploaded to the S3 file system.
> > > >
> > > > Could someone help on this issue?
> > > >
> > > >
> > > > Thank you very much !
> > > >
> > > >
> > > > [1] https://github.com/apache/flink-docker/pull/248
> > > > [2]
> > > >
> > >
> https://github.com/apache/flink-docker/actions/runs/24569669345/job/71839037545?pr=248
> > > > [3]
> > > >
> > >
> https://s3.amazonaws.com/flink-nightly/flink-2.4-SNAPSHOT-bin-scala_2.12.tgz
> > > > [4]
> > > >
> > >
> https://s3.amazonaws.com/flink-nightly/flink-2.3-SNAPSHOT-bin-scala_2.12.tgz
> > > >
> > > > Best regards,
> > > > Yuepeng Pan.
> > > >
> > >
>
>
>
> --
> Best regards,
> Sergey
>
Re: Help Needed - About 2.3 Release: S3 Missing flink‑2.4‑SNAPSHOT Binaries Causing flink-docker CI Failure
Posted by Sergey Nuyanzin <sn...@gmail.com>.
Right now there is issue with nightly: they are not running for some
releases, I create an issue for that
https://issues.apache.org/jira/browse/FLINK-39496
we had similar issues in past (see link in mentioned issue)
I already chatted with Qingsheng Ren who is looking into it
On Wed, Apr 22, 2026 at 2:47 PM Matthias Pohl <ma...@apache.org> wrote:
>
> Hi Yuepeng,
> There is a general problem with the CI pipeline. Sergey (CC'd) also runs
> into issues with it for the minor releases he planned to roll out.
>
> The nightly builds [1] seem to miss uploading snapshot versions which
> probably causes the missing binaries.
>
> Looking back into nightly runs: master [2] seems to not upload anything (no
> files are listed in the logs).
> Compare the most-recent release-2.1 CI run [3], where binary file uploads
> are occurring.
>
> Looks like we didn't upload any snapshot version for 2.4, yet?
>
> Apparently, there is an issue with the VMs that the CI agents are running
> on. Sergey can provide more insights here, I guess.
>
> Best,
> Matthias
>
> [1]
> https://dev.azure.com/apache-flink/apache-flink/_build?definitionId=1&_a=summary
> [2]
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=74339&view=logs&j=585d8b77-fa33-51bc-8163-03e54ba9ce5b&t=2f31de30-3dd6-5bd6-d86d-dcdc2d7cc3de&l=26
> [3]
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=74230&view=logs&j=585d8b77-fa33-51bc-8163-03e54ba9ce5b&t=2f31de30-3dd6-5bd6-d86d-dcdc2d7cc3de&l=27
>
> On Tue, Apr 21, 2026 at 9:28 AM Yuepeng Pan <pa...@apache.org> wrote:
>
> > Bumping this thread. Thanks!
> >
> > Best regards,
> > Yuepeng Pan
> >
> >
> >
> > On 2026/04/19 05:51:16 Yuepeng Pan wrote:
> > > Hi, community.
> > >
> > > When the RMs were advancing the rolling upgrade of the flink‑2.4‑SNAPSHOT
> > > [1] version for the flink‑docker repository’s dev‑master branch, we
> > > encountered a CI failure [2].
> > > We conducted a preliminary investigation and believe the likely cause is
> > > that the resource flink‑2.4‑SNAPSHOT‑bin‑scala_2.12.tgz does not exist in
> > > the S3 path.
> > > This is because the flink‑2.4‑SNAPSHOT [3] resource cannot be downloaded,
> > > whereas the flink‑2.3‑SNAPSHOT [4] resource is accessible.
> > >
> > > However, I'm not familiar with how the latest SNAPSHOT version tgz file
> > > from the main Flink repository is uploaded to the S3 file system.
> > >
> > > Could someone help on this issue?
> > >
> > >
> > > Thank you very much !
> > >
> > >
> > > [1] https://github.com/apache/flink-docker/pull/248
> > > [2]
> > >
> > https://github.com/apache/flink-docker/actions/runs/24569669345/job/71839037545?pr=248
> > > [3]
> > >
> > https://s3.amazonaws.com/flink-nightly/flink-2.4-SNAPSHOT-bin-scala_2.12.tgz
> > > [4]
> > >
> > https://s3.amazonaws.com/flink-nightly/flink-2.3-SNAPSHOT-bin-scala_2.12.tgz
> > >
> > > Best regards,
> > > Yuepeng Pan.
> > >
> >
--
Best regards,
Sergey
Re: Help Needed - About 2.3 Release: S3 Missing flink‑2.4‑SNAPSHOT Binaries Causing flink-docker CI Failure
Posted by Matthias Pohl <ma...@apache.org>.
Hi Yuepeng,
There is a general problem with the CI pipeline. Sergey (CC'd) also runs
into issues with it for the minor releases he planned to roll out.
The nightly builds [1] seem to miss uploading snapshot versions which
probably causes the missing binaries.
Looking back into nightly runs: master [2] seems to not upload anything (no
files are listed in the logs).
Compare the most-recent release-2.1 CI run [3], where binary file uploads
are occurring.
Looks like we didn't upload any snapshot version for 2.4, yet?
Apparently, there is an issue with the VMs that the CI agents are running
on. Sergey can provide more insights here, I guess.
Best,
Matthias
[1]
https://dev.azure.com/apache-flink/apache-flink/_build?definitionId=1&_a=summary
[2]
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=74339&view=logs&j=585d8b77-fa33-51bc-8163-03e54ba9ce5b&t=2f31de30-3dd6-5bd6-d86d-dcdc2d7cc3de&l=26
[3]
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=74230&view=logs&j=585d8b77-fa33-51bc-8163-03e54ba9ce5b&t=2f31de30-3dd6-5bd6-d86d-dcdc2d7cc3de&l=27
On Tue, Apr 21, 2026 at 9:28 AM Yuepeng Pan <pa...@apache.org> wrote:
> Bumping this thread. Thanks!
>
> Best regards,
> Yuepeng Pan
>
>
>
> On 2026/04/19 05:51:16 Yuepeng Pan wrote:
> > Hi, community.
> >
> > When the RMs were advancing the rolling upgrade of the flink‑2.4‑SNAPSHOT
> > [1] version for the flink‑docker repository’s dev‑master branch, we
> > encountered a CI failure [2].
> > We conducted a preliminary investigation and believe the likely cause is
> > that the resource flink‑2.4‑SNAPSHOT‑bin‑scala_2.12.tgz does not exist in
> > the S3 path.
> > This is because the flink‑2.4‑SNAPSHOT [3] resource cannot be downloaded,
> > whereas the flink‑2.3‑SNAPSHOT [4] resource is accessible.
> >
> > However, I'm not familiar with how the latest SNAPSHOT version tgz file
> > from the main Flink repository is uploaded to the S3 file system.
> >
> > Could someone help on this issue?
> >
> >
> > Thank you very much !
> >
> >
> > [1] https://github.com/apache/flink-docker/pull/248
> > [2]
> >
> https://github.com/apache/flink-docker/actions/runs/24569669345/job/71839037545?pr=248
> > [3]
> >
> https://s3.amazonaws.com/flink-nightly/flink-2.4-SNAPSHOT-bin-scala_2.12.tgz
> > [4]
> >
> https://s3.amazonaws.com/flink-nightly/flink-2.3-SNAPSHOT-bin-scala_2.12.tgz
> >
> > Best regards,
> > Yuepeng Pan.
> >
>
Re: Help Needed - About 2.3 Release: S3 Missing flink‑2.4‑SNAPSHOT Binaries Causing flink-docker CI Failure
Posted by Yuepeng Pan <pa...@apache.org>.
Bumping this thread. Thanks!
Best regards,
Yuepeng Pan
On 2026/04/19 05:51:16 Yuepeng Pan wrote:
> Hi, community.
>
> When the RMs were advancing the rolling upgrade of the flink‑2.4‑SNAPSHOT
> [1] version for the flink‑docker repository’s dev‑master branch, we
> encountered a CI failure [2].
> We conducted a preliminary investigation and believe the likely cause is
> that the resource flink‑2.4‑SNAPSHOT‑bin‑scala_2.12.tgz does not exist in
> the S3 path.
> This is because the flink‑2.4‑SNAPSHOT [3] resource cannot be downloaded,
> whereas the flink‑2.3‑SNAPSHOT [4] resource is accessible.
>
> However, I'm not familiar with how the latest SNAPSHOT version tgz file
> from the main Flink repository is uploaded to the S3 file system.
>
> Could someone help on this issue?
>
>
> Thank you very much !
>
>
> [1] https://github.com/apache/flink-docker/pull/248
> [2]
> https://github.com/apache/flink-docker/actions/runs/24569669345/job/71839037545?pr=248
> [3]
> https://s3.amazonaws.com/flink-nightly/flink-2.4-SNAPSHOT-bin-scala_2.12.tgz
> [4]
> https://s3.amazonaws.com/flink-nightly/flink-2.3-SNAPSHOT-bin-scala_2.12.tgz
>
> Best regards,
> Yuepeng Pan.
>