Package: cloud.debian.org
Severity: important
User: cloud.debian@packages.debian.org
Usertags: aws image
Testing the current buster releases for [mcr]6gd.* instance type support
reveals an issue that leads the instances to boot to "degraded" state in
systemd. The failing unit is
Actually, the problem seems to have been caused by
https://salsa.debian.org/cloud-team/debian-cloud-images/-/merge_requests/192/
Prior to that MR, we weren't using systemd-growfs at all.
I've confirmed impact on amd64 instances as well as the arm64 instances
on which originally observed it. It
Having done a bit of testing, this definitely seems to be a regression.
I've launched 63 instances of the 10.3 AMI in us-east-1
(ami-031d1abcdcbbfbd8f) and 63 of the current 10.4 AMI
(ami-0bb15d03913335eae) on a variety of 6g arm64 instance types. Exacly
zero of the 10.3 launches ended up in
On Mon, Jul 27, 2020 at 01:37:14PM +0100, Steve McIntyre wrote:
> >Recent directories in https://cloud.debian.org/images/cloud/buster/daily/
> >became inaccessible. E.g.
> >
> > https://cloud.debian.org/images/cloud/buster/daily/20200717-330/
> >
> >still works, but
>
Control: tags -1 + moreinfo
> The buster arm64 images in us-east-2 don't seem to come online - ping and ssh
> fail. The ec2 status checks pass, but take unusually long to get there. I
> tried a1 and c6g instances. There's nothing in the system log output, and no
> screenshots on arm64.
>
> I
On Thu, Jul 30, 2020 at 09:08:15PM +0200, Geert Stappers wrote:
> > Thank you for information Bastian.
> > I understand that there will be no new Debian 8 cloud images releases
> > but is there any chance that previous cloud images releases for Debian 8
> > will be available in Azure for some
On Thu, Jul 30, 2020 at 11:39:13PM +0200, Bastian Blank wrote:
> > IMO we should not be taking down published images except in cases where
> > we need to for some compelling reason like legal obligations. Doing so
> > risks confusion for our users, or worse, outright breakage, and that
> > leads
On Thu, Jul 30, 2020 at 10:12:54PM +0200, Franck Hamelin wrote:
>
> Installation the amazon way is easy but probably not in line with the idea of
> Debian packaging system. So my question is : what are the plan for AWS CLI V2
> on Debian ?
>
You're the second one to ask about this recently,
I just uploaded cloud-init 20.4 to unstable. It'll be included in the
nightly sid cloud image builds that we publish in the next day or so.
If you can, please try launching one of them in whatever cloud
environment you can, with whatever bits of userdata configuration you
can throw at them. File
Control: tags -1 + moreinfo
On Sun, Nov 29, 2020 at 03:04:20PM -0300, eingousef wrote:
> I followed the documentation here :
> https://www.scaleway.com/en/docs/object-storage-with-aws-cli/
These have you installing python packages using pip. That's not part of
Debian. What are the exact steps
On Wed, Oct 28, 2020 at 04:58:55PM -0700, Paul Graydon wrote:
> Okay, I'm getting confused here. These restrictions don't seem to match
> with the previous message, so I'm assuming I misunderstood something. I
> think this may hinge around what is meant by "official" images.
Official images are
On Tue, Oct 27, 2020 at 09:58:05AM -0700, Paul Graydon wrote:
> > If you are considering installations directly from the Deb package, how
> > do you consider the client software update procedure when the virtual
> > machine has been running for a while? Snapd has a built-in mechanism for
> >
On Mon, Jan 04, 2021 at 09:53:52AM +0900, Charles Plessy wrote:
> I am used to start building Singularity (https://sylabs.io/) images
> starting from Docker images, but the Debian images on Docker have not
> been updated for a while...
The Docker images should be actively maintained. CCing
On Tue, Jan 26, 2021 at 01:33:18PM +0300, Alexander Gerasiov wrote:
> New version (1.19) of python-botocore were releases last fall and
> brought some new API features we lack off.
>
> Would you mind to update package in bullseye?
Unfortunately, I believe it's too late to update botocore in
On Tue, Jan 26, 2021 at 07:32:35AM -0800, Noah Meyerhans wrote:
> Unfortunately, I believe it's too late to update botocore in bullseye. 1.19
> seems to break compatibility with 1.17, meaning it would require a transition.
> Per the bullseye release policy and timeline [1], tr
On Tue, Jun 08, 2021 at 08:39:45AM +0200, Bastian Blank wrote:
> docker-machine is a product by Docker upstream, but is not longer
> developed, without any replacement. Currently GitLab upstream makes
> heavy use of it, so I have no idea what they are going to do about it.
> But we don't need to
On Mon, Jun 07, 2021 at 11:00:42PM +0200, Vladimir Tiukhtin wrote:
> I use "ca-certs" to supply additional certificates. With just one certiticate
> everything
> works as expected, however when provided more than one, cloud-init adds them
> into a single
> file which causes "openssl rehash" to
Control: severity -1 wishlist
Control: forwarded -1 https://github.com/aws/aws-cli/issues/6186
awscli v2 remains quite difficult to package, but it seems that upstream
is looking to address this. See
https://github.com/aws/aws-cli/issues/6186 for details and tracking.
We'll continue to track
On Thu, Jun 17, 2021 at 05:54:03AM +, Yuhua Zou wrote:
>The version of package cloud-init in official repository of Debian 10.9 is
>20.2.
>This version 20.2 is far behind the latest released version 21.2.
>Please check [1]https://github.com/canonical/cloud-init
>
>With
On Mon, May 10, 2021 at 09:00:34PM +0200, Moritz Mühlenhoff wrote:
> > Hi, since this package was brought into Debian in ~2018, there have been
> > several transformations in the GCE guest software stack and thus the
> > current landscape is very different. Google doesn't actually maintain the
> >
On Thu, May 13, 2021 at 10:07:13PM -0700, Ross Vandegrift wrote:
> nm-cloud-setup uses systemd-networkd, but offers support for ipv6 prefix
> delegation, secondary ips, and per-interface policy routing. It provides a
> set
> of systemd services so that administrators can modularly enable and
On Mon, May 17, 2021 at 11:35:42AM -0700, Jeremy Drake wrote:
> I am attempting to launch a c6g.metal instance in us-west-2, but it hangs up
> and never seems to boot, with:
> ami-0a773686fc288ee18
> ami-054ec2aaf512d49c5
> ami-0bb3ac1447646faf5
They work, they just take a long, long time to
On Mon, May 17, 2021 at 12:46:20PM -0700, Jeremy Drake wrote:
>
>
> On Mon, 17 May 2021, Noah Meyerhans wrote:
>
> > They work, they just take a long, long time to boot. Figure about 10-15
> > minutes or so.
>
> Thanks, it did eventually boot. It's hard to
On Tue, May 11, 2021 at 12:44:49PM +0200, Dick Visser wrote:
> Then we sort this list by CreationDate and pick the last one, meaning
> we always use the latest image, which is released roughly every month.
> This worked well - so far.
> I just noticed that my dev environment was running on a fancy
On Fri, May 14, 2021 at 07:43:05PM +0200, Emmanuel Kasper wrote:
> > i noticed that the bullseye64 Vagrant libvirt box does not use
> > predictable network interface names. It is explicitely disabled with
> > 'net.ifnames=0 biosdevnames=0' in the grub configuration. Is there a
> > special reason
On Tue, Jun 01, 2021 at 01:03:11PM +0200, Steffen Möller wrote:
> > > The biggest tasks would be to package the SDK of AWS [0] (which would also
> > > benefit igv) and of Microsoft Azure [1]. We would also need to package
> > > Apache Ignite [2].
> > > After the freeze I shall discuss this on the
On Wed, Jun 02, 2021 at 09:45:05AM -0700, Ross Vandegrift wrote:
> > Let us start with a discussion where the sdk itself should be
> > team-maintained - cloud or med or java?
> >
> > Personally, I'd opt for Java, since this seems like to be the core
> > challenge for us. If this drags in other
On Sun, May 23, 2021 at 10:08:24AM -0400, Tong Sun wrote:
> I know there are many reasons not to use Debian testing in production.
> But now that Bullseye is in freezing, I think it is time for early adapters to
> start testing it in Azure.
>
> I for one am willing to do that. So I propose that
I recently finished adding buster-backports AMIs to the AWS Marketplace
along with the ѕtandard buster AMIs. These AMIs are basically іdentical
to the buster AMIs except that they use the buster-backports kernel
(currently Linux 5.10).
These may be useful for you if you require features only
Package: amazon-ec2-utils
Version: 1.3+git20200518-2
Severity: normal
The primary purpose of the amazon-ec2-utils package is to install some udev
rules to configure various hardware conveniences. For example, these
install symlinks providing compatibility symlinks for block devices such
that
Hi Thomas.
> Since Waldi, unilaterally, decided to close again the Octavia image
> patch for a 2nd time (for new reasons he didn't tell since we met
> Boston... yeah, just a new reason he found out!), I wonder where the
> cloud team would advise that I upload my work. It doesn't seem that
>
On Wed, Apr 28, 2021 at 09:53:02AM +0200, Thomas Lange wrote:
> I've created a proposal for updating the header seen in
> https://cloud.debian.org/cdimage/cloud/
>
> You can see it here
> https://public.cs.uni-koeln.de/lange/images-cloud-HEADER.html
>
> Any comments welcome.
Definitely an
Package: cloud-init
Version: 20.4-1
Severity: grave
Tags: security upstream patch
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
cloud-init has the ability to generate and set a randomized password for
system users. This functionality is enabled at runtime by passing
On Mon, Mar 22, 2021 at 01:52:11PM -0400, Theodore Ts'o wrote:
> Perhaps it would make sense to make an image for Bullseye in
> debian-cloud-testing, so it doesn't accidentally get picked up and
> used in production environments before Bullseye gets released as
> Debian Stable?
The situation is
We should be publishing release images for OpenStack and at least two
commercial cloud services approximately simultaneously with the bullseye
release. I'd like to include a short notice about cloud image
availability in the release notes, but it's not entirely clear where it
should go.
On Fri, Feb 26, 2021 at 07:41:28AM -0500, David H. Rhodes Clymer wrote:
> I have been building my own AMI for use at AWS because reasons.
> However, in order to make my images acceptable, I end up having to
> install the linux-image-3.16.0-.. image from Debian 8 (I think?). Any
> other kernel I
On Thu, Apr 08, 2021 at 04:32:37PM +, Jarosław Wygoda wrote:
>I tried to add complete key on debian 10 and it turns out it requires
>gnupg. Here's a relevant cloud-init config and error.
>apt:
> preserve_sources_list: true
> sources:
> docker.list:
>
On Thu, Apr 08, 2021 at 11:01:26PM +0200, Bastian Blank wrote:
> > In order for that to work, though, the
> > key needs to be available in *binary* format. So we still do need gpg
> > to do the conversion.
>
> No, apt does not require a binary key file. Just
On Wed, Apr 14, 2021 at 10:36:27PM -0700, Ross Vandegrift wrote:
> The Debian Project will release it's new stable release 11 (code name
> Bullseye) along with images for various cloud providers. Images will
nit: We don't typically capitalize the release codename in this context.
> * when
On Wed, Apr 14, 2021 at 10:36:27PM -0700, Ross Vandegrift wrote:
> Stable Cloud Images for Bullseye (stable)
> -
>
> The Debian Project will release it's new stable release 11 (code name
> Bullseye) along with images for various cloud providers. Images
On Tue, Apr 20, 2021 at 10:30:04PM +0100, Jelmer Vernooij wrote:
> > Did you ask the DPL for funding this?
> Yeah, there's an ongoing thread - though it would be ideal if this was
> part of an ongoing GCP billing account directly associated with Debian
> (and even nicer if Google sponsored it!)
On Wed, Aug 18, 2021 at 10:59:01PM +1000, James Healy wrote:
> I note there's some discussion in #966573 about packaging v2 and there's
> some complexity there.
>
> With the bullseye freeze over and the v2 plans uncertain, are you open
> to updating this package to the most recent release in the
On Wed, Aug 18, 2021 at 05:36:51AM -, Debian Wiki wrote:
> Dear Wiki user,
>
> You have subscribed to a wiki page or wiki category on "Debian Wiki" for
> change notification.
>
> The "Cloud" page has been changed by ThomasChung:
> https://wiki.debian.org/Cloud?action=diff=96=97
>
>
Control: tags -1 + upstream fixed upstream
On Tue, Jan 12, 2021 at 01:57:27PM +0100, Matteo Croce wrote:
> At boot cloud-init waits 120 seconds for an ephemeral disk, but some
> VM types doesn't have ephemeral storage at all, so this just blocks
> the boot for 120 seconds:
>
> Jan 12 11:23:13
On Tue, Aug 31, 2021 at 12:20:31PM +, Jeremy Stanley wrote:
> On 2021-08-31 10:54:02 + (+), Anton Scharnowski wrote:
> [...]
> > We run an OpenStack platform. The Issue leads to no IPv6 capabilty
> > on the VM until you manually execute a DHCPv6 request.
> [...]
>
> As an aside, do
On Mon, Aug 16, 2021 at 03:57:11PM +0200, Laura Arjona Reina wrote:
> I think we need some updates for the section about cloud images in our
> "distrib" page (https://www.debian.org/distrib ), there are two
> specific links to Debian 10 OpenStack images and I guess it's better
> to include the
Package: cloud.debian.org
Severity: wishlist
User: cloud.debian@packages.debian.org
Usertags: aws image
AWS has recently announced that VPC-internal services are available via
IPv6. In order to facilitate deployments that don't configure IPv4
addresses, we should enable support for
On Wed, Aug 11, 2021 at 08:11:27PM -0600, Ross Vandegrift wrote:
> > > 2. I will implement a temporary change to our bullseye images to revert
> > > the
> > >sudoers file to use the old syntax that cloud-init will detect.
> >
> > This is implemented by
> >
Control: severity -1 important
Please see https://www.debian.org/Bugs/Developer#severities
On Wed, Jul 28, 2021 at 05:22:43PM +0200, Thomas Goirand wrote:
> After spawning a VM, it takes a long time to get networking (output from
> the console):
>
> cloud-init[281]: Cloud-init v. 20.2 running
On Wed, Aug 11, 2021 at 02:05:39PM -0700, Noah Meyerhans wrote:
> 2. I will implement a temporary change to our bullseye images to revert the
>sudoers file to use the old syntax that cloud-init will detect.
This is implemented by
https://salsa.debian.org/cloud-team/debian-cloud-
On Sat, Aug 07, 2021 at 08:30:17PM -0600, Ross Vandegrift wrote:
> > > > In the sudoers file there is a duplicate includedir
> > > > statement; at the end of the file you will find the following contents:
> > > >
> > > > """
> > > > # See sudoers(5) for more information on "@include" directives:
On Thu, Oct 14, 2021 at 07:55:18AM -0700, Ross Vandegrift wrote:
> > On Thu, Oct 14, 2021 at 10:32:50AM +0100, Giambattista Piranesi wrote:
> > >I've noticed there are no official Debian 11 (Bullseye) images on AWS
> > >compatible with m6i instances.
>
> How are you trying to find them? I just
On Thu, Oct 14, 2021 at 08:23:32AM -0700, Noah Meyerhans wrote:
> > > >I've noticed there are no official Debian 11 (Bullseye) images on AWS
> > > >compatible with m6i instances.
> >
> > How are you trying to find them? I just launched an m6i.large in
>
On Tue, Sep 28, 2021 at 09:02:31PM +0200, Dick Visser wrote:
> Begin: Running /scripts/local-premount ... done.
> Begin: Will now check root file system ... fsck from util-linux 2.36.1
> [/sbin/fsck.ext4 (1) -- /dev/nvme0n1p1] fsck.ext4 -a -C0 /dev/nvme0n1p1
> /dev/nvme0n1p1: clean, 35442/516096
On Tue, Sep 28, 2021 at 09:48:15AM -0700, Ross Vandegrift wrote:
> > I'm regularly reinstantiating many AWS instances that run Debian
> > (bullseye).
> > I see some strange behavior, in that instance come up very
> > consistently in about 6 seconds (according to
> >
On Wed, Oct 06, 2021 at 03:56:25PM +0100, Phil Endecott wrote:
> > sed -i -e '/ExecStart/s/agetty/agetty -a root/' \
> > -e '/ExecStart/s/-p/-p -f/' \
> > /lib/systemd/system/serial-getty@.service
>
> So I think that is intended to replace this:
>
> ExecStart=-/sbin/agetty -o '-p -- \\u'
On Tue, Oct 05, 2021 at 06:55:19PM +0100, Phil Endecott wrote:
> What is the recommended way to permit login on the AWS serial
> console? I hesitate to try to work it out by trial and error,
> since a mistake could either leave me unable to log in at all
> or leave the instance insecure.
>
> This
On Mon, Dec 06, 2021 at 02:28:35PM +, Phil Endecott wrote:
> On one of my Lightsail instances, which was created a few years
> ago from a Debian image and has subsequently been upgraded a few
> times, I have a /etc/sysctl.d/01_ec2.conf file which sets
> vm.swappiness = 0. On another newer EC2
On Wed, Nov 17, 2021 at 07:45:31AM -0800, Ross Vandegrift wrote:
> > We like to do a global change to the way the network is setup on the new
> > AWS accounts. The goal is to reduce the amount of global IPv4 addresses
> > to a minimum, as those are an increasingly rare comodity nowadays.
>
>
On Wed, Nov 10, 2021 at 05:05:12PM +0100, Martin Zobel-Helas wrote:
> Due to an update on the Azure side, it would be helpful to support the
> newer API version of IMDS within cloud-init, a patch, that didn't make
> it to stable, as of the time the change was made, changes on cloud-init
> weren't
On Mon, Oct 25, 2021 at 03:49:59PM +, Matthias Bach wrote:
>
> For a specific use case we are still running Debian 9.13 on some VMs on
> Azure. Sadly, we had to notice that the
> linux-image-4.19.0-0.bpo.18-cloud-amd64 (4.19.208-1~deb9u1) version of
> linux-4.19 won't boot on 64 core VMs.
On Tue, Dec 07, 2021 at 03:53:07PM +, Phil Endecott wrote:
> > > dpkg -S doesn't tell me where this file came from. I don't
> > > think I created it myself!!
> >
> > It was installed as part of the image creation process. Similar to
> > files like /etc/hosts, it is not actually owned by a
On Tue, Nov 30, 2021 at 02:17:26PM +, Vins Vilaplana wrote:
> Can anyone enable the Debian 11 AWS Marketplace images on c6i instance types
> and submit an update request to AWS, please?
Done. It will take some time for the change to be reflected in the
Marketplace.
I've also toggled support
On Thu, Dec 09, 2021 at 04:02:24PM +0100, Paul Gevers wrote:
> Source: python-boto
> Version: 2.49.0-3
> Severity: serious
We should probably pursue the removal of this package before the
bookworm release rather than trying to drag it forward for another
release. It's dead upstream in favor of
On Thu, Jul 22, 2021 at 11:15:23AM +0200, Thomas Goirand wrote:
> In commit 522055bf, I added
> config_space/files/etc/cloud/cloud.cfg.d/01_debian_cloud.cfg/GENERICCLOUD
> and
> config_space/files/etc/cloud/cloud.cfg.d/01_debian_cloud.cfg/GENERIC, in
> the hope to get
On Thu, Jul 22, 2021 at 10:51:19PM +0200, Thomas Goirand wrote:
> >> In commit 522055bf, I added
> >> config_space/files/etc/cloud/cloud.cfg.d/01_debian_cloud.cfg/GENERICCLOUD
> >> and
> >> config_space/files/etc/cloud/cloud.cfg.d/01_debian_cloud.cfg/GENERIC, in
> >> the hope to get
On Fri, Jul 23, 2021 at 10:51:57AM +0200, Bastian Blank wrote:
> > In commit 522055bf, I added
> > config_space/files/etc/cloud/cloud.cfg.d/01_debian_cloud.cfg/GENERICCLOUD
> > and
> > config_space/files/etc/cloud/cloud.cfg.d/01_debian_cloud.cfg/GENERIC, in
>
> Why did you decide that you can do
On Mon, Mar 07, 2022 at 12:11:37PM +0100, Bastian Blank wrote:
> On Sun, Mar 06, 2022 at 04:40:24PM -0800, Noah Meyerhans wrote:
> > Are you not satisfied that the salsa issues have been addressed with the
> > latest maintenance? We are now running a current Gitlab release, at
&g
(Disclosure: I'm employed by AWS, and generally a fan of it, but am not
speaking in any official capacity on its behalf. Never the less, you
may want to consider the possibility that my position is biased.)
On Thu, Mar 17, 2022 at 12:03:18PM +0100, Julien Cristau wrote:
> DSA's looking into
On Sun, Mar 06, 2022 at 05:46:41PM +0100, Bastian Blank wrote:
> > > Yeah. That just reduces the possibilities to the large platforms.
> > I agree this is a downside. But we wouldn't be forever locked into a
> > plaform - it's easy to migrate to consul (and probably raft, but I've
> > never
Control: reassign -1 src:linux
Control: tags -1 + upstream
> Amazon EC2 instance types with Enhanced Networking use the ixgbevf.ko
> driver. The current AMIs successfully probe the ixgbevf driver and spawn
> dhclient as expected, but dhclient appears to never receive a lease. Older
> AMIs do
Package: cloud.debian.org
Severity: important
(I suspect this is actually a kernel issue, but I'm starting with
cloud.debian.org as that's where I've observed the issue and I want to rule
out cloud configuration issues.)
Amazon EC2 instance types with Enhanced Networking use the ixgbevf.ko
On Mon, Mar 28, 2022 at 12:39:25PM +0100, Vins Vilaplana wrote:
> Can anyone request AWS Marketplace to enable debian images compatibility
> with c6a instances, please?
I've submitted the request to the AWS Marketplace. I've also enabled
x2iedn.* and x2idn.* instance types. It'll take some time
Package: cloud.debian.org
Severity: normal
User: cloud.debian@packages.debian.org
Usertags: + aws infrastructure
The IDs for buster-backports AMIs for AWS are queryable via SSM public
parameters at /aws/service/debian/release/10-backports/ However, the release
pipeline is apparently not
On Fri, Apr 08, 2022 at 04:28:03PM -0700, Ross Vandegrift wrote:
> Our next team meeting is scheduled for next Wed, Apr 13 @20:00UTC.
> Normally, we'd meet at
> https://jitsi.debian.social/DebianCloudMeeting20220413
>
> I won't be able to attend next week, due to work travel. I'm happy if
> the
On Wed, Sep 13, 2023 at 02:50:19PM +0200, Bastian Blank wrote:
> > Our next team meeting is scheduled for 2023-09-13 20:00 UTC. We'll be
> > on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230913.
>
> I most likely won't be able to attend.
And now it seems like I won't make it,
On Sun, Sep 24, 2023 at 05:26:31PM -0400, tommym2...@gmail.com wrote:
> Actually s3 might not be as expensive as one might think if you are loading
> the data into an instance in the same region as the s3 bucket instead of
> going to the public internet with the data.
> Uploading out of Aws is
On Sun, Sep 24, 2023 at 04:09:31PM -0700, Noah Meyerhans wrote:
> > > Could we use the Debian AWS account to host that service?
> >
> > I would assume that a service like snapshot would be within the scope
> > for our AWS usage. Noah?
>
> It makes sense and I wi
On Fri, Sep 22, 2023 at 05:12:21PM +0200, Bastian Blank wrote:
> > Could we use the Debian AWS account to host that service?
>
> I would assume that a service like snapshot would be within the scope
> for our AWS usage. Noah?
It makes sense and I will look into it. Let's not start anything
On Mon, Aug 28, 2023 at 01:20:32AM +, Michael wrote:
>
> Did I miss something or was the Wiki page just not updated? :-)
>
The wiki's outdated. A tool generates the content, but actually
updating the wiki involves a manual copy & paste.
I'll get it updated.
noah
On Tue, May 31, 2022 at 09:30:54PM -0700, Ross Vandegrift wrote:
> Effective today, I'm resigning as cloud team delegate. I started a new job,
> and am no longer eligible due to our conflict of interest prohibition. Since
> very little of my cloud team work required delegation, I don't plan on
On Wed, Jun 08, 2022 at 10:50:01AM +0200, Oskar Gustafsson wrote:
>We noticed the publicly available region ap-southeast-3 is not among the
>regions which has the Debian 11 image available.
>[1]https://wiki.debian.org/Cloud/AmazonEC2Image/Bullseye
>
>As users of this image, would
On Wed, Jun 08, 2022 at 09:33:40AM -0700, Noah Meyerhans wrote:
> >We noticed the publicly available region ap-southeast-3 is not among the
> >regions which has the Debian 11 image available.
> >[1]https://wiki.debian.org/Cloud/AmazonEC2Image/Bullseye
&g
On Wed, Sep 07, 2022 at 07:37:45AM +0200, Alexander Wirt wrote:
> > > Now that buster is LTS and no longer officially supported, should the
> > > -backports pocket be closed? AFAIK, buster just receives the security
> > > uploads by the -security pocket and shouldn't have -backports open
> > >
On Wed, Oct 26, 2022 at 10:21:14AM -0700, Eric Stone wrote:
>I have a problem on AWS, where I have about 20 servers that I cannot
>access because I cannot re-subscribe to the AMI.
What is the exact operation you're trying to perform? What is the
specific error you're seeing in response
On Wed, Sep 21, 2022 at 03:11:53PM -0700, Viktor Bogdanov wrote:
>Could you please clarify why Debian AWS AMIs use "init" as process 1 while
>"regular" Debian uses "systemd"?
The official Debian AMIs, as listed on
https://wiki.debian.org/Cloud/AmazonEC2Image/Bullseye and
On Wed, Sep 21, 2022 at 03:58:16PM -0700, Viktor Bogdanov wrote:
>We use stretch AMI ID "ami-0e24a11c7e7dd6435" account ID "379101102735".
That AMI does use systemd, as you can see from the transcript below.
Please note, however, the stretch is ancient and is no longer supported
with security
On Wed, Oct 12, 2022 at 10:21:40PM -0700, Ross Vandegrift wrote:
> ec2 classic in legacy account
> =
>
> We received a warning from AWS that the legacy account will be losing EC2
> classic, and there might be systems running that environment. Noah took a
> quick look
Package: cloud.debian.org
Severity: normal
User: cloud.debian@packages.debian.org
Usertags: aws infrastructure
Per recent email from AWS, we need to update the usage instructions associated
with our AWS Marketplace AMI listings. The requirements are documented at
On Thu, Aug 04, 2022 at 10:13:05AM +, 'Amazon Web Services, Inc.' via
Debian cloud accounts wrote:
> We are writing to inform you of policy changes to Server products.
>
> As of 8/1/22, we have published new requirements regarding usage instruction
> content, as well as additional
Package: cloud.debian.org
Severity: important
User: cloud.debian@packages.debian.org
Usertags: aws image
When AWS originally launched IPv6-only VPC subnets, the DHCPv4 server
handed out a link-local v4 address and a default route that was a
blackhole for most destinations. It did route
Adding some tracing to the dhclient-script, I can see that
/etc/dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes is trying to add
the routes with calls like:
ip -4 route add 169.254.169.254/32 via 169.254.0.1 dev ens5
However, because there's no route to 169.254.0.1, the call fails with
On Mon, Oct 31, 2022 at 10:50:19PM -0700, Noah Meyerhans wrote:
> > aws-crt-python is the hard part. It depends on a bunch of C libraries which
> > follow a more modern development style. They:
> > - provide no abi/api stability guarantees.
> > - have versioned releases
Also it seems that generating this file triggers an OOM condition on
salsa. https://salsa.debian.org/noahm/awscli/-/jobs/3693800
Package: awscli
Version: 2.9.9-1
Severity: normal
Just making sure this is recorded:
The aws(1) man page installed by awscli 2.9.9-1 is not useful. Ideally it
should be split up in to per service pages, e.g. aws-vpc(1), aws-ec2(2), etc.
for all services (some services already have their own
tags -1 + pending
> This package ships /usr/share/zsh/vendor-completions/_awscli which I
> expect it to work like other files in zsh/vendor-completions.
>
> For example, I should have `aws` completion if I just called `compinit`
> in my zshrc.
>
> But I still need to `source
Package: cloud.debian.org
Severity: normal
Certain functionality built in to cloud-init depends on a reasonably
accurate clock, such as apt repo metadata signature verification. In the
case where a system's hardware clock is far out of sync, chrony may not have
completed synchronization before
On 12/12/2022 6:44 AM, Sam Hartman wrote:
>> From my quick read: Michael Biebl proposes dropping
>> network-pre.target
Ross> from cloud-init's After=, and replacing it with each of the
Ross> config backends that cloud-init supports. This sounds pretty
Ross> reasonable,
Package: wnpp
Severity: wishlist
Owner: Noah Meyerhans
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-cloud@lists.debian.org
* Package name: aws-crt-python
Version : 0.15.3
Upstream Author : Amazon Web Services
* URL : https://github.com/awslabs/aws-crt-python
On Sun, Dec 04, 2022 at 06:47:07PM +0100, Marco Biagiotti wrote:
> I want to install the official Debian distribution, but i am a bit confused
> about which distribution channels should i use.
>
> From wiki (https://wiki.debian.org/Cloud/AmazonEC2Image/Bullseye) i found
> two methods to obtain
201 - 300 of 347 matches
Mail list logo
