Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: cloud-i...@packages.debian.org, t...@security.debian.org
Control: affects -1 + src:cloud-init
Hi folks. This isn't a straightforward stable proposed-updates
On Tue, Apr 30, 2024 at 02:10:04AM +, Devidas Shanbhag, Amrutha wrote:
>Its available in AWS, but not in Azure yet. Previously I have been told
>that for Azure there is an additional step from your end to publish them.
>I wonder if that hasn’t been actioned yet.
Publishing on
On Thu, Apr 18, 2024 at 10:17:27AM +0200, Arthur LUTZ wrote:
>A small heads up on this issue, we have some minor impacts :
>* sudo commands show a warning
>
> sudo: unable to resolve host example: Name or service not known
Thanks for the report. This is resolved with the 20240429
On Fri, Apr 26, 2024 at 03:52:40PM +0100, Andy Holt wrote:
> I see from https://wiki.debian.org/Cloud/AmazonEC2Image/Bookworm that
> there are new Bookworm AMIs published, as of 15/Apr/2024. However, if
> (in eu-west-2 / London at least) I try to launch a Debian 12 EC2
> instance, using the plain
On Fri, Apr 26, 2024 at 04:04:14AM +, Devidas Shanbhag, Amrutha wrote:
>Is there any upcoming cloud image release planned for Debian 11.9 with
>security updates? There hasn’t been one since the point release of 11.9 on
>Feb 11^th.
Yes, we expect to publish new Debian 11 images
Source: cloud-init
Version: 21.1.4-1
Severity: serious
Tags: ftbfs upstream
Justification: fails to build from source
Cloud-init's test fails in a non-networked build environment, as visible in
recent buildd logs, e.g.
On Thu, Apr 18, 2024 at 09:33:32AM -0700, Noah Meyerhans wrote:
> >Do you plan to build and publish updated Buster AMI soon ?
>
> I expect to publish new Debian 10 cloud images on 2024-04-19. There are
> several outstanding fixes, including the recent tzdata update.
Ac
On Thu, Apr 18, 2024 at 02:30:26PM +0200, Matthieu Aohzan wrote:
>Do you plan to build and publish updated Buster AMI soon ?
I expect to publish new Debian 10 cloud images on 2024-04-19. There are
several outstanding fixes, including the recent tzdata update.
noah
On Thu, Apr 18, 2024 at 10:17:27AM +0200, Arthur LUTZ wrote:
>Hi,
>A small heads up on this issue, we have some minor impacts :
>* sudo commands show a warning
>
> sudo: unable to resolve host example: Name or service not known
>
>On a more problematic side (but not breaking) we
On Mon, Apr 15, 2024 at 11:55:22AM -0700, Zach Marano wrote:
> What are the specific packages that Google wants from the backports
> repo by default? From my perspective, the primary reasons to enable it
> are for backports kernels (which have historically provided a number of
>
On Mon, Apr 15, 2024 at 10:31:43AM -0700, Zach Marano wrote:
>It seems that the Debian 10 backports repo (buster-backports) moved out of
>the main Debian repos and into the archives ahead of the intended LTS EOL
>date (June 30, 2024). I don't recall this type of change happening with
>
On Wed, Apr 03, 2024 at 09:39:40PM -0700, Flavio Veloso Soares wrote:
> Hi Noah - I guess I'll be doing bullseye->bookworm installs in the meantime,
> until 12.6 so I can fill bug reports (if any).
It should be plenty to start with the bookworm images and simply remove
the libnss-resolve package.
On Thu, Apr 04, 2024 at 09:36:08PM -0700, Ross Vandegrift wrote:
> Our next team meeting is re-scheduled for next Thu, Apr 11 @ 20:00 UTC. Note
> the different day! We'll meet on jitsi at:
> https://jitsi.debian.social/DebianCloudMeeting20240411
Sorry, I think there was a misunderstanding. I
On Wed, Apr 03, 2024 at 09:14:31PM -0700, Ross Vandegrift wrote:
> > > Our next team meeting is scheduled for next Wed, Apr 10 @ 20:00 UTC. As
> > > usual we will chat at:
> > > https://jitsi.debian.social/DebianCloudMeeting20240410
> >
> > I'd like to be able to attend, but won't be able to at
Control: tags -1 + pending
On Wed, Apr 03, 2024 at 06:48:56PM -0700, Flavio Veloso Soares wrote:
> Is this the correct forum to report issues/ask question about the official
> Debian images on AWS?
The BTS isn't really the correct forum to ask questions about any Debian
topics, but it is the
On Wed, Apr 03, 2024 at 01:58:41PM -0700, Ross Vandegrift wrote:
> Our next team meeting is scheduled for next Wed, Apr 10 @ 20:00 UTC. As
> usual we will chat at:
> https://jitsi.debian.social/DebianCloudMeeting20240410
I'd like to be able to attend, but won't be able to at all during the
week
On Wed, Mar 13, 2024 at 09:23:35PM -0700, Ross Vandegrift wrote:
> Noah raised an issue related to a bug in systemd-resolved, and we agreed that
> it should be disabled for now. Upstream bug report:
> https://github.com/systemd/systemd/issues/29069
>
> This causes some percentage of DNS
On Wed, Feb 07, 2024 at 05:30:33AM +, yu, bing wrote:
>This is Bing Yu, a software engineer from NetApp. I am working on a
>project using Debian 11 and I realised our official Debian 11 (bullseye)
>AMIs for Amazon EC2 hasn’t been updated since Oct
>
On Tue, Feb 06, 2024 at 11:26:47AM +0100, Renzo Davoli wrote:
> > >no new sid cloud images have been created in
> > > https://cdimage.debian.org/cdimage/cloud/sid/daily/
> > > since Dec 23 2023.
> > > Is it a choice or a bug?
> > This is a known bug.
> Is it possible to foresee a time
On Wed, Jan 31, 2024 at 03:26:05PM +0100, Renzo Davoli wrote:
>no new sid cloud images have been created in
> https://cdimage.debian.org/cdimage/cloud/sid/daily/
> since Dec 23 2023.
>
> Is it a choice or a bug?
This is a known bug.
noah
On Fri, Jan 12, 2024 at 08:00:48AM +0100, Alexandre Detiste wrote:
> >> Or should the Debian package depend on python3-six?
> >
> > That s the fast solution
>
> Yes please do that, I've checked awscli upstream and it's a bit of a mess
> with so many pull request; I'll check again later.
Here's
On Thu, Jan 11, 2024 at 02:27:23PM -0500, Jeremy Bícha wrote:
> There is a diff at
> https://launchpad.net/ubuntu/+source/awscli/2.14.6-1ubuntu1 for this
> issue. You can ignore the build failure since that doesn't seem to
> currently affect Debian Unstable.
Thanks, I've applied that patch and
On Sun, Dec 31, 2023 at 07:10:26AM +0100, Philip Hands wrote:
> I'm new to this cloud image stuff, so may well have made broken
> assumptions in the following -- please correct me if I'm wrong.
>
> I see that `machinectl` (from systemd-container) has the subcommands
> pull-raw and pull-tar, so I
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: python-b...@packages.debian.org
Control: affects -1 + src:python-boto
Python-boto has long ago been superseded upstream by python-boto3, which has
been in Debian for several releases.
On Tue, Dec 12, 2023 at 08:14:41PM +0100, Andreas Tille wrote:
> maybe we need to remove python-boto and fix all its rdepends.
>
> According to upstream[1]:
>
> This repo, boto was deprecated in 2020 and the last supported Python 3
> version was 3.4. It's unlikely this package will ever work
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 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 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 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 Wed, Aug 02, 2023 at 09:58:01PM -0700, Ross Vandegrift wrote:
> Our next team meeting is scheduled for 2023-08-09 20:00 UTC. We'll be
> on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230809.
I'll be attending the cloud-init summit at this time. It's unclear if
I'll be able to join
Also, I'm curious to see what happens if you invoke the
write_files_deferred module by hand with a command like
$ sudo cloud-init single --name cc_write_files_deferred \
--frequency always --report
It should generate messages in /var/log/cloud-init.log.
On 7/14/23 06:49, Sven Strickroth wrote:
I'm not able to reproduce the behavior you describe. defer seems to
work as expected. For example:
admin@ip-10-0-0-87:~$ ec2-metadata --ami-id
ami-id: ami-0544719b13af6edc3
admin@ip-10-0-0-87:~$ sudo cat /var/lib/cloud/instance/user-data.txt
On 7/13/23 12:08, Emanuele Rocca wrote:
Hi,
https://lwn.net/Articles/937830/ mentions that a kernel developer could
not find arm64 virtualisation images for any distro except for openSUSE:
There are no local virtualization images for arm64 available, other
than for openSUSE Tumbleweed, that
Control: tags -1 + moreinfo
On Thu, Jul 13, 2023 at 05:30:52PM +0200, Sven Strickroth wrote:
> starting with the shipped version in Debian 12 the write_files feature with
> defer option does not work any more.
I'm not able to reproduce the behavior you describe. defer seems to
work as
Control: tags -1 + patch
Proposed fix is at
https://salsa.debian.org/cloud-team/cloud-init/-/merge_requests/9
On Sat, Apr 04, 2020 at 11:49:42AM +0100, Nick Holloway wrote:
> Package: cloud-init
> Version: 18.3-6
Confirmed that the behavior as described is still an issue in cloud-init
22.4.2-1 in bookworm.
> The command "locale-gen" does not accept a locale as an argument, but
> only generates the
On 6/21/2023 5:41 AM, Laura Arjona Reina wrote:
We have links to cloud images in https://www.debian.org/distrib/ and I
guess some of them should be updated to offer the cloud images of
Debian 12 bookworm. I don't know if all the cloud images are provided
already, and I don't know if more
On Fri, Jun 16, 2023 at 09:37:15AM +0200, Dick Visser wrote:
>On [1]https://wiki.debian.org/Cloud/AmazonEC2Image/Bookworm it says
>This preview AMIs are intended to allow you to start testing Debian 12
>deployments and migrations before the official release occurs on
>2023-06-10.
>
On Mon, Jun 12, 2023 at 11:32:03AM +1200, Andrew Ruthven wrote:
>I'm not sure if it is related to the Bookworm release, but it seems that
>no images have been published since 31 May. Looking at:
>[1]https://cdimage.debian.org/images/cloud/bookworm/
>Latest daily build is
+
+ * Install systemd services to /lib/systemd/system. (Closes: 1034212)
+
+ -- Noah Meyerhans Thu, 13 Apr 2023 10:22:32 -0700
+
amazon-ec2-net-utils (2.3.0-2) unstable; urgency=medium
* Set Maintainer to the cloud team and add myself to Uploaders
diff -Nru amazon-ec2-net-utils-2.3.0/debian
Control: reassign -1 wnpp.debian.org
Control: retitle -1 RFP: amazon-ec2-hibinit-agent -- Amazon EC2 instance
hibernation support
> So the request is to also ship the agent preinstalled in the Debian AMIs. See
> https://packages.ubuntu.com/search?keywords=ec2-hibinit-agent=names
> for Ubuntu
On Wed, Jan 18, 2023 at 10:22:42AM -0800, Noah Meyerhans wrote:
> > The latest image in:
> > http://cdimage.debian.org/cdimage/cloud/sid/daily/
> > is 10 days old.
> >
> > Is there something blocked in the image creation process?
>
> The "nocloud"
On 1/18/23 3:53 AM, Renzo Davoli wrote:
Dear Debian cloud project.
The latest image in:
http://cdimage.debian.org/cdimage/cloud/sid/daily/
is 10 days old.
Is there something blocked in the image creation process?
The "nocloud" images are failing to build and subsequently blocking the
upload
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
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
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: 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 Mon, Nov 28, 2022 at 10:24:42AM -0800, Ross Vandegrift wrote:
> > So, some time has passed and I haven't managed to work on this at all.
> > Given the number of packages involved and the dependencies between them,
> > I'm not optimistic that we'll be able to package them all individually
> > as
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
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, Nov 13, 2022 at 09:51:52PM -0800, Ross Vandegrift wrote:
> Noah Meyerhans has continued the work packaging awscli v2. We discussed the
> issues surrounding the current dependencies of aws-crt-python - upstream
> sometimes breaks api & abi compatibility without changi
On Mon, Nov 14, 2022 at 10:38:43PM -0800, Spike Wang wrote:
>Just wondering if there is any timeline for the availability of AMIs in
>AWS GOV Regions and China? I could successfully get the image copied into
>those regions, but it failed to launch due to Marketplace restriction… Any
>
On Fri, Nov 04, 2022 at 05:37:21PM +0100, Bastian Blank wrote:
> > > Are you sure this library can have a 1 as ABI? Can you please reproduce
> > > the ABI stability promisses?
> > Allegedly upstream has recently committed to proper SONAME and ABI
> > management in support of efforts to get these
On Fri, Nov 04, 2022 at 08:32:25AM +0100, Bastian Blank wrote:
> > My first pass only produces -dev packages with headers and static libraries.
> > To test them out, build the debian/sid branch from these repos, in this
> > order:
> > - https://salsa.debian.org/rvandegrift/aws-c-common
>
> Are
On Thu, Nov 03, 2022 at 09:35:14PM -0700, Ross Vandegrift wrote:
> > Honestly, filing some of the ITPs would be quite helpful at this point.
> > We'll need to get the following projects packaged:
> >
> > aws-c-auth
> > aws-c-cal
> > aws-c-compression
> > aws-c-event-stream
> > aws-c-http
>
> I
On Wed, Nov 02, 2022 at 07:55:51PM -0700, Ross Vandegrift wrote:
> > > - the aws-cli2-temp repo is based on upstream, not our awscli repo. I was
> > > intentionally being sloppy to quickly get through a test.
> >
> > Same. I essentially Debianized the upstream v2 repo from scratch,
> >
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
Hi Ross,
On Tue, Oct 05, 2021 at 11:10:43PM -0600, Ross Vandegrift wrote:
> > 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.
>
> Using the source dist poc from
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, 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
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, 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 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
> > >
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
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
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
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, 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 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 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
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 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
(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 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
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 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 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 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 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 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 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 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 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 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
> >
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 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
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 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
>
>
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 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
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
> >
1 - 100 of 347 matches
Mail list logo
