Skip to content
Snippets Groups Projects

FS#2403 - Disable apps vhost in server config

Merged Florian Schaal requested to merge (removed):master into master

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Florian Schaal Added 2 commits:

    Added 2 commits:

    • 61e08e76 - openvz: free all ip-addresses if the vm was deleted
    • ca069831 - FS#1990 - Additional V-Server Field - this commits add a custom-field for openvz-configs
  • Florian Schaal Added 1 commit:

    Added 1 commit:

  • Florian Schaal Added 1 commit:

    Added 1 commit:

  • Florian Schaal Added 1 commit:

    Added 1 commit:

    • 782f4abd - fixed ip-handling for vserver
  • Florian Schaal Added 1 commit:

    Added 1 commit:

  • Marius Burkard Status changed to merged

    Status changed to merged

  • Marius Burkard mentioned in commit 796661c5

    mentioned in commit 796661c5

    • Developer

      This change breaks the IP address display when editing a vserver, so instead of showing the veserver's ip address, is shows nothing. If I revert this change, the vserver's IP address shows up correctly again. Additional IP's seem to work, too.

      I'm trying to determine if my database needs updated or if there's a bug here. My 'server' table has a single entry, with server_id=1. My openvz_ip table has all entries with server_id=1, even a new IP address I just entered. According to the change in this commit, it looks like openvz_ip.server_id would have to be set the same as vm_id, which is .. broken? (I very well may not understand exactly what all the fields do.)

      Edited by Jesse Norell
    • Author Contributor

      I can not reproduce your problem.

    • Jesse is right, at least when I am looking at the code. Why do you set the "vm_server_id" with "vm_id" instead of "server_id" ?

    • Author Contributor

      I´ll have at the code after christmas. I just checked this this morning with a clean 3.1 and a new created vm and i had no problems with the IP. But there could be a bug if you upgrade to 3.1

    • Please register or sign in to reply
Please register or sign in to reply
Loading