[
https://issues.apache.org/jira/browse/BROOKLYN-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750232#comment-16750232
]
Aled Sage commented on BROOKLYN-607:
------------------------------------
Looking at the images from OpenLogic (using {{az vm image list --output table
--all --publisher OpenLogic}}), they include:
{noformat}
CentOS-SRIOV OpenLogic 7.3-SRIOV
OpenLogic:CentOS-SRIOV:7.3-SRIOV:7.3.20171005 7.3.20171005
CentOS OpenLogic 7.6 OpenLogic:CentOS:7.6:7.6.20181219
7.6.20181219{noformat}
The image chooser gives each of these the same score (3.5). Then it sorts by
various fields, starting with name (alphabetically). The result is it puts the
name "OpenLogic:CentOS-SRIOV..." above "OpenLogic:CentOS:7.6...".
Not sure what the best way to fix this is. Changing the image chooser is
fiddly: it risks breaking the behaviour of defaults on other clouds.
> azure-arm failure on `yum update` (due to image choice)
> -------------------------------------------------------
>
> Key: BROOKLYN-607
> URL: https://issues.apache.org/jira/browse/BROOKLYN-607
> Project: Brooklyn
> Issue Type: Bug
> Reporter: Aled Sage
> Priority: Major
>
> With brooklyn 1.0.0-SNAPSHOT, I'm hitting problems provisioning a simple
> software process entity on Azure - the VM fails when doing `yum update`.
> Digging into this...
> The imageId being used is:
> {noformat}
> northeurope/OpenLogic/CentOS-SRIOV/7.3-SRIOV, os={family=centos,
> version=7.3-SRIOV, description=7.3-SRIOV, is64Bit=true}
> {noformat}
> With hardwareId {{Standard_B1ms}}.
> The location.bom file contains:
> {noformat}
> item:
> type: jclouds:azurecompute-arm
> brooklyn.config:
> region: northeurope
> identity: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
> credential: xxxxxxxxxxxxxxxxxxxxxxxxx
> endpoint:
> https://management.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
> oauth.endpoint:
> https://login.microsoftonline.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/oauth2/token
> jclouds.azurecompute.arm.publishers: OpenLogic
> jclouds.azurecompute.arm.operation.timeout: 120000
> osVersionRegex: 7
> minRam: 2000
> {noformat}
> On executing {{yum update}}, it gives the stderr:
> {noformat}
> Error: Package: kmod-microsoft-hyper-v-4.2.6.1-20181010.x86_64 (openlogic)
> Requires: kernel(hid_input_report) = 0x4e8c53f3
> Installed: kernel-3.10.0-514.26.2.el7.x86_64 (@CentOS-Updates)
> kernel(hid_input_report) = 0x084ce8c6
> Available: kernel-3.10.0-957.el7.x86_64 (base)
> kernel(hid_input_report) = 0x6710144a
> Installing: kernel-3.10.0-957.1.3.el7.x86_64 (updates)
> kernel(hid_input_report) = 0x6710144a
> Available: kernel-debug-3.10.0-957.el7.x86_64 (base)
> kernel(hid_input_report) = 0x2003d78d
> Available: kernel-debug-3.10.0-957.1.3.el7.x86_64 (updates)
> kernel(hid_input_report) = 0x2003d78d
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
