I'm expecting utlemming to sponsor these uploads, so ~ubuntu-sponsors
don't need to worry about it. :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1422388
Title:
Fetch
** Patch added: debdiff for CloudStack passwords in precise
https://bugs.launchpad.net/cloud-init/+bug/1422388/+attachment/4328200/+files/precise-cloudstack-passwords.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Patch added: debdiff for CloudStack passwords in trusty
https://bugs.launchpad.net/cloud-init/+bug/1422388/+attachment/4328201/+files/trusty-cloudstack-passwords.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init
** Patch added: debdiff for CloudStack passwords in utopic
https://bugs.launchpad.net/cloud-init/+bug/1422388/+attachment/4328202/+files/utopic-cloudstack-passwords.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init
I've tested all of these on Interoute on amd64 and i386.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1422388
Title:
Fetch passwords from CloudStack virtual router
To manage
** Changed in: cloud-init
Status: New = Fix Committed
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = Daniel Watkins (daniel-thewatkins)
** Changed in: cloud-init (Ubuntu)
Status: New
** Changed in: cloud-init (Ubuntu Trusty)
Assignee: (unassigned) = Daniel Watkins (daniel-thewatkins)
** Changed in: cloud-init (Ubuntu Utopic)
Assignee: (unassigned) = Daniel Watkins (daniel-thewatkins)
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: cloud-init (Ubuntu Utopic)
Status: Confirmed = Fix Released
** Changed in: cloud-init (Ubuntu Utopic)
Assignee: Daniel Watkins (daniel-thewatkins) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: cloud-init
Status: New = In Progress
** Changed in: cloud-init
Assignee: (unassigned) = Daniel Watkins (daniel-thewatkins)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https
I've attached a branch which is ready for smoser's review.
** Branch linked: lp:~daniel-thewatkins/cloud-init/fix-azure
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1422993
Steve,
I think the conclusion we've reached is that cloud-init isn't an
appropriate way to add swap to an instance after it has been spun up.
cloud-init has been designed to do disk setup at first boot and so makes
assumptions that wouldn't hold after that point.
If people do want to add swap
** Description changed:
+ === Begin SRU Information ===
+ [Impact]
+ CloudStack provides an EC2-style metadata server which cloud-init consumes.
Unfortunately, the CloudStack metadata server does not exactly match the
behaviour of the EC2 metadata server. When an instance using cloud-init is
** Branch linked: lp:~daniel-thewatkins/ubuntu/trusty/cloud-
init/lp1356855
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1356855
Title:
Cloud-init 0.7.5 Failed to get
I'm unassigning myself; this isn't really a cloud image problem so much
as it is either a nova problem or a general Ubuntu problem; I'm not best
placed to solve either of these.
** Changed in: nova (Ubuntu)
Assignee: Daniel Watkins (daniel-thewatkins) = (unassigned)
--
You received
This problem (should) disappear with systemd; it takes care of
populating /etc/machine-id on first boot, though it does need the file
to exist and be empty[0].
So we should do one (or more) of:
- teach nova that an empty /etc/machine-id is equivalent to a missing one,
- introduce an Upstart job
So I'm doing some digging in to what's actually happening, and this
might be an unexpected response from the keystone server I'm pointing
at. Marking as Invalid while I do a bit more investigation.
** Changed in: python-glanceclient (Ubuntu)
Status: New = Invalid
--
You received this bug
Public bug reported:
Steps to reproduce:
- Install python-glanceclient
- Configure OS_* environment variables
- Run 'glance image-list' (or any other glance command, AFAICT).
Expected Behaviour:
A list of images.
Actual Behaviour:
Unable to establish connection to
** Changed in: nova (Ubuntu)
Assignee: (unassigned) = Daniel Watkins (daniel-thewatkins)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1413293
Title:
Unable to start instances
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Steve,
On 19/01/15 20:18, Stephen A. Zarkos wrote:
In case customers are not familiar with the term Custom Data or
how to use it, I would recommend linking to our documentation:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi trialotto,
On 20/01/15 02:15, trialotto wrote:
The documentation looks great.
Thanks!
However, can you add the following (important) remarks to the
documentation page:
a) as from cloud-init 0.7.6, the option exists to create swap by
means
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = Daniel Watkins (daniel-thewatkins)
** Changed in: cloud-init (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init
Steve, I've written up some documentation on how to create swap
partitions on Azure at https://wiki.ubuntu.com/AzureSwapPartitions
Please do let me know if there are any improvements that you'd like me
to make!
(Marking this as Fix Committed until I hear back from you)
** Changed in: cloud-init
Public bug reported:
Currently we assume it will be /dev/sdb, but this may change. There is
an example of how to handle this in the Azure Linux agent.
To quote stevez in a comment on bug 1410835:
Device names are not persistent in Linux and could change, so it is not
guaranteed that the
Hi trialotto,
cloud-init has default settings for Azure instances that ensure that the
first partition of the ephemeral disk is formatted as ext4. It does this
by providing default values for disk_setup and fs_setup; you can see
these at http://bazaar.launchpad.net/~cloud-init-dev/cloud-
Steve,
I have just filed https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1411582 regarding the inconstancy of device naming; could you
confirm that I've captured the issue accurately?
Thanks,
Dan
--
You received this bug notification because you are a member of Ubuntu
Server Team,
trialotto, I've just been doing some testing, and I've realised my above
answer is incorrect; this is definitely a problem in how cloud-init's
Azure data source works.
I'm looking in to it now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Actually, I've realised that I was passing in invalid cloud
configuration data. If I have the following in azure-disk.cfg:
#cloud-config
disk_setup:
ephemeral0:
table_type: mbr
layout: [66, 33]
overwrite: True
fs_setup:
- device: ephemeral0.1
filesystem: ext4
OK, so passing a file containing the following as custom-data gives us a
swap partition and a mounted disk at /mnt:
#cloud-config
disk_setup:
ephemeral0:
table_type: mbr
layout: [[66, 82], 33]
overwrite: True
fs_setup:
- device: ephemeral0.1
filesystem: swap
We need to decide how we're going to handle this.
The GCE tooling (and therefore documentation) suggest that if instance-
level keys are supplied, then project-level keys are disregarded. Do we
want to mirror this?
I'm torn on this one. On the one hand, we already don't match the GCE
docs in the
** Package changed: ubuntu = cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1398997
Title:
Ubuntu Cloud images do not work with SmartOS hypervisor
To manage
** Branch linked: lp:~daniel-thewatkins/ubuntu/precise/cloud-
init/lp1374600
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1378441
Title:
add GCE support for cloud-init on
Public bug reported:
Binary package hint: logwatch
I get the following in the email logwatch 7.3.6-1ubuntu1 sends. The
'Unknown lines' all seem reasonably standard, so I don't really care
about them, so they shouldn't be included.
- dpkg status changes Begin
32 matches
Mail list logo
