View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000069 | Cloud | General | public | 2021-11-24 19:20 | 2023-02-17 03:51 |
Reporter | Neil Hanlon | Assigned To | Neil Hanlon | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | won't fix | ||
Summary | 0000069: AWS Images for 8.5 have 'vmimport'-prefixed sysconfig files | ||||
Description | from: https://www.reddit.com/r/RockyLinux/comments/r1bth4/what_are_these_vmimport_files/ >I have a Rocky Linux 8.5 server on an EC2 instance in AWS. I have files in sysconfig with "vmimport" in their names: ``` # find /etc/sysconfig -iname '*vmimport*' -print /etc/sysconfig/network-scripts/vmimport.ifcfg-ens3-1 /etc/sysconfig/network-scripts/vmimport.ifcfg-ens3 /etc/sysconfig/network-scripts/vmimport.ifcfg-eth0 /etc/sysconfig/vmimport.network ``` > What are these files for? What effect do they have on my running system? Do they get rolled into the other ifcfg files? What do they do? | ||||
Tags | No tags attached. | ||||
These files are created when being imported into AWS by their vmimport process. Trying to find some exact details, but these shouldn't affect anything and can be safely deleted. From a quick search, it appears that the vmimport process renames them on import, presumably to prevent networking issues on boot in case something special was configured. In our case, we specifically craft the eth0 and network configs in our kickstart for EC2, which is in line with upstream, so I'll need to do a bit of poking around to see where this is exactly coming from. Thank you for the tip. I've opened a bug report for this issue. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2023-02-17 03:51 | Neil Hanlon | Status | assigned => closed |
2023-02-17 03:51 | Neil Hanlon | Resolution | open => won't fix |