Ask Your Question
0

"Something went wrong" - Access and Security Step 2: Enable SSH

asked 2014-11-29 10:49:14 -0500

Stuart gravatar image

updated 2014-11-30 14:18:12 -0500

dbaxps gravatar image

Hello

I am a new to all of this magic and am following these quickstart notes to install on a single server: https: // openstack . redhat . com / Quickstart

There has been a few bumps along the way but now I am stuck:

I have logged into the OpenStack dashboard for the first time using this: http: // 192.168.1.55 / dashboard

The Quickstart notes say to:

"Step 2: Enable SSH on your default security group Once logged in to the OpenStack dashboard, click the Project tab in the left-side navigation menu, and then click Access & Security under the heading Compute. "

However I receive this error on the web browser:

" Something went wrong! An unexpected error has occurred. Try refreshing the page. If that doesn't help, contact your local administrator."

The file /var/log/messages contains these entries below which are looping. They do not look like errors though.

.

Nov 29 16:18:50 OpStck-1 container-replicator: Beginning replication run
Nov 29 16:18:50 OpStck-1 container-replicator: Replication run OVER
Nov 29 16:18:50 OpStck-1 container-replicator: Attempted to replicate 0 dbs in 0.00087 seconds (0.00000/s)
Nov 29 16:18:50 OpStck-1 container-replicator: Removed 0 dbs Nov 29 16:18:50 OpStck-1 container-replicator: 0 successes, 0 failures
Nov 29 16:18:50 OpStck-1 container-replicator: no_change:0 ts_repl:0 diff:0 rsync:0 diff_capped:0 hashmatch:0 empty:0
Nov 29 16:18:53 OpStck-1 cinder-volume: 2014-11-29 16:18:53.721 4953 INFO cinder.volume.manager [-] Updating volume status
Nov 29 16:18:53 OpStck-1 cinder-volume: 2014-11-29 16:18:53.813 4953 INFO cinder.volume.manager [-] Updating volume replication status.
Nov 29 16:19:01 OpStck-1 systemd: Created slice user-163.slice.
-------------------------------------------------------------------------

Any ideas in how to proceed with the demo?

Thank you for your time. Stuart

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2014-11-30 12:17:42 -0500

Stuart gravatar image

updated 2014-11-30 12:18:09 -0500

Re-running through the installation seemed to fix this bug.

  1. Create an answer file: packstack --gen-answer-file=/root/packstack-AnswerFile.cfg
  2. Re-install, using the answer file: ./packstack --answer-file=/root/packstack-AnswerFile.cfg
edit flag offensive delete link more
0

answered 2014-11-30 13:53:06 -0500

dbaxps gravatar image

Same steps may be done via CLI. For instance for demo tenant

# source keystonerc_demo
[root@juno1 ~(keystone_demo)]#  neutron security-group-rule-create --protocol icmp \
  --direction ingress --remote-ip-prefix 0.0.0.0/0 default

[root@juno1 ~(keystone_demo)]#  neutron security-group-rule-create --protocol tcp \
  --port-range-min 22 --port-range-max 22 \
  --direction ingress --remote-ip-prefix 0.0.0.0/0 default

Login as demo into dashboard :-

Access & Security => Security Groups => Manage rules

Make sure changes been done

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-11-29 10:39:09 -0500

Seen: 656 times

Last updated: Nov 30 '14