Hide Forgot
Description of problem: The current data image includes v7-1.2 and needs to be updated to 1.3. Additional info: The data image needs the beta provided in the test package for more complete partner testing, but it should not be symlinked until the official package is readied and updated in the data image.
v7 1.3 adds required rpms for XSLT needed in the server's web interface. However, the guest runs don't use these server-specific features, so I'd recommend we change the rpm commands that install the v7 rpm in the guest be changed to use --nodeps. That way, we can use existing guest images (which don't have python-lxml and dependant packages). Also, v7 certify should be invoked with --mode auto. Both of these changes need to happen on the host instance of v7, as it configures the guest script run at startup.
--nodeps seems like an error, if the rpm is not normally required perhaps it should be moved to something similar to the plan requires for --server? or perhaps a new v7-server would make more sense?
The best solution is probably a separate v7-server/daemon rpm. Should we consider doing that for 1.3?
Hrm... we didn't announce that for the beta so it's probably best to move it out to 1.4. Could we move the requires for now and then separate out the packages in 1.4. The basic code of v7 server verifying rpms might make sense in context of not all servers need all packages (fencing agents come to mind) so there's probably some use case there for the code not to be wasted?
Created attachment 488239 [details] hardwaretest.py patch to move python-lxml check to "v7 server start"
Yes, I think we should move the python-lxml out of v7 rpm's required rpms, and have "v7 server start" check it and offer option to install it via yum if it's missing.
This should be resolved with the 1.4 push if not before.