[JBoss JIRA] (JBIDE-21711) Server Adapter: Need a way to restart modules
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21711?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-21711.
-------------------------------
Resolution: Done
> Server Adapter: Need a way to restart modules
> ---------------------------------------------
>
> Key: JBIDE-21711
> URL: https://issues.jboss.org/browse/JBIDE-21711
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.3.1.CR1
>
>
> When doing hot code reload in an OpenShift deployed EAP server, changing a method signature will make the debugger complain with
> !http://content.screencast.com/users/fbricon/folders/Jing/media/623c96cc-ae62-441b-b498-a39d9cf9b563/00000322.png|width=650!
> Triggering a full publish on the module is not sufficient.
> We need to at least have a way to trigger a module restart
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22165) Check "Add Route" checkbox for exposing services of docker image by default
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22165?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22165:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> Check "Add Route" checkbox for exposing services of docker image by default
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22165
> URL: https://issues.jboss.org/browse/JBIDE-22165
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> I think usually users would like to expose their services of a docker image being deployed to OpenShift. In the Deploy Image to OpenShift wizard we have a wizard page where mapping of ports is happening and also exposing of services to routes by checking a checkbox "Add Route" is placed there. By default we have this checkbox unchecked, but maybe we should enable it by default. In my humble opinion in many use case there will be an existing docker image of some application and user would like to deploy it to OpenShift and check application whether it is working or use some features of OpenShift itself...
> At the moment we don't have enabled exposing of OpenShift resources in tooling and therefore if user by accident or intentionally click on Finish button in Deploy Image to OpenShift wizard one page earlier (the one where env. vars, scaling and data volumes are located), it produce a running pod with service, but there is no route and it force user to swich to command line to use oc to expose a service to get a route.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22171) Change to cdk launch config is not persisted
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22171?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22171:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> Change to cdk launch config is not persisted
> --------------------------------------------
>
> Key: JBIDE-22171
> URL: https://issues.jboss.org/browse/JBIDE-22171
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> I had a cdk server set up and I wanted to change it to point to another directory.
> So I opened the server editor, opened launch config, changed the Working Directory path, clicked Apply, OK, closed the server editor.
> But it turns out this changed was not persisted.
> If I open the launch config again, the old path is still there.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22163) Allow to expose OpenShift 3 resource
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22163?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22163:
--------------------------------
Fix Version/s: 4.4.x
> Allow to expose OpenShift 3 resource
> ------------------------------------
>
> Key: JBIDE-22163
> URL: https://issues.jboss.org/browse/JBIDE-22163
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.x
>
>
> It would be nice to have exposing of OpenShift resources in our tooling. E.g. having a context menu item "Expose" in context menu of a resource - exposing a pod would create a service. Exposing a service would create a routing - same as it is for OpenShift command line client.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3799) Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3799?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3799:
---------------------------------
Fix Version/s: 10.0.0.Alpha1
> Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-3799
> URL: https://issues.jboss.org/browse/JBDS-3799
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Hardy Ferentschik
> Priority: Critical
> Labels: havoc
> Fix For: 10.0.0.Alpha1
>
>
> This unresolved issue: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/272
> Is causing rsync issues such as:
> default: Rsyncing folder: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant
> There was an error when attempting to rsync a synced folder.
> Please inspect the error message below for more info.
> Host path: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/
> Guest path: /vagrant
> Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ vagrant@127.0.0.1:/vagrant
> Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts.
> dup() in/out/err failed
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3795) Cant start CDK
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-3795?page=com.atlassian.jira.plugin.... ]
Rob Stryker resolved JBDS-3795.
-------------------------------
Resolution: Done
pushed to master / maintenance
> Cant start CDK
> --------------
>
> Key: JBDS-3795
> URL: https://issues.jboss.org/browse/JBDS-3795
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: cdk, installer
> Affects Versions: 9.1.0.CR1
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: havoc, respin-c
> Fix For: 9.1.0.CR1
>
> Attachments: screenshot-1.png
>
>
> CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1.
> "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments."
> I can access the OS console: https://10.1.2.2:8443/console
> The console output looks OK too:
> {code}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'cdkv2'...
> [KProgress: 10%
> [KProgress: 20%
> [KProgress: 90%
> [K==> default: Matching MAC address for NAT networking...
> ==> default: Setting the name of the VM: rhel-ose_default_1460496916213_82608
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 => 2222 (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> default: SSH username: vagrant
> default: SSH auth method: private key
> default: Warning: Connection timeout. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> default:
> default: Vagrant insecure key detected. Vagrant will automatically replace
> default: this with a newly generated keypair for better security.
> default:
> default: Inserting generated public key within guest...
> default: Removing insecure key from the guest if it's present...
> default: Key inserted! Disconnecting and reconnecting using new SSH key...
> ==> default: Machine booted and ready!
> ==> default: Checking for guest additions in VM...
> default: No guest additions were detected on the base box for this VM! Guest
> default: additions are required for forwarded ports, shared folders, host only
> default: networking, and more. If SSH fails on this machine, please install
> default: the guest additions and repackage the box to continue.
> default:
> default: This is not an error message; everything may continue to work properly,
> default: in which case you may ignore this message.
> ==> default: Configuring and enabling network interfaces...
> ==> default: Registering box with vagrant-registration...
> ==> default: Copying TLS certificates to C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> ==> default: Rsyncing folder: /cygdrive/c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default:
> ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory.
> ==> default: To modify the number of cores and/or available memory set the environment variables
> ==> default: VM_CPU respectively VM_MEMORY.
> ==> default:
> ==> default: You can now access the OpenShift console on: https://10.1.2.2:8443/console
> ==> default:
> ==> default: To use OpenShift CLI, run:
> ==> default: $ vagrant ssh
> ==> default: $ oc login 10.1.2.2:8443
> ==> default:
> ==> default: Configured users are (<username>/<password>):
> ==> default: openshift-dev/devel
> ==> default: admin/admin
> ==> default:
> ==> default: If you have the oc client library on your host, you can also login from your host.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3795) Cant start CDK
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3795?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3795:
-----------------------------
> Cant start CDK
> --------------
>
> Key: JBDS-3795
> URL: https://issues.jboss.org/browse/JBDS-3795
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: cdk, installer
> Affects Versions: 9.1.0.CR1
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: havoc, respin-c
> Fix For: 9.1.0.CR1
>
> Attachments: screenshot-1.png
>
>
> CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1.
> "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments."
> I can access the OS console: https://10.1.2.2:8443/console
> The console output looks OK too:
> {code}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'cdkv2'...
> [KProgress: 10%
> [KProgress: 20%
> [KProgress: 90%
> [K==> default: Matching MAC address for NAT networking...
> ==> default: Setting the name of the VM: rhel-ose_default_1460496916213_82608
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 => 2222 (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> default: SSH username: vagrant
> default: SSH auth method: private key
> default: Warning: Connection timeout. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> default:
> default: Vagrant insecure key detected. Vagrant will automatically replace
> default: this with a newly generated keypair for better security.
> default:
> default: Inserting generated public key within guest...
> default: Removing insecure key from the guest if it's present...
> default: Key inserted! Disconnecting and reconnecting using new SSH key...
> ==> default: Machine booted and ready!
> ==> default: Checking for guest additions in VM...
> default: No guest additions were detected on the base box for this VM! Guest
> default: additions are required for forwarded ports, shared folders, host only
> default: networking, and more. If SSH fails on this machine, please install
> default: the guest additions and repackage the box to continue.
> default:
> default: This is not an error message; everything may continue to work properly,
> default: in which case you may ignore this message.
> ==> default: Configuring and enabling network interfaces...
> ==> default: Registering box with vagrant-registration...
> ==> default: Copying TLS certificates to C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> ==> default: Rsyncing folder: /cygdrive/c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default:
> ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory.
> ==> default: To modify the number of cores and/or available memory set the environment variables
> ==> default: VM_CPU respectively VM_MEMORY.
> ==> default:
> ==> default: You can now access the OpenShift console on: https://10.1.2.2:8443/console
> ==> default:
> ==> default: To use OpenShift CLI, run:
> ==> default: $ vagrant ssh
> ==> default: $ oc login 10.1.2.2:8443
> ==> default:
> ==> default: Configured users are (<username>/<password>):
> ==> default: openshift-dev/devel
> ==> default: admin/admin
> ==> default:
> ==> default: If you have the oc client library on your host, you can also login from your host.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3795) Cant start CDK
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3795?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3795:
--------------------------------
> Cant start CDK
> --------------
>
> Key: JBDS-3795
> URL: https://issues.jboss.org/browse/JBDS-3795
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: cdk, installer
> Affects Versions: 9.1.0.CR1
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: havoc, respin-c
> Fix For: 9.1.0.CR1
>
> Attachments: screenshot-1.png
>
>
> CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1.
> "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments."
> I can access the OS console: https://10.1.2.2:8443/console
> The console output looks OK too:
> {code}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'cdkv2'...
> [KProgress: 10%
> [KProgress: 20%
> [KProgress: 90%
> [K==> default: Matching MAC address for NAT networking...
> ==> default: Setting the name of the VM: rhel-ose_default_1460496916213_82608
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 => 2222 (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> default: SSH username: vagrant
> default: SSH auth method: private key
> default: Warning: Connection timeout. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> default:
> default: Vagrant insecure key detected. Vagrant will automatically replace
> default: this with a newly generated keypair for better security.
> default:
> default: Inserting generated public key within guest...
> default: Removing insecure key from the guest if it's present...
> default: Key inserted! Disconnecting and reconnecting using new SSH key...
> ==> default: Machine booted and ready!
> ==> default: Checking for guest additions in VM...
> default: No guest additions were detected on the base box for this VM! Guest
> default: additions are required for forwarded ports, shared folders, host only
> default: networking, and more. If SSH fails on this machine, please install
> default: the guest additions and repackage the box to continue.
> default:
> default: This is not an error message; everything may continue to work properly,
> default: in which case you may ignore this message.
> ==> default: Configuring and enabling network interfaces...
> ==> default: Registering box with vagrant-registration...
> ==> default: Copying TLS certificates to C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> ==> default: Rsyncing folder: /cygdrive/c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default:
> ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory.
> ==> default: To modify the number of cores and/or available memory set the environment variables
> ==> default: VM_CPU respectively VM_MEMORY.
> ==> default:
> ==> default: You can now access the OpenShift console on: https://10.1.2.2:8443/console
> ==> default:
> ==> default: To use OpenShift CLI, run:
> ==> default: $ vagrant ssh
> ==> default: $ oc login 10.1.2.2:8443
> ==> default:
> ==> default: Configured users are (<username>/<password>):
> ==> default: openshift-dev/devel
> ==> default: admin/admin
> ==> default:
> ==> default: If you have the oc client library on your host, you can also login from your host.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3795) Cant start CDK
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3795?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3795:
---------------------------------
Target Release: 9.1.0.GA
> Cant start CDK
> --------------
>
> Key: JBDS-3795
> URL: https://issues.jboss.org/browse/JBDS-3795
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: cdk, installer
> Affects Versions: 9.1.0.CR1
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: havoc, respin-c
> Fix For: 9.1.0.CR1
>
> Attachments: screenshot-1.png
>
>
> CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1.
> "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments."
> I can access the OS console: https://10.1.2.2:8443/console
> The console output looks OK too:
> {code}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'cdkv2'...
> [KProgress: 10%
> [KProgress: 20%
> [KProgress: 90%
> [K==> default: Matching MAC address for NAT networking...
> ==> default: Setting the name of the VM: rhel-ose_default_1460496916213_82608
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 => 2222 (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> default: SSH username: vagrant
> default: SSH auth method: private key
> default: Warning: Connection timeout. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> default:
> default: Vagrant insecure key detected. Vagrant will automatically replace
> default: this with a newly generated keypair for better security.
> default:
> default: Inserting generated public key within guest...
> default: Removing insecure key from the guest if it's present...
> default: Key inserted! Disconnecting and reconnecting using new SSH key...
> ==> default: Machine booted and ready!
> ==> default: Checking for guest additions in VM...
> default: No guest additions were detected on the base box for this VM! Guest
> default: additions are required for forwarded ports, shared folders, host only
> default: networking, and more. If SSH fails on this machine, please install
> default: the guest additions and repackage the box to continue.
> default:
> default: This is not an error message; everything may continue to work properly,
> default: in which case you may ignore this message.
> ==> default: Configuring and enabling network interfaces...
> ==> default: Registering box with vagrant-registration...
> ==> default: Copying TLS certificates to C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> ==> default: Rsyncing folder: /cygdrive/c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default:
> ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory.
> ==> default: To modify the number of cores and/or available memory set the environment variables
> ==> default: VM_CPU respectively VM_MEMORY.
> ==> default:
> ==> default: You can now access the OpenShift console on: https://10.1.2.2:8443/console
> ==> default:
> ==> default: To use OpenShift CLI, run:
> ==> default: $ vagrant ssh
> ==> default: $ oc login 10.1.2.2:8443
> ==> default:
> ==> default: Configured users are (<username>/<password>):
> ==> default: openshift-dev/devel
> ==> default: admin/admin
> ==> default:
> ==> default: If you have the oc client library on your host, you can also login from your host.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years