| 2009-10-26 14:58:33 |
Markus Lindenberg |
bug |
|
|
added bug |
| 2009-10-26 15:30:29 |
Scott Moser |
eucalyptus (Ubuntu): status |
New |
Confirmed |
|
| 2009-10-26 15:33:49 |
Scott Moser |
eucalyptus (Ubuntu): importance |
Undecided |
Critical |
|
| 2009-10-26 15:34:07 |
Scott Moser |
bug task added |
|
eucalyptus |
|
| 2009-10-26 16:09:29 |
Thierry Carrez |
eucalyptus (Ubuntu): importance |
Critical |
High |
|
| 2009-10-26 16:09:29 |
Thierry Carrez |
eucalyptus (Ubuntu): milestone |
|
ubuntu-9.10 |
|
| 2009-10-26 16:20:06 |
Thierry Carrez |
eucalyptus (Ubuntu): assignee |
|
Thierry Carrez (ttx) |
|
| 2009-10-26 16:20:42 |
Thierry Carrez |
nominated for series |
|
Ubuntu Karmic |
|
| 2009-10-26 16:20:42 |
Thierry Carrez |
bug task added |
|
eucalyptus (Ubuntu Karmic) |
|
| 2009-10-26 16:21:03 |
Thierry Carrez |
eucalyptus (Ubuntu Karmic): assignee |
Thierry Carrez (ttx) |
|
|
| 2009-10-26 16:21:11 |
Thierry Carrez |
eucalyptus (Ubuntu Karmic): assignee |
|
Dustin Kirkland (kirkland) |
|
| 2009-10-26 16:21:27 |
Thierry Carrez |
bug task added |
|
ec2-init (Ubuntu) |
|
| 2009-10-26 16:24:23 |
Thierry Carrez |
ec2-init (Ubuntu Karmic): importance |
Undecided |
High |
|
| 2009-10-26 16:24:23 |
Thierry Carrez |
ec2-init (Ubuntu Karmic): status |
New |
Confirmed |
|
| 2009-10-26 16:24:45 |
Thierry Carrez |
ec2-init (Ubuntu Karmic): assignee |
|
Scott Moser (smoser) |
|
| 2009-10-26 16:24:55 |
Thierry Carrez |
ec2-init (Ubuntu Karmic): milestone |
|
ubuntu-9.10 |
|
| 2009-10-26 16:25:28 |
Thierry Carrez |
tags |
|
uec-images |
|
| 2009-10-26 16:36:52 |
Neil Soman |
eucalyptus: status |
New |
Fix Committed |
|
| 2009-10-26 16:37:05 |
Neil Soman |
branch linked |
|
lp:eucalyptus/1.6 |
|
| 2009-10-26 16:44:17 |
Matt Zimmerman |
eucalyptus (Ubuntu Karmic): status |
Confirmed |
Triaged |
|
| 2009-10-26 16:45:31 |
Matt Zimmerman |
ec2-init (Ubuntu Karmic): status |
Confirmed |
Invalid |
|
| 2009-10-26 16:45:35 |
Matt Zimmerman |
eucalyptus (Ubuntu Karmic): milestone |
ubuntu-9.10 |
karmic-updates |
|
| 2009-10-26 16:54:07 |
Thierry Carrez |
bug task added |
|
ubuntu-release-notes |
|
| 2009-10-26 17:47:20 |
Scott Moser |
bug task added |
|
euca2ools (Ubuntu) |
|
| 2009-10-26 17:48:09 |
Scott Moser |
euca2ools (Ubuntu Karmic): status |
New |
Triaged |
|
| 2009-10-26 17:48:15 |
Scott Moser |
euca2ools (Ubuntu Karmic): importance |
Undecided |
High |
|
| 2009-10-26 17:48:29 |
Scott Moser |
eucalyptus (Ubuntu Karmic): status |
Triaged |
Invalid |
|
| 2009-10-26 17:53:49 |
Neil Soman |
eucalyptus: status |
Fix Committed |
Invalid |
|
| 2009-10-27 01:10:34 |
Scott Moser |
euca2ools (Ubuntu Karmic): milestone |
|
karmic-updates |
|
| 2009-10-27 01:10:41 |
Scott Moser |
eucalyptus (Ubuntu Karmic): milestone |
karmic-updates |
|
|
| 2009-10-27 01:10:48 |
Scott Moser |
euca2ools (Ubuntu Karmic): assignee |
|
Scott Moser (smoser) |
|
| 2009-10-27 01:10:56 |
Scott Moser |
euca2ools (Ubuntu Karmic): status |
Triaged |
In Progress |
|
| 2009-10-27 01:11:18 |
Scott Moser |
ec2-init (Ubuntu Karmic): milestone |
ubuntu-9.10 |
|
|
| 2009-10-27 19:57:56 |
Scott Moser |
eucalyptus (Ubuntu Karmic): status |
Invalid |
Confirmed |
|
| 2009-10-27 19:58:03 |
Scott Moser |
eucalyptus (Ubuntu Karmic): milestone |
|
karmic-updates |
|
| 2009-10-27 20:01:10 |
Scott Moser |
attachment added |
|
cloud-error.log after euca-run-instances error http://launchpadlibrarian.net/34498784/eucalyptus-cloud-error.log |
|
| 2009-10-27 20:39:35 |
Neil Soman |
eucalyptus: status |
Invalid |
Confirmed |
|
| 2009-10-27 20:39:44 |
Neil Soman |
eucalyptus: importance |
Undecided |
High |
|
| 2009-10-27 20:40:31 |
Neil Soman |
summary |
User data is not base64 decoded before being presented to the instance |
User data is not parsed correctly by Eucalyptus in some cases |
|
| 2009-10-28 16:40:29 |
Thierry Carrez |
ubuntu-release-notes: assignee |
|
Scott Moser (smoser) |
|
| 2009-10-28 17:12:09 |
Mathias Gug |
ubuntu-release-notes: status |
New |
Confirmed |
|
| 2009-10-28 19:08:12 |
Mathias Gug |
description |
User data supplied using "euca-run-instances --user-data-file" is not decoded before being presented to the instance.
Inside the instance, "curl http://169.254.169.254/latest/user-data" should fetch the decoded user data, whereas eucalyptus will return a base64 and url encoded string. This breaks ec2-run-user-data from the ec2-init package, rendering instance configuration using the user-data mechanism unusable.
EC2 documentation at http://docs.amazonwebservices.com/AWSEC2/2007-03-01/DeveloperGuide/AESDG-chapter-instancedata.html states that EC2 will return decoded data (i don't have a ec2 account so i can't confirm this):
"The user data must be base64-encoded before being submitted to the API. The API command-line tools perform the base64-encoding for you. The data will be base64 decoded before being presented to the instance." |
User data supplied using "euca-run-instances --user-data-file" is not decoded before being presented to the instance.
Inside the instance, "curl http://169.254.169.254/latest/user-data" should fetch the decoded user data, whereas eucalyptus will return a base64 and url encoded string. This breaks ec2-run-user-data from the ec2-init package, rendering instance configuration using the user-data mechanism unusable.
EC2 documentation at http://docs.amazonwebservices.com/AWSEC2/2007-03-01/DeveloperGuide/AESDG-chapter-instancedata.html states that EC2 will return decoded data (i don't have a ec2 account so i can't confirm this):
"The user data must be base64-encoded before being submitted to the API. The API command-line tools perform the base64-encoding for you. The data will be base64 decoded before being presented to the instance."
=================
Karmic release notes:
user-data not usable by guest instances
Starting an instance with euca-run-instances and user-data (either using the -d option the -f option) will store the user data in base64 encoding. Accessing the user data from the instance at http://169.254.169.254/latest/user-data will return the user data in base64 encoding. Because of this bug ec2-init is unable make use of user-data. In order to use this data it must first be decoded. A fix for this issue is expected to be provided in a post-release update immediately after the Ubuntu 9.10 release.
================== |
|
| 2009-10-28 19:11:43 |
Mathias Gug |
ubuntu-release-notes: status |
Confirmed |
In Progress |
|
| 2009-10-28 20:52:36 |
Mathias Gug |
description |
User data supplied using "euca-run-instances --user-data-file" is not decoded before being presented to the instance.
Inside the instance, "curl http://169.254.169.254/latest/user-data" should fetch the decoded user data, whereas eucalyptus will return a base64 and url encoded string. This breaks ec2-run-user-data from the ec2-init package, rendering instance configuration using the user-data mechanism unusable.
EC2 documentation at http://docs.amazonwebservices.com/AWSEC2/2007-03-01/DeveloperGuide/AESDG-chapter-instancedata.html states that EC2 will return decoded data (i don't have a ec2 account so i can't confirm this):
"The user data must be base64-encoded before being submitted to the API. The API command-line tools perform the base64-encoding for you. The data will be base64 decoded before being presented to the instance."
=================
Karmic release notes:
user-data not usable by guest instances
Starting an instance with euca-run-instances and user-data (either using the -d option the -f option) will store the user data in base64 encoding. Accessing the user data from the instance at http://169.254.169.254/latest/user-data will return the user data in base64 encoding. Because of this bug ec2-init is unable make use of user-data. In order to use this data it must first be decoded. A fix for this issue is expected to be provided in a post-release update immediately after the Ubuntu 9.10 release.
================== |
User data supplied using "euca-run-instances --user-data-file" is not decoded before being presented to the instance.
Inside the instance, "curl http://169.254.169.254/latest/user-data" should fetch the decoded user data, whereas eucalyptus will return a base64 and url encoded string. This breaks ec2-run-user-data from the ec2-init package, rendering instance configuration using the user-data mechanism unusable.
EC2 documentation at http://docs.amazonwebservices.com/AWSEC2/2007-03-01/DeveloperGuide/AESDG-chapter-instancedata.html states that EC2 will return decoded data (i don't have a ec2 account so i can't confirm this):
"The user data must be base64-encoded before being submitted to the API. The API command-line tools perform the base64-encoding for you. The data will be base64 decoded before being presented to the instance."
=================
Karmic release notes:
user-data not usable by guest instances
Starting an instance with euca-run-instances and user-data (either using the -d, --user-data option or the -f, --user-data-file option) will store the user data in base64 encoding. Accessing the user data from the instance at http://169.254.169.254/latest/user-data will return the user data in base64 encoding. Because of this bug ec2-init is unable make use of user-data. In order to use this data it must first be decoded. A fix for this issue is expected to be provided in a post-release update immediately after the Ubuntu 9.10 release.
================== |
|
| 2009-10-28 20:53:13 |
Mathias Gug |
ubuntu-release-notes: status |
In Progress |
Fix Committed |
|
| 2009-10-28 23:17:02 |
chris grzegorczyk |
eucalyptus: assignee |
|
chris grzegorczyk (chris-grze) |
|
| 2009-10-29 00:35:03 |
Steve Langasek |
ubuntu-release-notes: status |
Fix Committed |
Fix Released |
|
| 2009-11-05 17:52:04 |
Mathias Gug |
tags |
uec-images |
uec uec-images |
|
| 2009-11-09 11:08:16 |
Thierry Carrez |
eucalyptus (Ubuntu): assignee |
Dustin Kirkland (kirkland) |
Thierry Carrez (ttx) |
|
| 2009-11-09 11:08:23 |
Thierry Carrez |
eucalyptus (Ubuntu): milestone |
karmic-updates |
|
|
| 2009-11-09 11:08:31 |
Thierry Carrez |
eucalyptus (Ubuntu Karmic): assignee |
Dustin Kirkland (kirkland) |
Thierry Carrez (ttx) |
|
| 2009-11-09 11:08:40 |
Thierry Carrez |
euca2ools (Ubuntu): milestone |
karmic-updates |
|
|
| 2009-11-09 11:08:58 |
Thierry Carrez |
tags |
uec uec-images |
eucalyptus uec uec-images |
|
| 2009-11-17 17:26:36 |
chris grzegorczyk |
eucalyptus: status |
Confirmed |
Incomplete |
|
| 2009-11-21 07:36:06 |
chris grzegorczyk |
eucalyptus: status |
Incomplete |
Fix Committed |
|
| 2009-11-27 10:10:06 |
Thierry Carrez |
eucalyptus (Ubuntu Karmic): status |
Confirmed |
In Progress |
|
| 2009-11-27 10:10:16 |
Thierry Carrez |
eucalyptus (Ubuntu): status |
Confirmed |
In Progress |
|
| 2009-11-27 10:14:20 |
Launchpad Janitor |
branch linked |
|
lp:~ttx/eucalyptus/karmic-sru2 |
|
| 2009-12-01 15:03:10 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/eucalyptus/ubuntu-karmic |
|
| 2009-12-01 21:33:18 |
Dustin Kirkland |
eucalyptus (Ubuntu): assignee |
Thierry Carrez (ttx) |
Dustin Kirkland (kirkland) |
|
| 2009-12-01 21:42:10 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/eucalyptus/ubuntu |
|
| 2009-12-02 03:15:09 |
Launchpad Janitor |
eucalyptus (Ubuntu): status |
In Progress |
Fix Released |
|
| 2009-12-02 04:07:10 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/eucalyptus |
|
| 2009-12-02 09:03:40 |
Thierry Carrez |
description |
User data supplied using "euca-run-instances --user-data-file" is not decoded before being presented to the instance.
Inside the instance, "curl http://169.254.169.254/latest/user-data" should fetch the decoded user data, whereas eucalyptus will return a base64 and url encoded string. This breaks ec2-run-user-data from the ec2-init package, rendering instance configuration using the user-data mechanism unusable.
EC2 documentation at http://docs.amazonwebservices.com/AWSEC2/2007-03-01/DeveloperGuide/AESDG-chapter-instancedata.html states that EC2 will return decoded data (i don't have a ec2 account so i can't confirm this):
"The user data must be base64-encoded before being submitted to the API. The API command-line tools perform the base64-encoding for you. The data will be base64 decoded before being presented to the instance."
=================
Karmic release notes:
user-data not usable by guest instances
Starting an instance with euca-run-instances and user-data (either using the -d, --user-data option or the -f, --user-data-file option) will store the user data in base64 encoding. Accessing the user data from the instance at http://169.254.169.254/latest/user-data will return the user data in base64 encoding. Because of this bug ec2-init is unable make use of user-data. In order to use this data it must first be decoded. A fix for this issue is expected to be provided in a post-release update immediately after the Ubuntu 9.10 release.
================== |
User data supplied using "euca-run-instances --user-data-file" is not decoded before being presented to the instance.
Inside the instance, "curl http://169.254.169.254/latest/user-data" should fetch the decoded user data, whereas eucalyptus will return a base64 and url encoded string. This breaks ec2-run-user-data from the ec2-init package, rendering instance configuration using the user-data mechanism unusable.
EC2 documentation at http://docs.amazonwebservices.com/AWSEC2/2007-03-01/DeveloperGuide/AESDG-chapter-instancedata.html states that EC2 will return decoded data (i don't have a ec2 account so i can't confirm this):
"The user data must be base64-encoded before being submitted to the API. The API command-line tools perform the base64-encoding for you. The data will be base64 decoded before being presented to the instance."
=================
SRU Report (eucalyptus, euca2ools):
Impact: This bug makes userdata unusable in cloud images used withing UEC. userdata is used for a lot of things, in particular boot-time configuration of our cloud images. This works within EC2 but not within UEC, due to this bug.
This requires a fix in euca2ools (do not b64_encode twice). But fixing it in euca2ools triggers a bug in eucalyptus when certain userdata is received (the previous bug was protecting eucalyptus from this), so this needs a eucalyptus update as well.
Fix in development release: This was fixed in lucid in eucalyptus (1.6.1~bzr1083-0ubuntu1) by applying the same patch. Was not fixed in euca2ools yet.
Minimal patch for eucalyptus:
http://bazaar.launchpad.net/~ubuntu-core-dev/eucalyptus/ubuntu-karmic/revision/726
Minimal patch for euca2ools:
--- euca2ools-1.0+bzr20091007.orig/bin/euca-run-instances
+++ euca2ools-1.0+bzr20091007/bin/euca-run-instances
@@ -170,8 +170,6 @@
print 'Invalid user data file path'
sys.exit(1)
user_data = read_user_data(user_data_file)
- if user_data:
- user_data = base64.urlsafe_b64encode(user_data)
euca_conn = euca.make_connection()
try:
reservation = euca_conn.run_instances(image_id = image_id,
TEST CASE:
euca-run-instances -k $MYKEY --user-data " << FOO >" $EMI -t c1.medium
ssh -i $MYKEYPRIV ubuntu@$IP 'wget -q http://169.254.169.254/latest/user-data -O -'; echo
Expected results: should return " << FOO >"
Fails with affected euca2ools and eucalyptus (returns "IDw8IEZPTyA-" instead of " << FOO >")
Succeeds with proposed euca2ools and proposed eucalyptus.
Regression potential:
The regression potential is small, since userdata is not really usable right now. In euca2ools, only someone relying on the bug (and base64_decoding the userdata in the cloud image itself) would be affected. Regression potential is slightly higher on eucalyptus side, since the fix is about escaping special characters in userdata. Careful testing with various userdata strings (to hit the special characters in the urlsafe-base64-encoded string) is necessary.
=================
Karmic release notes:
user-data not usable by guest instances
Starting an instance with euca-run-instances and user-data (either using the -d, --user-data option or the -f, --user-data-file option) will store the user data in base64 encoding. Accessing the user data from the instance at http://169.254.169.254/latest/user-data will return the user data in base64 encoding. Because of this bug ec2-init is unable make use of user-data. In order to use this data it must first be decoded. A fix for this issue is expected to be provided in a post-release update immediately after the Ubuntu 9.10 release.
================== |
|
| 2009-12-02 09:28:35 |
Thierry Carrez |
description |
User data supplied using "euca-run-instances --user-data-file" is not decoded before being presented to the instance.
Inside the instance, "curl http://169.254.169.254/latest/user-data" should fetch the decoded user data, whereas eucalyptus will return a base64 and url encoded string. This breaks ec2-run-user-data from the ec2-init package, rendering instance configuration using the user-data mechanism unusable.
EC2 documentation at http://docs.amazonwebservices.com/AWSEC2/2007-03-01/DeveloperGuide/AESDG-chapter-instancedata.html states that EC2 will return decoded data (i don't have a ec2 account so i can't confirm this):
"The user data must be base64-encoded before being submitted to the API. The API command-line tools perform the base64-encoding for you. The data will be base64 decoded before being presented to the instance."
=================
SRU Report (eucalyptus, euca2ools):
Impact: This bug makes userdata unusable in cloud images used withing UEC. userdata is used for a lot of things, in particular boot-time configuration of our cloud images. This works within EC2 but not within UEC, due to this bug.
This requires a fix in euca2ools (do not b64_encode twice). But fixing it in euca2ools triggers a bug in eucalyptus when certain userdata is received (the previous bug was protecting eucalyptus from this), so this needs a eucalyptus update as well.
Fix in development release: This was fixed in lucid in eucalyptus (1.6.1~bzr1083-0ubuntu1) by applying the same patch. Was not fixed in euca2ools yet.
Minimal patch for eucalyptus:
http://bazaar.launchpad.net/~ubuntu-core-dev/eucalyptus/ubuntu-karmic/revision/726
Minimal patch for euca2ools:
--- euca2ools-1.0+bzr20091007.orig/bin/euca-run-instances
+++ euca2ools-1.0+bzr20091007/bin/euca-run-instances
@@ -170,8 +170,6 @@
print 'Invalid user data file path'
sys.exit(1)
user_data = read_user_data(user_data_file)
- if user_data:
- user_data = base64.urlsafe_b64encode(user_data)
euca_conn = euca.make_connection()
try:
reservation = euca_conn.run_instances(image_id = image_id,
TEST CASE:
euca-run-instances -k $MYKEY --user-data " << FOO >" $EMI -t c1.medium
ssh -i $MYKEYPRIV ubuntu@$IP 'wget -q http://169.254.169.254/latest/user-data -O -'; echo
Expected results: should return " << FOO >"
Fails with affected euca2ools and eucalyptus (returns "IDw8IEZPTyA-" instead of " << FOO >")
Succeeds with proposed euca2ools and proposed eucalyptus.
Regression potential:
The regression potential is small, since userdata is not really usable right now. In euca2ools, only someone relying on the bug (and base64_decoding the userdata in the cloud image itself) would be affected. Regression potential is slightly higher on eucalyptus side, since the fix is about escaping special characters in userdata. Careful testing with various userdata strings (to hit the special characters in the urlsafe-base64-encoded string) is necessary.
=================
Karmic release notes:
user-data not usable by guest instances
Starting an instance with euca-run-instances and user-data (either using the -d, --user-data option or the -f, --user-data-file option) will store the user data in base64 encoding. Accessing the user data from the instance at http://169.254.169.254/latest/user-data will return the user data in base64 encoding. Because of this bug ec2-init is unable make use of user-data. In order to use this data it must first be decoded. A fix for this issue is expected to be provided in a post-release update immediately after the Ubuntu 9.10 release.
================== |
User data supplied using "euca-run-instances --user-data-file" is not decoded before being presented to the instance.
Inside the instance, "curl http://169.254.169.254/latest/user-data" should fetch the decoded user data, whereas eucalyptus will return a base64 and url encoded string. This breaks ec2-run-user-data from the ec2-init package, rendering instance configuration using the user-data mechanism unusable.
EC2 documentation at http://docs.amazonwebservices.com/AWSEC2/2007-03-01/DeveloperGuide/AESDG-chapter-instancedata.html states that EC2 will return decoded data (i don't have a ec2 account so i can't confirm this):
"The user data must be base64-encoded before being submitted to the API. The API command-line tools perform the base64-encoding for you. The data will be base64 decoded before being presented to the instance."
=================
SRU Report (eucalyptus, euca2ools):
Impact: This bug makes userdata unusable in cloud images used withing UEC. userdata is used for a lot of things, in particular boot-time configuration of our cloud images. This works within EC2 but not within UEC, due to this bug.
This requires a fix in euca2ools (do not b64_encode twice). But fixing it in euca2ools triggers a bug in eucalyptus when certain userdata is received (the previous bug was protecting eucalyptus from this), so this needs a eucalyptus update as well.
Fix in development release: This was fixed in lucid in eucalyptus (1.6.1~bzr1083-0ubuntu1) and in euca2ools (1.0+bzr20091007-0ubuntu2) by applying the same patches.
Minimal patch for eucalyptus:
http://bazaar.launchpad.net/~ubuntu-core-dev/eucalyptus/ubuntu-karmic/revision/726
Minimal patch for euca2ools:
--- euca2ools-1.0+bzr20091007.orig/bin/euca-run-instances
+++ euca2ools-1.0+bzr20091007/bin/euca-run-instances
@@ -170,8 +170,6 @@
print 'Invalid user data file path'
sys.exit(1)
user_data = read_user_data(user_data_file)
- if user_data:
- user_data = base64.urlsafe_b64encode(user_data)
euca_conn = euca.make_connection()
try:
reservation = euca_conn.run_instances(image_id = image_id,
TEST CASE:
euca-run-instances -k $MYKEY --user-data " << FOO >" $EMI -t c1.medium
ssh -i $MYKEYPRIV ubuntu@$IP 'wget -q http://169.254.169.254/latest/user-data -O -'; echo
Expected results: should return " << FOO >"
Fails with affected euca2ools and eucalyptus (returns "IDw8IEZPTyA-" instead of " << FOO >")
Succeeds with proposed euca2ools and proposed eucalyptus.
Regression potential:
The regression potential is small, since userdata is not really usable right now. In euca2ools, only someone relying on the bug (and base64_decoding the userdata in the cloud image itself) would be affected. Regression potential is slightly higher on eucalyptus side, since the fix is about escaping special characters in userdata. Careful testing with various userdata strings (to hit the special characters in the urlsafe-base64-encoded string) is necessary.
=================
Karmic release notes:
user-data not usable by guest instances
Starting an instance with euca-run-instances and user-data (either using the -d, --user-data option or the -f, --user-data-file option) will store the user data in base64 encoding. Accessing the user data from the instance at http://169.254.169.254/latest/user-data will return the user data in base64 encoding. Because of this bug ec2-init is unable make use of user-data. In order to use this data it must first be decoded. A fix for this issue is expected to be provided in a post-release update immediately after the Ubuntu 9.10 release.
==================
|
|
| 2009-12-02 09:29:16 |
Thierry Carrez |
euca2ools (Ubuntu): assignee |
Scott Moser (smoser) |
Thierry Carrez (ttx) |
|
| 2009-12-02 09:30:08 |
Launchpad Janitor |
euca2ools (Ubuntu): status |
In Progress |
Fix Released |
|
| 2009-12-02 09:39:11 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/euca2ools |
|
| 2009-12-03 00:01:01 |
Dustin Kirkland |
eucalyptus (Ubuntu Karmic): status |
In Progress |
Fix Committed |
|
| 2009-12-03 13:47:41 |
Martin Pitt |
tags |
eucalyptus uec uec-images |
eucalyptus uec uec-images verification-needed |
|
| 2009-12-03 14:00:29 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic-proposed/eucalyptus |
|
| 2009-12-03 14:34:15 |
Thierry Carrez |
euca2ools (Ubuntu Karmic): status |
In Progress |
Fix Committed |
|
| 2009-12-10 16:10:34 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic-proposed/euca2ools |
|
| 2009-12-11 10:05:47 |
Thierry Carrez |
tags |
eucalyptus uec uec-images verification-needed |
eucalyptus uec uec-images verification-done |
|
| 2009-12-18 10:34:46 |
Launchpad Janitor |
euca2ools (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
| 2009-12-21 16:00:43 |
Launchpad Janitor |
eucalyptus (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
| 2011-10-28 17:58:25 |
graziano obertelli |
eucalyptus: status |
Fix Committed |
Fix Released |
|
