Does samba-interop-install just update configuration files , if so can
you hand edit them to make likewise and samba work in precise? Since
precise is LTS can this be fixed please and pushed through SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have oneiric running with 6.1.0.406-0ubuntu4 and it is functioning. I
am overriding the following in the registry only from the default
package settings.
[HKEY_THIS_MACHINE\Services\lsass\Parameters]
SpaceReplacement=-
[HKEY_THIS_MACHINE\Services\lsass\Parameters\Providers\ActiveDirectory]
I merged this change to DataSourceEc2.py to my local repo for lucid
could we get this applied to lucid updates as well?
--
cc_mounts may need to translate device names for xvda or virtio
https://bugs.launchpad.net/bugs/611137
You received this bug notification because you are a member of Ubuntu
Scott did this get uploaded correctly?? I don't see it in the SRU
process.
--
add support for set selections
https://bugs.launchpad.net/bugs/582667
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I didn't see it here..
https://launchpad.net/ubuntu/lucid/+queue?queue_state=1
But now i do. :) so its all cool. Sorry
--
add support for set selections
https://bugs.launchpad.net/bugs/582667
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Sure will do, I am working on this stuff right now so once the build is
done I will deploy.
--
cloud-run-user-script.conf upstart script needs to run after all other
cloud-init processes
https://bugs.launchpad.net/bugs/613309
You received this bug notification because you are a member of Ubuntu
Looks good Scott. Everything seem to start and execute in the correct
order.
* I purged all packages and installed via user-data and executed custom
user run script.
Which included the following:
- Custom apt repo
- Custom key for repo
- packages:
- curl
- pwgen
- pastebinit
Sure will do, I am working on this stuff right now so once the build is
done I will deploy.
--
cloud-run-user-script.conf upstart script needs to run after all other
cloud-init processes
https://bugs.launchpad.net/bugs/613309
You received this bug notification because you are a member of Ubuntu
Looks good Scott. Everything seem to start and execute in the correct
order.
* I purged all packages and installed via user-data and executed custom
user run script.
Which included the following:
- Custom apt repo
- Custom key for repo
- packages:
- curl
- pwgen
- pastebinit
What version was the ppa for likewise when this fix was committed and
verified. Currently the ~ppa7 version fails to start lsassd on an amd64
system and ~ppa6 lsassd only will run when exeucted by hand (lsassd
--start-as-daemon --syslog). lwsm does not start the service correctly
and reports
Looking at 'cloud-config-misc.conf' script this only waits for the
filesystem. What prevents this from running prior to the cloud-init
upstart script? 'cloud-config-misc.conf' also is what the 'cloud-run-
user-script.conf' waits for to stop to allow the user scripts to run
after it. So I think
Looking at 'cloud-config-misc.conf' script this only waits for the
filesystem. What prevents this from running prior to the cloud-init
upstart script? 'cloud-config-misc.conf' also is what the 'cloud-run-
user-script.conf' waits for to stop to allow the user scripts to run
after it. So I think
Have we started the SRU (Lucid) process for this as well as (LP:
#575152)?
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Ok Scott, yup I was seeing two issues but after I fixed my metadata
issue in UEC you are correct. The main problem I am having is that the
user scripts run while apt-get is installing packages that are used in
my user run script.
So I will update the bug to reflect the following:
** Please have
Ok Scott, yup I was seeing two issues but after I fixed my metadata
issue in UEC you are correct. The main problem I am having is that the
user scripts run while apt-get is installing packages that are used in
my user run script.
So I will update the bug to reflect the following:
** Please have
Sorry about that Scott yes I had an old source for the cloud-init
upstart script your correct about the mount point.
The issue I was seeing is that the system was trying to query user data
prior to the system loading it from the meta data service. So by
waiting for cloud-init to load the
Sorry about that Scott yes I had an old source for the cloud-init
upstart script your correct about the mount point.
The issue I was seeing is that the system was trying to query user data
prior to the system loading it from the meta data service. So by
waiting for cloud-init to load the
See (LP #613309) for the upstart issue.
--
add support for set selections
https://bugs.launchpad.net/bugs/582667
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
If your regarding the patch to the upstart scripts I attached it to (LP:
#613309).
--
add support for set selections
https://bugs.launchpad.net/bugs/582667
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Description changed:
Binary package hint: cloud-init
All lucid/maverick source packages,
The following upstart scripts need to wait for the 'cloud-config' status
in addition to what they currently wait for, otherwise userdata might
not be loaded yet.
Set selection works, but the upstart scripts do not wait for the
'cloud-config' status.
So some of the scripts start too soon. I had to make most of the
scripts use 'start on filesystem and cloud-config' and I made the cloud-
run-user-scripts use 'start on (stopped rc RUNLEVEL=[2345] and
Public bug reported:
Binary package hint: cloud-init
All lucid/maverick source packages,
The following upstart scripts need to wait for the 'cloud-config' status
in addition to what they currently wait for, otherwise userdata might
not be loaded yet.
cloud-apt-update-upgrade.conf
** Patch added: This is the upstart scripts that I had to use to make this
functional.
http://launchpadlibrarian.net/53029398/cloud-init.patch
--
upstart scripts do not wait for 'cloud-config' status
https://bugs.launchpad.net/bugs/613309
You received this bug notification because you are a
Sure I will add it to my UEC image and give it a shot once the PPA build
is done and let you know.
--
add support for set selections
https://bugs.launchpad.net/bugs/582667
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I can confirm by using that
https://launchpad.net/~mgariepy/+archive/ppa, likewise once again works
as expected on my 32bit laptop (cache creds) and 64 server instance
(cloud). Will we see this soon in a SRU?
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You
Information for SRU:
* Since Lucid is an LTS release and cloud computing is here to stay.
* Having a way to preconfigured packages installed by cloud-init using
dpkg-setselection is necessary to help people stay away from golden images.
* adding this LP issue does not change any existing
Is there a possibility with getting this added to lucid-updates?
--
add support for set selections
https://bugs.launchpad.net/bugs/582667
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: cloud-init
-- Lucid, x86 x64
With the evolution of the cloud packages like this make it much easier
for provisioning base configurations. With that the ability of
installing packages in to the instance on initial startup provides much
flexibility
** Tags added: likewise lucid upstart
--
'lsassd' has to be restarted in order to login
https://bugs.launchpad.net/bugs/510683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Gerald, just thought of something and will test once I get in the
office. We are using CISCO switches that have portfast on them and so
do many production environments. This slows the time that the link will
become enabled with protocol up and intern slows the DHCP process. Have
you tested this
Ok so disabling portfast makes it work, so it looks like the only real
solution would be to write upstart scripts. Side note why doesn't
likewise handle the reconnect once networking is started?
What happens for laptop users when not connected to the dc? In karmic
this works fine using cached
31 matches
Mail list logo
