| 2016-08-30 14:21:55 |
David Coronel |
bug |
|
|
added bug |
| 2016-08-30 17:14:10 |
Andreas Hasenack |
landscape: status |
New |
Triaged |
|
| 2016-08-30 17:14:13 |
Andreas Hasenack |
landscape: importance |
Undecided |
Low |
|
| 2016-10-19 20:06:25 |
David Britton |
tags |
lds-squad |
bug-squad kanban lds-squad |
|
| 2016-12-08 08:28:23 |
Simon Poirier |
landscape: assignee |
|
Simon Poirier (simpoir) |
|
| 2016-12-08 09:17:18 |
Simon Poirier |
landscape: status |
Triaged |
In Progress |
|
| 2017-02-24 14:31:05 |
Simon Poirier |
landscape: assignee |
Simon Poirier (simpoir) |
|
|
| 2017-02-24 14:31:11 |
Simon Poirier |
landscape: status |
In Progress |
Confirmed |
|
| 2017-02-24 14:31:17 |
Simon Poirier |
landscape: status |
Confirmed |
Triaged |
|
| 2017-03-03 10:23:01 |
Alberto Donato |
landscape: assignee |
|
Alberto Donato (ack) |
|
| 2017-03-03 10:23:03 |
Alberto Donato |
landscape: status |
Triaged |
In Progress |
|
| 2017-03-06 14:59:44 |
Alberto Donato |
branch linked |
|
lp:~ack/landscape-client/landscape-config-no-reregister-by-default |
|
| 2017-03-30 21:15:32 |
Alberto Donato |
landscape: status |
In Progress |
Fix Committed |
|
| 2017-10-11 17:37:19 |
Alex Moldovan |
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 |
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 |
|
| 2017-11-10 15:52:18 |
Andreas Hasenack |
information type |
Proprietary |
Public |
|
| 2017-11-10 15:52:29 |
Andreas Hasenack |
affects |
landscape |
landscape-client |
|
| 2017-11-10 15:52:38 |
Andreas Hasenack |
bug task added |
|
landscape-client (Ubuntu) |
|
| 2017-11-10 15:52:47 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-11-10 15:52:47 |
Andreas Hasenack |
bug task added |
|
landscape-client (Ubuntu Xenial) |
|
| 2017-11-10 15:52:47 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Artful |
|
| 2017-11-10 15:52:47 |
Andreas Hasenack |
bug task added |
|
landscape-client (Ubuntu Artful) |
|
| 2017-11-10 15:52:47 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Trusty |
|
| 2017-11-10 15:52:47 |
Andreas Hasenack |
bug task added |
|
landscape-client (Ubuntu Trusty) |
|
| 2017-11-10 15:52:47 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-11-10 15:52:47 |
Andreas Hasenack |
bug task added |
|
landscape-client (Ubuntu Zesty) |
|
| 2017-11-10 16:12:19 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/landscape-client/+git/landscape-client/+merge/333548 |
|
| 2017-11-10 17:18:19 |
Andreas Hasenack |
landscape-client (Ubuntu): status |
New |
In Progress |
|
| 2017-11-10 17:18:22 |
Andreas Hasenack |
landscape-client (Ubuntu): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2017-11-20 17:21:35 |
Launchpad Janitor |
landscape-client (Ubuntu): status |
In Progress |
Fix Released |
|
| 2017-11-23 18:11:21 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/landscape-client/+git/landscape-client/+merge/334203 |
|
| 2017-11-23 18:11:33 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/landscape-client/+git/landscape-client/+merge/334204 |
|
| 2017-11-23 18:11:45 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/landscape-client/+git/landscape-client/+merge/334205 |
|
| 2017-11-23 18:11:56 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/landscape-client/+git/landscape-client/+merge/334206 |
|
| 2017-11-23 18:27:36 |
Eric Desrochers |
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 |
[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]
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
[Regression Potential]
[Other Info]
[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 |
|
| 2017-11-23 18:27:52 |
Eric Desrochers |
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]
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
[Regression Potential]
[Other Info]
[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 |
[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]
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
[Regression Potential]
[Other Info]
[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 |
|
| 2017-11-23 18:33:45 |
Eric Desrochers |
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]
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
[Regression Potential]
[Other Info]
[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 |
[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]
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
[Regression Potential]
[Other Info]
* Upstream revision:
http://bazaar.launchpad.net/~landscape/landscape-client/trunk/revision/939
[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 |
|
| 2017-11-24 12:26:00 |
Andreas Hasenack |
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]
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
[Regression Potential]
[Other Info]
* Upstream revision:
http://bazaar.launchpad.net/~landscape/landscape-client/trunk/revision/939
[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 |
[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]
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
[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!
"""
[Other Info]
* Upstream revision:
http://bazaar.launchpad.net/~landscape/landscape-client/trunk/revision/939
[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 |
|
| 2017-11-24 12:33:32 |
Andreas Hasenack |
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]
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
[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!
"""
[Other Info]
* Upstream revision:
http://bazaar.launchpad.net/~landscape/landscape-client/trunk/revision/939
[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 |
[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]
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
[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
[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 |
|
| 2017-11-24 12:47:07 |
Andreas Hasenack |
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]
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
[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
[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 |
[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]
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
[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 |
|
| 2017-11-24 15:39:26 |
Andreas Hasenack |
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]
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
[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 |
[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 |
|
| 2017-11-24 18:20:21 |
Andreas Hasenack |
landscape-client (Ubuntu Trusty): status |
New |
In Progress |
|
| 2017-11-24 18:20:24 |
Andreas Hasenack |
landscape-client (Ubuntu Xenial): status |
New |
In Progress |
|
| 2017-11-24 18:20:26 |
Andreas Hasenack |
landscape-client (Ubuntu Zesty): status |
New |
In Progress |
|
| 2017-11-24 18:20:28 |
Andreas Hasenack |
landscape-client (Ubuntu Artful): status |
New |
In Progress |
|
| 2017-11-24 18:20:32 |
Andreas Hasenack |
landscape-client (Ubuntu Trusty): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2017-11-24 18:20:34 |
Andreas Hasenack |
landscape-client (Ubuntu Xenial): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2017-11-24 18:20:36 |
Andreas Hasenack |
landscape-client (Ubuntu Zesty): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2017-11-24 18:20:39 |
Andreas Hasenack |
landscape-client (Ubuntu Artful): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2017-11-27 16:17:39 |
Łukasz Zemczak |
landscape-client (Ubuntu Artful): status |
In Progress |
Fix Committed |
|
| 2017-11-27 16:17:41 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-11-27 16:17:44 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2017-11-27 16:17:46 |
Łukasz Zemczak |
tags |
bug-squad kanban lds-squad |
bug-squad kanban lds-squad verification-needed verification-needed-artful |
|
| 2017-11-27 16:27:24 |
Łukasz Zemczak |
landscape-client (Ubuntu Zesty): status |
In Progress |
Fix Committed |
|
| 2017-11-27 16:27:28 |
Łukasz Zemczak |
tags |
bug-squad kanban lds-squad verification-needed verification-needed-artful |
bug-squad kanban lds-squad verification-needed verification-needed-artful verification-needed-zesty |
|
| 2017-11-27 16:32:31 |
Łukasz Zemczak |
landscape-client (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-11-27 16:32:36 |
Łukasz Zemczak |
tags |
bug-squad kanban lds-squad verification-needed verification-needed-artful verification-needed-zesty |
bug-squad kanban lds-squad verification-needed verification-needed-artful verification-needed-xenial verification-needed-zesty |
|
| 2017-11-27 16:38:48 |
Łukasz Zemczak |
landscape-client (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2017-11-27 16:38:53 |
Łukasz Zemczak |
tags |
bug-squad kanban lds-squad verification-needed verification-needed-artful verification-needed-xenial verification-needed-zesty |
bug-squad kanban lds-squad verification-needed verification-needed-artful verification-needed-trusty verification-needed-xenial verification-needed-zesty |
|
| 2017-12-01 21:21:22 |
Mathew Hodson |
landscape-client (Ubuntu): importance |
Undecided |
Low |
|
| 2017-12-01 21:21:24 |
Mathew Hodson |
landscape-client (Ubuntu Trusty): importance |
Undecided |
Low |
|
| 2017-12-01 21:21:26 |
Mathew Hodson |
landscape-client (Ubuntu Xenial): importance |
Undecided |
Low |
|
| 2017-12-01 21:21:28 |
Mathew Hodson |
landscape-client (Ubuntu Zesty): importance |
Undecided |
Low |
|
| 2017-12-01 21:21:30 |
Mathew Hodson |
landscape-client (Ubuntu Artful): importance |
Undecided |
Low |
|
| 2017-12-04 13:45:47 |
Eric Desrochers |
tags |
bug-squad kanban lds-squad verification-needed verification-needed-artful verification-needed-trusty verification-needed-xenial verification-needed-zesty |
bug-squad kanban lds-squad verification-done-artful verification-done-trusty verification-done-xenial verification-done-zesty verification-needed |
|
| 2017-12-05 15:18:11 |
Launchpad Janitor |
landscape-client (Ubuntu Artful): status |
Fix Committed |
Fix Released |
|
| 2017-12-05 15:19:03 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-12-05 15:19:19 |
Launchpad Janitor |
landscape-client (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-12-05 15:20:11 |
Launchpad Janitor |
landscape-client (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-12-05 15:20:30 |
Launchpad Janitor |
landscape-client (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
