This bug was fixed in the package landscape-client - 16.03-0ubuntu3.17.10.1
--------------- landscape-client (16.03-0ubuntu3.17.10.1) artful; urgency=medium [ Simon Poirier ] * Add proxy handling to package reporter. (LP: #1531150) * Fix regression in configuration hook under install-cd chroot (LP: #1699789) * Report autoremovable packages (LP: #1208393) * No not re-register client by default (LP: #1618483) -- Andreas Hasenack <[email protected]> Fri, 10 Nov 2017 15:44:17 -0200 ** Changed in: landscape-client (Ubuntu Artful) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1618483 Title: landscape-config new registration request prompt should default to no for subsequent runs Status in Landscape Client: Fix Committed Status in landscape-client package in Ubuntu: Fix Released Status in landscape-client source package in Trusty: Fix Released Status in landscape-client source package in Xenial: Fix Released Status in landscape-client source package in Zesty: Fix Released Status in landscape-client source package in Artful: Fix Released Bug description: [Impact] When running landscape-config, this prompt always defaults to Yes: "Request a new registration for this computer now? (Y/n):" The landscape-config command can be used to change configuration options in /etc/landscape/client.conf and should default to No when running this command on a computer that is already registered to a Landscape server and that server doesn't change during that run of landscape-config. [Test Case] 1) Install landscape-client package on computer. 2) Run landscape-config to register client for the first time. Note how the default answer for the registration question is "Y" 3) Run landscape-config again to change an option: sudo landscape-config --ping-interval=60 4) Verify that the question about requesting a new registration defaults to "N" this time. [Regression Potential] Admins and scripts who relied on the old behavior might be surprised that a new registration is not requested anymore by default if the client is already registered, but I believe it's a welcomed change. It was even a sort of known issue in our FAQ (https://help.landscape.canonical.com/RunningScripts#Enabling%20script%20execution): """ /!\ Very important: when using this method [Ed: calling landscape-config], you MUST NOT request a new registration for the computer, as that will create a duplicate machine in your Landscape account! """ If there is a regression here, it will just affect the default answer given to the "do you wanted to register" question. The admin can still answer however he/she wishes. [Other Info] * Upstream revision: http://bazaar.launchpad.net/~landscape/landscape-client/trunk/revision/939 This PPA has test packages built from these branches, using a ~ppaN suffix: https://launchpad.net/~ahasenack/+archive/ubuntu/lsclient-sru-1721383 --- Original description --- When running landscape-config, this prompt always defaults to Yes: "Request a new registration for this computer now? (Y/n):" The landscape-config command can be used to change configuration options in /etc/landscape/client.conf and should default to No when running this command on a computer that is already registered to a Landscape server and that server doesn't change during that run of landscape-config. Steps to replicate: 1) Install landscape-client package on computer $ sudo apt-get install landscape-client 2) Run landscape-config to register client for the first time $ sudo landscape-config --account-name standalone --url https://<server>/message-system --ping-url http://<server>/ping 3) Run landscape-config again to change an option $ sudo landscape-config --ping-interval=60 [Test Case] When running landscape-config, this prompt always defaults to Yes: "Request a new registration for this computer now? (Y/n):" The landscape-config command can be used to change configuration options in /etc/landscape/client.conf and should default to No when running this command on a computer that is already registered to a Landscape server and that server doesn't change during that run of landscape-config. To reproduce: 1) Install landscape-client package on computer. 2) Run landscape-config to register client for the first time. 3) Run landscape-config again to change an option: sudo landscape-config --ping-interval=60 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1618483/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : [email protected] Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
