Hi,
https://filedump.ceph.com/ceph/ <https://filedump.ceph.com/ceph/>
has been unavailable again for the past few days. Is this a known
issue?
Thanks,
Lucian
*From: *Dan Mick <mailto:dmick@xxxxxxxxxx>
*Sent: *Wednesday, December 21, 2022 1:05 PM
*To: *dev@xxxxxxx <mailto:dev@xxxxxxx>
*Subject: *Re: filedump.ceph.com down, affecting Windows CI job
It appears as though the read access through
https://filedump.ceph.com/ceph/ <https://filedump.ceph.com/ceph/>
has been restored. I believe the
ssh/scp access from the jenkins server also should work, so that new
Windows builds should be able to drop their artifacts in the expected
places.
Still have to work out the details of sftp to drop.ceph.com for
ceph-post-file etc., but the Windows builds should be working again.
On 12/19/2022 1:10 PM, Dan Mick wrote:
> It has been a battle trying to get the OCP cluster to behave.
Containers
> don't work because you can't add another external Ceph cluster. VMs
> don't work because whenever you define one with a second NIC it just
> fails to come up with no error messages.
>
> We've also recently lost the FOG reimaging server in the lab
(more RHEV
> unexplained damage) and are scrambling to get it running on a
physical
> machine. Had that been done as it appeared this morning, my next
task
> was to bring up a replacement filedump on that physical machine,
but it
> appears that there are still issues there (which affect all of Ceph
> testing on all releases), so, sadly, that's my priority today.
>
> I know this is frustrating. You should see it from my side.
I'll be
> sure to let you know on this forum when it's resolved.
>
> On 12/19/2022 3:00 AM, Lucian Petrut wrote:
>> Hi,
>>
>> I was wondering if there’s been any progress on this. Can we please
>> get read-only access at least?
>>
>> I’m a bit concerned since we’re getting close to the feature
freeze /
>> branch cut and we have quite a few Windows related PRs that are
stalling.
>>
>> Thanks,
>>
>> Lucian
>>
>> *From: *Lucian Petrut <mailto:lpetrut@xxxxxxxxxxxxxxxxxxxxxx
<mailto:lpetrut@xxxxxxxxxxxxxxxxxxxxxx>>
>> *Sent: *Wednesday, December 7, 2022 9:19 AM
>> *To: *Dan Mick <mailto:dmick@xxxxxxxxxx
<mailto:dmick@xxxxxxxxxx>>; dev@xxxxxxx
>> <mailto:dev@xxxxxxx <mailto:dev@xxxxxxx>>
>> *Subject: *RE: filedump.ceph.com down, affecting Windows CI job
>>
>> Hi,
>>
>> We don’t need to update the Windows image very often, so read-only
>> access would be enough for the time being, assuming that the
previous
>> image is still there.
>>
>> Thanks a lot,
>>
>> Lucian
>>
>> *From: *Dan Mick <mailto:dmick@xxxxxxxxxx
<mailto:dmick@xxxxxxxxxx>>
>> *Sent: *Wednesday, December 7, 2022 12:26 AM
>> *To: *dev@xxxxxxx <mailto:dev@xxxxxxx <mailto:dev@xxxxxxx>>
>> *Subject: *Re: filedump.ceph.com down, affecting Windows CI job
>>
>> filedump is being worked. We could bring up the http access to
read
>> files, but I'm assuming you need to be able to write them as
well (to
>> use as a transfer from Jenkins to the test runs). Let me know if
>> readonly access would help, because we could probably get that
working
>> marginally sooner.
>>
>> Regardless I'm hoping to solve the issues in a matter of days.
>>
>>
>> On 12/6/2022 5:55 AM, Gregory Farnum wrote:
>> > Adding sepia list. I know those were on the list to rebuild
after the
>> > lab outage.
>> >
>> > On Tue, Dec 6, 2022 at 4:37 AM Lucian Petrut
>> > <lpetrut@xxxxxxxxxxxxxxxxxxxxxx
>> <mailto:lpetrut@xxxxxxxxxxxxxxxxxxxxxx
>> <mailto:lpetrut@xxxxxxxxxxxxxxxxxxxxxx
<mailto:lpetrut@xxxxxxxxxxxxxxxxxxxxxx>>>>
>> > wrote:
>> >
>> > Hi,
>> >
>> > The Windows CI job has been down for the past few weeks
because of
>> > filedump.ceph.com <http://filedump.ceph.com
>> <http://filedump.ceph.com <http://filedump.ceph.com>>> /
>> > drop.front.sepia.ceph.com <http://drop.front.sepia.ceph.com
>> <http://drop.front.sepia.ceph.com
<http://drop.front.sepia.ceph.com>>>, which
>> > is inaccessible.
>> >
>> > I'd need a little help since we don't have access to that
>> environment.
>> > The Windows VM image used by the CI job is stored there
[1][2][3].
>> >
>> > I'm a bit concerned since we're now seeing breaking
changes [4]
>> and we
>> > have a growing pile of Windows PRs, some of which have been
>> waiting for
>> > a while [5].
>> >
>> > Thanks,
>> > Lucian
>> >
>> > [1]
>> >
>>
https://github.com/ceph/ceph-build/blob/2e957bc220b68744bfff53af87bbbbc0bc9f019a/ceph-windows-image-build/build/build#L199
<https://github.com/ceph/ceph-build/blob/2e957bc220b68744bfff53af87bbbbc0bc9f019a/ceph-windows-image-build/build/build#L199>
<https://github.com/ceph/ceph-build/blob/2e957bc220b68744bfff53af87bbbbc0bc9f019a/ceph-windows-image-build/build/build#L199
<https://github.com/ceph/ceph-build/blob/2e957bc220b68744bfff53af87bbbbc0bc9f019a/ceph-windows-image-build/build/build#L199>>
<https://github.com/ceph/ceph-build/blob/2e957bc220b68744bfff53af87bbbbc0bc9f019a/ceph-windows-image-build/build/build#L199
<https://github.com/ceph/ceph-build/blob/2e957bc220b68744bfff53af87bbbbc0bc9f019a/ceph-windows-image-build/build/build#L199
<https://github.com/ceph/ceph-build/blob/2e957bc220b68744bfff53af87bbbbc0bc9f019a/ceph-windows-image-build/build/build#L199>>>
>> > [2]
>> >
>>
https://github.com/ceph/ceph-build/blob/main/scripts/ceph-windows/setup_libvirt_windows_vm#L7
<https://github.com/ceph/ceph-build/blob/main/scripts/ceph-windows/setup_libvirt_windows_vm#L7>
<https://github.com/ceph/ceph-build/blob/main/scripts/ceph-windows/setup_libvirt_windows_vm#L7
<https://github.com/ceph/ceph-build/blob/main/scripts/ceph-windows/setup_libvirt_windows_vm#L7>>
<https://github.com/ceph/ceph-build/blob/main/scripts/ceph-windows/setup_libvirt_windows_vm#L7
<https://github.com/ceph/ceph-build/blob/main/scripts/ceph-windows/setup_libvirt_windows_vm#L7
<https://github.com/ceph/ceph-build/blob/main/scripts/ceph-windows/setup_libvirt_windows_vm#L7>>>
>> > [3]
>> >
https://jenkins.ceph.com/view/Windows/job/ceph-windows-image-build/
<https://jenkins.ceph.com/view/Windows/job/ceph-windows-image-build/>
>>
<https://jenkins.ceph.com/view/Windows/job/ceph-windows-image-build/
<https://jenkins.ceph.com/view/Windows/job/ceph-windows-image-build/>>
>> >
>>
<https://jenkins.ceph.com/view/Windows/job/ceph-windows-image-build/
>>
<https://jenkins.ceph.com/view/Windows/job/ceph-windows-image-build/
<https://jenkins.ceph.com/view/Windows/job/ceph-windows-image-build/>>>
>> > [4] https://github.com/ceph/ceph/pull/49277
<https://github.com/ceph/ceph/pull/49277>
>> <https://github.com/ceph/ceph/pull/49277
<https://github.com/ceph/ceph/pull/49277>>
>> > <https://github.com/ceph/ceph/pull/49277
>> <https://github.com/ceph/ceph/pull/49277
<https://github.com/ceph/ceph/pull/49277>>>
>> > [5]
>> >
>>
https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+label%3Awin32
<https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+label%3Awin32>
>>
<https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+label%3Awin32
<https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+label%3Awin32>>
>> >
>>
<https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+label%3Awin32
>>
<https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+label%3Awin32
<https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+label%3Awin32>>>
>> >
>> >
>> > _______________________________________________
>> > Dev mailing list -- dev@xxxxxxx <mailto:dev@xxxxxxx
>> <mailto:dev@xxxxxxx <mailto:dev@xxxxxxx>>>
>> > To unsubscribe send an email to dev-leave@xxxxxxx
>> > <mailto:dev-leave@xxxxxxx <mailto:dev-leave@xxxxxxx
<mailto:dev-leave@xxxxxxx>>>
>> >
>> >
>> > _______________________________________________
>> > Dev mailing list -- dev@xxxxxxx
>> > To unsubscribe send an email to dev-leave@xxxxxxx
>>
>> _______________________________________________
>> Dev mailing list -- dev@xxxxxxx
>> To unsubscribe send an email to dev-leave@xxxxxxx
>>
>>
>> _______________________________________________
>> Dev mailing list -- dev@xxxxxxx
>> To unsubscribe send an email to dev-leave@xxxxxxx
>
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
