Bug#932101: release-notes: S3QL unable to resolve hostname due to S3 URL format change

[Shannon Dealy]

Package: release-notes
Severity: normal

Dear Maintainer,

After upgrading from Stretch to Buster, I was unable to use S3QL with any of
my Amazon S3 buckets. All attempts to access gave errors like:

ERROR: Can't connect to backend: unable to resolve hostname

I was eventually able to track the problem down to a change in the format
of the Amazon S3 URL which occurred two years ago. The new format of the
URL is:

s3://<region>/<bucket>/<prefix>

Note the addition of a "region" section in the URL.

Unfortunately this change is not displayed by "apt-listchanges" during the
upgrade, nor is it documented in the release notes.

Please add this information to the release notes for Buster so that others
don't waste hours trying to figure it out.


-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[Paul Gevers]

Control: tags -1 patch

Hi

Post by Shannon Dealy
After upgrading from Stretch to Buster, I was unable to use S3QL with any of
ERROR: Can't connect to backend: unable to resolve hostname
I was eventually able to track the problem down to a change in the format
of the Amazon S3 URL which occurred two years ago. The new format of the
s3://<region>/<bucket>/<prefix>
Note the addition of a "region" section in the URL.
Unfortunately this change is not displayed by "apt-listchanges" during the
upgrade, nor is it documented in the release notes.
Please add this information to the release notes for Buster so that others
don't waste hours trying to figure it out.

So, something along the following lines should work?

<section id="s3ql">
<!-- stretch to buster -->
<title>
S3QL URL changes for Amazon S3 buckets
</title>
<para>
When using <systemitem role="package">s3ql</systemitem> with
Amazon S3 buckets, the configuration needs updating for a change
in the URL. The new format is: <programlisting>s3://&lt;region&gt;/&lt;bucket&gt;/&lt;prefix&gt;</programlisting>
</para>
</section>

Paul

[Debian Bug Tracking System]

Post by Paul Gevers
tags -1 patch

Bug #932101 [release-notes] release-notes: S3QL unable to resolve hostname due to S3 URL format change
Added tag(s) patch.

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 21:21:36 +0200
with message-id <2e905e6b-633b-d7b4-9ec1-***@debian.org>
and subject line Re: Bug#932101: release-notes: S3QL unable to resolve hostname due to S3 URL format change
has caused the Debian Bug report #932101,
regarding release-notes: S3QL unable to resolve hostname due to S3 URL format change
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)