Skip to content

Commit All Changes button is missing via Netopeer-GUI when connected to a device #87

Open

Description

@tbrito01

Hello,

Followed David's instructions below with his fix to this on how update the Netopeer GUI and retest it.

  1. cd /var/www/netopeer-gui/
  2. git remote set-url origin https://github.com/CESNET/Netopeer-GUI.git
  3. rm /var/www/netopeer-gui/app/netopeerWebGui.db
  4. composer install

Commit All Changes button still does not appear in the GUI

Activity

  1. alexadavid commented on Nov 23, 2015

    @alexadavid
    Contributor

    Hello,
    sorry for late answer. After my fix commit all button should be visible everytime (just disabled when you are not allowed to apply changes). The button was renamed into Apply changes.

    We could try a few commands to be sure your installation was successful:

    1. cd /var/www/netopeer-gui
    2. git remote set-url origin https://github.com/CESNET/Netopeer-GUI.git
    3. git pull origin master (if you run git log after that, you should see commit cb14709)
    4. php app/console cache:clear --env=prod
    5. php app/console assetic:dump --env=prod --no-debug
    6. php app/console app:install --post=install

    Now, you should see Apply changes button

    Note: I'll just mention @cejkato2 to get notification

  2. tbrito01 commented on Nov 24, 2015

    @tbrito01
    Author

    Hi David,

    Thank you for the steps, but still no button appear in the GUI. :( I am not
    sure if it is because of step 3. I am following your steps to the "T"s and
    still no button. Could it possibly be something else missing? Logs below:

    1. git pull origin master
      error: Couldn't resolve host 'github.com' while accessing
      https://github.com/CESNET/Netopeer-GUI.git/info/refs
      fatal: HTTP request failed

    On Mon, Nov 23, 2015 at 1:11 AM, David Alexa notifications@github.com
    wrote:

    Hello,
    sorry for late answer. After my fix commit all button should be visible
    everytime (just disabled when you are not allowed to apply changes). The
    button was renamed into Apply changes.

    We could try a few commands to be sure your installation was successful:

    1. cd /var/www/netopeer-gui
    2. git remote set-url origin https://github.com/CESNET/Netopeer-GUI.git
    3. git pull origin master (if you run git log after that, you should see
      commit cb14709
      cb14709
      )
    4. php app/console cache:clear --env=prod
    5. php app/console assetic:dump --env=prod --no-debug
    6. php app/console app:install --post=install

    Now, you should see Apply changes button

    Note: I'll just mention @cejkato2 https://github.com/cejkato2 to get
    notification

    —
    Reply to this email directly or view it on GitHub
    #87 (comment).

  3. alexadavid commented on Nov 24, 2015

    @alexadavid
    Contributor

    You can not connect to github server. It is possible, that you have no access to internet from virtualbox?

    Make sure you have set network to NAT in virtualbox settings.

    screen shot 2015-11-24 at 17 52 38

    After that, you should be able to ping to github from terminal - running ping github.com. You should get some response as following.

    screen shot 2015-11-24 at 17 54 26

    The fact, you could not connect to remote github server, is the reason, you could not download fix from github repository.

  4. tbrito01 commented on Nov 24, 2015

    @tbrito01
    Author

    Good point!! I will check on this and let you know soon.

    Thanks,

    Tatiana

    On Tue, Nov 24, 2015 at 11:56 AM, David Alexa notifications@github.com
    wrote:

    You can not connect to github server. It is possible, that you have no
    access to internet from virtualbox?

    Make sure you have set network to NAT in virtualbox settings.

    [image: screen shot 2015-11-24 at 17 52 38]
    https://cloud.githubusercontent.com/assets/984450/11374064/82ace768-92d4-11e5-9eb6-e315aa91313e.png

    After that, you should be able to ping to github from terminal - running ping
    github.com. You should get some response as following.

    [image: screen shot 2015-11-24 at 17 54 26]
    https://cloud.githubusercontent.com/assets/984450/11374092/9fbc7fc6-92d4-11e5-8c73-b528a7c8c7ff.png

    The fact, you could not connect to remote github server, is the reason,
    you could not download fix from github repository.

    —
    Reply to this email directly or view it on GitHub
    #87 (comment).

  5. tbrito01 commented on Nov 24, 2015

    @tbrito01
    Author

    Great news I see the button now!!! The git needed to be updated and so it was failing after I also enabled the eth0 on virtual.

    However, the commit is failing due to reached timeout for reading response. I pinged our device via the virtual box and it is ping able so I am not sure what could be the problem now. Any ideas?
    capture

    Thank you for working with us on this issue!

  6. tbrito01 commented on Jan 18, 2016

    @tbrito01
    Author

    Hi David,

    We resumed testing on Netopeer-GUI and we are able to apply changes, the
    request is edited, but the commit button is no where to be found. Can you
    please indicate where the Commit button should be?

    Thanks!

    Tatiana

    On Tue, Nov 24, 2015 at 11:56 AM, David Alexa notifications@github.com
    wrote:

    You can not connect to github server. It is possible, that you have no
    access to internet from virtualbox?

    Make sure you have set network to NAT in virtualbox settings.

    [image: screen shot 2015-11-24 at 17 52 38]
    https://cloud.githubusercontent.com/assets/984450/11374064/82ace768-92d4-11e5-9eb6-e315aa91313e.png

    After that, you should be able to ping to github from terminal - running ping
    github.com. You should get some response as following.

    [image: screen shot 2015-11-24 at 17 54 26]
    https://cloud.githubusercontent.com/assets/984450/11374092/9fbc7fc6-92d4-11e5-8c73-b528a7c8c7ff.png

    The fact, you could not connect to remote github server, is the reason,
    you could not download fix from github repository.

    —
    Reply to this email directly or view it on GitHub
    #87 (comment).

  7. alexadavid commented on Feb 1, 2016

    @alexadavid
    Contributor

    I've answered this question in #89

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions