Same warning, regarding deprecation of use-floating-ip, seen 3 times during bootstrap.

Bug #1897944 reported by Heather Lanigan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Medium
Heather Lanigan
2.9
Fix Released
Medium
Heather Lanigan

Bug Description

Warning 1 time in the same command is sufficient.

$ juju bootstrap serverstack test-ipv6
WARNING Config attribute "use-floating-ip" is deprecated.
You can instead use the constraint "allocate-public-ip".
Creating Juju controller "test-ipv6" on serverstack/serverstack
Looking for packaged Juju agent version 2.9-beta1 for amd64
No packaged binary found, preparing local Juju agent binary
WARNING Config attribute "use-floating-ip" is deprecated.
You can instead use the constraint "allocate-public-ip".
Launching controller instance(s) on serverstack/serverstack...
 - cc323e34-9e09-4ad5-869b-83ad860956fd (arch=amd64 mem=4G cores=2), wait 10 seconds before retry, attempt 1
WARNING Config attribute "use-floating-ip" is deprecated.
You can instead use the constraint "allocate-public-ip".
Installing Juju agent on bootstrap instance
Fetching Juju Dashboard 0.2.0
Waiting for address
Attempting to connect to 10.x.x.x:22
Attempting to connect to 10.x.x.x:22
Connected to 10.x.x.x
Running machine configuration script...
Bootstrap agent now started
Contacting Juju controller at 10.x.x.x to verify accessibility...

Bootstrap complete, controller "test-ipv6" is now available
Controller machines are in the "controller" model
Initial model "default" added

Changed in juju:
status: New → Triaged
importance: Undecided → Medium
tags: added: bitesize usability
Revision history for this message
Heather Lanigan (hmlanigan) wrote :

One way to resolve the too many warnings, remove the deprecated config.

Changed in juju:
status: Triaged → In Progress
assignee: nobody → Heather Lanigan (hmlanigan)
milestone: none → 3.0.0
Revision history for this message
Heather Lanigan (hmlanigan) wrote :
Revision history for this message
Heather Lanigan (hmlanigan) wrote :

2.9 upgrade step to remove unnecessary warnings when value set to false and not used anyways. https://github.com/juju/juju/pull/14242

Revision history for this message
Heather Lanigan (hmlanigan) wrote :

This is as resolved as it will be. The warnings will not be removed in total for 2.9.x, but quieted some. The config key has been removed in 3.0

Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.