ConfigDrive with symlink inside breaks cloudbase-init

asked 2019-09-23 19:41:05 +0300

goldyfruit
31 ●3 ●3 ●3 https://blog.incloudus...

updated 2019-09-23 20:01:59 +0300

Hi guys,

I just ran into an issue, I'm using ConfigDrive as MetaData service, the ISO was detected but cloudbase-init was not able to extract it (cf. [1]).

The reason is that my ConfigDrive had a symlink 2015-10-15 pointing to latest and it seems to not be very appreciated on Windows (my Windows knowledge is very poor). After removing the symlink, cloudbase-init was running as expected.

There are two solutions (IMHO):

Let's cloudbase-init detects symlinks and handle them properly
Add a note into the documentation saying that there should be no symlinks into the ConfigDrive

Hope it helps.

[1]: http://paste.openstack.org/show/778950/

edit retag flag offensive close merge delete

Comments

Can you please post a cloudbase-init log on http://paste.openstack.org or similar service and link it here? Thanks

alexpilotti ( 2019-09-23 19:45:08 +0300 )edit

I updated my initial post with a link.

goldyfruit ( 2019-09-23 20:04:19 +0300 )edit

add a comment

2 answers

Sort by » oldest newest most voted

answered 2019-09-23 22:48:27 +0300

goldyfruit
31 ●3 ●3 ●3 https://blog.incloudus...

updated 2019-09-23 22:51:29 +0300

Adrian,

Yeah I'm running Bifrost (Ironic standalone), ConfigDrive ISO are generated manually with genisoimage.

For some compatibility reason with cloud-init I need to have 2015-10-15 version in the ConfigDrive which is pointing as a link to latest (to avoid data duplication).

Just to be clear, I solved my issue by duplicate data (which is not the best but acceptable for now). I opened this question as KB for people who have the same issue.

Let me know if you need more information.

Thank you,

Gaëtan