Comment 36 for bug 1790213

Revision history for this message
Erich Cordoba (ericho) wrote :

It has been found out that the issue was some bad permission in the RPMs from the mirror.

These RPMs are stored into the ISO and then put it into /www/pages/feed/<release>/Packages/ to be used by anaconda in the provision of an additional controller or compute. As the http server that runs there runs as non-root, the files couldn't be served, thus causing a failure in the installation of the packages. See[0] and [1]

After changing the permissions to 644, now the system is able to boot. A proposed next step is to ensure that the files under /www/pages/feed/<release>/Packages has the correct permission to be read by the web server, this could be done through a kickstart script.

However, as this has been root caused I recommend to lower the importance (maybe Medium) as this is not a blocking issue anymore.

[0] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-September/001057.html
[1] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-September/001056.html