V38581: Failed to create the hardlink for /boot/grub.conf about ash-linux-formula HOT 3 CLOSED

In general, /boot/grub.conf should always exist (GRUB generally won't boot the system without it since its contents tell GRUB where to find the subsequent parts of the boot-time chain-load of the OS). This handler is in place mostly to ensure that the other (mostly redundant) pointers to the cardinal grub.conf are also present. My assumption on the "could not create" is that Salt is ungracefully complaining that the target already exists (stuff run from 'module.run' seem to have less-graceful handling of such "already-exists" types of scenarios).

from ash-linux-formula.

There's some kind of conflict in the handling of /boot/grub.conf. It seems the end result is desired for it to be a hard link to /boot/grub/grub.conf. On the centos build, that's how it starts out, as well. But after running the ash-linux states, it's a hard link to /boot/grub/grub.conf.bak. /boot/grub/grub.conf is actually a different file. I'm guessing the conflict is in one of the other states using file.replace on /boot/grub/grub.conf...

from ash-linux-formula.

Ok, I figured out the logic and inter-play between V38579, V38581, and V38583 that was causing the error where it could not create the hard link. I've resolved that with an unless test that executes at run-time rather than render-time. I'm going to create a new issue to track the conflict with file.replace where the hard link ends up pointing to the wrong file.

file_V{{ stig_id }}-hardlink:
  module.run:
    - name: 'file.link'
    - src: '/boot/grub/grub.conf'
    - path: '/boot/grub.conf'
    - unless: 'test -e /boot/grub.conf'

from ash-linux-formula.