lxd/kvm integration test failures due to changed metadata value

Bug #1797155 reported by Chad Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Invalid
High
Chad Smith

Bug Description

Cosmic integration tests are failing on lxd and nocloud kvm platforms due to failed/invalid assertions.

v1_data (instance-data.json) changed cloud_name for nocloud kvm and lxd to report 'nocloud' instead of 'unknown' for the cloud_name key. Need to fix test assertions.

FAIL: test_instance_data_json_kvm (tests.cloud_tests.testcases.bugs.lp1628337.TestLP1628337)
Validate instance-data.json content by nocloud-kvm platform.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-integration-nocloud-kvm-c/cloud-init/tests/cloud_tests/testcases/base.py", line 263, in test_instance_data_json_kvm
    self.assertEqual('unknown', v1_data['cloud_name'])
AssertionError: 'unknown' != 'nocloud'
- unknown

FAIL: test_instance_data_json_lxd (tests.cloud_tests.testcases.modules.ssh_auth_key_fingerprints_disable.TestSshKeyFingerprintsDisable)
Validate instance-data.json content by lxd platform.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-integration-lxd-c/cloud-init/tests/cloud_tests/testcases/base.py", line 226, in test_instance_data_json_lxd
    self.assertEqual('unknown', v1_data['cloud_name'])
AssertionError: 'unknown' != 'nocloud'
- unknown
+ nocloud

Chad Smith (chad.smith)
Changed in cloud-init:
importance: Undecided → High
status: New → In Progress
assignee: nobody → Chad Smith (chad.smith)
Chad Smith (chad.smith)
Changed in cloud-init:
status: In Progress → Invalid
Revision history for this message
Chad Smith (chad.smith) wrote :

Marked invalid. This failure was due to cloud-init's integration tests filed LP: #1797189 to track integration test fixes.

Revision history for this message
James Falcon (falcojr) wrote :
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.