[Bug 992970] Re: samba-interop not compatible with precise samba 3.6
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992970 Title: samba-interop not compatible with precise samba 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/992970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 534629] Re: AssumeDefaultDomain does not work
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] HomeDirTemplate=%H/%D/%U SpaceReplacement=- AssumeDefaultDomain=dword:0001 NssGroupMembersQueryCacheOnly=dword:0001 RequireMembershipOf=sza: -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of linux.girl Sent: Wednesday, February 08, 2012 10:41 AM To: pet...@xley.com Subject: [Bug 534629] Re: AssumeDefaultDomain does not work Hello, I am using oneiric oncelot 64 bit with likewise version 6.1.0.406 and assumedefaultdomain is not working for me. Is there a fix for this? Thanks in advance, linux.girl -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/534629 Title: AssumeDefaultDomain does not work Status in “likewise-open” package in Ubuntu: Fix Committed Status in “likewise-open” source package in Lucid: Confirmed Status in “likewise-open” source package in Maverick: Confirmed Bug description: Binary package hint: likewise-open Setting AssumeDefaultDomain=dword:0001 does not work with likewise-open 5.4.0.39949-3 on Ubuntu 10.04 (development branch) 64 bit. IMPACT STATEMENT Many Likewise Open prefer to set AssumeDefaultDomain, as it make the users/groups name more consistent with local one. It is particularly true in deployment where there is a single domain, where prepending the domain name would be somewhat redundant anyway. Moreover, this is a regression. People upgrading to a version of likewise-open where the AssumeDefaultDomain work as expected will find their user/group names have changed, and that they now need to prepend them with the domain name and separator. TEST CASE = Steps to reproduce: 1. Install likewise-open, join domain. 2. Check likewise behavior: getent passwd domain\\testuser returns information, getent passwd testuser does not. 3. Change AssumeDefaultDomain to dword:0001 in /etc/likewise-open/lsassd.reg 4. Run lwregshell import /etc/likewise-open/lsassd.reg 5. Run lw-refresh-configuration 6. Check behavior again: getent passwd testuser should return information 7. Logins without domain included should work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/534629/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/534629 Title: AssumeDefaultDomain does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/534629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611137] Re: cc_mounts may need to translate device names for xvda or virtio
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582667] Re: add support for set selections
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582667] Re: add support for set selections
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613309] Re: cloud-run-user-script.conf upstart script needs to run after all other cloud-init processes
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 Server Team, which is a direct subscriber. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 613309] Re: cloud-run-user-script.conf upstart script needs to run after all other cloud-init processes
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 - python-software-properties - chef - rubygems - Custom script to configure chef - validation.pem role list and node id (instance-id) from meta-data service -- 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 Server Team, which is a direct subscriber. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 613309] Re: cloud-run-user-script.conf upstart script needs to run after all other cloud-init processes
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613309] Re: cloud-run-user-script.conf upstart script needs to run after all other cloud-init processes
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 - python-software-properties - chef - rubygems - Custom script to configure chef - validation.pem role list and node id (instance-id) from meta-data service -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534629] Re: AssumeDefaultDomain does not work
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 dead. . on boot.. I see: lwreg running (standalone: 1491) dcerpc running (standalone: 1653) eventlogrunning (standalone: 2075) lsass dead lwiorunning (standalone: 2438) netlogonrunning (standalone: 1726) npfsrunning (io: 2438) pvfsstopped rdr running (io: 2438) srv stopped srvsvc stopped ~ppa7 error lsassd on 64bit r...@ubuntu:~# lsassd 20100809221100:INFO:0x7f3c8994d760:Lsass crashed with signal 11 20100809221100:INFO:0x7f3c8994d760:0 - lsassd() [0x406bb3] 20100809221100:INFO:0x7f3c8994d760:1 - /usr/lib/likewise-open/liblwbase_nothr.so.0(LwRtlRBTreeFind+0x18) [0x7f3c847022f8] 20100809221100:INFO:0x7f3c8994d760:2 - /usr/lib/likewise-open/liblwbase_nothr.so.0(LwRtlRBTreeFind+0x18) [0x7f3c847022f8] 20100809221100:INFO:0x7f3c8994d760:3 - /usr/lib/likewise-open/libsamdb.so(SamDbAttributeLookupByName+0x1e) [0x7f3c7a7cd62e] 20100809221100:INFO:0x7f3c8994d760:4 - /usr/lib/likewise-open/libsamdb.so(SamDbSearchObject_inlock+0x3f9) [0x7f3c7a7d9129] 20100809221100:INFO:0x7f3c8994d760:5 - /usr/lib/likewise-open/libsamdb.so(SamDbSearchObject+0x78) [0x7f3c7a7d9b18] 20100809221100:INFO:0x7f3c8994d760:6 - /usr/lib/likewise-open/libsamdb.so(+0xa53b) [0x7f3c7a7d153b] 20100809221100:INFO:0x7f3c8994d760:7 - /usr/lib/likewise-open/libsamdb.so(SamDbInit+0x208) [0x7f3c7a7d5f48] 20100809221100:INFO:0x7f3c8994d760:8 - /usr/lib/likewise-open/libsamdb.so(DirectoryInitializeProvider+0x147) [0x7f3c7a7d6137] 20100809221100:INFO:0x7f3c8994d760:9 - /usr/lib/likewise-open/libdsapi.so.0(DirectoryLoadProvider+0x100) [0x7f3c88b16f30] 20100809221100:INFO:0x7f3c8994d760:10 - /usr/lib/likewise-open/libdsapi.so.0(DirectoryGetProvider+0xbe) [0x7f3c88b1711e] 20100809221100:INFO:0x7f3c8994d760:11 - /usr/lib/likewise-open/libdsapi.so.0(DirectoryOpen+0x2c) [0x7f3c88b16c7c] 20100809221100:INFO:0x7f3c8994d760:12 - /usr/lib64/likewise-open/liblsass_auth_provider_local.so(LocalSyncDomainInfo+0xc5d) [0x7f3c7abff9fd] 20100809221100:INFO:0x7f3c8994d760:13 - /usr/lib64/likewise-open/liblsass_auth_provider_local.so(LsaInitializeProvider2+0x16d) [0x7f3c7ac07e5d] 20100809221100:INFO:0x7f3c8994d760:14 - /usr/lib/likewise-open/liblsaserverapi.so.0(LsaSrvInitAuthProvider+0x9e) [0x7f3c8954510e] 20100809221100:INFO:0x7f3c8994d760:15 - /usr/lib/likewise-open/liblsaserverapi.so.0(LsaSrvInitAuthProviders+0x797) [0x7f3c895461c7] 20100809221100:INFO:0x7f3c8994d760:16 - /usr/lib/likewise-open/liblsaserverapi.so.0(LsaSrvApiInit+0x2c0) [0x7f3c8954d040] 20100809221100:INFO:0x7f3c8994d760:17 - lsassd() [0x404127] 20100809221100:INFO:0x7f3c8994d760:18 - lsassd() [0x4065ef] 20100809221100:INFO:0x7f3c8994d760:19 - /lib/libc.so.6(__libc_start_main+0xfd) [0x7f3c83903c4d] 20100809221100:INFO:0x7f3c8994d760:20 - lsassd() [0x402f89] Segmentation fault -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613309] Re: cloud-run-user-script.conf upstart script needs to run after all other cloud-init processes
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 there is still an issue with ordering and making sure these upstart scripts all complete prior to the execution of 'cloud-run-user-script.conf' -- 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 Server Team, which is a direct subscriber. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 613309] Re: cloud-run-user-script.conf upstart script needs to run after all other cloud-init processes
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 there is still an issue with ordering and making sure these upstart scripts all complete prior to the execution of 'cloud-run-user-script.conf' -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534629] Re: AssumeDefaultDomain does not work
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613309] Re: upstart scripts do not wait for 'cloud-config' status
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 the upstart/cloud-run-user-script.conf what for a status after the other cloud-init processes have completed. This will allow users to configure/execute programs that were installed during the cloud-init process. Thanks for taking your time to understand my issue, also allowing me to work through my miss-configuration. ** Summary changed: - upstart scripts do not wait for 'cloud-config' status + cloud-run-user-script.conf upstart script needs to run after all other cloud-init processes ** Patch removed: This is the upstart scripts that I had to use to make this functional. http://launchpadlibrarian.net/53029398/cloud-init.patch -- 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 Server Team, which is a direct subscriber. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 613309] Re: upstart scripts do not wait for 'cloud-config' status
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 the upstart/cloud-run-user-script.conf what for a status after the other cloud-init processes have completed. This will allow users to configure/execute programs that were installed during the cloud-init process. Thanks for taking your time to understand my issue, also allowing me to work through my miss-configuration. ** Summary changed: - upstart scripts do not wait for 'cloud-config' status + cloud-run-user-script.conf upstart script needs to run after all other cloud-init processes ** Patch removed: This is the upstart scripts that I had to use to make this functional. http://launchpadlibrarian.net/53029398/cloud-init.patch -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613309] Re: upstart scripts do not wait for 'cloud-config' status
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 metadata/userdata everything else worked. I will try and pull the maverick sources and see what I get just from the repo with out any patching. (but i will run them on a lucid uec image).. once i figure out my ssh issue in my cloud :) More info to come! Thanks for the info. -- upstart scripts do not wait for 'cloud-config' status https://bugs.launchpad.net/bugs/613309 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 613309] Re: upstart scripts do not wait for 'cloud-config' status
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 metadata/userdata everything else worked. I will try and pull the maverick sources and see what I get just from the repo with out any patching. (but i will run them on a lucid uec image).. once i figure out my ssh issue in my cloud :) More info to come! Thanks for the info. -- upstart scripts do not wait for 'cloud-config' status https://bugs.launchpad.net/bugs/613309 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582667] Re: add support for set selections
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582667] Re: add support for set selections
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613309] Re: upstart scripts do not wait for 'cloud-config' status
** 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. cloud-apt-update-upgrade.conf cloud-config-misc.conf cloud-config-mounts.conf cloud-config-ssh.conf cloud-disable-ec2-metadata.conf cloud-ec2-ebs-mounts.conf cloud-raid.conf cloud-runurl.conf ~~ - most of these need to just add 'and cloud-init' but one or two need to just 'start on cloud-init' + most of these need to just add 'and cloud-config' but one or two need to just 'start on cloud-config' ~~~ cloud-run-user-script.conf needs 'start on (stopped rc RUNLEVEL=[2345] and stopped cloud-config- misc)' - - We need this package to work in ec2 as well as UEC otherwise it make provisioning of a new instance much harder and defeats the purpose of this package. Since Lucid is LTS I would like to see a SRU for this issue as well since it prevent out of the box/repo use of this feature. + We need this package to work in ec2 as well as UEC otherwise it make + provisioning of a new instance much harder and defeats the purpose of + this package. Since Lucid is LTS I would like to see a SRU for this + issue as well since it prevent out of the box/repo use of this feature. -- upstart scripts do not wait for 'cloud-config' status https://bugs.launchpad.net/bugs/613309 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582667] Re: add support for set selections
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 stopped cloud-config-misc)' I will create a new issue but I feel this should be fixed prior to the SRU since this will prevent the usage of the cloud-init in UEC and maybe ec2. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613309] [NEW] upstart scripts do not wait for 'cloud-config' status
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 cloud-config-misc.conf cloud-config-mounts.conf cloud-config-ssh.conf cloud-disable-ec2-metadata.conf cloud-ec2-ebs-mounts.conf cloud-raid.conf cloud-runurl.conf ~~ most of these need to just add 'and cloud-init' but one or two need to just 'start on cloud-init' ~~~ cloud-run-user-script.conf needs 'start on (stopped rc RUNLEVEL=[2345] and stopped cloud-config- misc)' We need this package to work in ec2 as well as UEC otherwise it make provisioning of a new instance much harder and defeats the purpose of this package. Since Lucid is LTS I would like to see a SRU for this issue as well since it prevent out of the box/repo use of this feature. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: ec2 uec upstart userdata -- upstart scripts do not wait for 'cloud-config' status https://bugs.launchpad.net/bugs/613309 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613309] Re: upstart scripts do not wait for 'cloud-config' status
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582667] Re: add support for set selections
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534629] Re: AssumeDefaultDomain does not work
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582667] Re: add support for set selections
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 syntax in the cloud-init config file, only enabling additional support, prior configuration files will not break. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582667] Re: add support for set selections
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582667] [NEW] add support for set selections
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 with configuration management systems such as CHEF, and PUPPET. Though some of these prereqs have user directed input required on install. Trying to stay away from the golden image complex, cloud- init could benefit from implementing the debconf set selections. I have seen a purposed syntax in the TODO file in the example directory and I feel that would be a great addition. If I have time I might work on a patch and update this Bug/ER when I have time. Till then I wanted to see if others are limited by this issue like myself. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: cloud ec2 wishlist -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510683] Re: 'lsassd' has to be restarted in order to login
** 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510683] Re: 'lsassd' has to be restarted in order to login
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 on your side with similar hardware? Since lo interface can come up without a link, I may theorize that you are correct the DHCP process is taking long and lssad is not able to start correctly. -- '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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510683] Re: 'lsassd' has to be restarted in order to login
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 creds I have not see this work since upgrading to lucid. I was wondering if this is also a lssad issue since it is not running on startup correctly? Dunno. -- '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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
