Skip to end of metadata
Go to start of metadata

IssueDate ReportedDate ResolvedMitigation

Active Issues

3Some Jetstream virtual machines remain stuck in the Networking stage when they launch. This prevents users from logging into or using the virtual machine.8/30/2016
Try redeploying the virtual machine as described here, Instance management actions.
4X2GO on the Biolinux8 image is currently experiencing keyboard mapping issues on first login.9/28/2016

Using the x2goclient software on your remote machine

  • suspend the x2go session
  • restore the x2go session by re-authenticating

This restored session will have the correct keyboard map.


Laptops with touchscreens are unable to use the mouse in the web desktop.

There is a bug in the web browser code in both Chrome and Firefox for using a touchscreen PC with the web desktop of Jetstream. This is not a bug we can easily work around since it's in the browser code itself.


While we generally don't recommend using Internet Explorer, we've found it does not have the same issue.

Using a VNC viewer also is a workaround.

8Cannot login with external ssh-client using DSA ssh-keys in my settings.5/12/2017neverDSA keys should not be used with Jetstream. Please use another protocol like RSA
9Users with a brace " { " in their passwords may experience errors with openstack command line commands.5/23/2017

Use a password that does not contain a brace.

Also may try enclosing passwords in single quote mark (e.g.

export OS_PASSWORD='password{with-brace}'

in your openrc file

Resolved Issues


Jetstream is not currently recognizing all XSEDE staff allocations, such as TG-STA060015, as being valid for some users. This is in part because these allocations are roaming allocations.

XSEDE users whose only Jetstream allocation is one of these staff allocations may not be able to log into the system or manage VMs.

8/30/20169/12/2016XSEDE users can resolve this by requesting a non-roaming or startup allocation on Jetstream. See Jetstream Allocations for details or email
2Jetstream may not recognize XSEDE-associated usernames that differ from TACC usernames due to unresolved issues with identity mapping. This primarily affects long-time users of XSEDE or Teragrid.8/30/20163/1/2017This can be mitigated by filing a ticket at requesting that your TACC and XSEDE usernames be brought into alignment. 
5If there is a dot/period within the last three characters of the instance name, that instance will fail to launch. This is not considered a bug by the OpenStack community but rather a feature that ties into a dynamic DNS feature.9/30/20167/11/2016Code now changes all dots to underscores to prevent this
6A power issue resulted in some issue being inaccessible. Staff are restoring these instances.4/12/20174/17/2017Retry your instance. Contact if it continues to not respond.

  • No labels