[Bug 1691428] [NEW] LXDAPIException: json: cannot unmarshal bool into Go value of type string when using config-drive

[James Page]

Public bug reported:

[Impact]
Not possible to use the config-drive support (as currently in yakkety-proposed, zesty and artful)

[Test Case]
Deploy Nova-LXD based OpenStack Cloud
openstack server create --wait --image xenial --flavor m1.small --key-name testkey --nic net-id=XXXX --min 1 --max 1 --config-drive True xenial-config-drive
instance will go into ERROR state and fail to boot.

[Regression Potential]
Minimal; this feature has never worked correctly, the fix resolves and issue with passing the readonly flag for the config-drive device as a boolean rather than a string (as required by the LXD API).

[Original Bug Report]
When booting instances using the --config-drive flag, the instance fail to boot with the following error:

  LXDAPIException: json: cannot unmarshal bool into Go value of type
string

nova-lxd is passing the 'readonly' flag as a boolean, not as a string,
and the LXD API fails to unmarshall it as a result.

** Affects: cloud-archive
     Importance: Undecided
         Status: New

** Affects: cloud-archive/newton
     Importance: Undecided
         Status: New

** Affects: cloud-archive/ocata
     Importance: Undecided
         Status: New

** Affects: cloud-archive/pike
     Importance: Undecided
         Status: New

** Affects: nova-lxd
     Importance: Undecided
         Status: New

** Affects: nova-lxd (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: nova-lxd (Ubuntu Yakkety)
     Importance: Undecided
         Status: New

** Affects: nova-lxd (Ubuntu Zesty)
     Importance: Undecided
         Status: New

** Affects: nova-lxd (Ubuntu Artful)
     Importance: Undecided
         Status: New

** Also affects: nova-lxd (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: nova-lxd (Ubuntu Artful)
   Importance: Undecided
       Status: New

** Also affects: nova-lxd (Ubuntu Zesty)
   Importance: Undecided
       Status: New

** Also affects: nova-lxd (Ubuntu Yakkety)
   Importance: Undecided
       Status: New

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/newton
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/ocata
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/pike
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova-lxd in Ubuntu.
https://bugs.launchpad.net/bugs/1691428

Title:
  LXDAPIException: json: cannot unmarshal bool into Go value of type
  string when using config-drive

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive newton series:
  New
Status in Ubuntu Cloud Archive ocata series:
  New
Status in Ubuntu Cloud Archive pike series:
  New
Status in nova-lxd:
  New
Status in nova-lxd package in Ubuntu:
  New
Status in nova-lxd source package in Yakkety:
  New
Status in nova-lxd source package in Zesty:
  New
Status in nova-lxd source package in Artful:
  New

Bug description:
  [Impact]
  Not possible to use the config-drive support (as currently in yakkety-proposed, zesty and artful)

  [Test Case]
  Deploy Nova-LXD based OpenStack Cloud
  openstack server create --wait --image xenial --flavor m1.small --key-name testkey --nic net-id=XXXX --min 1 --max 1 --config-drive True xenial-config-drive
  instance will go into ERROR state and fail to boot.

  [Regression Potential]
  Minimal; this feature has never worked correctly, the fix resolves and issue with passing the readonly flag for the config-drive device as a boolean rather than a string (as required by the LXD API).

  [Original Bug Report]
  When booting instances using the --config-drive flag, the instance fail to boot with the following error:

    LXDAPIException: json: cannot unmarshal bool into Go value of type
  string

  nova-lxd is passing the 'readonly' flag as a boolean, not as a string,
  and the LXD API fails to unmarshall it as a result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1691428/+subscriptions