By default, all config drive types are checked.
But if somehow, the implementation of each type
fails, the metadata service errors out and does not
check for the next type.
The issue was reported here:
https://ask.cloudbase.it/question/3094/windows-server-2016-extendvolumespluginp-doesnt-work/
In that case, in the method is_vfat_drive:
match = VOLUME_LABEL_REGEX.search(out)
return match.group(1) in CONFIG_DRIVE_LABELS
if match value is None, the return line throws an error:
AttributeError: 'NoneType' object has no attribute 'group'
To make sure that no other implementation will bubble up
the error, we catch the error in the config_drive metadata
service.
Catching the error will allow that the next config_drive
type will be checked for metadata.
Change-Id: I0d9967ec6a81214c7d78be667cffa4a98758587a
5dba5c60f6