Valentin Aitken created BROOKLYN-512: ----------------------------------------
Summary: osVersionRegex not choosing latest version for centos on AWS-EC2, AzureARM Key: BROOKLYN-512 URL: https://issues.apache.org/jira/browse/BROOKLYN-512 Project: Brooklyn Issue Type: Improvement Reporter: Valentin Aitken Scenario 1: Deploy a sample app in Azure ARM using the following blueprint: {noformat} name: app on AzureARM osVersionRegex location: 'jclouds:azurecompute-arm': region: northeurope jclouds.azurecompute.arm.publishers: OpenLogic osVersionRegex: 7 identity: xxxxxxxxxxxidentity credential: xxxxxcreds endpoint: "https://management.azure.com/subscriptions/sub-idxxxx oauth.endpoint: "https://login.microsoftonline.com/oathxxxxxxxx" services: - type: org.apache.brooklyn.entity.software.base.EmptySoftwareProcess {noformat} This chooses {{CentOS Linux release 7.1.1503}} and I expect to choose latest available for OpenLogic which is CentOS 7.3.x as a workaround I can use {{imageId: northeurope/OpenLogic/CentOS/7.3}} ----- Scenario 2, AWS EC2: {noformat} name: aws centos 7 location: 'jclouds:aws-ec2:eu-central-1': osFamily: centos osVersionRegex: 7\..* loginUser: root services: - type: org.apache.brooklyn.entity.software.base.EmptySoftwareProcess {noformat} Chooses {{CentOS Linux release 7.0.1406}}. Again as a workaround I should specify imageId. ---- It is most likely to be a jclouds issue. Not sure whether the two have same cause though. -- This message was sent by Atlassian JIRA (v6.3.15#6346)