[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon updated JENKINS-62231 Jenkins / JENKINS-62231 ec2 downgrade from 1.50 fails removing the configured cloud Change By: Ramon Leon Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206170.158974000.24219.1589124300286%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud Daniel Beck Added the specific steps to the description. Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206170.158974000.24218.1589124300250%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon updated an issue
Jenkins / JENKINS-62231
ec2 downgrade from 1.50 fails removing the configured cloud
Change By:
Ramon Leon
If you downgrade from a recent version of ec2-plugin with the security fixes: 1.50.2 or 1.49.2 or 1.46.3 to the previous installed version after you disabled the Administrative Monitor which show the message about weak strategies used (clicking on *_Dismiss these messages_*): !Screenshot from 2020-05-10 12-45-00.png|thumbnail! the previous ec2-plugin version doesn't initialize correctly and the *_cloud configuration is lost_*. The nodes configurations are still there, but they cannot be used as the plugin didn't start. !Screenshot from 2020-05-10 13-17-57.png|thumbnail! The log printed out:{code:java}2020-05-10 11:12:03.789+ [id=33]INFOjenkins.InitReactorRunner$1#onAttained: Listed all plugins2020-05-10 11:12:04.301+ [id=30]SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Amazon EC2 plugin v1.49.1 (ec2)java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451)at hudson.diagnosis.OldDataMonitor.get(OldDataMonitor.java:91)at hudson.diagnosis.OldDataMonitor.report(OldDataMonitor.java:223)at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:368)at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:267)at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)Caused: com.thoughtworks.xstream.converters.ConversionException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 Debugging information message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0cause-exception : java.lang.IllegalStateExceptioncause-message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0class : hudson.plugins.ec2.PluginImplrequired-type : hudson.plugins.ec2.PluginImplconverter-type : hudson.util.RobustReflectionConverterpath: /hudson.plugins.ec2.PluginImplline number : 4version : not available---at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79)at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon updated an issue
Jenkins / JENKINS-62231
ec2 downgrade from 1.50 fails removing the configured cloud
Change By:
Ramon Leon
If you downgrade from a recent version of ec2-plugin with the security fixes: 1.50.2 or 1.49.2 or 1.46.3 to the previous installed version after you disabled the Administrative Monitor which show the message about weak strategies used (clicking on *_Dismiss these messages_*): !Screenshot from 2020-05-10 12-45-00.png|thumbnail! the previous ec2-plugin version doesn't initialize correctly and the *_cloud configuration is lost_*. The nodes configurations are still there, but they cannot be used as the plugin didn't start. !Screenshot from 2020-05-10 13-17-57.png|thumbnail! The log printed out:{code:java}2020-05-10 11:12:03.789+ [id=33]INFOjenkins.InitReactorRunner$1#onAttained: Listed all plugins2020-05-10 11:12:04.301+ [id=30]SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Amazon EC2 plugin v1.49.1 (ec2)java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451)at hudson.diagnosis.OldDataMonitor.get(OldDataMonitor.java:91)at hudson.diagnosis.OldDataMonitor.report(OldDataMonitor.java:223)at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:368)at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:267)at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)Caused: com.thoughtworks.xstream.converters.ConversionException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 Debugging information message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0cause-exception : java.lang.IllegalStateExceptioncause-message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0class : hudson.plugins.ec2.PluginImplrequired-type : hudson.plugins.ec2.PluginImplconverter-type : hudson.util.RobustReflectionConverterpath: /hudson.plugins.ec2.PluginImplline number : 4version : not available---at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79)at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon updated an issue
Jenkins / JENKINS-62231
ec2 downgrade from 1.50 fails removing the configured cloud
Change By:
Ramon Leon
If you downgrade from a recent version of ec2-plugin with the security fixes: 1.50.2 or 1.49.2 or 1.46.3 to the previous installed version after you disabled the Administrative Monitor which show the message about weak strategies used (clicking on *_Dismiss these messages_*): !Screenshot from 2020-05-10 12-45-00.png|thumbnail! the previous ec2-plugin version doesn't initialize correctly and the *_cloud configuration is lost_*. The nodes configurations are still there, but they cannot be used as the plugin didn't start. !Screenshot from 2020-05-10 13-17-57.png|thumbnail! The log printed out:{code:java}2020-05-10 11:12:03.789+ [id=33]INFOjenkins.InitReactorRunner$1#onAttained: Listed all plugins2020-05-10 11:12:04.301+ [id=30]SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Amazon EC2 plugin v1.49.1 (ec2)java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451)at hudson.diagnosis.OldDataMonitor.get(OldDataMonitor.java:91)at hudson.diagnosis.OldDataMonitor.report(OldDataMonitor.java:223)at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:368)at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:267)at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)Caused: com.thoughtworks.xstream.converters.ConversionException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 Debugging information message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0cause-exception : java.lang.IllegalStateExceptioncause-message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0class : hudson.plugins.ec2.PluginImplrequired-type : hudson.plugins.ec2.PluginImplconverter-type : hudson.util.RobustReflectionConverterpath: /hudson.plugins.ec2.PluginImplline number : 4version : not available---at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79)at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon updated an issue
Jenkins / JENKINS-62231
ec2 downgrade from 1.50 fails removing the configured cloud
Change By:
Ramon Leon
If you downgrade from a recent version of ec2-plugin with the security fixes: 1.50.2 or 1.49.2 or 1.46.3 to the previous installed version after you disabled the Administrative Monitor which show the message about weak strategies used (clicking on *_Dismiss these messages_*): !Screenshot from 2020-05-10 12-45-00.png|thumbnail! the previous ec2-plugin version doesn't initialize correctly and the *_cloud configuration is lost_*. The nodes configurations are still there, but they cannot be used as the plugin didn't start. !Screenshot from 2020-05-10 13-17-57.png|thumbnail! The log printed out:{code:java}2020-05-10 11:12:03.789+ [id=33]INFOjenkins.InitReactorRunner$1#onAttained: Listed all plugins2020-05-10 11:12:04.301+ [id=30]SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Amazon EC2 plugin v1.49.1 (ec2)java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451)at hudson.diagnosis.OldDataMonitor.get(OldDataMonitor.java:91)at hudson.diagnosis.OldDataMonitor.report(OldDataMonitor.java:223)at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:368)at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:267)at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)Caused: com.thoughtworks.xstream.converters.ConversionException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 Debugging information message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0cause-exception : java.lang.IllegalStateExceptioncause-message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0class : hudson.plugins.ec2.PluginImplrequired-type : hudson.plugins.ec2.PluginImplconverter-type : hudson.util.RobustReflectionConverterpath: /hudson.plugins.ec2.PluginImplline number : 4version : not available---at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79)at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud Filed a PR on Jenkins Core to avoid the OldDataMonitor triggers a plugin load failure: https://github.com/jenkinsci/jenkins/pull/4718 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206170.158974000.24208.1589123700351%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud I've filed a PR just to warn users: https://github.com/jenkinsci/ec2-plugin/pull/462 but we should avoid any critical exception because of OldDataMonitor modifying the RobustReflectionConverter IMO. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206170.158974000.24206.1589122800232%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon commented on JENKINS-62231
Re: ec2 downgrade from 1.50 fails removing the configured cloud
I may try to modify the start() method of PluginImpl on EC2 plugin to something like:
@Override
public void start() {
try {
...
load();
} catch (Throwable t) {
if (t.getCause() instanceof ConversionException && t.getCause().getMessage().contains(OldDataMonitor.class.getName())) {
logger.log(Level.INFO, "There was an error loading the plugin, most likely not critical. See https://issues.jenkins-ci.org/browse/JENKINS-62231", t);
} else {
throw t;
}
}
}
But it will help for future problems, not to the current problem.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206170.158974000.24189.1589121360175%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud Currently, the only workaround is to remove the ec2.xml file before downgrading to a previous version. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206170.158974000.24190.1589121360189%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Daniel Beck commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud How can this be reproduced? Specific, detailed and complete steps to do that please. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206170.158974000.24171.1589118420167%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon edited a comment on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud It looks like a bug on Jenkins core more likely than a bug on the EC2 plugin itself. [~danielbeck] , [~oleg_nenashev] any idea would be appreciated Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206170.158974000.24070.1589114580244%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud It looks like a bug on Jenkins core more likely than a bug on the EC2 plugin itself. Daniel Beck Oleg Nenashev any idea would be appreciated Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206170.158974000.24069.1589114580082%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon edited a comment on JENKINS-62231
Re: ec2 downgrade from 1.50 fails removing the configured cloud
The error seems to be a kind of race-condition between the initialization of the ec2-plugin and the OldDataMonitor extension point. RobustReflectionConverter has to report a non-existing field, but it fails with an exception when it tries to do:{code:java}OldDataMonitor.report((Saveable)result, (ArrayList)context.get("ReadError"));{code}This call ends up on this other one:{code:java} return ExtensionList.lookupSingleton(OldDataMonitor.class); {code}which triggers:{code:java}java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0{code} I will try to add an Adding _@Extension( ordinal =-1)_ to the @Extension of the EC2 plugin to try to load this one after the AdministrativeMonitors doesn't solve the problem .
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206170.158974000.24051.1589114340048%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud It seems to be a similar issue: https://issues.jenkins-ci.org/browse/JENKINS-59582 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206170.158974000.24050.1589114280046%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon edited a comment on JENKINS-62231
Re: ec2 downgrade from 1.50 fails removing the configured cloud
The error seems to be a kind of race-condition between the initialization of the ec2-plugin and the OldDataMonitor extension point. RobustReflectionConverter has to report a non-existing field, but it fails with an exception when it tries to do:{code:java}OldDataMonitor.report((Saveable)result, (ArrayList)context.get("ReadError"));{code}This call ends up on this other one:{code:java} return ExtensionList.lookupSingleton(OldDataMonitor.class); {code}which triggers:{code:java}java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0{code} I will try to add an ordinal to the @Extension of the EC2 plugin.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206170.158974000.24044.1589113560049%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon commented on JENKINS-62231
Re: ec2 downgrade from 1.50 fails removing the configured cloud
The error seems to be a kind of race-condition between the initialization of the ec2-plugin and the OldDataMonitor extension point. RobustReflectionConverter has to report a non-existing field, but it fails with an exception when it tries to do:
OldDataMonitor.report((Saveable)result, (ArrayList)context.get("ReadError"));
This call ends up on this other one:
return ExtensionList.lookupSingleton(OldDataMonitor.class);
which triggers:
java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You recei
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon started work on JENKINS-62231 Change By: Ramon Leon Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206170.158974000.24042.1589111220359%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-62231 ec2 downgrade from 1.50 fails removing the configured cloud Issue Type: Bug Assignee: Ramon Leon Attachments: Screenshot from 2020-05-10 12-45-00.png, Screenshot from 2020-05-10 13-17-57.png Components: ec2-plugin Created: 2020-05-10 11:46 Environment: Jenkins 2.235, EC2 1.50 > EC2 1.49 Priority: Critical Reporter: Ramon Leon If you downgrade from a recent version of ec2-plugin with the security fixes: 1.50.2 or 1.49.2 or 1.46.3 to the previous installed version after you disabled the Administrative Monitor which show the message about weak strategies used (clicking on Dismiss these messages): the previous ec2-plugin version doesn't initialize correctly and the cloud configuration is lost. The nodes configurations are still there, but they cannot be used as the plugin didn't start.The log printed out: 2020-05-10 11:12:03.789+ [id=33]INFOjenkins.InitReactorRunner$1#onAttained: Listed all plugins 2020-05-10 11:12:04.301+ [id=30]SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Amazon EC2 plugin v1.49.1 (ec2) java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451) at hudson.diagnosis.OldDataMonitor.get(OldDataMonitor.java:91) at hudson.di
