Unsolved
This post is more than 5 years old
9 Posts
0
7505
July 2nd, 2015 10:00
OME 2.0 not updating after changing catalog
I'm having some issues and was hoping someone could provide some tips. I changed my catalog file to not include certain updates and I have set it to the active catalog in OME but it's still referencing the old catalog with the updates that I don't plan on using so I'm getting lots of erroneous non-compliant servers.
I have also had some issues with getting OME to refresh the status of servers after updates have been applied. They will still show the servers need updates even though they were already applied. In that case, if I run inventory and relaunch OME interface again it usually corrects the problem within a few minutes but in the case of the new catalog nothing seems to work.
Does anyone know of a way to force OME to use a new catalog and stop referencing the old one?
DELL-Vijay B
183 Posts
0
July 2nd, 2015 14:00
Hi,
Thanks for your post.
On the refresh of status after updates, OME automatically triggers the refresh inventory on the nodes where system updates are successfully after some delay of 30 minutes. If you wish to see the refreshed inventory immediately, then manual refresh of inventory is the option which you are using.
Regarding Catalog, just wanted to understand 'changed my catalog file' -which type of Catalog source you are using?
The behavior you are seeing on Catalog usually happens when OME detects the Catalog is not new/changed, then it doesn't parse the Catalog again. You may try out changing the Catalog File maintaining the same source, import it once and fall back to the original Catalog file.
Let us know if this helps.
Thanks
Vijay
cproatx
9 Posts
0
July 2nd, 2015 14:00
The network these servers are on is quarantined and off the Internet so I'm not able to set OME to connect directly to the Dell ftp site. Instead, I am creating my own custom SUU directory with Dell Repository Manager and hosting the repository on my own ftp server which also has the OME installation.
Originally, I was selecting catalog source and choosing "use file system source (SUU)" and browsing to the catalog file location of the SUU directory I created. It was working fine but when I changed the catalog and pointed to a different one it sometimes would update to reflect the new catalog and sometimes it didn't seem to. For instance, I created a new SUU with no NIC card firmware but even after setting this as the active catalog all the servers were still showing NIC firmware updates.
I did manage to figure out a workaround by changing the catalog source option from "use file system source (SUU)" to "use repository manager file" and just browsing to the same location. Not sure what the difference is but the interface did refresh and reflect the new catalog once I did that.